Crash AnalysisThe official Space Age expansion pack fails to initialize during the prototype registration phase. Specifically, downstream core systems—including advanced planetary logistics and space platform material processing—expect the prototype tree for technologies like "tree-seeding" to safely inherit and bind their standard requirements.When a third-party mod (bio-oil) unexpectedly executes a hard-coded database override during the earlier loading stages, it completely purges the root "carbon-fiber" technology key from the global registry.Consequently, the expansion's data-final-fixes compiler attempts to reference a non-existent prototype string. The engine's internal assignID handler is unable to generate a valid object index for the missing prerequisite, forcing a defensive hard lock to prevent save state corruption. Rather than neutralizing the rogue third-party script, the engine's automatic error handler defaults to prompting the user to disable the official space-age DLC itself.
Proposed Solutions & Feature Requests for WubeTo permanently immunize the Factorio 2.0 / Space Age data lifecycle against catastrophic data overrides from third-party scripts, we propose two structural architectural safeguards inspired by proven community compatibility patterns:1. Native Cycle-Break & Asset Protection LogicWe can look at community workarounds for structural inspiration—specifically the architecture found in omniab-space-age-compat (version 1.3.2), which successfully implements an internal cycle-break logic. It dynamically scans the property tree during loading phases and automatically removes unsafe prerequisites from downstream processing technologies when they would create recursive Space Age chains [z1].Engine Integration: The data-final-fixes compiler should incorporate a native cycle-break validation pass to intercept recursive dependency chains created by external mods, automatically severing invalid loop points instead of shutting down the entire game to desktop with an unrecoverable hard lock.Asset Ownership Rules: The engine must enforce strict asset protection. Baseline extension nodes or core planetary resources tied to active Space Age expansion mechanics should only be mutated or modified by downstream scripts, never completely purged from the global data.raw table.2. Dependency and Load-Order Protection PassAlternatively, Wube should adapt broader suite management mechanisms similar to the load-order and dependency targeting updates implemented in community frameworks (e.g., version 0.3.0 changes for large suite families).Strict Load-Order Validation: The engine should establish strict, immutable loading and execution priorities for expansion-critical technologies. No minor downstream mod should have the structural permission to alter core database slots before checking compliance with global DLC prerequisites.Automated Conflict Quarantine: If a minor utility attempts an unsafe deletion that conflicts with global expansion dependencies, the internal Error Handler must be smart enough to protect the official DLC. It should automatically catch the faulty mod (bio-oil), place it in quarantine/disable it, and allow the core game and official space-age DLC to boot up safely, rather than crashing the whole pipeline.Let the engine natively protect the official expansion from rogue LUA data overrides by enforcing automated structure and compliance checks!Thank you for looking into this trace, logs and full mod pack layouts are fully documented and available if needed! 
- 06-04-2026, 10-16-39.png (82.62 KiB) Viewed 92 times
