- rig the game to be able to write map ticks (or leave a server running without auto pause for 2 weeks)
- start a new world
- /cheat all
- hold a roboport ghost
- /c game.ticks = 40000000 -- (40 million), this is when it becomes noticable
- observe the ghost skipping some frames
- /c game.ticks ...

It is going out of bounds several times, the artifacts of which can be seen ingame in the corners, see the pics:

- install the mod
- create new world
- /cheat all
- grab washbox from the power poles and pipes category
- place one
- connect infinity pipe with water on the input side
- notice the water is not flowing in

see the comments in data.lua around line 40, the furnace just refuses to take in any liquid ...

When you have an item/ghost of something like an accumulator and you build in a line by holding down the place button and moving the cursor it gets placed as soon as the preview of it renders in the correct spot, but when you create a blueprint of a single accumulator it doesn't place until your ...

- host new game (other players not required)
- type `[item=iron-plate]` in the chat
- click on it
- notice factoriopedia opened
- open remote view
- click on it (clicking and then dragging keeps it open)
- notice factoriopedia blinked

- spin up two instances of the game, one for the host and one for the client
- host a new multiplayer game (optional: set some minimal latency)
- join it with the client
- have either player run /c game.player.character.cheat_mode = true
- craft some iron/copper to trigger the first two trigger ...

https://lua-api.factorio.com/latest/prototypes/AssemblingMachinePrototype.html#fluid_boxes_off_when_no_fluid_recipe
https://discord.com/channels/139677590393716737/1217401074877599745/1382287164452376626

It currently has no description at all, and based on observation and the above conversation ...

Typically the "Can only be used if this is X" error when you call it from the wrong type, this one returns nil then.

Ideally that notice gets edited, or the api call crashes if its not a logistics or infinity container, also dropping the optional return.

The methods to set the slot filters and the bar exist on the inventory, but while the container is a ghost it is nil and thus inaccessible.

https://lua-api.factorio.com/latest/types/LightningProperties.html#exemption_rules

if you set/keep them at nil the game loads up just fine, this leads modders into a false sense of security that they don't have to check if the array exists first.

so it would be nice if they were both marked as ...

The installed tab shows it localized, whilst the updates tab shows the raw mod name. (the two planet ones are sticking out like a sore thumb)

When GuiAnchor was implemented ghost guis weren't a thing yet.

When you use name or names as a filter it'll stop appearing on ghosts even if they share the name, which would require the player to just listen to the gui opened event of that gui type in general and then manually toggling it, which is ...

Currently it only remembers it if its the latest played world, i.e. the one shown on the big green button on the menu screen.

Whilst playing online i have to occasionally drop into a local save or just save the server's world to test some stuff, and each time you return you'd have to re-enter the ...

- try to open a world
- open the sync and load mods gui
- press the sync button
- uncheck the "load save after sync"
- wait for all the green bars are full
- notice the game restarting and then loading the world

expected behavior: for the checkboxes to either still "work" after clicking the sync ...

Forwarding this here since it got confirmed as a bug, and so i can link to this issue from the elevated pipes mod.

+1

It currently has no description, it would be nice if it was documented that this is what controls which entities can freeze or not.
https://lua-api.factorio.com/latest/pro ... ing_energy
https://discord.com/channels/1396775903 ... 7697374328

isn't the difference generally that one is integer and the other one decimal?

TL;DR
It would be nice if recipes that are disabled due to lack of fluid connections say so in their tooltip, just like recipes restricted by surface conditions.

What?
Something like "Cannot be crafted in this machine. There are not enough fluid ports.", but a little bit more snappy than that ...

Wow that's quite out of sight near the bottom and in a normal font, not used to read the on_load documentation since i know what the event is for, it might be worth moving it to a more visible spot, like right below the lifecycle diagram in a noticable color