Talk:Protocol FAQ - Revision history

imported>Barneygale at 15:07, 13 December 2011

2011-12-13T15:07:33Z

← Older revision		Revision as of 15:07, 13 December 2011
Line 27:		Line 27:
	:::::::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)		:::::::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)
	:::::::::::(and you need to send 0x01 Login) [[User:Barneygale\|Barneygale]] 10:03, 12 December 2011 (MST)		:::::::::::(and you need to send 0x01 Login) [[User:Barneygale\|Barneygale]] 10:03, 12 December 2011 (MST)
			::::::::::::I completely forgot about the fact that they were hexadecimal rather than just normal bytes. Also, I removed everything after the byte that was causing errors because I was messing around with the packet to see if it was inside the packet. It all makes sense now. I'll try converting my packet headers to hexadecimal and see if that clears things up. (it would make sense)
			::::::::::::Well, I'm still getting the error. Do I have to change anything in my encoder? My process for packets is one where the packet header is saved as an int, and then when packets are queued to be sent to the client, the header is written (one byte, the int that was saved) and the payload follows. Same error. I changed all my packets to add the 0x prefix, and if it was a single digit it was prefixed with 0x0. Is there something I'm missing here? :/ Tonight I can't look further into it because I'm extremely busy, but I will check back tomorrow. Thank you for your time, I'm sorry I'm being such a pain >.< I'll ask a friend to try and login tomorrow so I can give you another result to examine.
			:::::::::::::I'm totally lost as to what your problem is. Store your packet types as bytes. Specify them in hex, i.e. when writing a packet, do buf.writeByte(0x32) rather than buf.writeByte(32). Wireshark should be your go-to tool for debugging - filter by tcp.port==25565, find a packet, right click > follow TCP stream [[User:Barneygale\|Barneygale]] 08:07, 13 December 2011 (MST)

imported>Barneygale: Indentation fix

2011-12-12T17:05:08Z

Indentation fix

imported>Barneygale at 17:03, 12 December 2011

2011-12-12T17:03:09Z

← Older revision		Revision as of 17:03, 12 December 2011
Line 26:		Line 26:
	:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)		:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)
	:::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)		:::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)
			:::::::(and you need to send 0x01 Login) [[User:Barneygale\|Barneygale]] 10:03, 12 December 2011 (MST)

imported>Barneygale at 16:55, 12 December 2011

2011-12-12T16:55:22Z

← Older revision		Revision as of 16:55, 12 December 2011
Line 25:		Line 25:
	:::::::Note, <code>7f 0f</code> remains on the server->client buffer		:::::::Note, <code>7f 0f</code> remains on the server->client buffer
	:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)		:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)
			:::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)

imported>Barneygale at 16:49, 12 December 2011

2011-12-12T16:49:32Z

← Older revision		Revision as of 16:49, 12 December 2011
Line 19:		Line 19:
	::::I already mentioned that your issue is likely with a previous packet. If possible, just dump everything your server is sending to your client. Use wireshark if you can't do it from the program itself. [[User:Barneygale\|Barneygale]] 17:16, 10 December 2011 (MST)		::::I already mentioned that your issue is likely with a previous packet. If possible, just dump everything your server is sending to your client. Use wireshark if you can't do it from the program itself. [[User:Barneygale\|Barneygale]] 17:16, 10 December 2011 (MST)
	:::::Additionally this will be much easier to solve if you come on IRC - irc.freenode.net #mcdevs [[User:Barneygale\|Barneygale]] 20:47, 10 December 2011 (MST)		:::::Additionally this will be much easier to solve if you come on IRC - irc.freenode.net #mcdevs [[User:Barneygale\|Barneygale]] 20:47, 10 December 2011 (MST)
			::::::You're not on the IRC at the moment, but I'll try to use wireshark to dump it all. Thanks for your time!
			::::::Here's the Wireshark dump: http://www.mediafire.com/?hyy89jbrimxywq2
			:::::::Cleaned up hex dump: https://gist.github.com/1468145
			:::::::Parsed data: https://gist.github.com/1468147
			:::::::Note, <code>7f 0f</code> remains on the server->client buffer
			:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)

imported>Barneygale at 03:47, 11 December 2011

2011-12-11T03:47:26Z

← Older revision		Revision as of 03:47, 11 December 2011
Line 18:		Line 18:
	:::Don't really understand how to dump this with the api I'm using. I'm sending handshake->login request->pre-chunk->chunk data at the moment, and I showed you what it's writing in the chunk data packet. What else do you need exactly? :o		:::Don't really understand how to dump this with the api I'm using. I'm sending handshake->login request->pre-chunk->chunk data at the moment, and I showed you what it's writing in the chunk data packet. What else do you need exactly? :o
	::::I already mentioned that your issue is likely with a previous packet. If possible, just dump everything your server is sending to your client. Use wireshark if you can't do it from the program itself. [[User:Barneygale\|Barneygale]] 17:16, 10 December 2011 (MST)		::::I already mentioned that your issue is likely with a previous packet. If possible, just dump everything your server is sending to your client. Use wireshark if you can't do it from the program itself. [[User:Barneygale\|Barneygale]] 17:16, 10 December 2011 (MST)
			:::::Additionally this will be much easier to solve if you come on IRC - irc.freenode.net #mcdevs [[User:Barneygale\|Barneygale]] 20:47, 10 December 2011 (MST)

imported>Barneygale at 00:16, 11 December 2011

2011-12-11T00:16:12Z

← Older revision		Revision as of 00:16, 11 December 2011
Line 16:		Line 16:
	::Ah, I see. Sorry, misunderstood your question. I wrote the bytes from my ChannelBuffer (see the Netty networking library's API, it's in the org.jboss.netty.buffer package) using the ChannelBuffer#array() method to a text file. Here you go: http://www.mediafire.com/?bb665aj7i4uhjt5		::Ah, I see. Sorry, misunderstood your question. I wrote the bytes from my ChannelBuffer (see the Netty networking library's API, it's in the org.jboss.netty.buffer package) using the ChannelBuffer#array() method to a text file. Here you go: http://www.mediafire.com/?bb665aj7i4uhjt5
	:::Er, what's this data? I don't see any 0x33, 0x32. Server data should start with a 0x02 for the handshake, yours starts with two keep-alives, then a 0x0F player block placement with an invalid direction. What exactly am I looking at? [[User:Barneygale\|Barneygale]] 21:44, 7 December 2011 (MST)		:::Er, what's this data? I don't see any 0x33, 0x32. Server data should start with a 0x02 for the handshake, yours starts with two keep-alives, then a 0x0F player block placement with an invalid direction. What exactly am I looking at? [[User:Barneygale\|Barneygale]] 21:44, 7 December 2011 (MST)
			:::Don't really understand how to dump this with the api I'm using. I'm sending handshake->login request->pre-chunk->chunk data at the moment, and I showed you what it's writing in the chunk data packet. What else do you need exactly? :o
			::::I already mentioned that your issue is likely with a previous packet. If possible, just dump everything your server is sending to your client. Use wireshark if you can't do it from the program itself. [[User:Barneygale\|Barneygale]] 17:16, 10 December 2011 (MST)

imported>Barneygale at 04:44, 8 December 2011

2011-12-08T04:44:38Z

← Older revision		Revision as of 04:44, 8 December 2011
Line 14:		Line 14:
	:Hey, please help me out with this (lol) if you can you. It kinda makes me have to stop my project entirely, as I can't continue with chunk distribution, and that is my primary focus right now. Thanks :p haha		:Hey, please help me out with this (lol) if you can you. It kinda makes me have to stop my project entirely, as I can't continue with chunk distribution, and that is my primary focus right now. Thanks :p haha
	::Again, you'll need to dump what your server is sending so we can analyse it. Just write your raw bytes to a file. Use wireshark if you have to [[User:Barneygale\|Barneygale]] 21:54, 5 December 2011 (MST)		::Again, you'll need to dump what your server is sending so we can analyse it. Just write your raw bytes to a file. Use wireshark if you have to [[User:Barneygale\|Barneygale]] 21:54, 5 December 2011 (MST)
			::Ah, I see. Sorry, misunderstood your question. I wrote the bytes from my ChannelBuffer (see the Netty networking library's API, it's in the org.jboss.netty.buffer package) using the ChannelBuffer#array() method to a text file. Here you go: http://www.mediafire.com/?bb665aj7i4uhjt5
			:::Er, what's this data? I don't see any 0x33, 0x32. Server data should start with a 0x02 for the handshake, yours starts with two keep-alives, then a 0x0F player block placement with an invalid direction. What exactly am I looking at? [[User:Barneygale\|Barneygale]] 21:44, 7 December 2011 (MST)

imported>Barneygale: typo

2011-12-06T17:24:06Z

typo

← Older revision		Revision as of 17:24, 6 December 2011
Line 13:		Line 13:
	:This is the downstream packet I'm sending (header 33, which is identified in the documentation as the packet to send detailing a chunk.: http://pastebin.com/A25u25eD		:This is the downstream packet I'm sending (header 33, which is identified in the documentation as the packet to send detailing a chunk.: http://pastebin.com/A25u25eD
	:Hey, please help me out with this (lol) if you can you. It kinda makes me have to stop my project entirely, as I can't continue with chunk distribution, and that is my primary focus right now. Thanks :p haha		:Hey, please help me out with this (lol) if you can you. It kinda makes me have to stop my project entirely, as I can't continue with chunk distribution, and that is my primary focus right now. Thanks :p haha
	::Again, you'll need to dump what your server is sending so we can analyse it. Just write your raw bytes to a ~~fine~~. Use wireshark if you have to [[User:Barneygale\|Barneygale]] 21:54, 5 December 2011 (MST)		::Again, you'll need to dump what your server is sending so we can analyse it. Just write your raw bytes to a file. Use wireshark if you have to [[User:Barneygale\|Barneygale]] 21:54, 5 December 2011 (MST)

imported>Barneygale at 04:54, 6 December 2011

2011-12-06T04:54:15Z

← Older revision		Revision as of 04:54, 6 December 2011
Line 11:		Line 11:
	UPDATE: I've fixed this, but now, it gets stuck on the byte which sends 16 - 1 (15) and it's telling me Bad packet id 15, as if it is trying to make that byte a packet itself, rather than part of the chunk packet. Removing this causes another error, telling me that the string is over the max limit (this is part of the compressed data being sent to the client.) I don't really know what is wrong. Here's my code for writing the 0x33 packet message from S->C http://pastebin.com/A25u25eD		UPDATE: I've fixed this, but now, it gets stuck on the byte which sends 16 - 1 (15) and it's telling me Bad packet id 15, as if it is trying to make that byte a packet itself, rather than part of the chunk packet. Removing this causes another error, telling me that the string is over the max limit (this is part of the compressed data being sent to the client.) I don't really know what is wrong. Here's my code for writing the 0x33 packet message from S->C http://pastebin.com/A25u25eD
	:Probably a problem with a previous packet you've sent, then. Dump what your server is sending and upload somewhere. [[User:Barneygale\|Barneygale]] 09:00, 28 November 2011 (MST)		:Probably a problem with a previous packet you've sent, then. Dump what your server is sending and upload somewhere. [[User:Barneygale\|Barneygale]] 09:00, 28 November 2011 (MST)
			:This is the downstream packet I'm sending (header 33, which is identified in the documentation as the packet to send detailing a chunk.: http://pastebin.com/A25u25eD
			:Hey, please help me out with this (lol) if you can you. It kinda makes me have to stop my project entirely, as I can't continue with chunk distribution, and that is my primary focus right now. Thanks :p haha
			::Again, you'll need to dump what your server is sending so we can analyse it. Just write your raw bytes to a fine. Use wireshark if you have to [[User:Barneygale\|Barneygale]] 21:54, 5 December 2011 (MST)

← Older revision		Revision as of 17:03, 12 December 2011
Line 26:		Line 26:
	:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)		:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)
	:::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)		:::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)
			:::::::(and you need to send 0x01 Login) [[User:Barneygale\|Barneygale]] 10:03, 12 December 2011 (MST)

← Older revision		Revision as of 17:05, 12 December 2011
Line 11:		Line 11:
	UPDATE: I've fixed this, but now, it gets stuck on the byte which sends 16 - 1 (15) and it's telling me Bad packet id 15, as if it is trying to make that byte a packet itself, rather than part of the chunk packet. Removing this causes another error, telling me that the string is over the max limit (this is part of the compressed data being sent to the client.) I don't really know what is wrong. Here's my code for writing the 0x33 packet message from S->C http://pastebin.com/A25u25eD		UPDATE: I've fixed this, but now, it gets stuck on the byte which sends 16 - 1 (15) and it's telling me Bad packet id 15, as if it is trying to make that byte a packet itself, rather than part of the chunk packet. Removing this causes another error, telling me that the string is over the max limit (this is part of the compressed data being sent to the client.) I don't really know what is wrong. Here's my code for writing the 0x33 packet message from S->C http://pastebin.com/A25u25eD
	:Probably a problem with a previous packet you've sent, then. Dump what your server is sending and upload somewhere. [[User:Barneygale\|Barneygale]] 09:00, 28 November 2011 (MST)		:Probably a problem with a previous packet you've sent, then. Dump what your server is sending and upload somewhere. [[User:Barneygale\|Barneygale]] 09:00, 28 November 2011 (MST)
	:This is the downstream packet I'm sending (header 33, which is identified in the documentation as the packet to send detailing a chunk.: http://pastebin.com/A25u25eD		::This is the downstream packet I'm sending (header 33, which is identified in the documentation as the packet to send detailing a chunk.: http://pastebin.com/A25u25eD
	:Hey, please help me out with this (lol) if you can you. It kinda makes me have to stop my project entirely, as I can't continue with chunk distribution, and that is my primary focus right now. Thanks :p haha		::Hey, please help me out with this (lol) if you can you. It kinda makes me have to stop my project entirely, as I can't continue with chunk distribution, and that is my primary focus right now. Thanks :p haha
	::Again, you'll need to dump what your server is sending so we can analyse it. Just write your raw bytes to a file. Use wireshark if you have to [[User:Barneygale\|Barneygale]] 21:54, 5 December 2011 (MST)		:::Again, you'll need to dump what your server is sending so we can analyse it. Just write your raw bytes to a file. Use wireshark if you have to [[User:Barneygale\|Barneygale]] 21:54, 5 December 2011 (MST)
	::Ah, I see. Sorry, misunderstood your question. I wrote the bytes from my ChannelBuffer (see the Netty networking library's API, it's in the org.jboss.netty.buffer package) using the ChannelBuffer#array() method to a text file. Here you go: http://www.mediafire.com/?bb665aj7i4uhjt5		::::Ah, I see. Sorry, misunderstood your question. I wrote the bytes from my ChannelBuffer (see the Netty networking library's API, it's in the org.jboss.netty.buffer package) using the ChannelBuffer#array() method to a text file. Here you go: http://www.mediafire.com/?bb665aj7i4uhjt5
	:::Er, what's this data? I don't see any 0x33, 0x32. Server data should start with a 0x02 for the handshake, yours starts with two keep-alives, then a 0x0F player block placement with an invalid direction. What exactly am I looking at? [[User:Barneygale\|Barneygale]] 21:44, 7 December 2011 (MST)		::::::Er, what's this data? I don't see any 0x33, 0x32. Server data should start with a 0x02 for the handshake, yours starts with two keep-alives, then a 0x0F player block placement with an invalid direction. What exactly am I looking at? [[User:Barneygale\|Barneygale]] 21:44, 7 December 2011 (MST)
	:::Don't really understand how to dump this with the api I'm using. I'm sending handshake->login request->pre-chunk->chunk data at the moment, and I showed you what it's writing in the chunk data packet. What else do you need exactly? :o		::::::::Don't really understand how to dump this with the api I'm using. I'm sending handshake->login request->pre-chunk->chunk data at the moment, and I showed you what it's writing in the chunk data packet. What else do you need exactly? :o
	::::I already mentioned that your issue is likely with a previous packet. If possible, just dump everything your server is sending to your client. Use wireshark if you can't do it from the program itself. [[User:Barneygale\|Barneygale]] 17:16, 10 December 2011 (MST)		:::::::::I already mentioned that your issue is likely with a previous packet. If possible, just dump everything your server is sending to your client. Use wireshark if you can't do it from the program itself. [[User:Barneygale\|Barneygale]] 17:16, 10 December 2011 (MST)
	:::::Additionally this will be much easier to solve if you come on IRC - irc.freenode.net #mcdevs [[User:Barneygale\|Barneygale]] 20:47, 10 December 2011 (MST)		:::::::::Additionally this will be much easier to solve if you come on IRC - irc.freenode.net #mcdevs [[User:Barneygale\|Barneygale]] 20:47, 10 December 2011 (MST)
	::::::You're not on the IRC at the moment, but I'll try to use wireshark to dump it all. Thanks for your time!		::::::::::You're not on the IRC at the moment, but I'll try to use wireshark to dump it all. Thanks for your time!
	::::::Here's the Wireshark dump: http://www.mediafire.com/?hyy89jbrimxywq2		::::::::::Here's the Wireshark dump: http://www.mediafire.com/?hyy89jbrimxywq2
	:::::::Cleaned up hex dump: https://gist.github.com/1468145		:::::::::::Cleaned up hex dump: https://gist.github.com/1468145
	:::::::Parsed data: https://gist.github.com/1468147		:::::::::::Parsed data: https://gist.github.com/1468147
	:::::::Note, <code>7f 0f</code> remains on the server->client buffer		:::::::::::Note, <code>7f 0f</code> remains on the server->client buffer
	:::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)		:::::::::::After the client sends a login (0x01), your data doesn't make any sense [[User:Barneygale\|Barneygale]] 09:49, 12 December 2011 (MST)
	:::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)		:::::::::::Looks to me like you're sending 32 and 33 as decimal values for your Pre-Chunk and Chunk packets, hence them showing up as 0x20 and 0x21 in the hex dump. Additionally, you're not sending the Compressed Size and Compressed Data fields for the Map Chunk (0x33) packet [[User:Barneygale\|Barneygale]] 09:55, 12 December 2011 (MST)
	:::::::(and you need to send 0x01 Login) [[User:Barneygale\|Barneygale]] 10:03, 12 December 2011 (MST)		:::::::::::(and you need to send 0x01 Login) [[User:Barneygale\|Barneygale]] 10:03, 12 December 2011 (MST)