Does your network show more stress after you reload the world, even with the machines turned off? Does it get worse every time you log back in, until everything is overstressed and only breaking and replacing a part fixes it? This addon stops that.
Fixes Create issue #10516. Not affiliated with the Create team. Please report bugs here.
What it fixes
When a chunk loads, a network starts from the total stress it saved. Each block then takes its own part back out as it loads, and adds it again for real. That works as long as nothing changes the network while it loads.
Something often does. A redstone link's receiver can load before its transmitter, see no signal for a moment, and flip a gearshift or clutch off and on. Blocks behind that gearshift get disconnected, or connected again, before their own load step runs. Create then skips that step for them, so their part of the saved total is never taken out. It stays on the network as stress nothing applies, gets saved, and comes back on top of the real stress at the next load. That's why it grows every time you reload, and why it depends on where the machine stands: it all comes down to which block happens to load first.
With this addon, those blocks take their part out of the saved total anyway. The stress you see after a reload is the stress your machines apply.
Networks that already have phantom stress saved keep it until you break and replace one part, as before. After that it won't come back.
Config
config/phantom_stress_fix.properties: enabled.
If a Create update changes the code this addon hooks into, the fix switches itself off and logs a warning. It never stops your game from loading.
FAQ
Client or server? The server needs it (or your game, in singleplayer). Players don't need it to join.
Does it need anything else? Create 6.0 for Minecraft 1.21.1, on NeoForge.
How is it tested? A game test builds a creative motor, a gearshift switched by a redstone link pair, and a fan. Then it unloads every block and loads it again from its saved data, the way a chunk reload does, with the receiver loading before its transmitter. Without the fix the network's stress climbs from 32 to 96 over three reloads. With it, it stays at 32. A second test loads the transmitter first, so nothing switches, and checks the stress stays the same as well.
Can I use it in my modpack? Yes, go ahead, no need to ask.
MIT. Developed with AI assistance. Source: https://github.com/traelmyx/create-phantom-stress-fix

