The Twilight Forest

The Twilight Forest

155M Downloads

Hedge Maze feature placement crashes server

834000 opened this issue ยท 9 comments

commented

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.
commented

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

commented

fixed in 829b19e, will be in the next update

commented

If you call it a fix 1.21, when the issue was on 1.20.1 then it wasnt really a fix

1.20.1 isn't supported anymore, so this is as much of a fix as you're going to get.

commented

fixed in 829b19e, will be in the next update

If you call it a fix 1.21, when the issue was on 1.20.1 then it wasnt really a fix

commented

If you call it a fix 1.21, when the issue was on 1.20.1 then it wasnt really a fix

1.20.1 isn't supported anymore, so this is as much of a fix as you're going to get.

Describe where 1.20.1 isnt supported.
I dont see it on any page

commented

Oh so you gotta join the discord to even get anything about the mod? lol the fix is too stupidly simple to push for 1.20.1

commented

If you call it a fix 1.21, when the issue was on 1.20.1 then it wasnt really a fix

1.20.1 isn't supported anymore, so this is as much of a fix as you're going to get.

Describe where 1.20.1 isnt supported. I dont see it on any page

It is in the FAQ on their discord

https://discord.com/channels/313006291012288521/355784377516687362/1127768921563471903

When will you release an update for Fabric/Forge?
Fabric will not be ported past 1.19.2 due to a lack of porters. Forge will get no further releases past 1.20.1 because we're using NeoForge now.
Contact us if you are willing to work on the Fabric port.

commented

At best you could try downgrading the mod to see if that resolves the issue, or possibly look into disabling the structure via datapacks, but other than that, I'm pretty certain that 1.20.1 isnt going to receive any updates, especially on a closed issue.

commented

welp time to fork since the fix is super simple and refuses to get fixed for the version the issue was reported on