1.5 KiB
Forsaken Abbey population import
Forsaken Abbey gameplay never connects to Microsoft SQL Server. Both offline and online builds consume the checked-in Zone 102 snapshot, generated TypeScript, and creature GLBs.
Normal portable build
Run this after the snapshot and actor manifest have been created:
node scripts/runewaker-pipeline/build-forsaken-population.mjs
This command reads only project files. It transforms and navmesh-projects all 251 source rows, excludes Treasure Chest 100567 from combat, emits the static population and eight boss objectives, and writes an auditable import report.
Rebuild the nine static creature assets separately when the preserved ROS sources change:
node scripts/runewaker-pipeline/build-forsaken-population.mjs --actors-only
Explicit forensic refresh
Start the isolated development instance HEALERMAN_RW manually, then run:
node scripts/runewaker-pipeline/refresh-forsaken-population.mjs
The refresh command uses Windows integrated authentication. It temporarily
restores ROM_Global.bak and ObjectEdit.bak under HealerMan-specific
database names, marks both restored databases read-only, exports active Zone
102 rows, and drops both databases in a finally block. The backup files are
never modified. The normal build has no SQL or network dependency.
The source snapshot records SHA-256 hashes for both backups and the three
preserved object catalogs. RuneWaker identifiers are namespaced in generated
runtime ids and are never assigned to AzerothCore's serverEntry.