Hi,

I followed the steps for the "Example circuit breaker" but the "Damage Critical" output only trips when the damage is > 100%. I made a backup of my world and tried it out by not providing enough water. Sure enough at 100% the reactor SCRAMd. But, the temperature was so high that after around a minute there was a meltdown anyway.

I am luckily well versed in ruining worlds from a reactor meltdown and needing to give up or cheat away the radiation. However, I would hope that level of experience isn't the threshold. I propose the following changes:

1. Change from "Damage Critical" to "High Temperature" - this SCRAMs the reactor much earlier
2. Change from sand/gravel to a regular pushable block like cobble - this prevents oscillations from the observer. Essentially a manually needing reset SR latch. Possibly streamline with just a redstone block on a block of slime or something? Unsure.

With these 2 changes, I saw damage get to maybe 30% on my reactor of increased size then recover.

Not a pull request because I don't consider this the solution per say, but I think it's a worthwhile path to follow for the quest writers.

Thank you

There are several issues with this, as it all depends on the size of the reactor. Certain sized reactors will reach high temps without getting damage. Also, these failsafe's won't always save the reactor, depending on the size and what causes it to create the damage. High temp damage doesn't tick as fast if it's just slightly over, where as having no water will cause the damage to escalate quickly. The failsafe is designed to catch most things, but won't always catch all of it. I personally set up 1 failsafe for each. Hope this helps!