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

Hedge Maze feature placement crashes server #2316

Open
3 tasks done
834000 opened this issue Dec 25, 2024 · 1 comment
Open
3 tasks done

Hedge Maze feature placement crashes server #2316

834000 opened this issue Dec 25, 2024 · 1 comment
Labels

Comments

@834000
Copy link

834000 commented Dec 25, 2024

NeoForge Version

Forge 47.3.12

Twilight Forest Version

4.3.2508

Client Log

No response

Crash Report (if applicable)

https://gist.github.com/834000/9eaeb414cbdd4a1f26c5a1dd0b0a9592

Steps to Reproduce

  1. Ran server for some time (~ a week)
  2. Players began exploring Twilight Forest
  3. After a day of players exploring, the server began crashing when one player generated chunks that should contain hedge mazes (the structure had previously generated without issue multiple times)

What You Expected

The server should properly generate new chunks that contain the hedge maze allowing the player to continue exploring.

What Happened Instead

The server crashes when new chunks where hedge mazes were supposed to be placed are loaded.

Additional Details

It is very important to note that before this, plenty of other players had spent a lot of time in the dimension loading these structures without issue and progressing through the pack. No mods or configs had been changed between the initial exploration and the exploration where feature placement is crashing the server.

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.
@834000 834000 added the bug label Dec 25, 2024
@c0du
Copy link

c0du commented Dec 26, 2024

Same bug, same issue. Hopefully there's an answer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants