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

Server Crash w/ Fluid Extractor #21

Closed
nathantfaust opened this issue May 4, 2018 · 1 comment
Closed

Server Crash w/ Fluid Extractor #21

nathantfaust opened this issue May 4, 2018 · 1 comment

Comments

@nathantfaust
Copy link

I am reporting this along with an issue report posted on the SevTech Ages issue tracker. Please refer to this link: DarkPacks/SevTech-Ages#2219

What I did:

Fluids were pumping into a buffer before being pumped into another machine

What happened:

The pipes stopped moving fluid out of the tank and server crash with a null pointer exception related to ticking the fluid extractor.

What should have happened:

The system should have maintained its function as it was working previously without any changes to the mechanism.

Used Versions:

  • Minecraft-1.12.2
  • InductiveLogistics-1.1.3
  • CD4017BE_lib-?.?.?
  • Forge-14.23.2.2651
  • Carry On
  • set by SevTech Modpack
@CD4017BE
Copy link
Owner

CD4017BE commented May 5, 2018

The described issues definitely match some bugs I fixed in 1.2.0 and finally 1.2.1

These bugs involved networks of the Advanced Universal Pipes sometimes getting into invalid states after chunk (or World) unloading and reloading. These then caused all sorts of problems from the pipes not working anymore, entire loss of attached connectors and filters, up to sometimes pipe connectors being ticked although they weren't part of the network anymore causing the above mentioned crash.

The pipe network has been greatly redesigned now to ensure that these invalid states don't happen anymore and to make ticking of components without network impossible.

@CD4017BE CD4017BE closed this as completed May 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants