Placing second network transmitter/receiver bricks entire system

Question

Placing second network transmitter/receiver bricks entire system

imjaywalking opened this issue 7 months ago · 6 comments

imjaywalking commented 7 months ago

Describe the bug

Placing a second network transmitter and receiver caused first set to no longer work and when trying to open the crafting grid it says you dont have permission. This bug also makes it so cant break any refined storage blocks and if you manage to break them they dont drop they just disappear, it basically completely bricks your entire system. It also turns controllers off aswell so its any block in the network that breaks.I also had the problem occur again when placing a fluid storage block and trying to break the cable that was connected to the system. The pack it happened on is modified cobblemon plus v11.3.0 on curse forge.

How can we reproduce this bug or crash?

place down a network transmitter and link it to a receiver and then place down another transmitter and link it to a new receiver

What Minecraft version is this happening on?

Minecraft 1.21.1

What NeoForge or Fabric version is this happening on?

21.1.141

What Refined Storage version is this happening on?

neoforge 2.0.0-beta.1

Relevant log output

raoulvdberge · Answer 1 · 2025-04-03T10:56:39.000Z

Any relevant logs?

raoulvdberge · Answer 2 · 2025-04-03T10:56:54.000Z

Are you sure of these reproduction steps?

imjaywalking · Answer 3 · 2025-04-03T15:03:37.000Z

Just tried replicating in a single player world and even with multiple transmitter and receiver it worked fine, even breaking and replacing worked fine, could it be a server side config?

…

On Thu, Apr 3, 2025 at 6:57 AM Raoul ***@***.***> wrote: Are you sure of these reproduction steps? — Reply to this email directly, view it on GitHub <#926 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BRDSDA2OQN7QZDLPRPBKOMD2XUHYZAVCNFSM6AAAAAB2KQNGJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZVGM3TGOJSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: raoulvdberge]*raoulvdberge* left a comment (refinedmods/refinedstorage2#926) <#926 (comment)> Are you sure of these reproduction steps? — Reply to this email directly, view it on GitHub <#926 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BRDSDA2OQN7QZDLPRPBKOMD2XUHYZAVCNFSM6AAAAAB2KQNGJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONZVGM3TGOJSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

Moobien · Answer 4 · 2025-04-03T18:19:22.000Z

I experienced this in milestone 4.14

Darkere · Answer 5 · 2025-04-03T18:24:44.000Z

I'm guessing this happens when you are low on power

raoulvdberge · Answer 6 · 2025-04-04T12:05:54.000Z

I think the crash might be related to #850.
I'm going to close this for now as there are no good reproduction steps, but please let me know if you find a good way to reproduce.
And I'll also need some logs next time.