20188.319 Error MainLoop.cpp:1456: Exception at tick 12840214: The mod ○🌐Planet Rubia (0.69.120) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event rubia::on_player_banned (ID 130)
rubia/script/chunk-checker.lua:367: bad argument #2 of 2 to 'get_player' (string expected, got nil)
stack traceback:
[C]: in function 'get_player'
rubia/script/chunk-checker.lua:367: in function 'fun'
rubia/lib/event-lib.lua:82: in function <rubia/lib/event-lib.lua:81>
20188.319 Error ServerMultiplayerManager.cpp:84: MultiplayerManager failed: "The mod ○🌐Planet Rubia (0.69.120) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event rubia::on_player_banned (ID 130)
rubia/script/chunk-checker.lua:367: bad argument #2 of 2 to 'get_player' (string expected, got nil)
stack traceback:
[C]: in function 'get_player'
rubia/script/chunk-checker.lua:367: in function 'fun'
rubia/lib/event-lib.lua:82: in function <rubia/lib/event-lib.lua:81>"

Thanks for the report. My deepest apologies. I believe this will be an easy fix. I will look into this.

I did not test this because my gaming rig makes it very difficult to test multiplayer properly. I will put out a fix in the upcoming days. Please let me know if you have any issues after that.

Thank you. I guess that is caused by banning a player that does not exist (by name typo)

Ohhh, you made a typo when banning a player? That is very interesting, and may lead to an engine bug, maybe. I can still fix my logic (so the game does not crash obviously). The main thing that will slow me down is that my current dev build of Rubia has changes for compat with several mods. So it will take me a hot minute to actually get out a fix.

If you can successfully ban the guy and keep playing, I have more breathing room to make fixes with more testing.

Yeah, I have successfully removed that guy. I mean, (I am not a factorio modder and I dont know much about LUA, following is just my guess), from the error message
"get_player' (string expected, got nil)"
I would assume that your function listens to engine's ban event and expects the player's name from the engine but if the player does not exist(my typo leads to a non-exist player name) then the engine will return you a nil instead, which would crash your code.

When I tried to ban the guy with the correct name later, everything went well.

That is exactly the issue. I did not expect the engine to raise an event notifying me that nil player was banned.

Fixed in v0.69.122