Linux server side issue.
Error while running event kry-logistics-reactor-next::on_init()
LuaPlayer doesn't contain key player_index.
stack traceback:
[C]: in function 'index'
__kry-logistics-reactor-next/scripts/reactor-storage.lua:244: in function 'handler'
kry_stdlib/stdlib/event/event.lua:341: in function 'pcall'
kry_stdlib/stdlib/event/event.lua:361: in function 'dispatch_event'
kry_stdlib/stdlib/event/event.lua:437: in function 'dispatch'
kry_stdlib/stdlib/event/event.lua:77: in function <kry_stdlib/stdlib/event/event.lua:76>"

Can load that save at Windows client.

Interesting, not used to Linux, but is it running in some kind of headless mode (i.e. no attached player when loading the save)?

The startup script relies on the locale of the player loading the game, in order to create unique named request categories for each type of logistic reactor, with the default requests filtered to the allowed fuel types (otherwise the default would be unnamed/empty slots). I don't believe there's any other way to get the localized name of the reactors, since it relies on the player's locale, and using the internal name of the reactor for the request categories doesn't look as good (using a default for all reactors also doesn't work, since they each have different allowed fuel types)

I'll see if I can add a startup setting to change this behavior though, default/empty request filter is probably preferable.

Okay, I can't test this since I don't have a linux install ready, but should theoretically be fixed in v7.1.1

I side-stepped the localization issue entirely and just use the item icon of the logistic reactors in place of their names. This should be platform-agnostic and should not require a player to host (also isn't subject to multiplayer localization issues)

Interesting, not used to Linux, but is it running in some kind of headless mode (i.e. no attached player when loading the save)?

The startup script relies on the locale of the player loading the game, in order to create unique named request categories for each type of logistic reactor, with the default requests filtered to the allowed fuel types (otherwise the default would be unnamed/empty slots). I don't believe there's any other way to get the localized name of the reactors, since it relies on the player's locale, and using the internal name of the reactor for the request categories doesn't look as good (using a default for all reactors also doesn't work, since they each have different allowed fuel types)

I'll see if I can add a startup setting to change this behavior though, default/empty request filter is probably preferable.

Yes, headless server.