Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crush when quickly use waystones #920

Closed
uhloin opened this issue Oct 26, 2024 · 5 comments
Closed

Crush when quickly use waystones #920

uhloin opened this issue Oct 26, 2024 · 5 comments
Labels
bug Something isn't working as expected Forge Issues occurring on the Forge platform Minecraft 1.21 Issues occurring in Minecraft 1.21.x needs repro This issue needs a minimal reproduction case before it can be solved

Comments

@uhloin
Copy link

uhloin commented Oct 26, 2024

Minecraft Version

1.21.1 (LTS)

Mod Loader

Forge

Mod Version

waystones-neoforge-1.21.1-21.1.5.jar

Describe the Issue

I tried jump from one Waystone to another and back as soon as possible and after ~10 times got this crush.
May be it's important - one side used chunkloader mod to keep chunk loaded and another side is normal.

Attempt to jump again after crush:
"The waystone you tried to teleport to is currently being moved or has gone missing"
After crush this waystone was turned to "Undiscovered" state
Break and set this waystone again - teleport - ok, but if teleport back then again
"The waystone you tried to teleport to is currently being moved or has gone missing"
Attempt to go to another waystone - ok

Logs

crash-2024-10-27_02.56.04-server.txt

Do you use any performance-enhancing mods (e.g. OptiFine) or custom server distributions (e.g. SpongeForge or Arclight)?

Sodium+Iris

@uhloin uhloin added the bug Something isn't working as expected label Oct 26, 2024
@BlayTheNinth
Copy link
Member

Duplicate of #882. There has been no cases of this happening with only Waystones which indicates that it is caused by another mod, likely a chunk or performance-related one. Until that mod is identified (e.g. through trial and error) or the issue is reproduced with only Waystones, there's nothing I can do.

@BlayTheNinth BlayTheNinth added needs repro This issue needs a minimal reproduction case before it can be solved Forge Issues occurring on the Forge platform Minecraft 1.21 Issues occurring in Minecraft 1.21.x labels Oct 27, 2024
@BlayTheNinth BlayTheNinth moved this to 📧 On Hold in Issues Oct 27, 2024
@uhloin
Copy link
Author

uhloin commented Oct 27, 2024

Ok, I really have a lot of mods. I will try to narrow to minimal combination to reproduce. Currently, I have a save with buggy Waystone, if I brake and set it again or even if I use another waystone item, then it becomes buggy again, as if chunk itself is corrupted by some way.

@uhloin
Copy link
Author

uhloin commented Oct 27, 2024

With my long list of mods and the same world I was able to reproduce a crash after 46 fast teleports between 2 waystones.

Also I checked crossing between my case and #882.

architectury-13.0.6-neoforge.jar
balm-neoforge-1.21.1-21.0.20.jar
corpse-neoforge-1.21.1-1.1.2.jar
cupboard-1.21-2.8.jar
curios-neoforge-9.0.14+1.21.1.jar
jei-1.21.1-neoforge-19.21.0.247.jar
mcw-doors-1.1.1-mc1.21.1neoforge.jar
mcw-fences-1.1.2-mc1.21.1neoforge.jar
mcw-furniture-3.3.0-mc1.21.1neoforge.jar
mcw-trapdoors-1.1.3-mc1.21.1neoforge.jar
mcw-windows-2.3.0-mc1.21.1neoforge.jar
Terralith_1.21.x_v2.5.5.jar
travelersbackpack-neoforge-1.21.1-10.1.3.jar
waystones-neoforge-1.21.1-21.1.5.jar

I was not able reproduce a crash after 100 teleports, but after press Alt+F4 just after 100th teleport my game stopped responding instead of normal exit. This is bag too, it is related to crashes with some probability. The test was like this:

  1. create a creative world
  2. set 2 waystones "1" and "2" near each other
  3. creative flight 1000 blocks
  4. set 2 more waystones "x" and "y" near each other
  5. teleport between "1" and "x" waystones as quick as possible with use pair waystones to jump faster with face to some waistone and do not spend time to rotate character back to waystone.

After this I was able to reproduce this Alt+F4 issue with different list of mods, and the crossing is only 3 mods:

balm-neoforge-1.21.1-21.0.20.jar
jei-1.21.1-neoforge-19.21.0.247.jar
waystones-neoforge-1.21.1-21.1.5.jar

With this list there are no crashes after 300 teleports with 4, 5 or 2 waystones, but the same exit bug on Alt+F4. So, if it's not a sole JEI bug, then waystones is involved.

@BlayTheNinth
Copy link
Member

I appreciate the effort you've put into testing this but an unclean exit on ALT+F4 is not related to this particular crash.

@BlayTheNinth
Copy link
Member

Closing for now until it can be narrowed down with which mod in particular it's occurring, since there hasn't been any reports of this happening with only Waystones installed.

@BlayTheNinth BlayTheNinth closed this as not planned Won't fix, can't repro, duplicate, stale Dec 25, 2024
@github-project-automation github-project-automation bot moved this from 📧 On Hold to 🎉 Done in Issues Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as expected Forge Issues occurring on the Forge platform Minecraft 1.21 Issues occurring in Minecraft 1.21.x needs repro This issue needs a minimal reproduction case before it can be solved
Projects
Archived in project
Development

No branches or pull requests

2 participants