Open lhunath opened 2 years ago
Note: I can still open the Defender's Forge.
When pressing F8
, do you see the number after 32: rx:
(in the leftmost panel roughly below the middle) increase when attempting to open a chest?
Do the chests open when you open a copy of the world in a vanilla server?
I can't find anything that could be broken without producing any logs within tShock off the bat.
I also recommend backing up your world just in case, if you don't already do that.
The 32
numbers do not change (rx
or tx
), however the 31: tx:
numbers change on each click (rx
does not).
Copied the wld
with rsync -a
over to a local machine and opened it in Terraria directly as a local map, where I can open the chests just fine and the item I had placed into it is present.
At last you can try opening a different world in the same server and check if chests open. Otherwise this sounds like a case for actual debugging
I have created a new world locally, placed a chest into it, with the same item, rsync
'ed it over to the TShock server and launched the server with it. Connecting to it remotely and opening the chest in this new world works, and the item can be found in it. It would seem the issue is a combination of TShock + the original world file.
You are absolutely sure you have no other plugins installed? tShock does hardly any interference with chests, especially none that would break based on a world file, to my knowledge
I have placed a chest into the local copy of the world and then uploaded that to the server. Now when I launch TShock with this locally-modified copy of the world file, I can open the chest as well as other chests again. Exiting and entering or restarting the server does not resurface the issue. If you are interested, I could share the old and new world file.
If the old world file still causes the chest issue, sure
... Restoring the old world file now allows chests to open again.
That pretty much reduces the error space to the network, even tho the log suggests that the connection was reasonably stable the entire time Happens :)
Regardless, here are the wld
files, in case they might prove interesting. I do not know how to inspect their binary format.
https://stuff.lhunath.com/Arcadia.chestsbroken.wld https://stuff.lhunath.com/Arcadia.localfix.wld
That pretty much reduces the error space to the network
Seems dubious given the available evidence (multiple restarts, logins, spaced out over hours, no logs/indicators as you say, and coincidentally disappears as a local copy is loaded?), though I certainly have nothing better to offer. I can come back should the problem resurface.
When clicking to open a chest in the world, nothing happens.
Note: this was working earlier today. I put an item in a chest, restarted the server, and then I could no longer open any chests.
"RegionProtectChests": true,
was set when I put the item in my chest. After restarting, I could no longer open any chests (though building was fine). I shut the server down and set"RegionProtectChests": false,
, but I can still not open any chests.4.5.17.0
Reproduction steps (if applicable)?
Any stack traces or error messages (if known)?
None.
Any screenshots?
Any log messages from files that end in
.log
or.txt
? What are the last 100 log messages from the server console?With
"DebugLogs": true,
:Clicking to open the chest does not generate any log events.
What plugins and what versions of those plugins are you running?
No plugins installed at all.