Mekanism

Mekanism

111M Downloads

mechanical pipe

Midnighthd opened this issue ยท 4 comments

commented

Please use the search functionality before reporting an issue. Also take a look at the closed issues!

Issue description:

Steps to reproduce:

Version (make sure you are on the latest version before reporting):

**Forge: 13.20.1.2476
**Mekanism: 9.3.4
**Other relevant version:

Hello,
2017-09-25_22 32 29
I have a issue with the Thermal Evaporation Block, the mechanical pipe won't connect to the Thermal Evaporation Valve. I tried with the configurator, same issue.

[gist/pastebin/etc link here]

commented

This is fixed in 1.12

commented

Please fill out the reproduction steps in the template.

Is your evaporation plant fully formed? Was the pipe placed before or after the plant was formed? Is it something that happens after server/game restart?

commented

yes it is completely form the pipe was placed after the plantation and cella does not come from the server

commented

Can confirm this happening in certain situations.

Steps to reproduce:

  • Place the tubes next to an invalid structure (completely build, controller missing), like in above picture.
  • Complete the structure by placing the controller (you can break & place as often as you want)
  • See pipe not connect
  • Break pipe & place it again OR place a block next to the misbehaving pipe OR replace another thermal evaporation block
  • See pipe connect

Tech guess:
Pipe isn't allowed to connect if the structure is invalid, if the structure is made valid, with a block which doesn't cause a direct block update it doesn't update the connection status of the pipe.

This is probably also the cause of some other random pipe not connecting issues. Pipe gets loaded, may not connect, structure is loaded (and validated), pipe may connect but isn't aware of this.
Even bigger guess for a solution: Once a structure is validated (and maybe even invalidated) let all things that interact with the "outside world" (valves & blocks) execute a block update letting blocks next to it know its state has changed.

--Edit--
Missed the versions:
Minecraft 1.12.1
Mekanism 9c7164c (version of 1.12.1, 5 hours ago)

--Another edit--
Looks like it is already causing block updates, but not 100% reliable, this isn't caused by chunk borders. My test setup is not crossing any border). Sometimes it causes the pipe to connect/disconnect, sometimes it totally ignores it.

Updated my reproduction path a bit more to make the error appear more reliable.
My guess is that the ThermalEvap controller is missing some stuff to cause the block updates or the removal of it causes such a state which isn't checked correctly.