Thanks for the report, the issue is fixed for the next release.

Duplicate of 104354

Thanks for the report. The operation is a bitwise AND and works as intended. It performs logical AND on individual bits, so 10 and 1 (in decimal) = 1010 and 0001 (in binary) = 0000.

Thanks for the report. This is not a bug.

Thanks for the report. The issue is fixed for the next release.

This is not a bug. LuaItemStack doesn't know it is supposed to be temporary. I am moving it to modding interface requests. For the next release, I added LuaPlayer::cursor_stack_temporary (read/write boolean) which you can use to mark cursor stack as temporary. It works for blueprints, blueprint book...

Thanks for the report. This and other issues with fallback group parsing are fixed for the next release.

Merged similar topics. This is implemented for the next release as a "fallback group" format. The format picks the first correct parameter in a localised string. The key is always "?" and is ignored in the translation. If no parameters are correct, the last one is returned. {&qu...

Thanks for the report. The issue is fixed for the next release.

I can't reproduce this issue. Can you share more information (save file + video)?

Thanks for the report. I think this is intended. When you select new contents for an existing blueprint, the blueprint keeps its other properties, including grid values. Grid size can be changed manually and I don't think it should be reset just because you changed blueprint content. As for the gree...

Thanks for the report; however, this is not a bug.

Thanks for the report. The issue should be fixed for the next release.

This is not a bug. Modifier "character-additional-mining-categories" is not listed as a valid type for the prototype stage (the wiki docs). I am moving this topic to Modding interface requests. Currently the only way to change the value is at runtime using LuaControl::character_additional_...

Thanks for the report. I don't think this is worth fixing right now.

Klonan helped me to find the root cause: the value was reset when any prototype data changed. It is fixed for the next release.

Can you share more details about this issue (logs, save files, reproduction steps)? My guess is that the mod triggering it changes SpiderVehicle prototype but I don't have enough information to confirm this theory.

Thanks, it's fixed for the next release.

The issue is different from the linked duplicate (and was also reported internally). It is fixed for 1.2 major release. I merged the CLI and the GUI map preview, so their output is now consistent.

Hello, this seems to be a bug in one of your mods and not a Factorio bug. The mod disabled your driving permission. Type "/permissions" in chat and remove yourself from "driving-lock" group.