Issue description

On my tests, placing a fission reactor and then placing a boiler next to the fission reactor (valve to valve technique) and setting the burn rate to something that coolant can't handle and reactor takes damage causing the reactor glitch out and "reset" its content. It is possible to get infinite sodium out of this glitch. I don't know if the same things would happen on another person's game but I am going to explain everything I know.

Video: https://youtu.be/4yepujjXs3M

Steps to reproduce

1. Build a Fission Reactor (I had this issue on a max fission reactor, 18x18x18)
2. Build a Boiler next to the Fission Reactor
3. Fill the Reactor with Sodium and Fissile Fuel then cut all the wires/break all the tanks that you used to filled the reactor.
4. Run the reactor on a burn rate that sodium can't handle.
5. The reactor is supposed to remove its content after flickering a few times.

In my game, I did a few tests about this glitch and those happened. But in another world, it went even further and caused me to get infinite sodium.

Minecraft version

1.18.2 (Latest)

Forge version

40.1.25

Mekanism version

10.2.1 (Latest)

Other relevant versions

I don't think it is related about other mods.

If a (crash)log is relevant for this issue, link it here: (It's almost always relevant)

No response

I forgot to add, valve to valve has to be correct to make it work, boiler coolant output goes into the reactor and reactor coolant output goes right into the boiler.