Refined Storage

Refined Storage

115M Downloads

Fix for network receiver

Closed this issue ยท 2 comments

commented

Describe the bug

Related to #963 #949.
After looking into these issues, here is what I discovered. When RS components update every tick, they run a split and merge on the network. What this means is that the first node to update will dictate the network. Because updates go from -x, -z, when components are put in that direction from the receiver they will override the receiver network because the receiver will get merged onto it.
To solve this there are a couple options I came up with.

  1. Hardcode the network receiver to update first
  2. Replace the network receiver+transmitter with a network link which will act as a wireless cable, merging the two networks they touch into 1.
  3. Go back to RS1 mechanics where only a controller came create a new network
  4. Redo the update method to update network components separate from block entities. Maybe a update network method.

How can we reproduce this bug or crash?

See other issues involving network transmission

What Minecraft version is this happening on?

Minecraft 1.21.1

What NeoForge or Fabric version is this happening on?

All of them

What Refined Storage version is this happening on?

2.0.0Beta.2

Relevant log output

commented

Also having these issues on beta.1, but doesn't look like beta.2 fixed it yet

commented

Duplicate of #949