Spatial Anchor requiring manual movement after server restart

[Visteus]

Describe the bug

On starting a server, any spatial anchors must be moved to a new block before they properly chunkload the network again. All previous positions seem to be "stored", as a block where I had originally placed the anchor still does not work, even after many "server cycling events". Even graceful shutdowns then starting the server causes this.

I am unsure if this is an issue with the version that the modpack is using, but there are several mentions of this bug in both open (#7828 ) and closed (#8034 ) issues on the repository, so I'm assuming its still an unsolved problem.

How to reproduce the bug

1. Create an AE2 network that spans multiple chunks.
2. Place an Spatial Anchor in some position attached to network. It should load the entire network.
3. Save and close server.
4. Start server and join. Spatial Anchor will not be loading all chunks, if any.
5. Move the spatial anchor, even 1 block adjacent to the original location. Now the spatial anchor will be loading the network properly.

Repeat steps 1-5. Each time you need a unique, new location. Previous locations will still be bugged.

Expected behavior

Spatial Anchors should not require manual movement of the anchor itself after every server start.

Additional details

This is on Minecraft Eternal 2 modpack, modpack version 1.2.0.3, using forge modloader and currently on AE2 version 15.3.2-beta. Its not using VanillaFix, but I'm unsure if there's other mods that can cause the same issues as VanillaFix.

Which minecraft version are you using?

1.20

On which mod loaders does it happen?

Forge

Crash log

n/a

[Visteus]

I must emphasize that this impacts all spatial anchors on the network, including those loading other dimensions. This causes a problem when there are multiple server cycles due to other crashes, config changes, etc. as players need to keep finding yet more spots for their spatial anchors.