https://lua-api.factorio.com/latest/typ ... oductivity

Since you set 'ignored_by_stats' to be 1000 and it propagates to ignored_by_productivity due to a default value, all product is treated as catalyst and as such productivity applies to 0 items

Thanks for the report. Issue is now fixed for the next release.

Thanks for the report. Issue is now fixed for the next release.

This is quite serious problem because it may cause a desync in MP. Core of the problem is that assembler reports as being full when it has a fluid product overload but fluid product overload is checked in a way that introduces a 1 tick ...

Well, the problem here is basically a build order: when blueprint is placed, entities are not placed all at once but they are placed one at a time, and in some orderings the outer undergrounds will pair up and adjust their direction and in other orderings they wont connect due to other entity in ...

So the problem here is that this upper underground gets flipped? That sounds like duplicate of 56695

Looking at the stack, it looks like the freeze is inside of a SteamContext. Because of that i do not see anything here that needs to be fixed on factorio side.

Thanks for the report. Issue is now fixed for the next release. Flipping logic was incorrectly computing flip transformations due to missing check of pipe connection categories making it consider related pipe connections as equal.

"surface" json migration is related to instances of SurfacePrototype and its ID's.

There are also surfaces (on which you build entities) that have their own name. That one you can chance through write to LuaSurface::name in the control stage.

Names are quite confusing here but those are 2 ...

I suspect the issue is caused by the flipping logic comparing connections using only direction(transformed) + offset(transformed) + connection_type + flow_direction + max_underground_distance, but ignoring other parameters like connection_categories or underground_collision_mask, and as such it ...

I completly disagree with this request.

Maybe the connector does not draw when having only script wires, but the control behavior is active and can disable the entity. Not showing circuit connection gui when it could contain settings that make entity disabled or work differently, it is important to ...

Well, lets analyze this problem more thoroughly so you can see the problem as i see it:

When a super force blueprint building is used, it is expected that after all intermediate state is resolved (entities to be removed being removed, entities to be upgraded being upgraded, ghosts being built etc ...

Rationale for linked topics is that a regular chest does not have logistic filters where it could store settings of the target entity, and so if a simple "upgrade" request was set to upgrade regular chest into a storage chest, then a storage chest would have no settings in it. That would mean if you ...

Given that rocket silo does not use inventory index 12, for the next release i made it only report max inventory index of 11. There will be no changelog record for this because i am not considering this to be a bug: max inventory index only represents an upper bound of inventory index that can be ...

This is the same type of not a bug as 131712

Currently that is a limitation that only some entities (mainly ones that need update) support auto heal: units, spider units, turrets, enemy spawners and characters. Trees are an exception since they can regenerate without being updatable.

Looks like asteroids are updatable but they were not made ...

This definitely looks like some sort of CPU hicckup, item production statistics for "player" force had statistics for invalid item. One of the options was to completly cut the item production statistics data out of the save file, but for now i decided to only change this one record to represent ...

How is this different than resolution of 117390 ?

In the next release, "give-item" modifier will throw an error given count of 0.

Do you have a save file i could load and it would crash after some amount of time? Without it there is not much to be done since i am first time seeing crash in that specific place (transport line consistency and connector range start) which makes me believe this may be a hardware issue (possibly ...

I am not considering this to be a bug. Since requester has non trivial settings (item requests), if the passive provider was only ordered to be upgraded then it would not be able to store requests because passive provider has no requests leading to a behavior that would require restamping blueprint ...