Refined Storage 2.0: Network Fails to Reconnect After World Load / Controller Flashes Red

[piotrgubin-sketch]

Describe the bug

Summary
Refined Storage 2.0 networks in larger bases fail to reconnect correctly after loading a world.
Even when the entire RS core (controller + disk drives) is located in a single chunk and force-loaded, the controller frequently flashes red on world load and parts of the network fail to register. This happens regardless of cable layout, chunkloader configuration, or network size optimization.

This issue appears to be caused by RS 2.0 initializing before all chunks containing RS cables and machines are fully loaded, causing the network graph to be evaluated in an incomplete state.

Environment
Minecraft: 1.21.1

Refined Storage: 2.0.x

NeoForge: 21.1.x

Chunk loading enabled (FTB Chunks / other loader)

Large but modular base

No external storage connected during testing

All RS components in force-loaded chunks

Expected Behavior
On world load, RS should wait until all relevant chunks are loaded before evaluating the network graph.

The controller should remain blue and the network should initialize consistently.

Cables crossing chunk borders should not cause the network to fail if all chunks are force-loaded.

Actual Behavior
After loading the world, the controller flashes red repeatedly.

Parts of the network (cables, autocrafters, machines) fail to register.

Autocrafters flicker between connected/disconnected states.

The network sometimes reports “missing” items even though all ingredients and patterns exist.

The issue persists even when:

controller + disk drives are in the same chunk,

all chunks containing RS cables are force-loaded,

external storage is disconnected,

cable layout is simplified,

relays are used (which isolate but do not solve the issue),

the world is restarted multiple times.

Steps to Reproduce
Build a moderately large RS 2.0 network (controller, disk drives, autocrafter manager, autocrafters, importers/exporters).

Place the entire RS core (controller + disk drives) in a single chunk.

Ensure all chunks containing RS cables and machines are force-loaded.

Save and exit the world.

Reload the world.

Observe the controller flashing red and parts of the network failing to initialize.

Additional Notes
This issue does not occur in RS 1.x.

It appears to be related to the order of initialization: RS 2.0 attempts to build the network graph before all chunks are fully loaded, even if they are force-loaded.

Using Relays does not help because Relays intentionally break the network graph (they isolate segments rather than reconnect them).

Using Network Transmitter/Receiver works around the issue, but this is not desirable for players who want a fully wired network.

The problem is reproducible even with short cable runs and minimal chunk boundaries.

Suggested Fix
Delay RS network graph evaluation until:

all chunks containing RS blocks are fully loaded,
or

the chunkloader has activated all relevant chunks.

Alternatively, provide a config option to force RS to rebuild the network graph a few ticks after world load.

How can we reproduce this bug or crash?

1. Create a new world (Creative mode recommended).
2. Enable chunk borders (F3+G).
3. Place the following setup:
   Put an RS Controller and Disk Drive in the same chunk.

Add a 1k or 4k disk (any disk works).

Run an RS Cable across the chunk border into the next chunk.

In the second chunk, place:

Autocrafter Manager

1–3 Autocrafters

Any importer/exporter (even without machines)

This creates a small, two‑chunk RS network.

4. Force‑load both chunks
   (using FTB Chunks, Chunk Loaders, or any mod that keeps chunks loaded).

5. Save and exit the world.

6. Reload the world.

7. Observe the RS Controller.
   Actual Result
   The controller flashes red for several seconds or permanently.

Autocrafters in the second chunk flicker between connected/disconnected.

The network sometimes reports missing items even though they exist.

Removing and replacing a single cable segment often fixes the network temporarily.

Expected Result
The RS network should initialize fully and remain stable on world load.

Force‑loaded chunks should prevent any cable disconnection issues.

The controller should remain blue and the network graph should rebuild correctly.

What Minecraft version is this happening on?

Minecraft 1.21.1

What NeoForge or Fabric version is this happening on?

NeoForge

What Refined Storage version is this happening on?

2.0.0

What modpack and modpack version, if any, are you using?

No response

Relevant log output

[raoulvdberge]

This is kind of weird. RS was tested for months before release and this (very obvious) issue did not come up. Can you reproduce it with only RS installed, or is some other mod interfering?

[raoulvdberge]

What I don't really like about your issue is that you're adding a technical explanation to the problem, describing what is causing the bug and proposing a fix based on that. However, have you actually looked in the code and attached a debugger to verify your assertions? In other words, on what is your entire post based? Or is it hypothetical? If yes, it's better to not speculate as to not steer me in the wrong direction, causing delay in solving the bug. In that case it's better to stay close to the facts you know.

Your steps to reproduce are not sufficient. Ideally I'd need to know the pack, a world download, and whether you can reproduce it on a setup with just RS installed.

[piotrgubin-sketch]

My problem is ongoing.
I've tried many options.
My system is running on 8 chunks. Every time I start the game, the controller flashes red. Every autocrafter flashes and refuses to produce recipes.
The machines are from Mekanism.
I've tried running the autocrafter directly on the machine, indirectly with a cache as a buffer, and wirelessly.
External storage immediately throws an error.
I have one main line, and from it, there are branches to each segment. I don't have loops or any other returns to the controller.
From online tips, I learned that the mod is to blame when loading chunks, because RS 2.0 doesn't like being on multiple chunks.
Your mod is simply unfinished. On 1.16.5 it worked perfectly, on 1.20.1 I had to destroy the controller and reinstall it every time, and now on 1.21.1, this mod is completely broken. Why did you focus on the technical aspects when AE2 has it? Couldn't they have made an alternative version, like in previous versions?

And I'm not the only one who's annoyed by this strange behavior of version 2.0.0.

[EspiMKII]

Not Raoul, but I'd like to interject for a second here.

Firstly, I've finished atm10 with rs2, and my base spans multiple chunks and dimensions, and absolutely nothing happened. So just because you've encountered this problem doesn't make it applicable across all users.

Secondly, Raoul has a kid, and 2 jobs, and goes outside and exercises, and have an actual life. If you think you can do a better job than he does or know someone who does, send PRs.

Thirdly, I think it'd be better for demonstration purposes that you record some footage of your bases, and be as detailed as possible about it. Show is always better than tell.

[raoulvdberge]

From online tips, I learned that the mod is to blame when loading chunks, because RS 2.0 doesn't like being on multiple chunks.

And that is simply not true.