A user of my mod Logistics Insights posted a bug report that actually is a bug in Time Control Fork.
As far as I can tell, it's caused by Logistics Insights changing a global mod setting during startup (migration), and Time Control Fork assumes that the settings being changed are per-player ones. To reproduce: Have a save with LI v0.9.12 and TCF, then upgrade to the latest version of LI and reload.
Here is the crash report:
The mod Logistics Insights (0.10.6) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event logistics-insights::on_configuration_changed
The mod Time Control Fork (2.0.45) caused a non-recoverable error.
Please report this error to the mod author.
Error while running event TimeControlFork::on_runtime_mod_setting_changed (ID 67)
TimeControlFork/control.lua:25: bad argument #3 of 3 to 'index' (string expected, got nil)
stack traceback:
[C]: in function '__index'
__TimeControlFork/control.lua:25: in function 'update_gui'
TimeControlFork/control.lua:103: in function <TimeControlFork/control.lua:99>
stack traceback:
[C]: in function 'newindex'
__logistics-insights/scripts/migrations.lua:176: in function 'func'
flib/migration.lua:70: in function 'run'
flib/migration.lua:97: in function 'on_config_changed'
logistics-insights/control.lua:315: in function <logistics-insights/control.lua:311>
