Extreme Reactors

Extreme Reactors

75M Downloads

Loading into a save turns off reactors (Allthemods 10 modpack)

gbeans44 opened this issue ยท 6 comments

commented

Every time I load into my save, my reactors shut off. However, both the number of reactors and which reactors shut off seems to be random. Out of the three I have (1 max 32x32x48, 1 28x11x8, and 1 7x7x8), sometimes the max shuts off and the other two stay on, sometimes its the opposite. I don't think I noticed it before updating the modpack to 3.0.

commented

I have noticed this issue as well. I am in ATM 10 also..

Minecraft: 1.21.1
NeoForge: 21.1.185
ExtremeReactors2: 2.4.21

My reactor is controlled by a reactor redstone port. Upon loading into my world save, I have round my reactor off multiple times. To get it started again, I open the redstone port and click the save button. The reactor fires right up. I am trying now, to remember to check the reactor after quitting and reloading the game, lest I find my AE2 system sudden offline because it burned through my FE reserves while the reactor unexpectedly off.

The answer the question from above, yes, the reactor is still a multiple block when I load my save. I can see the fuel inside and the redstone port and controllers are accessible.

commented

Does this happens with turbines and energizers too?
Z

commented

Also, does this happens only for multiblocks that lays on multiple chunks?
Z

commented

Are the shutdown reactors assembled?

PS: are the reactors really off or is just the textures of the controller block that's "off" ?

commented

It might not matter since I'm on ATM9 but I've got the same issue. Yes it does affect multiblocks of all types, all of them go down together. No it doesn't matter if the whole thing is inside a single chunk, my turbine array is all chunk aligned to avoid boundaries and it still shuts off. The coils shut off too so it's extra annoying to restart it all. It's also worth noting that it doesn't happen every time, but often enough that I can't really rely on this as primary power. Can't the blocks fail/default to an "ON" state as opposed to off?

commented

This should be fixed in ER 1.20.1-2.0.94 and 1.21.1-2.4.25
Z