#Server Rollback

30 messages · Page 1 of 1 (latest)

gilded apex
#

I am playing on my friends server and he is running it via 'Host & Play'. The first few days everything was running and working fine, however yesterday & today we have been experiencing roll back issues making us lose our progress. For example, we killed planterra yesterday and got off on that note. However, logging on this morning we still have planterras loot, however the unlocks you get from planterra we did not get (e.g ectoplasm from dungeon, tiki set from witch doctor). It's also important to mention that our character progress themselves (i.e items in inventory) do not roll back, only changes made to the world (includes placement of chests and items in chests).

We are currently running the following mods:
Terraria Overhaul (v5.0 BETA 12C) v5.0.0.21
Recipe Browser v0.9.8
Ore Excavator v0.8.4
Calamity Mod Infernum Mode v1.8.17 (Disabled however)
Fargo's Mutant Mod v2.8.8
Calamity Mod Music v2.0.2.2
Catalyst Mod v1.1.0.6
Calamity's Vanities v10.2
Calamity Mod v2.0.2.3

📎 client.log 📎 server.log
ornate coral
#

we saw in the list of known bugs about the world sync issues, we tried both the world sync fix mod & removing beds/housing on the left and right side of the maps, but we still have issues regarding closing the game, the game still seems to be 'hung' and won't fully close

stark schooner
#

I would recommend not combining overhaul with calamity, as that leads to a multitude of bugs (not sure if this bug is related)
Try disabling that mod and see if the problem still happens

ornate coral
#

however, we’ll give it a try

ornate coral
stark schooner
#

the bug lists aren't timed with anything in particular, it's not specifically related to that

gilded apex
#

I have disabled overhaul and the problem still persists
"server hung for more than 10 seconds. cannot determine cause from watchdog thread" continues popping up when trying to close the game. We suspect this may be causing the failure to sync causing rollbacks.

ornate coral
#

@stark schooner ^

ornate coral
#

we've deduced that this specific world is causing the server to hang, preventing it from closing & preventing the world from syncing but we have no idea how to fix it

unborn knoll
#

yea its likely that the world bricked with mod conflicts

#

Overhaul does not like other mods

unborn knoll
#

@ornate coral also do not rush me to get to see your bug reports.

I always tend to look at them anyways when I can, rushing me just puts unnecessary stress when I'm busy with something else

# 
   at System.IO.BinaryReader.InternalRead(Int32 numBytes)
   at System.IO.BinaryReader.ReadSingle()
   at Terraria.Utils.ReadVector2(BinaryReader bb) in tModLoader\Terraria\Utils.cs:line 649
   at CalamityMod.Systems.WorldSyncingSystem.NetReceive(BinaryReader reader) in CalamityMod\Systems\WorldSyncingSystem.cs:line 297
   at Terraria.ModLoader.IO.WorldIO.<>c__DisplayClass24_0.<ReceiveModData>b__0(BinaryReader r) in tModLoader\Terraria\ModLoader\IO\WorldIO.cs:line 525
   at Terraria.ModLoader.IO.BinaryIO.SafeRead(BinaryReader reader, Action`1 read) in tModLoader\Terraria\ModLoader\IO\BinaryIO.cs:line 27
   at Terraria.ModLoader.IO.WorldIO.ReceiveModData(BinaryReader reader) in tModLoader\Terraria\ModLoader\IO\WorldIO.cs:line 525
[14:36:36.913] [Main Thread/ERROR] [tML]: Above IOException error caused by WorldSyncingSystem from the CalamityMod mod.```

By any chance did you generate the world on 2.0.2.1?
#

usually the solution to this if its 2.0.2.1 its just to make a new world, as it cant be saved
if its 2.0.2.2 or 2.0.2.3 then trying the worldsync mod helps

#

the server crashing error is still a mystery

#

but my best guess is Overhaul + content mods causing issues

ornate coral
#

we tried removing overhaul

#

but the server is still hanging

unborn knoll
#

yea the world was bricked already

#

either load a backup or just play on another world

ornate coral
#

daaamn alright

#

thanks for the help

unborn knoll
#

also by any chance did you have Fargo's lootbonus before killing skeletron?

#

if you did well... the backup will need to be pre-Skele

#

if no then just use backups til one doesnt crash

ornate coral
unborn knoll
#

alr so if you're lucky you wont need to go all the way back to pre-skele

ornate coral