Sorry for long post, I am not a succinct individual.

I have seen previous issues posted about BigReactors using fuel when offline, and it has been stated that this is intentional, and that you should build a control system for your reactor. Well, I have, and I have had a CC control system for my reactor since day one.

Here is the issue. My reactor, being controlled by CC, is off 95% of the time, it just produces too much power and I have a lot of storage. With CC 1.6 and MCPC+ (IDK if this affects forge or not) when a chunk is unloaded then loaded, or the server re starts, the computer will not start running until it is right clicked by a player. So every time I log off, I have to carefully check that the reactor is not running, because if it is on it will use fuel for the entire time I am off, without the computercraft program running to turn it off when the energy buffer is full.

In 3 days of being at my base for ~8 hours a day I used a WHOPPING 28 ingots of fuel. The server I play on gets laggy during the weekends so I usually do not log on Fri-Sun. Imagine my surprise logging on monday to well over 20 stacks of used fuel, even though I have a control system set up to automatically manage my system.

The server I play on the chunk loaders only work when online. This is an option with chickenchunks. So as soon as I log off my chunks are unloaded, and CC will not control the reactor again until I log in and right click the computer, but BigReactors still churns away eating fuel, even though I am offline. There is absolutely NO way I can prevent this with in game mechanics, the only way I can stop it is if I manually check my reactor(s) before I log off to ensure they are not enabled.

This is a trident issue. CC starting the program when right clicked is only supposed to happen at restart, not unloading/realoading of a chunk. BUT MCPC+ causes this issue to happen with CC when unloading/reloading of chunks. CC says it is MCPC+ issue, MCPC+ says they see no issue and CC needs to deal with it, and this issue causes me severe issues with your mod... so you see I am in a conundrum...

I am not asking you to disable this feature, I actually kinda like it. Probably what I would hope for is a CC API that enables a "heartbeat" so to say. If the reactor has a CC port, and the reactor has been turned on by a computer, then there should be a "heart beat" authentication between the reactor and the computer say once a minute, and if the computer stops responding, then the reactor should go into a failsafe SCRAM mode.

Thanks for reading this far and I am open to input as to a resolution of this issue, either in game, or by code changes(Even if it is code changes I have to do and compile the mod myself, rather than PRs to the code base).

This is a CC/MCPC+ issue. Sorry, but I'm not going to pollute the mod with hacks to work around an issue between two external pieces of software.

I would recommend testing to see if OpenComputers has the same start-up issue. BigReactors connects with OC as of 0.3.2A; that may be a viable alternative until the CC/MCPC+ issue is resolved.