Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Pipez disconnecting from some mekanism multiblocks on game launch. #1942

Open
nickpilato1 opened this issue Aug 2, 2024 · 2 comments
Labels
Bug Something isn't working

Comments

@nickpilato1
Copy link

Possible Fixes

Yes

Modpack Version

1.1.0

What happened?

Every time I seem to join my world the fluid pipe from Pipez that I have connected to the side of my Thermal Evaporation multiblock disconnects on the extract side and pops any upgrade I have in it out. I noticed it's happening because the mekanism multiblocks seems to unform when you join back to the world so it's not registered as a valid output for the machine. So the pipe is just detaching until the multiblock reforms. It's just a pain because I forget to reconnect it sometimes and it just messes up my whole Fission setup.

latest.log

No response

Developer reports

No response

@nickpilato1 nickpilato1 added the Bug Something isn't working label Aug 2, 2024
@colin094
Copy link

this is a known issue between Pipez and Mekanism, when multi-blocks unload especially across chunk boundaries, they revert to individual blocks which are incompatible to Pipez end connections.

@Ninizzzzz
Copy link

Hum, I think it's a little more specific than that. I use extensively pipez gaz pipe for all mekanism machinerie for fossile fuel and ore treatment to avoid "buffer" with mekanism pipe (just too much of inventory to setup to reach a point where I can know how much I can use in the fission reactor) and I did a couple of observation:

  • All broken pipez where extracting (so, if it get the issue on the input, it "fix" itself later) and are now input
  • Sink is one of those who broke (I presume something about the infinite value that also break refine storage on external storage)
  • The broken one where the extracting from empty quantum only (can't tell for the machinery)
  • I'm pretty sure I saw it happen with Extreme reactor too.

My tought:

  • If it's pipez : it's trying to read if it can connect and in the loading process it can or get an error from the quantum when it's empty. Mekanims has a particular way to work for output/input.
  • I'm actually switching some with ender io chemical conduit to see if they get the same issue.
  • Async init on some info from mekanism for performance ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants