More Infinite Research


Productivity for intermediates, science packs, final products, spoilage rate, and modded recipes. Bonuses for player stats, robot specs, weapon speed, stack size, cargo landing pads, and more... Override game limits on productivity, efficiency, speed, quality, and recycling. Settings to disable, limit, and rebalance each added research. Designed for vanilla, Space Age, and overhaul mods.

Tweaks
5 hours ago
0.13 - 2.1
8.03K
Logistics Trains Combat Character Mining Fluids Logistic network Manufacturing Cheats

g Error when launching

a day ago

The mod More Infinite Research (5.0.21014) caused a non-recoverable error.
Please report this error to the mod author.

Error while running event more-infinite-research::on_configuration_changed
more-infinite-research/runtime/worker_robot_storage.lua:739: MIR worker storage history: older default source requires its qualified Base engine and unchanged settings; keep the protected original COPY. Load a separate copy with the previous mod selection and matching MIR settings. Only if that copy has MIR-owned default infinite worker4, run /mir-worker-storage-recovery prepare, then save and exit. Other prior routes require their own verified history; this command cannot infer it; restore the previous mod selection and original save [MIR-WORKER-HISTORY technology=unobserved]
stack traceback:
[C]: in function 'error'
more-infinite-research/runtime/worker_robot_storage.lua:8: in function 'refuse'
more-infinite-research/runtime/worker_robot_storage.lua:234: in function 'recover_error'
more-infinite-research/runtime/worker_robot_storage.lua:739: in function <more-infinite-research/runtime/worker_robot_storage.lua:734>
(...tail calls...)
more-infinite-research/runtime/worker_robot_storage.lua:1008: in function <more-infinite-research/runtime/worker_robot_storage.lua:1003>
(...tail calls...)
more-infinite-research/runtime/bootstrap.lua:376: in function <more-infinite-research/runtime/bootstrap.lua:370>

Now I got this error without any config actually changing

6 hours ago

I am pretty sure this is already being worked on. Creator of the mod responded to (very closely) the same issue I had not so long ago after .21014 update.

New response