Please read the FAQ before submitting a bug report!

Bug description
after server restart some pipe not connected to mekanism multiblock, - visually they are connected, but nothing transfert.
energy pipe to (insert) induction matrix - every server restart
fluid pipe to (insert) evaporator - every server restart
gas pipe to (insert) industrial turbine - random (~50% chanse)
gas pipe to (insert) fission reactor - random
fluid pipe to (insert) fission reactor - random
gas pipe to (insert) thermo. boiler - random

Steps to reproduce the issue

1. Go to '...'
2. Click on '...'
3. Scroll down to '...'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Log files
latest (after server boot) https://gist.github.com/ptk2003/73501d9e058e05a75e241b0c00beeab5
debug (after server boot) https://gist.github.com/ptk2003/50acaa914150e7856c0bb40f47cb75fa

Versions
1.18.2-forge-40.1.51
pipez-1.18.2-1.1.5

Other mods
Mekanism-1.18.2-10.2.3.463

Screenshots (Optional)
Screenshots of the issue.

I'm having this problem too, but in the latest version of 1.16.5, it happens not only with multblock but all machines in general, especially the gas and energy pipes, I have to remove the tip and put it back to work again

Same problem in 1.16.5. Mekanism's multiblock will always refresh when chunk loads, and the ports of multiblock are only connectable when the multiblock is formed. So pipes will always reconnect, but Pipez does not handle/process that correctly.

And the pipes' input(pull) must be reconfigured after chunk reloads. I think Pipez must keep the pipes' input(pull) until the multiblock is formed correctly.

(Just my guess)

This is a critical bug. I think it should be fixed as soon as possible.

Not same. We have same in 1.16.5, but it enother in 1.18.2 - destinations not connected (look as connected)
And we have forced loaded chunks (by chunkloader).

1. Remove equalBlockState Check and always do pipeDirty when neighborChanged

2. Don't setConnecting false when Capability isn't available
   

   pipez/src/main/java/de/maxhenkel/pipez/blocks/tileentity/PipeTileEntity.java

   Line 73 in 7e72b00

   pipeTe.setExtracting(side, false);

This 2 modifications should fix this issue.

If it would be that simple I would have already done it.
Changing this would mess up a whole lot of other stuff.

Still happens in 1.19.2

AllTheMods/ATM-8#723

@henkelmax
But it should be possible to always check, if the block state changes or not? I mean how are the mekansim pipes doing it then?

1. Remove equalBlockState Check and always do pipeDirty when neighborChanged

pipez/src/main/java/de/maxhenkel/pipez/blocks/PipeBlock.java

Line 318 in 7e72b00

if (!state.getProperties().stream().allMatch(property -> state.getValue(property).equals(newState.getValue(property)))) {

2. Don't setConnecting false when Capability isn't available
   

   pipez/src/main/java/de/maxhenkel/pipez/blocks/tileentity/PipeTileEntity.java

   Line 73 in 7e72b00

   pipeTe.setExtracting(side, false);

This 2 modifications should fix this issue.

Do you have a fixed version of this mod? Or at least tried out changing the code?

Any updates to this problem ?
I just destroyed my Fission Reactor with a server restart. xD
(1.18.2)

is it fixed or we need to scram reactors?

afaik it's not fixed

I'm uninstalling this mod now.
The bug is nearly one year old now and still not fixed.
I understand that mod devoloping is hard, but this mod had much potential.