This hapoens if a mod changes the attributes of the beacon interface to be invalid during startup.
Does the machine upgrades mod change the beacons?
I am having the same problem with the modules everywhere mod.
__beacon-interface__/control.lua:63: {
allowed_module_categories = {
["beacon-interface--module-category"] = true,
efficiency = true,
productivity = true,
quality = true,
speed = true
},
history = {
changed = {
"module_everywhere_beacon_config"
},
created = "beacon-interface"
}
}
stack traceback:
[C]: in function'assert'
__beacon-interface__/control.lua:63 in main chunk
And this is the relevant assert from the control.lua
assert(#on_created_entity_filters > 0, serpent.block({
history = prototypes.get_history("beacon", mod_prefix .. "beacon"),
allowed_module_categories = prototypes.entity[mod_prefix .. "beacon"].allowed_module_categories,
}))