Server suddenly insta-crashing everyone

[Elso_Valager 0]

Not quite sure what's causing this, but we seem to have run into a bug that is all of a sudden booting us all to a crash report the moment we join the server. Only two of us were on at the time, and both got this crash at the same time.

 

Could anyone help us with why this is happening?

 

http://pastebin.com/4s4HbBbc

 

For the bug report.

 

Thanks in advance, lads~

[Kittychanley 1,002]

Did you delete a section of the crash report? There should be more information in this area:

java.lang.ArrayIndexOutOfBoundsException HERE A detailed walkthrough of the error, its code path and all known details is as follows:

[Elso_Valager 0]

I can copy the .txt file in an attachment if it'll help clear things up, but nothing is written after that in that specific java line.

[Elso_Valager 0]

Oh, WOW, nevermind, I just read it and found the missing part.. Lemme just copy the right bits.

 

If you check the pastebin link above now, it should have all the information.. NO idea how all of that vanished from the pastebin.

[Kittychanley 1,002]

Did you do any OP commands like /time set day ?

 

The game thinks that you are in a month that doesn't exist, which really only happens if you use OP commands.

[Elso_Valager 0]

I had not, but I think I can probably guess WHY this happened.. I went into TFC Options and changed the length of a year, from 96 days to 360. It says multiple of 12 but I'm guessing this might be a too high-a multiple.. I mostly went with that number so it more accurately portrayed a real-time year. Anyway on the server I did /time set 0 and it reset the calender back to March 1st 1000.

[Kittychanley 1,002]

That would be your problem. 360 is a valid number to set for year length, but the config needs to be changed on both the client and the server or you will get crashes like the ones you described.

 

If you set that value to be the same on both your config, and the server's config, you shouldn't have anymore problems.

 

As for /time set 0, putting the calendar back to March 1st 1000 is the correct behavior. However, by doing that reset, any animals that were born after world generation will have issues, as they are now seen as having a negative age. Other issues might happen for the same reason as well.

[Elso_Valager 0]

Ooooooh.. That explains why our calenders were behaving so strangely. I couldn't predict what the season was because it was telling me it was December when the apple tree we were next to was acting like it was fall.

[Deviator 51]

That would be your problem. 360 is a valid number to set for year length, but the config needs to be changed on both the client and the server or you will get crashes like the ones you described.

 

If you set that value to be the same on both your config, and the server's config, you shouldn't have anymore problems.

 

As for /time set 0, putting the calendar back to March 1st 1000 is the correct behavior. However, by doing that reset, any animals that were born after world generation will have issues, as they are now seen as having a negative age. Other issues might happen for the same reason as well.

Is there a better way to set the world timer back to 0 without the issues? I want to create a server world with a spawn town and everything but that takes time and I would like the world to start at 0 when I upload it to the server.

[Kittychanley 1,002]

Is there a better way to set the world timer back to 0 without the issues? I want to create a server world with a spawn town and everything but that takes time and I would like the world to start at 0 when I upload it to the server.

 

As long as you don't breed any animals, or do anything else that is dependent on time passed (only other thing I can think of right now is tilled soil and crops), you shouldn't have any issues with /time set 0. Otherwise, you could always use debug mode and open the calendar to add time to the map until it is March 1st of the next year. That way your new players would still start in the same season as if you had done /time set 0.