At most what i could make is a quality_behavior on item product prototype with 3 options: "default" (for current behavior), "no_bump" for product not affected by quality but preserving input quality, and "set_normal" that would always give normal quality product regardless of ingredients quality ...

It seems like a good idea to better differentiate fluids, especially in big mods, and it would make sense to also add that to lava and molten metals in space age. +1

I will add that draw_sprite also doesn't show render_mode field

What is your usecase for reading these values?


Modifying the various gui properties in-game as a tool for modders, as i've seen many people having trouble making GUIs. While modifying element properties and copying element styles and style properties work, for modifying the style properties ...

To show the problem, these are all the properties: This is what mods see:

prototypes.style only allows accessing the type of the style, which isn't very useful. LuaStyle returns nil when reading "default" properties, ones that have not been overwritten. This means that to read the actual properties of styles, using ModData is needed, which comes with all of its flaws ...

https://lua-api.factorio.com/latest/pro ... _oil_ocean says indexed by "allow_on_deep_oil_ocean", however it seems to actually be indexed by "rail-ramp/allow_on_deep_oil_ocean"

Though when the train is going fast they still look bad, hmm. It's like I'm setting the position for the last draw, so it's always lagging behind.

Even the rotation is wrong, hmm. It's like I'm getting the data at the start of the frame, applying that, then the train's update is handled, moving ...

Only it drifts off centre on corners compared to the normal way, as well as the rotation not being quite right (seems to be using the angle between the front/rear wheels, when a wagon is actually floatier than that).

Any tips?


That's because due to the game's apparent camera angle, the actual ...

You can use LuaRendering to draw stuff in a way thay it looks like a part of the wagon. But it is kind of complex, and swapping the wagon to a different one may be better. Or just not modifying graphics at all if its not strictly necessary

The docs say it returns a single DeciderCombinatorCondition, however in reality it returns a table with an array of DeciderCombinatorConditions and an array of DeciderCombinatorOutputs:

In certain languages, for example in russian, the button causes the whole GUI to stretch.
Expected behaviour would be for the button to be squashed, like on character logistics GUI:

+1, special pumps for special wagons opens quite a few possibilities

https://github.com/wube/factorio-data/b ... lua#L10185
Base game uses it, but there is no mention of it on the docs anywhere.

There is no stat for robot energy usage, it's (gravity/pressure) * 100

What?
Ability to access the agui flow's style properties that is created as an element inside every frame. Doesn't need to be a LuaStyle, just margin and padding would cover most of the cases.

Why?
When LuaGuiElement of type frame is created, a child agui flow is created which is used to ...

I'm working on a mod that allows editing Gui Elements in-game, and all of the properties which can be set on the elements can then be read back in some way.
Except for the icon_selector, which can be set on textboxes and textfields, but there is no way for a script to read whether it is set.
Read ...

If a mod invalidates the state of an event, and doing that

the mod resets the schedule of the train wihin the event handler.

probably does invalidate it, the event does not propagate further. That is intended.

The custom input event is defined like this:
{
type = "custom-input",
name = "right-click",
key_sequence = "mouse-button-2",
action = "lua",
}
And i react to it like this:
script.on_event("right-click", function(event)
game.print(event.element)
end)
When clicking "in-world" (in-game and in ...

Also document that multioctave_noise uses the same algorithm as basis_noise but allows for having multiple layers of it with different scales, to make it clear that it also has the same issue. And remove the example with no input_scale from it too as it effectively removes the first layer.