Issue description

The redstone port for enabling and disabling fuel burn on the reactor can become faulty when a redstone flicker occurs, sometimes this results in the reactor being set to 0.1mB burn rate, but much more seriously it can actually be set to being pernamently latched on and at full burn rate until the reactor explodes, with no redstone sent to the port at all, completely defeating its purpose

Steps to reproduce

No response

Minecraft version

1.21.1 (Latest)

NeoForge version

21.1.141

Mekanism version

10.7.13 (Latest)

Other relevant versions

No response

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

No response

I had a similar issue, where it would get a bit of water and turn on, then throws a positive signal for just a half a second, and eventually this makes it blow up. I had the thing blow up ~5 times now. I need some way to detect the levels of the material inside. Maybe add a redstone signal to say how full the input fluids and out put fluids are. In the mean time is there a config to turn off the melt down?

edit: I found it in the generators.toml under [fission_reactor.meltdowns]

Please provide a reproduction setup where you are having problems

2025-04-08_20-44-32_reactor detonation test.zip

I made this one just to recreate the detonation problem, however instead this particular reactor just decides to not respond to its redstone ports in any reasonable pattern, you can configure the ports however you wish and their GUI will mention whether or not the redstone signal and the normal-inverted toggle is giving the correct state ("IDLE" vs "activated"), however the reactor does not reliably respond to this for some reason, you can flip the lever back and forth a few times and sometimes the reactor will power up or shut down, but just not remotely reliably.

in another save I had a sodium reactor just send all its coolant into the boiler, at which point the overheat redstone signal would be sent to turn the reactor off, but instead this would flicker the redstone on and off for a couple ticks, at which point the reactor then just stopped responding to the lack of a redstone signal, sending it into a runaway to 50KC, at which point you could open the UI still to manually SCRAM the reactor and remove its fuel, but even though the reactor would still be cooled and the temperature droping the damage would just keep going above 150-200% and eventually detonate the reactor without any fuel.

Should also be noted that if you have the reactor's UI open when the redstone signal flicker occurs, the reactor will close the UI on you, so this seems to suggest that it resets the whole multiblock for some reason, tho I have not seen an exception thrown in the logs when this happens

The small test reactor I linked in the uppermost prior comment also has the resetting to 0.1mB burn bug, no idea why but it just resets itself at random intervals when trying to enable and disable it

I found a work around for this, but it is not a great one. It requires another mod. If you use integrated dynamics you can set it to essentially put 100,000B of water into the reactor every 20 ticks from whatever sources have that much. I then made some extra redstone logic to say if the containers that are hooked up to integrated dynamics are ever under 100,000B of water turn off the reactor because that means it is only 20 ticks from destroying everything.

This is not a great solution, but it is a solution. I would prefer to keep things inside Mekanism. The solution is to add another redstone outputter that outputs the water level. when you are dealing with that much water it is super easy to accidentally have too much steam, then your steam turbine cant take all of that steam, then your reactor blows up...

I think this might just be a feature request to add a redstone control to say there is water in the reactor. Right now it says if there is ANY water turn on, which is not good enough.