This sounds like a reasonable idea to me rn. However I am not sure about the implications of this for other things until I test it. On paper it looks like it would make the dropping behavior more consistent with my expectations. Specifically regarding planet filtered thrashing.

I had another situation where I used a lot of bots and spiked my power shortly. First i tried accumulators, but their output rate was again too slow. Instead it was much better to just increase the amount of turbines to also cover the biggest peaks.

This is still very bothersome, in particular to us speedrunners. But I can assure that my chat is consistently not understanding why force print is not working on Aqilo on arrival. I also happened to be confused on that on my first playthrough.

https://youtu.be/Edc_A7OPTrs
Save attached

If this is not a bug and intended behavior, that behavior should imo be reconsidered. It does not appear very intuitive.

Thanks for the report however autosave indexes are based off the time in the save file and are not shared/incremented across different saves.

Specifically the autosave index used is computed as: (update-tick / autosave-interval - 1) % autosave-slots + 1


I see that it works this way. However I ...

With many autosave slots (e.g., 1000), loading an older save makes the autosave counter jump back to earlier numbers.
Example: at autosave ~600, loading a save from 1 hour ago causes new autosaves to start around ~540.
This overwrites recent autosaves even though free slots exist.

Expected ...

I see, I get the point with the request space even though it feels a bit inconsistent to me overall. I will just work around this using set requests for my use case then. I think both bahaviors are totally valid, just felt like an oversight at first as the non requesting chest just upgrade plan.

Passive provider to requester does deconstruct isntead of upgrade plan when force printing with set requests
https://youtu.be/Z8OPzEM6qnA

Interesting. No fix is fine for me. I can just build the other network first.
Thanks for explaining!

https://youtu.be/5eEdXV61YxU
Savegame attached

This is still a problem in every playthrough and people struggle to understand why they cannot force print on aquilo water.

Description:
When “Custom minimum payload” is checked, rockets sometimes launch with cargo below the defined limit.

Steps to reproduce:

Load attached savegames.
Platform 201 LDS → Custom minimum payload checked with 200
Platform 301 BC → Custom minimum payload checked with 300
Trigger launches ...

FactorioBot wrote: Wed Oct 22, 2025 11:08 am Changes

• Decider combinator, arithmetic combinator and selector combinator are now primary energy consumers and have buffer size increased to make them more reliable in case of low power.

Awesome!

Quality accomulators not uncharging fast enough for the vulcanus night is an interesting point!

Koub wrote: Fri Oct 17, 2025 9:29 pm

AntiElitz wrote: Fri Oct 17, 2025 2:29 pm Please de-merge my thread.

[Koub] Done.

Thank you <3 . Seemingly this is now also implemented. viewtopic.php?p=683167#p683167

Silos are just one example. It basically is equally true for power spiked on space platforms and other peaking environments


Spite is a powerful motivator, so I thought to actually look more carefully at the rocket silo example.

A common quality accumulator stores 16.7 seconds of charge.

In my ...

From the entity definition :
energy_source =
{
type = "electric",
buffer_capacity = "5MJ",
usage_priority = "tertiary",
input_flow_limit = "300kW",
output_flow_limit = "300kW"
},
5 Mega-Joules / 300 kilowatts * 60 Ticks per Second = 1000 Ticks at full drain

I think that the Accumulator's ...