Might be a signed-ness issue somewhere in the protocol handling.
I can confirm that the client crashes when breaking sandstone stairs in survival mode. ProtoProxy reports a weird value in PACKET_SPAWN_PICKUP - the item is "<empty>".
Dear diary,
I don't have any time left for MCServer. All my free time has been eaten by dance training. On Monday, I'll be making a public performance, and I'm really nervous because of it. Let's just hope for the best. I promise to post a video, if I can make someone record it
So you think you can dance?
![[Image: so_you_think_you_can_dance.jpg]](http://blog.basic-fit.nl/wp-content/blogs.dir/3/files/2012/10/so_you_think_you_can_dance.jpg)
(11-25-2012, 08:26 PM)xoft Wrote: [ -> ]Actually, I think I can
Nice
(11-24-2012, 08:00 PM)Luksor Wrote: [ -> ]There seems to be a problem with drops that have ItemType higher than 127. MCServer sends "-1" as an pickup ItemType therefore crashing the client. It think it only happens with pickups spawned by breaking blocks in survival (for example Sandstone Stairs).
Just to let you know: I fixed this bug in r1068.
(11-26-2012, 10:22 PM)Luksor Wrote: [ -> ]Just to let you know: I fixed this bug in r1068.
We should add some asserts to that code, so that we catch these errors at their source (and why are we doing the check, anyway? what if we wanted plugins that added some blocks?)
i'm so curious how xoft's performance went
Nope. It will not affect MCServer at all. They want to replace all hardcoded IDs to names, just like BlockID enums in MCServer.
![[Image: _img_0668.jpg]](http://xoft.cz/img/_img_0668.jpg)