Rail Entity Being Ticked
FlamingCatz opened this issue ยท 4 comments
Forge Version
36.2.34
Twilight Forest Version
4.0.870
Client Log
Crash Report (if applicable)
Steps to Reproduce
- I downloaded many around 29 mods, including Twilight Forest, onto an Aternos server.
- I then started the server.
- The server crashed almost as soon as it started.
What You Expected
I expected the server to continue working, especially after I used a new seed.
What Happened Instead
The server crashed and it said that it was because of a rail entity.
Additional Details
I wasn't sure what happened, so I asked for help and someone said that they thought it had something to do with the Twilight Forest mod and how it affected world generation.
Please Read and Confirm The Following
- I have confirmed this bug can be replicated without the use of Optifine.
- I have confirmed the details provided in this report are concise as possible and does not contained vague information (ie. Versions are properly recorded, answers to questions are clear).
- I have confirmed this issue is unique and has not been reported already.
I'm looking at the crash reports and there's nothing pointing to any specific mod, nor even Twilight Forest.
The crash is java.lang.BootstrapMethodError: java.lang.LinkageError: loader constraint violation: loader (instance of sun/misc/Launcher$AppClassLoader) previously initiated loading for a different type with name "org/apache/logging/log4j/util/MessageSupplier", however, I wouldn't have a clue what results in this. Perhaps a bad mod.
However, it says, https://gist.github.com/FlamingCatz/b73e75e9a6f183cd37d922c1de35fd0f/revisions#diff-6eb5aa2af122281945d8d42cc285a04af319c927fec0b2e03ce47987c39985a2 in the crash report under the entity being ticked version.
