[Crash]: Replication network crashed the server

[Drakest-0]

Have you tried the solutions mentioned above?

Yes

Modpack

FTB StoneBlock 4

Modpack Version

1.5.0

Describe what happened

I was about to add some new items to a memory chip, but when I took out one from the chip storage, it just vanished after puttiung in in my inventory. Then I tesdted with new chips and they worked fine, but with the one currently on the storage, they just dissappear...
Also the matter network did not accept any FE, even with a gate or flux point connected.
The remove a replication pipe and placing it on the network just crashed the server.

Right before the crash, the logs are filled with this message:

[Server thread/ERROR] [net.unfamily.repae2bridge.block.entity.RepAE2BridgeBlockEntity/]: Bridge at BlockPos{x=-34, y=128, z=4}: Network element exists but is not a MatterNetwork!

Maybe is something related to the 1.5.0 or 1.4.0 updates, as this did not happen before.

Link to logs

crash-2025-12-23_14.10.10-server.txt

debug.log

Steps to reproduce

No response

Additional information

I lost almost all the memory chips and the ability to use my replication setup.

Look like this is already reported here: Buuz135/Replication#93

[nosewad]

I have been dealing with this problem as well. From what I have found, these are the steps to reproduce:

1. connect ae2 replication bridge between replication network and ae2 network
2. shutdown server
3. launch server
4. replication network is nullified. mentions this in logs when chunk is loaded. can't access replication network until total network rebuild (remove all blocks that were part of the network and build it again).
5. adding any replication block to the replication network crashes the server

This causes memory chips to disappear when directly removing them from the chip storage (you can break the storage to get the chips).

here are my crash logs:
crash-2025-12-23_22.59.57-server.txt

here is the error that I get in the console when I tried to access the terminal on a nullified network:
console_error.txt

[Appulcake]

This now has an update out from Replication AE2 Bridge that aims to address this: https://www.curseforge.com/minecraft/mc-mods/replication-ae2-bridge/files/7483756 (1.7.0.1.3)

[Mediekore]

At this moment with stoneblock version 1.7.3 this is still an issue.

[12:29:41] [Server thread/WARN] [ne.un.re.bl.en.RepAE2BridgeBlockEntity/]: Bridge: Replication network not ready during onLoad, will retry later. Error: Element network is null!
[12:29:44] [Server thread/WARN] [ne.un.re.bl.en.RepAE2BridgeBlockEntity/]: Bridge at BlockPos{x=-66, y=131, z=-5}: Initialization completed after 60 ticks
[12:29:44] [Server thread/WARN] [ne.un.re.bl.en.RepAE2BridgeBlockEntity/]: Bridge at BlockPos{x=-66, y=131, z=-5}: Post-initialization updates completed
[12:29:59] [Server thread/ERROR] [minecraft/ServerPacketListener]: Failed to handle packet net.minecraft.network.protocol.game.ServerboundUseItemOnPacket@3db8a8d, suppressing error
[12:30:56] [Server thread/WARN] [co.hr.ti.bl.NetworkManager/]: Removed element at BlockPos{x=-66, y=133, z=-4} has no associated network

[Appulcake]

Just got a log of it happening to someone's server still when on pack version 1.8.0 and thus including the latest Rep AE2 Bridge mod version (1.7.0.1.3) that's supposed to address this, so it doesn't seem fixed yet: https://mclo.gs/6CDKChU

Also another, on single player: https://gnomebot.dev/paste/mclogs/pV7jXIW

It seems at that point, that save can no longer be loaded without crashing right away, even when loading it in a previous pack version (1.7.3, so downgraded Rep AE2 bridge mod), or even when disabling Rep AE2 bridge mod altogether - so far only option I've found is to use an external save editor to dismantle the replication network, or load the save with the Replication mod and all its related addons disabled (which'll also need datapacks/ftb/data/irons_jewelry/irons_jewelry/material/replica.json to be temporarily disabled or the save only loads in safe mode), and then quit then everything re-enabled again, but I'm not sure of any unforeseen consequences this brings on long term to the save by loading it with those various KubeJS errors once so I'd hesitate to recommend it - ideally, if you encounter this, both roll back to pre-bridge mod update pack (1.7.3) and use a previous backup of your save (that hasn't been loaded in 1.8.0 yet)

Update: Seems like once this happens to a save in 1.8.0, if you then load it in 1.7.3, it crashes but then after subsequent launches (sometimes needs multiple tries), it does finally launch, at which point it's back to the old behaviour where the network might not be interactable everywhere or adding to it could crash, but at least the world still loads

[Mediekore]

Can confirm. Same is still happening to me in the newest stoneblock 1.8.0 version

[Appulcake]

Replication AE2 Bridge (issue there: unfamily/Replication-AE2-Bridge#34) released another update earlier today, this version 1.7.0.1.4 of that mod does now seem to be successful - my 2 test saves with this issue can now load and the replication network seems intact and can be interacted with.

There's one caveat, it seems that Replication base mod and/or Titanium can't gracefully handle such a null network state, so on first load it might crash (just like how it does right now in 1.8.0 of the pack even if you disable Rep AE2 Bridge mod altogether once it's in a bad state), however, with this new version of the Rep AE2 Bridge mod, after one such crash it seems to fix whatever is wrong as subsequent loads start to work fine.