Adrian Brock

My guess is that it won't fix the problem, but it is an easy test to eliminate one possible source of the issue.

"if you do it this way all multiblock using the FueledMultiblockController will have a throttle even if it makes no sense" These are not intended to be the final implementations....

> by doing things this way I don't think the calculateXXMultiplier was need. Yes, I was also trying to see how to implement a generic throttle if those methods don't...

> On a reload of the generator/cover there is no natural hook to reinject the throttle into the generator. I have done this in a first tick handler for the...

My conclusion is that a cover is not that good of a fit for a throttle. The pluses for a cover are: * It does not require changing existing blocks...

> in fact single block generator stop using fuel when they are not producing therefore I don't see any reason why you would be using a throttle with single block...

> if the generator doesn't need to run full power it will full his internal buffer then stop reproducing a throttle behavior without a throttle. The idea is to let...

> so far it's always below or equal to 100% 100% is just the prototype value. It shouldn't be linear it should follow some curve where reducing the throttle to...

> this might just ending up in people making more machines reducing their throttle to have better efficiency If they want to invest the materials then fair enough. And there...

> You should test this, I think you may be surprised :) Its a separate issue I’ve been looking into for some time. I see what you mean. The cable...