4.6 KiB
Mission-scoped faction catalogs
The successor's initial Everon vehicle scope is the finite depot UAZ469 ({259EE7B78C51B624}) and the extraction Mi8MT unarmed transport ({DF5CCB7C0FF049F4}). These are the only two vehicle prefabs authored in the current scene definitions. Both US and USSR receive the same two-entry vehicle catalog so a captured mission vehicle can still be looked up through either faction. This does not change the default affiliation, physical prefab, seats, damage, fuel, weapons or handling of either asset. It does not add vehicles or spawning orders.
The manager is the successor resource Prefabs/ERR/FactionManager.et (5414041A15DC4B54), inheriting only vanilla FactionManager_Base.et. It uses successor US (5C67A1DDE0044806) and USSR (D7A5CFA62A36480D) profiles and the successor MissionVehicles.conf (E4785D3AF1D043C2). No resource inherits vanilla US.conf, USSR.conf, FactionManager_USxUSSR.et or their full vehicle catalogs. This avoids initializing unneeded M151A2, BRDM2 and BTR70 catalog entries. It does not fix those installed vehicle schemas or establish those vehicles as compatible.
The faction profiles preserve all properties of installed vanilla US/USSR profiles except the vehicle-catalog reference. They derive directly from vanilla BLUFOR/OPFOR as the installed originals do. This preserves faction keys, enmity rules, soldier identities, voice settings, flags, ranks, callsigns, encryption keys, frequencies and home territories. The full CHARACTER, GROUP, WEAPONS_TRIPOD, ITEM and SUPPLY_CONTAINER_ITEM catalogs retain their original references. In particular no medical consumable, radio, weapon, ammunition, uniform, group or medical support item is removed by this change. Installed US/USSR supply-container catalogs are empty; their type remains available with that same empty content.
These are new successor resource identities authored using vanilla profiles and documented native catalog containers. No original Escapists code or resources are reused. Source extraction SHA-256 values are recorded in faction-catalog-source-hashes.json; extraction came from the locally installed stable Reforger PAKs. Tests also pin normalized profile contents to catch unintended changes outside the deliberate vehicle reference.
Validation and limitations
The candidate passed the full existing offline checker in /tmp/erri-faction-check, including three new catalog-scope tests. It has 27 unique addon resources and valid declared vanilla references. This does not compile Enforce, load configs natively, exercise vehicle physics or prove improved FPS. No engine was launched by the author of this candidate.
ERR_NativeFactionCatalogProbe.Run(mode) is a WORKBENCH-only, read-only assertion entry point. Invoke once after faction initialization and successful scene preparation, before the transport or extraction destructive tests. It verifies both factions' exact two-vehicle catalog contents and prefab lookups, all six catalog types, nonempty native content where appropriate, dressing/saline/backpack radio entries, global catalog-manager access, US/USSR identities and mutual enmity, radio encryption/frequencies, callsign data, physical UAZ/Mi8 and the helicopter's required seat capacity. It does not load old full faction resources as a comparison, because that would reintroduce their unwanted catalogs.
Parent integration should compile and run the complete Core/companion scenario for two rounds, with this probe before destructive tests and the unchanged raw-log parser afterward. The expected seven schema messages must actually disappear from raw startup logs for this scope change to help the clean-runtime gate. Any remaining errors, including intermittent support-station/catalog-manager teardown errors, continue to fail that gate. No log message or validation rule is suppressed or reclassified here.
Future vehicle support must add an intentional catalog entry and validate that asset's own native schema/handling, inventories and support behavior. Retaining complete inventory and group catalogs does not justify a claim that every original gameplay feature or remote multiplayer path is covered.
Native evidence
063559 completed 67 combined environment/catalog assertions with no script/VM failures and no engine errors. Exact native catalogs retained medical and radio entries; all three weather families and a leap date applied without resetting the clock. Defaults and next-round settings behavior were exercised. This one-round development result does not establish multiplayer replication or repeated-restart reliability.