Thanks for the report however without any way to reproduce this issue there is nothing i can do.

Thanks for the report. Issue is now fixed for 1.2.

Thanks for the report however i cannot reproduce this issue in 1.1.77, maybe i am missing some steps or it was already fixed. Moving to pending.

Meh

Thanks for the report. I am not considering this to be a bug. There are not many reasons why you would want to upgrade existing electric poles other than using newer items that are easier to produce. Having more connections may actually be desired since it creates extra rendundant connections that w...

Thanks for the report. Issue is now fixed for 1.2.0

Thanks for the report. I am not considering those tooltips need to mention obvious key combinations like the "clear cursor" binding.

Thanks for the report. Issue is now fixed for 1.1.78.

Thanks for the report. Issue is now fixed for 1.1.78. There was a missing energy source notification due to separate code for rotating loaders that does not go through setDirection code.

Thanks for the report. Loader will increase the buffer size to at least ElectricEnergySourcePrototype::buffer_capacity starting from 1.1.78.

Thanks for the report. I made some tiny improvement here for 1.1.77 so it should discharge roboports equally if possible, but if some roboports are empty it may discharge other roboports more or go into fallback discharging. That however should not be a problem in most cases.

Eh... fixed for 1.1.77.

Not a bug. There is a non zero distance an item has to travel from the miner to the center of a splitter when the splitting logic happens and so that setup is limited by throughput of a single belt line.

I see where the issue comes from: that beacon is supplied by 2 electric networks. That entity has a primary electric network which is the small one, and the secondary electric network which is the huge network. The problem is that the huge network updates first, does not apply drain since its not a ...

Thanks for the report. I see this issue does not happen in 1.2 so i am moving this to "Fixed for 1.2"

Thanks for the report. Issue will be fixed in 1.2. Both cases will be correctly handled with an error message: Failed to prepare global: Error while running setup for entity prototype "rocket-silo" (rocket-silo): fixed_recipe="rocket-part" cannot be used on this machine. Reason=D...

I cannot observe this issue in 1.2 so i am assuming it was fixed in the meantime. Moving to "Fixed for 1.2"

Thanks for the report. I am going to call this not a bug. My fix for this case if applied would be to disallow rotating existing entity at all due to collision box not being rotationally symmetric around the {0,0} position but i am considering such fix to be possibly mod breaking and as such i am no...

I have no idea what exactly this bug reports is about. emissions_per_minute is set on energy source prototype and it causes pollution when entity asks for the energy from the energy source. Accumulators are not updatable so they cannot extract energy from energy source and as such they cannot pollut...

When trying to load that blueprint storage it fails on some internal asserts because a boolean was loaded with unexpected value "13" for a GenericOnOffControlBehavior::entityDisabled for a lamp. Because of the file corruption and no reproduction i have to move this to 1/0 magic.