You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I first placed the Spatial Anchor, it worked as expected.
Then I restarted the server and the Spatial Anchor shows:
Breaking and replacing it had no effect.
But! When placing it on a different cable (freshly connected to the controller) loads the chunks again:
Removing the block once more and putting it on the old cable yields the previous broken result.
Removing the block and putting it on the fresh cable / controller side yields the correct result again.
The issue persists through restarts and gets progressively worse, as I start to burn more and more sides I can connect it to.
Removing the cable entirely from the controller does not help, I need a new controller side. (what does this have to do with anything?)
How to reproduce the bug
See description
Expected behavior
At least breaking and replacing the block should get rid of the broken state.
So I spent at least an hour investigating this only to arrive at the following conclusion:
The modpack you are playing is using something called "vanillafix" which completely breaks NeoForge chunkloading.
Please let the modpack maker know so they can remove it.
Describe the bug
I am on Neoforge 1.20.4
When I first placed the Spatial Anchor, it worked as expected.
![image](https://private-user-images.githubusercontent.com/6238896/348559091-470648a4-b357-4193-9a75-532499f72559.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU1NTg4OTUsIm5iZiI6MTcyNTU1ODU5NSwicGF0aCI6Ii82MjM4ODk2LzM0ODU1OTA5MS00NzA2NDhhNC1iMzU3LTQxOTMtOWE3NS01MzI0OTlmNzI1NTkucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDVUMTc0OTU1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MWVjM2RhYzM4ZWE5YTQ0MzgxOTA4NDYwNDNjYjM3ODEyM2Q2MGFiNTE5OWJkZTZhZGU0NmNiZGU1NDA1MzkyMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.HtqBG5zFqSKbIdd78YCjmZCRUFqBjBMbmyDZkIdCoT0)
Then I restarted the server and the Spatial Anchor shows:
Breaking and replacing it had no effect.
But! When placing it on a different cable (freshly connected to the controller) loads the chunks again:
![image](https://private-user-images.githubusercontent.com/6238896/348559181-73b9ef6d-511c-4865-845e-3dcd32b3ded6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjU1NTg4OTUsIm5iZiI6MTcyNTU1ODU5NSwicGF0aCI6Ii82MjM4ODk2LzM0ODU1OTE4MS03M2I5ZWY2ZC01MTFjLTQ4NjUtODQ1ZS0zZGNkMzJiM2RlZDYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkwNSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MDVUMTc0OTU1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9YmU5OTE3MzZhYjdiMTI2OTNiZDk2YWMxYzU0MjE1NGFlOWEyNWUwZTYyOWNkZjgxOTgwYTM5ZTk2NjY5MmUyMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.1nX-4tf6FfgyZ2KDsQ37XReAkYaQ2LTrbXjyeEnMrDw)
Removing the block once more and putting it on the old cable yields the previous broken result.
Removing the block and putting it on the fresh cable / controller side yields the correct result again.
The issue persists through restarts and gets progressively worse, as I start to burn more and more sides I can connect it to.
Removing the cable entirely from the controller does not help, I need a new controller side. (what does this have to do with anything?)
How to reproduce the bug
See description
Expected behavior
At least breaking and replacing the block should get rid of the broken state.
Additional details
No response
Which minecraft version are you using?
1.20
On which mod loaders does it happen?
NeoForge
Crash log
https://github.com/user-attachments/files/16228207/latest.log
The text was updated successfully, but these errors were encountered: