Whole-roster batch audit

Applied together

Worker variants2022 and2025: levels3/4→2, affecting nine spawn points. Queen2108: dedicated spell list3760 with Fire Beetle Spit1009. New script-only fire hatchling2000913: three or four spawn at the queen’s actual death position; idle hatchlings expire after30seconds and engaged ones are retained. Five database rows passed rollback rehearsal and full-row readback. Two new quest scripts passed977 assertions.

The worker level correction follows the explicit March2010 P99 patch, with a February2011 level-two observation; the uncited wiki2–3 range remains a conflicting reference. The May2010 patch documents the queen’s fire proc.

Not accepted: exact hatchling size/stats, proc frequency, full live death/combat/despawn behavior, queen spawn placement/timer and worker HP/damage. Hatchling2000913 currently reuses the local level-two fire-beetle baseline at size1; proc parameter3 is the engine default, not a measured P99 rate. These defaults are disclosed, not scored as historical parity. New script-only2000913 is not included in the150 spawnentry-referenced NPC count.

Missing-from-North correction: Umvera Dekash

The June15,2012 P99 patch explicitly returns Umvera from South to Crow’s bar in North. Spawn10688 was moved to the documented(y36,x364) location. Original terrain confirms floor0; existing body-centerZ3.75 and heading3 were retained. Exact historical facing remains unverified.

His original quest was copied byte-for-byte into North. Both hand-in branches, rewards, dialogue and wrong-item returns passed script regression tests. The guarded two-row migration preserved all NPC statistics/timers and backed up only the old noncorpse South cache record before removing it to avoid a duplicate. No player corpses were removed. Both cities were unloaded during this placement change; no occupied zone was interrupted.

Live acceptance passed: normal native player entered the tavern through its door, found the visible Umvera model in the lower room, selected him and received his named hail response. Inspected screenshot and scope. Exact appearance/facing, historical timer and complete quest acceptance remain open.

Reverse-reference review also found misleading wiki categories: Runethar belongs in South; Terago’s page names Toxxulia; Ulia’s page names West Freeport. Those were not blindly copied into North. Guard Sylus is associated with the later badge chain; Priest of Order is documented as a P99-specific support addition. Beggar/zombie/sewer-rat placements and generic bat mappings remain unresolved. The two snake names have since been corrected below.

North-specific database repair: snake names

NPC2003 and2101 changed from grass/gopher snake to a snake, following the official February10,2019 P99 patch. Fourteen existing spawn points retain their coordinates, grids, chances and timers. Stats, loot and factions were not changed.

Rollback rehearsal and full-row/dependency readback passed.175 local/global quest scripts were checked for name-sensitive behavior. The fresh roster has109 eligible types with NPC references and16 requiring separate handling, down from18. No other zone or client code changed.

Native name display verified: after normal QA logout and a confirmed empty-zone refresh, the native player walked from the Temple bank through city streets into the field. A nearby level1 snake was accepted by the server as the target; its name and indifferent con display correctly. Health remained full. Earlier distant target attempts were rejected and not counted. This verifies a live name/UI case, not both definitions individually, all14spawns, exact models, combat or loot. Overall coverage remains52%.

Inspected native target-name screenshot

North-specific quest repair: courier faction rewards

Installed changes affect only the North Qeynos quest scripts for Jracol Brestiage, Knargon Lanenda and Zannsin Resdinet. No renderer, animation, terrain, shared client code or Highpass script changed.

The August 2016 P99 developer correction explicitly covers Rogue Errands faction rewards. Its linked reference contains a November 2015 firsthand transaction log for these three hand-ins, including the final reward; numeric values were checked against that dated log, not just the modern page summary.

Original scripts fail the exact-value regression; the initial faction-only batch passed 702 assertions across all four trade slots, wrong and extra items, repeated submissions and the actual installed item/faction adapters. C++ hand-in persistence is modeled in these tests: this is not live hand-in proof. That initial batch preserved item rewards, XP, dialogue and conditions; the separate Jracol follow-up below changes dialogue handling. Backups and exact-hash guards protected deployment after confirming North was empty and unloading only that zone.

Live acquisition verified: ordinary native travel through Crow’s tavern and underground passages reached Knargon. The server confirmed his target and apprehensive con. Hail and shipment dialogue delivered one Bent Playing Card; database readback then confirmed normal storage of that card, preservation of all existing items, unchanged faction/XP and full health. No quest-item fixture, forced NPC or coordinate edit. Inspected live dialogue and card-delivery screenshot.

Installed follow-up: Jracol’s shared dialogue flag removed

Regression tests reproduced a script defect: another speaker could reset or arm a player’s hand-in, and the item check ran before that shared flag. Jracol now processes cards independently of other speakers, requires indifferent-or-better standing for rewards, and has his missing success response restored. Item, XP and corrected faction reward amounts are unchanged. The initial installed follow-up passed 867 assertions, including no-speech and repeated hand-ins, interleaved speakers and all nine faction ranks; these cases remain in the expanded suite below.

The P99 firsthand quest account supports the standing boundary and unsuccessful low-faction card consumption. Dialogue independence is inferred from the explicit historical no-conversation account in the linked quest reference and the 2011 P99 repeated-card workflow; it is not a newly measured P99 server trace. This single-script follow-up was backed up and installed only after normal QA camp and empty-North unload. No other zone, server binary or client code changed.

Live Jracol reward hand-in verified

Normal native travel reached Jracol; at 18:49:02 UTC the server confirmed the nearby target and indifferent standing. Without the old dialogue sequence, the naturally obtained card was offered and accepted. One Sealed Note For Knargon was received and stored. Before/after database captures verify Carson McCabe +5, Coalition of Tradefolk Underground +3, Ring of Scale −1, Highpass Guards +5 and Merchants of Highpass +5; every prior item and unrelated faction value was preserved, with no coin change. Normal camp preserved the note and all five rewards.

The measured XP increase was 1,000 (level 1 to 2); this verifies the installed behavior, not exact historical XP. Inspected live reward response · Stored note and level 2 inventory.

Lifecycle gap observed: Jracol was still present at 11:23 game time. The night spawn-selection filter therefore does not establish a complete night-only lifecycle. Nearby target, standing and daytime clock.

Second ordinary character: Jracol exchange and XP discrepancy

A normally created Human Rogue acquired the card from Knargon at amiable standing and walked to Jracol. An initial distant target failed and was excluded. Jracol returned naturally on his existing patrol; at 20:27:15 UTC the server confirmed the nearby target, with indifferent standing. The card was verified in the server trade slot before acceptance. The earned note was stored, all five corrected faction changes matched, and all seven other items and all coin balances were preserved across a later normal save. This is a second live Jracol exchange, not completion of Knargon's successful return branch.

Server-wide XP review item, not a client or North-only repair: this Rogue received 1,050 XP from the script's 1,000 XP award. The current server applies a 5% Rogue gain bonus while its old class-requirement modifier is also enabled. Level 2 displayed normally. The P99 experience reference describes reduced class requirements; the additional gain modifier needs separate classic-fidelity review. Current behavior is measured, not historically certified. No global rule or earned XP was changed.

Nearby Jracol and indifferent standing · Stored note and level 2 inventory. Knargon successful-standing delivery, Zannsin restrictions/rewards and full night-cycle acceptance remain open. No percentage increase is claimed.

Installed: Knargon return-note eligibility

Knargon previously rewarded the return note at any standing. The installed script now requires indifferent or better, preserving the documented failed hand-in consumption below that rank. Highpass and McCabe questions also reach their existing responses. Reward items, faction amounts, XP, currency, patrol and client code did not change.

The dated November 2015 transaction establishes successful indifferent delivery and identifies that minimum; a May 2021 P99 Blue report corroborates failure at apprehensive. Applying that success boundary to P99 is a documented inference, not a newly captured P99 server trace. The prior script fails the new low-standing regression; actual installed scripts pass 1,301 assertions, including all nine ranks in four trade slots, unrelated items, changing standings and dialogue aliases. Backed up and installed only after empty-North unload.

Live Knargon low-standing branch and dialogue verified

On September 29 at 19:29 UTC, ordinary native traversal reached the guild and the server confirmed Knargon with apprehensive standing. Both Highpass and McCabe questions produced their restored responses. The naturally earned Sealed Note was then offered and accepted: the note was consumed, with no XP, coin or faction reward. Eight other items, all eleven existing faction rows and level 2 were preserved in before/after readback and after relog. This verifies the documented failing-standing case, not a successful reward hand-in.

Apprehensive standing · Both live dialogue responses · Inventory after note consumption.

Wrong-item return verified; shared client dependency repaired

A separate Snake Scales hand-in exposed a native packet bug: offering a stackable item to an empty trade slot sent a merge count, causing two server kicks before acceptance. The corrected client sends the whole-stack form for an empty slot and bounds matching-stack merges. Seven trade regressions and the full library suite pass (291 passed, 2 ignored); Linux release build and Windows compile checks pass. This is a shared client repair, not a North database correction.

The isolated QA build then completed the same Knargon test normally. Database snapshots show one Snake Scales moving from cursor to trade slot, being returned after Accept, and being stored again. All eight items, eleven faction rows, XP and currency were preserved after normal camp. Inspected live return response. This accepts one wrong-item case, not every stack size, merge or player trade. The public client downloads and production spectator executable are unchanged; release acceptance remains open.

Still open: Knargon/Zannsin faction prerequisites and their live rewards, repeated/failure hand-ins, exact historical XP, remaining coin behavior, the cross-zone stages and full courier lifecycle. No whole quest is certified and no percentage increase is claimed from this single hand-in.

North-specific database repair: skeletons versus gnolls

The P99 developer correction documents non-KOS decaying skeletons and aggression toward newbie gnolls. North NPC2000/2104 previously had NPC scanning disabled and no hostile gnoll relationship. Both now use a private faction group with hostility to gnoll faction306 and NPC scanning enabled. Player primary faction and kill adjustments are unchanged.

Four rows passed guarded rollback rehearsal and full readback after confirming North had no players and unloading only that zone. The13 affected spawn points retain their placement and timers. Shared faction38 and381 other NPC definitions were preserved. No client code changed.

Observed after ordinary login: two live death notifications identify a gnoll pup killed by a decaying skeleton, without QA attacks, forced spawns or NPC movement. Matching death receipts at17:19:48 and17:20:20UTC identify nonplayer killers. This confirms natural combat outcomes, not exact encounter timing, every skeleton variant or visual combat animation. An initial distant skeleton target attempt was rejected; it is not accepted player-con evidence.

Inspected live death-notification screenshot. Full faction acceptance, social assistance, exact aggro radius and historical numerical tuning remain open. No broad checklist item is marked complete from this narrow repair.

Nearby skeleton: player standing verified

At17:23:39UTC, ordinary field traversal brought the player within range of a level2 decaying skeleton. The server confirmed the target; both targeting and /con showed indifferent. Normal level1 Human Monk, full health, no faction override. This verifies that player case, not every race/class/deity or the complete faction checklist.

Inspected nearby target and indifferent-con screenshot

North-specific database repair: night courier

Jracol Brestiage previously had unrestricted spawn hours. His one North spawn entry is now restricted to night, following the official October2011 P99 patch. Displayed20:00–04:59 follows the NPC reference; exact historical boundaries are not independently measured.

The actual server clock predicate passed all1440minutes. A guarded one-row transaction passed rollback rehearsal and full readback after empty-North unload. The entire catalog comparison shows only two time fields changed. Placement, patrol, timer, NPC statistics and nighttime50/50 gnoll placeholder weights were preserved. One stale saved Jracol actor was backed up and removed after empty-zone unload so it could not bypass the new spawn filter. That record is recoverable; no corpses, other actors, client code or other zone changed.

Still open: natural night appearance, dawn lifetime and restored-state behavior. A spawn-time filter does not despawn an existing actor at dawn. Full courier quest, timer and chance acceptance remain open; this is not whole-roster completion.

Related checks found Enic and four named corrupt guards already have the primary factions specified by that patch. Five North monks already have compatible assistance faction entries; their zero DB assist radius becomes70 in the server, rather than disabling assistance. Those existing rows were not changed. Complete live assistance and faction-hit acceptance remain open.

Klicnik worker: corrected level displayed live

After ordinary native travel from the city gate into the field, the server confirmed nearby worker55 as the target at17:38:43UTC. The inspected UI shows level2 and a dubious player con. Earlier distant requests were rejected and excluded. Normal level1 Human Monk, full health, no NPC forcing or coordinate edits.

Inspected native worker-level screenshot. This accepts one live target/level case. It does not identify both database variants individually or certify all nine worker spawns, appearance, movement, HP, damage, loot, social behavior or the queen encounter.

Next acceptance group

Remaining worker variants and combat statistics; queen proc and hatchling appearance, combat survival and idle expiry; then remaining guard greetings and full shift-cycle edge cases. Three warrior/noble replacements, three generic bat mappings, nine invisible helpers and Kane’s era-specific level are explicit unresolved roster items. No missing reference was treated as proof to delete content.

North was unloaded only after confirming zero players. South was already unloaded for Umvera’s relocation. Other zones, production spectator and public client downloads were untouched.