Machine Controllers don't do their Job on Servers after Restart

[HikariTenshi]

Checked for existing issues

• I have checked for existing issues, and have found none.

Tested latest version

• I have checked that this occurs on the latest version.

GregTech CEu Version

7.4.0

Minecraft Version

1.20.1 Forge

Recipe Viewer Installed

EMI

Environment

Multiplayer - Dedicated Server

Cross-Mod Interaction

Unsure

Other Installed Mods

Modpack: Monifactory 0.13
Updated: mae2 to beta i, gtmutils to 2.5.0, Forge to 47.4.13, Java to 25
Removed: waterframes, watermedia, lostcities

Expected Behavior

Using the following settings on machine controllers and level emitters controlling them should result in machines that are controlled like this to produce up to 2000 buckets and then stop:

Actual Behavior

Despite limiting the machines as described, I now have too much of the chemicals they've been set to and therefore too little of basic resources like Oxygen and Fluorine, most noticeable with Rocket Fuel:

The machines keep overproducing due to them randomly turning on despite them saying they're disabled, which happens like for a second every 5 minutes or so. Additionally after server restart, all machine controllers enter this state where they allow the machine to run uninterrupted despite not having a redstone signal that would allow them to do that. Opening the Machine Controller GUI causes them to resume normal functionality where they actually limit the machines, yet that does not guarantee it won't revert to randomly allowing the machine to operate regardless. Here's the sequence of what that looks like in action, hard to catch since it's only for a brief moment:

This issue did not occur in any previous versions of Monifactory that i've played, most recent of which is 0.12.6 (that version ran on a much older gtm version). The issue also does not seem occur when loading the exact same world in singleplayer, making it hard for me to debug.

Steps to Reproduce

1. Run Monifactory 0.13 on a dedicated server (I suspect a minimal build using just gtm will do fine too but haven't tested that)
2. Make a Large Chemical Reactor (or any other multiblock machine)
3. Equip it with a Machine Controller
4. Set the Machine Controller to inverted mode, only allowing the machine to run when the redstone signal is higher than 1
5. Provide the machine with power and the resources to do a particular recipe and enough space to output the results into (so that it would run it if it had a redstone signal)
6. Restart the server
7. Join back on the server to see that the machine keeps running despite the machine controller that is supposed to tell it to not do that

This is the method to trigger the part of this issue that is consistent; I haven't found a way to reliably trigger the occasionally running inconsistent part of it.

Additional Information

Here is the server world if that helps you at all:
https://files.catbox.moe/a9oczq.zip