Rigor Module


New type of module: Rigor modules. Rigor modules increase the probability of a recipe returning its most valuable product.

Content
a day ago
2.0 - 2.1
27.8K
Manufacturing

b Map load hangs at "Checking consistency" after updating to 1.1.22 (old saves, migration 1_0_0.lua)

a month ago

Factorio 2.1.24 (build 87808, linux64, steam, Space Age).
Rigor Module 1.1.22 (released 2026-11-03).

After updating Rigor Module to 1.1.22, loading a save made with the
previous version hangs forever on the "Checking consistency" screen.
One Factorio thread spins at ~100% CPU for many minutes (a debugger
attach shows it stuck inside the game's collides function), the log
stops progressing, and the system eventually runs out of memory.

The hang happens right after the mod's migration runs. Log of a hung
load:

43.292 Loading map /home/gevorg/.factorio/saves/KRASTORIO_SPACE_AGE_2.2.zip: 53366088 bytes.
43.309 Loading level.dat: 176254433 bytes.
43.309 Info Scenario.cpp:152: Map version 2.1.24-1
45.363 Loading blueprint storage: Local timestamp -1, Cloud timestamp 1792959384
46.631 Loading script.dat: 7368495 bytes.
46.910 Applying migration: Rigor Module: 1_0_0.lua
48.794 Script @__PlanetsLib__/scripts/unreachable-techs.lua:69: PlanetsLib: [technology=aai-hyper-loader] due to hidden prerequisite 'planetaris-hyper-transport-belt'

(log ends here — nothing further is ever written, the load never
finishes; a second run froze at the same point with the same
"Applying migration: Rigor Module: 1_0_0.lua" as the last mod line)

Reproduction:
1. Save made on 2026-10-31 with an older Rigor Module version
(heavily modded map: Krastorio2 + about 25 planet mods).
2. Update Rigor Module to 1.1.22 and load that save.
3. The load hangs at "Checking consistency" every time (reproduced
in two consecutive runs).

With Rigor Module removed (the rest of the mod set unchanged), the
same save loads normally. So it looks like the 1_0_0.lua migration or
the 1.1.22 prototype/script changes are incompatible with maps made
by the old version.

a month ago
(updated a month ago)

I don't think it's the migration itself, which doesn't do that much; I believe migrations are just the last things to run before the "checking consistency" step.

Some questions for further details:

  • What was the previous Rigor Module version (was it still Factorio 2.1)?
  • Did any other mods get updated too?
  • Can you try again with the -v launch option (for extra logging)?
  • How big is the save file?

If the save was already on 2.1, the migration should not run just from updating the mod. And if Factorio is really stuck in an internal function (and not a Lua function), this is probably a Factorio bug. Even though Rigor Module seems somehow to be responsible, the game engine is supposed to throw better errors when mods mess something up lol.

a month ago

Can you also share your save file so I can try to reproduce it?

New response