WildBraas wrote: ↑

Sun May 15, 2022 7:06 pm

Now its possible using Factorio mod debug for Visual Code, with breakpoints and code analysis.

It's hardcoded into the plugin for each LuaObject type.

To reproduce: 1. Register the following custom input: { type = "custom-input", name = "rb-open-selected", key_sequence = "ALT + mouse-button-1", include_selected_prototype = true, } 2. In-game execute the following command: /c script.on_event('rb-open-selected', functio...

You can partially work around this by doing your stuff when the item proxy is destroyed.

Honktown wrote: ↑

Mon May 09, 2022 9:54 am

If an empty players table passed to LuaRendering draw functions means "everyone" not "nobody". It'd be convenient if that were noted somewhere.

It is, though maybe not where you'd expect: LuaRendering.set_players.

Can we get a description of what FluidBox#production_type is supposed to mean as opposed to PipeConnectionDefinition#type? Description for both, maybe?

Implemented in 1.1.58.

https://lua-api.factorio.com/latest/LuaEntity.html#LuaEntity.get_output_inventory wrote:Gets the entities output inventory if it has one.

entity's

-> Thanks, fixed.

https://lua-api.factorio.com/latest/LuaItemPrototype.html#LuaItemPrototype.module_effects wrote: Effects of this module; nil if this is not a module.
Can only be used if this is ModuleItem

So can it or can it not be used on other items?

-> Thanks, I decided to remove the redundant description text.

An item stack button would be helpful. Doesn't have to be sprite-button specifically.

I'm not so sure about hiding old versions. It can be useful for debugging mod interaction to know in what version a certain behaviour, feature, entity etc. has been introduced. Finding nothing about it because the game decided that version was too old and the entry should be hidden would make life ...

IMO, it was wrong to merge these topics. They suggest different and only loosely related things.

Anyway, I am here to support the "only new changes" suggestion. The game already does this on game update, it should be easy to add it for mods as well.

If you think it's a bug, report it in the correct forum, not write to modding API requests.

Types/StyleSpecification#effect need description, or at the very least a list of possible values.
-> The list of possible values is hardcoded to one value, severely limiting its usefulness. But it's documented now, thank you for pointing it out.

LuaItemStack.set_stack should say why it can fail.

-> Improved, thanks.

KiwiHawk wrote: ↑

Tue Mar 29, 2022 11:04 pm

Seems that this was missed from the changelog

A lot of Nexela's PRs didn't make it to the changelog, AFAICT.

Prototype/Turret#attack_parameters - the description is wrong. The vanilla gun turret exists without ammo_type, so obviously it's not required. You may want to say that specific turret subtypes require some parent fields to be a certain way, though IDK how you would present that. -> Thanks, fixed.

There is no "INI specification". The format is not standardized. You can request the support of quoted values, but requesting to follow the INI specification makes no sense. Alternatively, you can say "Crowdin's INI specification", since it sounds like Crowdin has a specific set ...

thesixthroc wrote: ↑

Fri Mar 18, 2022 9:07 pm

There is a subtle reason I haven't tried; I want to perform this action every tick, on multiplayer. Ne pas.

If you just want to get rid of the mapping of terrain, you can set map size to something very small and generate the actual map during runtime.

Nexela told me the other day that he PRed it.

You could always work around it. Use find_chart_tags to find all the tags in the area you want to clear and remember them, and after you cleared the chart you add_chart_tag them all back in. It's more complicated than that: Note The chunk must be charted for a tag to be valid at that location.