Closed Quinowell closed 5 months ago
Are you using the latest 1.20.4 version? I haven't updated my public server to 1.20.4 yet (still using SparklyPaper 1.20.2) so I haven't worked out all the issues with it.
However this is very weird, especially because that code should always be ran on the world's ticking thread, so I don't know how a CME could happen.
Now that I noticed that you said that this doesn't happen with ALTERNATE_CURRENT
whoops, yeah we use ALTERNATE_CURRENT
@ SparklyPower
Okay now that I took a look into the code, the reason it borks out is because RedstoneWireTurbo
instance is shared between all redstone wire blocks, so the code will bork out if you have two redstone contraptions in two different worlds and they end up ticking at the same time, this will cause concurrent modification exceptions and unexpected behavior with redstone.
For now, it is better to use ALTERNATE_CURRENT
instead, I may fix this issue later, but no promises, because I don't use EIGENCRAFT
on my server, however it is probably not that hard to fix it, I just need to make the RedstoneWireTurbo
class be unique for each world.
I fixed this, but I haven't tested it thoroughly, so bugs may still happen!
As I mentioned in first message - any system that is not alternate-current crashes game.
Vanilla one is also crashes (when restone runs more than in one world)
Have you tried that in vanilla Paper? If this happens with the vanilla redstone behavior (which is "thread-safe" all things considered) then that may be just the server locking up due to too many redstone updates (see the "The server has not responded for 15 seconds!")
Also try Eigencraft in the latest build, I have fixed the concurrent modification exception there.
EIGENCRAFT works fine now. Just paper with vanilla works. Low tps.
I need to check that out later then, but I don't think it is a issue inherently in SparklyPaper, but I haven't tested that issue out yet
Any progress with vanilla system? I'd like to use ALTERNATE_CURRENT
, but it hurts vanilla Redstoners 😔
Redstone lag machine randomly crashes server 🤨 Simple redstone stuff sometimes (and sometimes not?!?) crushes server with exeption:
or sometimes
Here is save. archive-2024-03-10T190116Z.tar.gz
Steps to replicate (all versions with Parallel World Ticking): 0 - Set redstone implementation something that is not alternate-current 1 - Load this save 2 - Interact with machine (observers and wires) 3 - Have bad luck (sometimes it works perfectly fine) If good luck: 3.1 - Use worldedit to copy/paste and try again
https://github.com/SparklyPower/SparklyPaper/assets/54205453/1e2076a4-27a0-4f6b-8dad-a4a29240b0d8