Hi :)

I'm using this mod now that it is included in TNP Limitless 3. I used to use old Extreme Reactors in 1.12. I'm using my standard setup to automate turning it on and off.

3 Redstone Ports.

• 1 port set to signal below 10%
• 1 port set to signal above 90%
• 1 port set to turn on/off on pulse.

They are all wired together with simple vanilla redstone. When I am standing there watching, it seems to trigger correctly in both directions. However it has happened 3 or 4 times now, if I'm in a separate area (like the nether), I come back to find the reactor either on full bore at 100%, or off at 0%. The whole thing sits in a single chunk (it's only 5x5x1), and it is chunkloaded with FTB Utils.

I will keep trying to troubleshoot what is happening, but it seems something is buggy between this automation setup and chunkloading somewhere.

Thanks!!

Thank you for letting me know. Could you please post a pic of your redstone setup somewhere so I could rebuild it and check this out?

Here is the layout of the redstone. The leftmost port is above 90% trigger, second one is below 10% trigger, and the other port on the other side is the pulse trigger to turn the reactor on/off.

I think I may have figured it out some potential problem. Apparently the redstone signal leaks out of the corner through the corner block, and sometimes triggers in weird ways. For instance I captured this screenshot that doesn't make any sense to me. Both lines are hot, even though both ports are off, and the port on the right is on, even though it should be a receiving only port.

Also, when it's in this state, if I break and replace the redstone, it all goes dark again. It's as though something is not properly propagating the block updates in certain conditions. And this time I was standing here the whole time when it happened so it seems to have nothing to do with chunkloading either.

I am going to try moving the redstone line out one further so it doesn't pick up residual redstone around the side. But is it new behavior that the port to receive an on/off signal can also output a redstone signal?

I was watching it again as it went below 10%, and this time the port lit up, but no redstone signal activated. I had to break and replace the redstone dust directly adjacent and then it kicked on correctly. So it does seem to be some issue with block update not triggering neighboring blocks correctly when the redstone port changes signal.

But is it new behavior that the port to receive an on/off signal can also output a redstone signal?

Nop, the Redstone Port turn bright red when it is receiving a redstone signal OR is emitting one

So it does seem to be some issue with block update not triggering neighboring blocks correctly when the redstone port changes signal.

It does look like that indeed. I'll run some tests and see what's going on

I have noticed this too, an on/off mode redstone port does not de-power unless it is broken, and a battery level mode port does not turn off once the battery storage falls below the percentage after turning on once the battery level reaches/goes above the target precentage, however the latter can be block updated to update its state to off. Additionally, when the on/off mode redstone port is on toggle on pulse, the reactor's controller does not properly update visually.

EDIT: The ports when emitting a signal, emit the signal from the block in front of it, rather than from the block itself.

@Gluton-Official Ahh.. excellent point. I do sort of remember that from the old BigReactors. You needed to actually run the redstone one block above the port. I changed my reactor to be wired one block above the output ports, but I still had to do it the same level for the input port, and now it seems to be working as expected. IIRC in the old BigReactors it wouldn't emit a redstone signal at all one block below so you wouldn't make that mistake.

[Edit] Sorry this is what it look like now, and it seems to work perfectly. I seem to remember having to do this with BigReactors a long time ago but maybe I misremember. Some blocks do require redstone interact one above, for example OpenBlocks fan has to be turned on/off from a redstone wire one block higher than the fan.

Hi, I've had the same issues with using the "hardset" redstone signal of ON or OFF. Found that PULSE works much better. Here's a pix below.

Redstone Ports that are set to OUTPUT a signal from the reactor also activate the adjacent blocks... note how the Redstone wiring is attached to a Reactor Casing Block and also note there is NO connection to the Reactor from the TOGGLE LATCH (prevent backfeeding of signal).

Redstone Port on LEFT is LOW Energy Storage (Reactor ON). Restone Port on RIGHT is HIGH Energy Storage (Reactor OFF). The logic gates are vanilla MineCraft Repeater (4 ticks) and Comparator (subtractor mode). TOGGLE LATCH is from PowerCraft Gates Mod feeds the CENTER Redstone INPUT set to Turn the Reactor ON and OFF.

The 2 Yellow buttons are Momentary ON buttons from Redstone Gauges and Switches for 1st time setup and future manual control. Otherwise it will run totally automatic.

The pulsing and latching circuit is very similar to the ones I've used in 1.12.2 systems.

Hope this helps for a workaround.

OK so, I should have fixed it:

T0, no energy in the buffer, port "below 10%" emitting signal:

T1, energy buffer filled more than 10%, no redstone signals:

T2. energy buffer filled more than 90%, relevant port emitting signal, reactor is off:

Now the Redstone Port emit power from it's own block as it probably did not make sense otherwise even in 1.10+

I should release and updated version later today

2.0.9 is out

I can confirm on 2.0.10 now the redstone works correctly on the same level as the redstone ports. Thanks!!

Thank you, have fun!