[2.0.39] the newly LuaSchedule::get_records, set_records, and clear_records have parameters of type "uint: interrupt_index" instead of "interrupt_index: uint".

...have you considered making a compiler to check for type errors? I guess I accidentally have

- only give bonus items once main item is complete.

Also possible fix: Count the ingredients as consumed for the current crafting cycle, whenever a bonus productivity item is created.

- doesn't give back item when cancel recipe like before (that could hurt player)

But please please don't ...

It requires manual input, but is possible to parallelize:



If this ends up _not_ getting fixed, factorio speedrunning may end up no longer "glitchless". Which may be an interesting world to live in?

Thanks for the fix!

Not sure those 2 saves are based on the same version. I think I loaded an old game version and copied blueprints to a new save to continue.

In any case there weren't any issues loading the saves until updating to the new version.

Narrator: it was, in fact, not fixed in 2.0.35.
(Or maybe the save was already doomed to fail in 2.0.34?)

Save file and log attached.

update... the same error seems to occur when loading the save in 2.0.33, when adding a new mod.
This might point to it being in the migration logic somewhere?

After updating to 0.34, get a crash loading a 0.33 save.
Crash message indicates this might be because I was doing demolisher shenanigans in editor mode (deleted some naturally spawning ones, added then deleted more).

Log and save are attached.

Edit: attached the correct log file this time

What?
We wish for a command-line option to start a replay, e.g. `--load-replay FILE`.

Why?
In speedrun.com administration, we often check replays submitted with a runs. This involves inserting a script into the control.lua of the save, which logs certain events, then running the replay. We ...

I've narrowed it down a bit more:

- Load the save without mods
- .destroy() train shown in the youtube video
/c game.player.selected.destroy()
- Try to save game -- crash

Removing the item request before destroying the train avoids the crash (as suggested by the logs saying stuff with item ...

[2.0.24]
TriggerEffect has "DamageEntityTriggerEffectItem" as a union member, but that type no longer exists (did you mean "DamagerTriggerEffectItem")?

[2.0.17] LuaControl set_driving takes parameters of type "bool", they should be "boolean"?
There's also a typo in that method's description. Spell checker?

[2.0.15] PipeConnectionDefinition::linked_connection_id has type uint32. But uint32 doesn't exist, it should be just uint

LuaPostEntityDiedEventFilter::type is specified to only be "ghost", but the variant parameter imply that type can also be `"type"`.

More:
defines.default_icon_size is empty and unused

In SoundPath's description, the last 2 "notes" have been removed. Compare with docs for v1.1.110

In FluidIdentification, ForceIdentification, TechnologyIdentification, "Identification" has been shortened to "ID", but not for SurfaceIdentification ...

Hi Bilka & co, it's me again!

This has now evolved into a random list of things I've noticed are inconsistent or problematic in the lua-api docs.
Title has been updated to latest version where all these issues are still confirmed.

The following concepts don't seem to be referenced anywhere else ...

Given a blueprint LuaItemStack, with blueprint_snap_to_grid=nil but blueprint_position_relative_to_grid set:
- With a small blueprint, no entities are visible, and trying to place it gives "cannot build out of map".
- With a very large blueprint, the game crashes. Attached are the logs of such a ...

According to https://github.com/libsdl-org/SDL/issues/9250, SDL2 seems to have been fixed this on their end, but Factorio needs to update.

So... can we has not tiny cursor on wayland please?

Since v1.1.108 (version 5), $ref($runtime, (name)) appears the documentation for LuaBootstrap::on_event and LuaBootstrap::raise_event, in the "examples".
These look like there were meant to be links instead.