Implemented crash after restart, please fix

ok i had just raided a jungle temple and gotten a mega rubber sapling and an enchanted sacred saping, then we have a restart, after that, NO one can join it seems without being disconnected from the server near instantly, firstly ban the enchanted sacred rubber sapling, you know why and secondly get the server running!

 

yep, just kicked a couple seconds after connecting.

and agree, sacred rubber trees are cool (in single player) would be nice to have ONE on the server, so people can see one.

 

i have ONE xD[DOUBLEPOST=1415748391,1415748034][/DOUBLEPOST]aaaaaaaaaaaaaaaaaannnnnnnnnnnnnnnnnnd the server's straight up down

 

We are working on it, please be patient.

 

Thanks, since just starting, expecting some significant hiccups.

 

Oh, edit: surprisingly it has gone very well, this is the first big issue so far.

 

the issue seems to be ongoing?

 

their working on it

 

It's a new server, just barely under 48 hours old, at least to the public, so there's going to be a few hiccups as they optimize and fine tune the details and fix problems that we, as players, find along the way.

 

Me, cbro and xfel have all bashed our heads against it and unfortunately we have no idea how to fix it, I've been googling the issue for the past hour now and nothing remotely helpful could be found..

I'm afraid DW20 will be unavailable until Slind or Willi can take a look at it, and they are both offline right now so I can't give you an ETA.

 

dang!

 

What exactly is the issue, if I may ask?

 

Don't worry, we're patient people and will await the fix, thank you for letting us know

 

the server forces you to disconnect

 

Internal Exception: io.netty.handler.codec.DecoderException: java.io.IOException: Bad packet id 6

FYI the bad packed ID 6 doesn't even exist accordin to google, if you search "Bad packet id 6" with the quotes it returns nothing at all.

 

apparently this bug is on all versions scince 1.7, mojang has no comment on this issue from what i've seen

 

You have any logs at all?
T'would be helpful if you could pastebin those.

 

actually a mod of them posted below it this

Spoiler

[Mod] CubeTheThird

Spoiler

added a comment - 31/Oct/13 2:12 PM
This is not a bug. Simply change the server setting "player-idle-timeout" to 0.

this is from the mojang forums *looking in the comment section of this, that doesn't work*
found what looks to be a proper solution!

Spoiler

It is your PC/SERVER - we took the server files (No alterations) and migrated to a new box. The error has completely gone away - anyone having this issue should address the box they are working on - it is a setting within the computer that MC/JIRA will have no control over - could be anything from a win update, Java install/path(Location) to anti-virus program... after months of trouble shooting to no positive source, we have thrown out the other box even though it was much bigger as there was an issue in the win7 environment that was not accepting the newest MC server updates and/or allowing them to be played.

So suggestion, ask someone else to host with the same exact files and you will find that it runs like a champ again! Sad but true....

 

There are no logs to go with it, that error code is what comes up in console when a player logs in immediately before they get disconnected again.

We already have it set to 0 in our server properties... :/

 

i said after that it doesn't work apparently on the mojang forums