Unimplemented packetIDs for 1.5

[buschtoens]

With or without keepAlive: true the client randomly crashes without any errors.
The Server shows this error:

java.net.SocketException: Connection reset
        at java.net.SocketInputStream.read(SocketInputStream.java:189)
        at java.net.SocketInputStream.read(SocketInputStream.java:121)
        at java.io.FilterInputStream.read(FilterInputStream.java:133)
        at asa.a(Unknown Source)
        at asa.read(Unknown Source)
        at java.io.FilterInputStream.read(FilterInputStream.java:83)
        at ei.a(SourceFile:185)
        at ci.i(SourceFile:250)
        at ci.c(SourceFile:16)
        at cj.run(SourceFile:94)
2013-03-14 18:12:11 [INFO] username lost connection: disconnect.genericReason

[buschtoens]

Okay, now I get some Unrecognized packetIds like 127, 237, 150.

[andrewrk]

I can confirm this bug. There is still some work to be done to be up to date with 1.5.

[mappum]

I added everything documented in the wiki, and the vanilla client works on my server which uses this library. We can try to figure out any other new packets, or just wait for other people to do it.

[andrewrk]

I plan to figure it out. I can duplicate the issue by connecting to a proxy which can dump packets. When you look at packet dumps just prior to a crash you can usually figure out why it's crashing.

[zuazo]

These packet IDs (127, 237, 150) do not actually exist in 1.5.1. These errors are caused by incorrect parsing of other packets. I think I've fixed this bug in the #50 Pull Request.

[andrewrk]

I think it's fixed by zuazo's pull request. Re-open if it is not.