Lua says that if you call `prototype:get_max_wire_distance("normal")` (using ":") then it passes `prototype` as first parameter and "normal" becomes second parameter. Please use correct call (using "."):

prototype.get_max_wire_distance("normal")

In that case you can also not provide quality ...

Not a bug. You have artillery turret at {189, -836} which has "auto targeting" checkbox turned off.

percent_spoiled - item below X spoilage not accepted.


If an item is inserted into ingredient inventory and then time progresses, based on that rule it would become not acceptable while being in the ingredient inventory. That would require some piece of logic to detect incorrect ingredient and ...

Sorry but this is not going to happen due to ill-formed interface request, there are not even any example use cases provided that would allow refining this request.

What would "probabiliy" mean? If a probability roll would fail, would that mean the ingredient is not consumed? That would require ...

Since this item can also be crafted on space platforms, it is not exclusive to aquilo. Not a bug.

Welcome on forums. This is a duplicate of https://forums.factorio.com/118257.

To be more precise why this is not a bug, by pipetting an item and placing ghost you are asking for a plain spidertron to be placed so all equipment of selected item gets removed after placement and moved to storage ...

Then the resulting spoilage ought to remain in the fuel slot and be used as fuel, rather than being removed from the fuel slot, no?


`pentapod-egg` spoils to trigger (spawns wriggler pentapods), not to an item. Because of that if it spoils while in the fuel inventory, it will leave fuel slot ...

I am not considering this to be a bug for 2 reasons: quality upcycling does not matter here since you cannot automate production of base items, and recycling to base ingredients does not make iron or copper unbalanced (does not introduce overpowered recipe that would make other means of obtaining ...

Thanks for the report. It looks like the fusion reactor failed to account for neighbour bonus value inside of a tooltip for a built entity. Issue should be now fixed for 2.1.

Managed to reproduce it. 2.0.72
C:\factorio_2_0\src\Entity\Entity.cpp(327): Entity::forceDestroy
C:\factorio_2_0\src\Entity\Entity.cpp(314): Entity::destroy
C:\factorio_2_0\src\GameStateAdapter.cpp(145): GameStateAdapter::destroy
C:\factorio_2_0\src\Blueprint\BlueprintBuilder.cpp(494 ...

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

This interface request as stated right now is a "wont implement" due to implementation details since kill_count and killed_players is not a real thing on a train, it is an aggregate: those values are stored on each rolling stock individually and what LuaTrain provides is sum of those values of all ...

Provided reproduction steps do not work for me regardless of using 2.0.72 steam space-age or using 2.0.72 standalone space-age. Given the log file says you have 14700K cpu that is known to be affected by 13th/14th gen raptor lake issues, did you update your bios within the latest 12 months?

Please note that get_circuit_network does not accept defines.wire_type. It takes defines.wire_connector_id.

defines.wire_type.red == 2, defines.wire_type.green == 3.
defines.wire_connector_id.circuit_red == 1, defines.wire_connector_id.circuit_green == 2.

By providing wire_type.red, you get ...

Looks like there exists "mirror" parameter that is undocumented and works as requested.

call it whatever you want, i say its fixed for 2.1.

That looks like a bitflip, one of items on a transport line (i was not checking which one) was corrupted as it had quality "9" saved. Happy new year.

Duplicate 130726

Given that the crash happened inside of a steamclient64.dll, there is nothing to be done on factorio side. Moving this to 1/0 magic.

No. This would create a lot of problems around items that can be produced by more than one recipe, which is extra fragile when one recipe can be crafted by one machine while other recipe can be crafted by other machine. This suggestion is under-specified and as such is not going to happen. It is ...