[2.0.55] Tips and Tricks: Entity pipette scenario crash

[Tumby]

What did I do?

Play the game in any mode. Enter the "Tips and Tricks" menu. Click on "Entity pipette". (With everything unlocked, it is the 4th item in the list.) Finally, watch the scenario play out.

What happened?

After roughly 11 seconds, the scenario crashes. (The game continues to work just fine. I can even rewatch the scenario crash.) The scenario screen gets replaced with the following text:

Code: Select all

The scenario level caused a non-recoverable error.
Please report this error to the scenario author.

Error while running event level::on_tick (ID 0)
[string "    require("__core__/lualib/story")..."]:146: attempt to index local 'belt' (a nil value)
stack traceback:
[string "    require("__core__/lualib/story")..."]:146: in function 'action'
__core__/lualib/story.lua:111: in function 'story_update'
__core__/lualib/story.lua:10: in function <__core__/lualib/story.lua:8>

I hope I copied the text correctly, as there is no way to simply select it and press Ctrl+C.

What did you expect to happen instead?

I expect the scenario to not get replaced by an error message.

Also, it appears that the scenario tries to create ghosts of burner inserters and transport belts, but fails to do either:

• It middle-clicks the burner inserter in the hot bar, but ends up removing burner inserters from the hot bar instead of adding burner inserter ghosts to the cursor. Then the mouse moves to two spots where burner inserter ghosts would fit in perfectly, but as the cursor is not holding anything, not even ghosts, nothing happens.
• Similarly, it middle-clicks transport belts in the crafting menu, which does nothing. It then tries to place a line of transport belt ghosts, but nothing gets placed at all, since again, there are no items or ghosts in the cursor.

Does it happen always, once, or sometimes?

Happens every time. With and without mods. With and without Space Age enabled. Any game mode. (Freeplay, Tutorial, Supply challenge...)

[boskid]

Thanks for the report. I am considering this to be a duplicate of 116465 as you have modified bindings. In this case having pipette on middle click causes ambiguity on the quickbar because usually middle click is used for clearing filter and you have it bound to pipette, script tries to do pipette and clears quickbar slot instead. Saying it differently: this tip "correctly" crashes because with your current bindings, what the tip suggests being possible is not possible (you cannot pipette quickbar using middle mouse).

[Tumby]

Thanks for the report. I am considering this to be a duplicate of 116465 as you have modified bindings. In this case having pipette on middle click causes ambiguity on the quickbar because usually middle click is used for clearing filter and you have it bound to pipette, script tries to do pipette and clears quickbar slot instead. Saying it differently: this tip "correctly" crashes because with your current bindings, what the tip suggests being possible is not possible (you cannot pipette quickbar using middle mouse).

Would it be possible for the game to detect such key bind conflicts and perhaps display a message? Maybe something like this: "The shown demonstration may be incorrect or incomplete. Your custom controls make some game features inaccessible."

Also, what about middle-clicking transport belts in the crafting menu? What's the conflict there?