Skip to content

Nuclearcraft Fluid Incompatibilities #289

@evollbrecht

Description

@evollbrecht

Describe the bug

  1. Crash due to a null pointer exception while ticking a block, triggered when a Nuclearcraft fluid attempts to flow into the blockspace of a flux point or plug from Flux Networks (potentially other tile entities as well, untested). Any attempts to re-enter the world will immediately trigger the crash again.

  2. Fluid logging anything with Nuclearcraft fluids that behave like a gas (i.e. flow upwards and disperse) will instantly delete the placed object.

To Reproduce
NPE Crash:

  1. Install E2:EE modpack
  2. Place one or more flux points
  3. Place a bucket of liquid helium, ammonium sulfate solution, or similar such that it will flow into the flux point
  4. Repeat as needed until crash occurs. This is not always consistent, and it may take multiple tries before the fluid actually attempts to enter the flux point's blockspace rather than flowing around it.

Gas Logging Deletion:

  1. Install E2:EE modpack
  2. Place anything that can be fluid logged (fence, fluiduct, flux point, etc. etc.)
  3. Fluid log the placed object with a Nuclearcraft gas like helium, nitrogen, etc.
  4. Placed object instantly disappears.

Expected behavior
NPE Crash: Fluid either always flows around the placed object, or fluid logs it without causing a crash.

Gas Logging Deletion: Placed object is not deleted.

Screenshots

Image Example test setup used to recreate the NPE crash. Screenshot shows expected behavior; I had to place down another few buckets nearby after this to trigger the crash.

Logs
https://mclo.gs/P3tIyps
Example of the NPE crash.

Additional context
I originally triggered the NPE crash during normal play after misclicking while holding a bucket of liquid helium, and after using NBTExplorer to delete the fluid, accidentally did the same thing again. It's possible I was just unlucky to trigger the crash "first try" twice, but I think it's more likely that the crash can be more consistently reproduced in more computationally-intensive settings like a player base, as opposed to an empty testing world, where it always took multiple tries.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working as intendedincompatibilityThis issue relates to another mod

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions