Put the summary of the bug you're having here
What I expected to happen was...:
As I had a similar problem before but then I only got kicked from the server with error messages like Internal Exception: java.oi.OIException: Bad Compressed Data Format and Internal Exception: java.oi.OIException: Bad packed id (numbers like 144, 79, 102 and many more) and several other error messages. As I was trying to fix this with help fomr the Mojang support team I just expected an error message.
What actually happened was...:
What actually happened was that after just a few seconds on the server Minecraft crashed.
Steps to Reproduce:
1. Open minecraft 1.6.1 on a mac
2. Pick any 1.6.1 compitable minecraft server
3. Try to connect to it
(This may be something on my computer, but I doubt it as I have never had issues like that before. I am thinking it may be that somehow minecraft 1.6.1 multiplayer is incompitable with Macs)
Linked issues
duplicates 1
Attachments
Comments 5
Duplicate of MC-20289, please use the search function to see if your bug has already been submitted. Currently over 58% of tickets are being closed as duplicate.
It's not only crashes that are my problem sometimes when I connect to a server Minecraft doesn't crash but instead kicks me and give me error messages like
Internal Exception: java.io.IOException: Bad Compressed Data Format
Internal Exception: java.io.IOException: Bad packet id (different numbers like 144, 102, 79 I really changes every time I get this error message)
Internal Exception: java.net.SocketException: Connection Reset
There is also a difference to my problem from the problem I "sublimated". I have a mac which may be important here. I have tried every possible solution the mojang support team could give me, and nothing works. I have tried a bunch of other solutions, but nothing works. So I am thinking this may be that somehoe mine craft 1.6.1 multiplayer is incompitable with macs.
Matias, that sounds like MC-2968, which probably means you are using Bukkit. Any non-standard client/server build needs to be taken up with the appropriate team, not Mojang. This site is for addressing issues related to the base unmodded Minecraft.
Based on a crash report provided in this issue, I believe with high certainty that this report may be a duplicate of MC-20289. You can view all information known about this specific crash at MCX-803.