Thanks for the report - have you been able to reproduce this crash? It's crashing while trying to save a random resource entity which I've only ever seen on computers where the RAM/CPU were failing.

Thanks for the report however I am not able to reproduce any such "adding" logic. When I paste, it always sets the requests to the amount in the blueprint - never adding to the requested amount.

Once robots deliver the requested amount - if I paste again - it re-sets the request to what's in the ...

Thanks for the report. I was able to fix this, however it's going to be for 2.1 as the change is potentially risky and I don't want to break things in 2.0 at this point.

The crash is happening when migrating non-electric-pole entities into electric poles in the save file. Specifically - I think the ...

You've got a lot of suggestions but don't seem to ever reply when someone asks additional questions about one of them.

Thanks for the report however that is working correctly. The pump cannot eject the fluid it has pumped into the pipe it is connected to and so it fills itself half way and stops.

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

I implemented this for 2.1.

Can you please provide the full code required to reproduce this? "profile = { -1 }" does not reproduce what you're showing.

Thanks for the report however I don't consider this to be a bug. This is a simple belt-update-order observation where *some* transport line will be first to update and when splitters/side-loading are involved there's no perfect update order the game can determine. As things flow/move/go-active/go ...

Thanks for the report. Looking into the save file - this seems to be a duplicate of https://forums.factorio.com/129482 combined with not having any "military" targets nearby for the enemies to attack.

Enemies are put to sleep when they have nothing to attack - and landmines are not standard ...

Given this doesn't break anything, and would add extra complexity/fragility to the logic to try to prevent - I'm putting this into "won't fix".

I’m also interested in the save file, because we explicitly have each platform use its own random generator for asteroids to prevent this exact kind of issue.

This is now fixed for the next release.

Thanks for the report. That is working as intended and works that way to prevent you from halting crafting to halt spoilage.

Thanks for the report. I've added some simpler filtering when applying upgrade planners to prevent this when possible.

Thanks for the report however the log doesn't show anything interesting. I've seen some crashes in that general area but nobody is ever able to reproduce anything.

As best I can guess: a random bit-flip corrupted the lua state, or maybe less likely your RAM/CPU are starting to fail. Unless you know ...

Thanks for the report and the save file. This is now fixed for the next release.

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

Thanks for the report. The highlight logic doesn’t know anything about item data. It operates purely on just the basic ID of items.

Even if i do not research bulk inserter tech, there is still no way to know that research is giving a +1 to a non-bulk inserters, researched or not researched the tooltip only says that apply to bulk and stack inserters.


The bulk-inserter technology does not give a +1 to non-bulk inserters or ...