Is Opis enabled serverside? It isn't auto enabled.Hi,
i just tested 2.1.3. After removing all TE item ducts before the update the server runs again. Putting the item ducts back where they belong and let them get stuffed the server crashes again with the same error as posted by others above me.
Since yesterday (still 2.1.2) i get weird spam on the server console if someone is connected to the server:
[INFO] [ForgeModLoader] Current Stage is 1
[INFO] [ForgeModLoader] Current Stage is 0
this spams at a frequency of 1-2 messages/second. The 0/1 at the end seems to be random.
Also (may be a bug):
Maybe i should contact ProfMobius about this but i will also write this here:
/opis doesnt do anything for me (my server and im op)
no message ingame and the swing interface doesnt show up
what do you mean ?[DOUBLEPOST=1399294046][/DOUBLEPOST]Can you PM me on these forums please I will have a build but no way to effectively test it ,
thanks. Might I ask how many player files these servers have when you take a look under /world/players and if they got deleted with the last questbook reset if there was one?I already messaged them. But until they come back and say that's correct. I find it slightly hard to understand myself since I have several servers with enough people to hit that limit and I have no idea why we haven't hit it. But I am waiting to hear back from the devs. In the meantime there's a 2.1.3 update in the dropdown that should fix a lot of other issues. Its not recommended yet because I want to make sure some of the new updates and additions don't make the whole thing blow up.
I have no idea. I transferred the world from server to SSP, did multiple up-and-downgrades from 2.1.2 to 2.1.3 and back, and then put it all back on a server environment. I had one crash from stuffed item ducts. My quests did not reset, and my world was never deleted.[DOUBLEPOST=1399300089][/DOUBLEPOST]tnx for testing that out for us @PurpleMentat but that still doesn't explain the fact for resetting the quests, do you think there might be any possibility the stuffed itemducts cause some corruption in the player.dat file (which thaumcraft didn't got resetted) and caused the quests to reset, or do you think it's a bug standing alone from all the itemduct behaviour since 2.1.3?
The problem with worlds crashing when they are updated to 2.1.3 looks to be an issue with TE188.8.131.52. Removing conduits before you you update won't prevent the issue. Eventually, if that method is called the world will crash.
And it's not an issue specifically with Crucibles, I don't have any left in my world and it still crashed as soon as I updated it.
Description: Exception in server tick loop
java.lang.ClassCastException: java.util.SubList cannot be cast to java.util.LinkedList
Folks attempting to update:
Back up your world, and don't panic. We likely need to remove all ItemDucts from the world before updating. I'm testing that myself this morning.
tnx for testing that out for us @PurpleMentat but that still doesn't explain the fact for resetting the quests, do you think there might be any possibility the stuffed itemducts cause some corruption in the player.dat file (which thaumcraft didn't got resetted) and caused the quests to reset, or do you think it's a bug standing alone from all the itemduct behaviour since 2.1.3?