EscapistsReintroduced/docs/nogova-publishing.md

Publish Escape on Nogova

Server-owner setup (no connector)

Publish the updated Co10 Escape Reintroduced core. Server owners add Escape and Nogova Reforger to their mods and select Nogova's exploration scenario:

{469880DFE1B48F95}Missions/Nogova_TerrainTest.conf

Escape automatically takes over. There are no required custom header fields, AMP settings, airport coordinates or changes to Nogova. When no physical airport is detected it surveys a clear helicopter landing zone. See automatic terrain takeover for requirements and test scope. Do not remove a connector while the server still selects its ERR_nogova.conf header; switch to the existing Nogova scenario first.

Optional authored integration

The remaining instructions describe the older authored integration inside Nogova. Use these only when deliberately providing a separate Escape scenario.

1. Publish the updated Co10 Escape Reintroduced core containing Prefabs/ERR/TerrainConnector.et and the terrain-independent runtime. The connector resource is {8FB1559AE3F29722}Prefabs/ERR/TerrainConnector.et.
2. Copy the contents of terrain-integrations/nogova/Missions/ and Worlds/ into the corresponding folders in your Nogova project. Include the .meta files and Worlds/ERR_nogova_Layers/ directory. Merge folders; do not replace Nogova's existing files. No root terrain or navigation file is overwritten.
3. Add "2528466DE220D91C" to Nogova's addon.gproj Dependencies block in Workbench. Preserve its existing dependencies. This makes Escape a required dependency of Nogova for all its scenarios; use the optional approach below if you want the terrain to remain independent of Escape.
4. Publish Nogova Reforger, including its configured AI world and native navmeshes. The Escape scenario inherits that navigation.
5. Update Escape and Nogova on RKS 2 and keep the mission-header resource below in AMP's Scenario ID setting. Remove the optional Escape–Nogova addon from the enabled mods if previously installed, to avoid duplicate resources. Start the server after downloads complete.

{681921DC9921F915}Missions/ERR_nogova.conf

Equivalent server config property, inside the existing game object:

"scenarioId": "{681921DC9921F915}Missions/ERR_nogova.conf"

For this authored route, use ERR_nogova.conf. The automatic route above uses Nogova’s exploration scenario. Neither route accepts Worlds/Nogova/Nogova.ent as a mission header. The scenario subscene references the shared Escape connector and supplies a mainland airport-centre marker at [1525, 0, 5075]. The aircraft is placed only after actual terrain, navigation, clearance and physical-settling checks.

The native local Nogova test placed 16 sites and spawned a soldier after preparation. Ten hill scouts were ready and the extraction helicopter was supported and fueled. Known resource/schema engine diagnostics remain in the raw log; the test is not clean-release, multiplayer or full-escape qualification. See evidence/nogova-2026-09-30-startup/report.json.

The October 1 universal connector also completed local startup on Nogova and Everon: 16 sites and a player soldier on each, with zero script errors. Both runs retain 13 resource/schema engine errors; dedicated multiplayer remains untested. See evidence/universal-connector-2026-10-01/ for the logs and source hashes.

Optional separate scenario addon

If you do not want Nogova itself to depend on Escape, keep the small scenario in terrain-adapters/nogova/addon.gproj (GUID 26C8E5E5AC063B1A). This project now references the very same universal connector. Publish it after the updated core, then enable it alongside Escape and Nogova on RKS 2. Use the same scenario ID. Do not use this project and the embedded scenario simultaneously.

Publication, terrain-source edits and RKS 2 changes are left to the owner as requested. Only the export files in this repository have been prepared.

The September 30 version, before the universal-prefab refactor, also passed a native adapter package build. Its PAK contains the mission header and its resource database contains the expected scenario GUID. See evidence/nogova-2026-09-30-package/report.json. Source and native candidate ZIPs are in .build/nogova-publish/; these older ZIPs do not contain the October 1 universal connector changes. Use the current source files described above.