Pipenet Hypernob Blocking Own Reaction

[knightshade0]

Severity

Inconvenience

Short Description

Hypernobilium reaction self-blocks in pipenets

Reproduction

1. Fill pipenet with N2/Tritium mix
2. Superheat mix using fusion canister
3. Hypernob will execute a single production tick
4. Hypernob will block after reaching 5 moles

Venting the pipe network via injector causes hypernob production to sporadically start and stop as the value falls below the halting threshold, then executes a reaction cycle before halting again.

Image of the setup used for testing here.

Pipenet Internals:

Misc Notes:

• Disconnecting the Cans made no difference to blocking reaction.
• Nor did removing non-pipenet parts (connectors, heat exchanger, etc.)
• Cans operate as expected with reaction halting once reactants consumed
  
• Was not able to test with tile reactions

Round ID

(Private Server Test, git pull of 2021-11-04)

Test Merges

No response

BYOND Username

No response

Additional information

No response

[ToasterBiome]

hypernol stops all reactions, even itself as reactions are pretty generic

code functions as it stopping all reactions, even itself - don't know if this is an oversight or intended and wires got crossed somewhere in explaining what it does.

[sdk2013]

Hypernob does not stop itself. Hypernob formation is 1001 priority, hypernob reaction stopping is priority 1000.

Hypernob formation works normally (and does not impede itself) when the formation is done in a canister.

[ToasterBiome]

Freaky. Ignore my response then. Was looking at the bit flags and the react proc. I presume the bug is in extools somewhere.

[ShoziOffical]

this is fixed in the recent pr #17092