Razi Protocol 3.0


A giant Space Age modpack bridge that connects many planet, science, enemy, and endgame mods into one coherent progression route across multiple star systems. Please view the mod page for the full overview and explanations.

Mod packs
4 days ago
2.0 - 2.1
5.28K
Factorio: Space Age Icon Space Age Mod
Planets Logistics Combat Enemies Environment Logistic network Circuit network Manufacturing

b [FIXED] Crash at load: Unknown entity name: vaterite (Paracelsin 1.13.0 + Nexus 1.4.0)

6 days ago

Factorio 2.1.24, razi-protocol 3.1.3
All 65 required dependencies installed.

Error:
Error while running setup for space-location prototype "paracelsin" (planet): Unknown entity name: vaterite

Cause:
Nexus 1.4.0's compatibility/paracelsin/planet_paracelsin_compatibility.lua
registers an autoplace-control for "vaterite" during data.lua, but
Paracelsin 1.13.0 defines the vaterite resource in
prototypes/resources.lua, which it requires AFTER prototypes/planet.lua.

So the autoplace-control references an entity that does not exist yet.

Workaround: load order fix in Nexus, or move the vaterite definition earlier in
Paracelsin's data.lua.

6 days ago

Correction — my first diagnosis was wrong, please ignore it.

Paracelsin 1.13.0 does not define the vaterite resource at all. Comparing the
two versions:

Paracelsin 1.11.6:
- items.lua:131 type = "item", name = "vaterite"
- resources.lua:141 type = "resource", name = "vaterite"
- planet.lua:28 type = "autoplace-control", name = "vaterite"

Paracelsin 1.13.0:
- only item references remain
- type = "resource" and type = "autoplace-control" are gone

Crystalline-Library 1.0.0 (the mod that received the moved prototypes)
defines only the item — no resource, no autoplace-control.

Nexus 1.4.0's compatibility/paracelsin/planet_paracelsin_compatibility.lua
still registers autoplace-control "vaterite" and lists it under
autoplace_settings.entity.settings, so prototype setup fails.

I am reporting this to Paracelsin / Crystalline-Library instead.
Sorry for the noise.

6 days ago

Fixed, thanks for the report!

New response