Live recovery and player changes — 2026-10-14

Five-host status and requested lookalike grant

  • River: matched the exact account/character River and granted 13 pictured cosmetic items through the trusted inventory API: all four Night Hunter pieces, all four Demon Bane pieces, all four Blaze Hawk pieces, and AR_FROST17_HELM (Frostfall Crown). Before/plan/receipt/after files are preserved privately under backups/river-requested-cosmetics-20261014/River; all 13 entitlements were read back successfully. Shadow Scythe and The Debt Collector were absent from the extracted 1.4.4 gear DisplayName metadata and a fresh scan of the available catalog assets, so neither was granted or replaced with an unrequested substitute. Recheck if newer client assets/catalogs are installed.

  • The scheduled Discord status task executes discord-status/worker.mjs, not discord-status/discord-status.mjs. The old worker rejected fleet.rows.length > 4, so the healthy five-host dashboard produced Monitoring unavailable. Replaced the actual worker after preserving its script, environment, supervisor and message state under backups/status-oct14-five-hosts. The existing Discord message was fetched back: EU, key bot, US, Germany and EU overflow all reported, with sample ages and partial counts rather than fabricated totals. Main hunt telemetry now uses local deploy capacity.running, never the aggregate gameserver array (which includes remote workers). Twelve status tests passed. Existing message ID preserved; no replacement message was created.
  • Host 5.175.140.184 was already deployed under E:/DauntlessEU2 when inspected: Windows Server 2022, 12 logical CPUs, 64 GB RAM, 28 running game processes, four running deployment/tunnel/allowlist/health tasks. Main registry had an active loopback 61051 overflow URL and matching overflow instances. No reinstall or game restart was performed.
  • Preciouskitty resolved uniquely to Preciouskitty_TV. Owner accepted lookalikes. Granted and read back AR_SAINTS19_ROMANTIC_CHEST (The Steadfast Heart), AR_SAINTS19_ROMANTIC_ARMS (The Rapturous Embrace), AR_SAINTS19_ROMANTIC_LEGS (The Star-Crossed Walk), and WP_DP_ROMANTIC (Love & Devotion). No crown grant. The existing trusted inventory API was used with deterministic transaction/instance IDs and private before/plan/receipt/after backups under backups/preciouskitty-lookalikes-20261014/Preciouskitty_TV.
  • OCE removal source changes remain uncommitted: launcher choices removed and legacy saved preference maps to US; backend no longer advertises OCE and rejects selection; stale deploy configuration cannot restore its host. Deploy tests 95 passed, metagame 757 passed, launcher 253 passed/3 skipped. These additional source changes have not yet been deployed or published as a launcher release.
  • Anti-cheat video requests remain unverified: web access to both supplied YouTube videos was throttled and exact cheat behavior has not been established. No new automatic-ban policy has been enabled. Rubber-banding or falling alone must not be interpreted as proof of cheating.

Follow-up: Ramsgate waiting and renamed-account login

  • Owner selected waiting in Ramsgate for a hunt slot. Local matchmaking now renews capacity waiting on active polls, instead of failing every active player at 60 seconds. Disconnected waiters still expire after a 60-second idle lease. Regional retry priority avoids newcomers overtaking an idle older waiter; in-flight launches do not serialize all available capacity. Worker capacity admission and startup failure checks remain authoritative. This is not a guarantee that every process starts successfully.
  • Tests cover two minutes of active capacity waiting followed by successful entry on all existing paths, disconnected expiry, late response rejection after the renewed lease, regional isolation and cancellation. Full metagame suite: 756 passed with –test-concurrency=2. Default concurrent run had one bountiesported process failure; that file passed independently (13 tests), and the complete bounded-concurrency rerun passed. No production queue rollout yet.
  • Existing Miau key successfully returned HTTP 200 and MiauStyleZzツ. Launcher settings sanitation incorrectly reused ASCII signup validation for authenticated display names. Local fix accepts the existing safe display-text contract and keeps signup restrictions. Launcher suite: 252 passed, 3 skipped; typecheck and Windows packaging passed. Package remains an unpublished local 0.1.34 build; do not describe it as a released update.
  • Live dashboard recovery instructions now point to Players & accounts / Show login key. Authenticated recovery endpoint verified the renamed account without printing the key.
  • Latest git fetch still resolves upstream to 5e25932; checkout is zero commits behind. This does not establish fleet-wide compiled-file parity.
  • Follow-up live dashboard snapshot now contains a fifth host, Server #5 · EU overflow (30 hunts), alongside US (26), Germany (12), key bot (0) and main (unknown). All five reported online. Earlier four-host observations below are historical snapshots, not the current topology. Do not overwrite this newer topology using the earlier inventory.
  • Character/inventory API endpoint mappings alone do not prove that inventory replication is causing current hitches. No character-blob transport rewrite or CPU-affinity change has been deployed on this evidence.

Verified changes

  • GitHub checkout: 5e25932, including PR64/65. Main matchmaking.js and capacity.js matched rebuilt upstream, despite older build-info metadata. Do not use build-info alone to infer deployed code.
  • Main routing: removed retired AUS_DEPLOYSERVER_URL and EU2 OVERFLOW_DEPLOYSERVER_URL. RegionalRouter now uses US for overflow when OCE is not configured; explicit unavailable OCE requests fail closed. Added regression test; deploy suite 95 passed. Updated /gameservers to include US. Live snapshot complete=true, main/Germany/US present, no OCE/EU2 game workers.
  • Migrated 353 saved OCE preferences to US, preserving their prior values in a private rollback JSON on main. This was an owner-authorized replacement, not automatic latency-based rerouting.
  • Bot moved from main to EU2 C:/DauntlessBot. Protected config and key/counter state copied only after the old instance stopped. Main bot task disabled. New SYSTEM startup task has a restart supervisor, 512 MB Node heap limit and AboveNormal priority. EU2 game worker drained to zero and its deploy task disabled. Final check: one bot process, ready/authenticated, zero bytes in error log. No real-user DM/recovery transaction was performed by this audit.
  • Screenshot /key generate response is the already-redeemed invite guard. Existing linked accounts use /key recover; unused invites use /key resend. Do not remove the guard to issue duplicate invites.
  • Dashboard and existing status embed relabeled Server 2 as Key bot and Server 3 as US (NA); US monitoring uses loopback 61124. Final dashboard check: all four hosts reporting. Main hunt count remains unknown because its old performance sampler is disabled; remote hunt counts and CPU/RAM report.
  • Main native DLL was F1DE8581491099EA40D6FB166D7F2732273AE616CCD9E999BA2D3084DE858260, unlike Germany/US and current repository A090E8B25044647CE409B313525501DA578D632D3FCB9EB351F020CA94FA64FB. The main source copy lacked the current SetChannelActor assignment observer/cold channel lookup work. Replaced the main DLL by renaming the mapped old file and installing the verified current DLL; existing game processes were not terminated. New main game PIDs 4584 and 11012 reported DR_ChannelAssignmentTrackingEnabled=1 via read-only process-memory inspection at exported RVA 0x3FEB8. Existing instances retain their old DLL until they exit.
  • Native tests passed with MSVC /std:c++20 /W4 /WX: channel lookup, hunt idle policy, owner relevancy, replication cadence, connected player snapshot. Cold join channel inspections were linear: 3,000 for 1,000 actors and 24,000 for 8,000 actors.
  • Main supervisor did not restart the drained deploy process within its advertised minute. Performance WMI queries had also hung; disabled PerformanceLog and restarted only the supervisor task. Existing backend/gateway PIDs survived and deploy recovered. Blocking performance collection is a probable cause, not proven from a stack trace.

Player changes

  • Renamed exactly MiauStyleZzUwU to MiauStyleZzツ in users and its one character, atomically. IDs/keys/inventory unchanged. Existing registration/rename API accepts only ASCII, so this explicit owner-requested exception used a narrow, uniqueness-checked database transaction. Preserved old names in JSON and a standalone SQLite rollback database with quick_check=ok. A full online backup attempt was stopped before mutation because it was not completing under writes; its partial file is named before.db.incomplete and is not a valid recovery backup.
  • TFBTA: 16 new entitlements, 17 verified including the already-owned TITLE_DEV_ALL. Original Phoenix Labs sigil and team flare, Phoenix glowing orange dye, translator banner plant/self-five/arrival, Universal Language sword skin, translator sigil/flares/titles, Lobster title. IDs and API receipts are in Grant-TFBTA-Phoenix.mjs and private main inventory backups.
  • Catalog evidence: BUNDLE_PROMO_PHXTEAM_00 explicitly contains QI_FLARE_PROMO_086, BNC_SIGIL_020 and DYE_RESTRICTED_ORANGE04_GLOWING_DURABLE. WP_EB_QUILL_00 is named Universal Language in 1.4.4. The 2022 Phoenix Labs variants do not exist in the scanned 1.4.4 catalogs; none were fabricated. Ownership was read back; no interactive client equip/render test was performed.

Important limits and rollback

  • Rubber-banding/mid-hunt disconnects are NOT proven resolved fleet-wide. Germany CPU reached about 97% in an earlier sample. Sampled Germany deploy exits were code 0; no fatal/connection-timeout/watchdog evidence in that sample. Main logs contain character save-version conflicts and intermittent allowlist helper timeouts, without correlation proving the reported kick cause. Do not suppress save conflict protection on this evidence alone.
  • Germany capacity.js is older and lacks HuntsDraining/MAX_PENDING_HUNTS support. Not all live files match upstream. No speculative worker restart or native rewrite was done to claim full deployment parity.
  • US firewall helper is intentionally reverse-forwarded to MAIN port 61025, NOT 61045 in the actual current Run-Tunnel.ps1. Main gateway already feeds 61025. Removing the old-looking port would break US admission. Existing 61025 feed was preserved.
  • Main rollback files: C:/DauntlessRevived/backups/routing-oct14 (deploy env, routes/controllers, dashboard/status/config and old DLL). Restore routing only during a controlled drained restart; restoring OCE endpoints would reintroduce the retired host. Restore native DLL only for newly started instances after verification.
  • Bot rollback: stop EU2 bot before ever enabling old main task, and first synchronize current EU2 keys.json/counters.json back privately. Never run both state writers. Keep EU2 deploy task disabled for resource isolation.
  • Rename rollback: restore only the account/character names from rename-rollback.db after uniqueness checking. Inventory rollback must subtract only recorded additions through the trusted API; never restore the whole player database over newer progress.
  • Source publication does not deploy the queue change or publish a launcher release. Live changes and unpublished artifacts are distinguished above.