I have a modder server for a few friends of mine and I've been trying to use the spatial storage drives, no matter what I do it won't store into the drive. Tested the same setup in single player and it works. Do the spaitl drives not work server side?

Could it be respawn point protection?

Please read the instructions that are shown in the textbox when you create an issue.
Without detailed information, we cannot you help.

So, made a new test server same issue.
Only running ae2 to limit the chance of mod confilcts
Respawn point protection isn't the issue

Current setup I have, this works in single player

Other info:
Forge Version: 1.16.1-32.0.108
Ae2 Version: 8.0.0-beta.1

@AidenWilkins I just tested this locally with 1.16.1 and it worked for me (with a server).

Could you please enable debug logging in your AE2 config, and send the server-log after trying again?

To enable debug-logging please find config/appliedenergistics2-common.toml and set DebugLogging = true. This should log spatial transition issues.

latest.log
So I enabled debuging and it now just works

Hm alright. I'm gonna close the issue, but if you keep debug log enabled and this issue occurs again, please let us know.

OK so said fix worked on my test server but not on the actual server. It appears that the Spatial IO port isn't taking the redstone signal as I see no logging from the port in the console (Like i did with the test server)

You need to provide an actual log file of the place where it doesn't work.

I will provide when I can, don't currently have access to the server. Though providing that might be a little harder than just giving the log file because even with DebugLogging set to true it's not actually logging anything (or at least doesn't appear to be, based on the fact that the console did have any out from ae2 appearing in it)

@AidenWilkins I've heard reports that the Minecraft dedicated (and only that, not the singleplayer one) will sometimes not load dimensions when it creates a new world, but will load dimensions whenever it loads an existing world.

It is possible this bug occured on a server that had created a new world, and was not restarted since then?

Relevant Minecraft-Bug here: https://bugs.mojang.com/browse/MC-195468