Screenshot taken by /screenshot command and by os; display panel text is not shown. Assembler included to show it's not somehow turning off alt mode.

Steps to reproduce: hover over a roboport and run /c game.player.selected.active=false
Result: nothing happens. Reading back the state with /c game.player.print(tostring(game.player.selected.active)) shows it is still true.
Expected: doing the same thing to, for example, an assembling machine ...

If you press q while hovering over a blueprint, it should put that blueprint on your cursor.

The expanded pipette support in 2.0, remote mode, etc encourages you to just use q everywhere without stopping to consider whether clicking on it to pick it up (like a normal inventory item) would make ...

Switching to yellow belts and letting it get backed up did nothing. As you can see in the original image, the inserters not stuck like this have no problem grabbing the items. Manually adding fuel to a stuck inserter fixes it immediately.

Out of fuel despite holding a burnable item and items passing by on the belt. Progressively more inserters get stuck like this the longer it runs.

A stationary roboport (not a second tank) with construction bots will work if you ghost-deconstruct the bots inside the tank in addition to the ghost request, but... that won't help you get the construction bots into that roboport in the first place if it doesn't have any (such as if you just built ...

In a remote driven tank, which has plenty of construction bots and some other item (say, belts) in its inventory, and which is out of range of any roboports but its own, place a chest next to the tank and inside the chest make a ghost request for a stack of construction bots and a stack of belts ...

If you place a blueprint containing an assembler that is set to build an unresearched item, it will allow the assembler to be placed, you can open the assembler and mouseover the recipe etc, but with a circle and slash over it to indicate that it won't start actually building that item yet. I want ...

This was also useful for indicating which item should go on which lane of a belt. Not respecting the order is a solid loss of functionality.

Prior to the 2.0 release, I would periodically convert my main save to a scenario and start a "new" game from that scenario, as a method of keeping replay recording going after changing mods. Trying to load that save in 2.0 gives the error


Error while running event level::on_configuration_changed ...