CoaBots.AutoLogin.MaxCount only makes the server log in companions that already exist: with 50
companions and a limit of 300, 50 came online. The Manager now creates the difference.
- coa-core: fleet_shortfall / queue_fleet_top_up queue one durable pending job per realm for
limit - existing (at most 2000 per job, the most one server command takes). Nothing is queued
when the fleet is complete or an unfinished job exists for the realm.
- start_server: after the world is up, each realm whose auto-login is on is topped up before its
pending job runs (shared reconcile_realm_companions helper). If the existing count cannot be
read, nothing is created.
- Saving the startup settings of a running server tops up right away (new top_up_startup_fleet
command); a shortfall above 200 asks for confirmation.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The community moved the game client behind its official launcher (account
sign-in, signed manifest, its own CDN), so the public manifest now answers 404
and the Manager must not pose as the launcher. Remove the client download and
update path (clientdl, plan/sync/download/cancel commands, update job and
progress UI, version tracking) and reduce "Set up the game client" to: open
coa-development.org for the launcher, or pick a folder that already has the
game. Linking a folder, realmlist switch, companion addon and the custom-race
patch are unchanged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Installs the 2.0.2 client set (retail body cache, subclass and HD patches, current
CoACustomRace.exe, newer subclass addon without the Skinshifter collection),
with the 2.0 inventory kept for installs that still carry that manifest.
Archive sizes and hashes verified against the real release archives.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Version 0.9.14; reviewed Manager (12) and server (6) records with translations in all
five languages; server components from the lock of build run 43758471036; bundled server
history through 0.261115.110 from build main 45c013be9.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A client without the races patch crashes on a unit of race 12+, so the server now keeps
those characters out while custom races are off. The Custom Races card shows how many
player characters and bots that are (active realm, read only while the database runs) and
offers botcmd purgecustomraces for the companion bots.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The uncommitted RC hardening of the multirealm Manager branch: a per-realm pending job
state machine reconciled against the database (no duplicate bots after a crash or an RA
timeout), cancelled by Stop spawning / Delete all bots, legacy file migrated; spawn
requests and build ids validated; tests JOB-01..JOB-14.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
addons/catalog.json pins SquidBots Lite, DragonUI (+Options), IncahootsCoA and CoACombat
to a commit and lists every file with its git blob SHA-1 and size. Install downloads
GitHub's archive of that commit, verifies each file (archives are not byte-stable, their
contents are), stages next to AddOns and moves the folders in; a foreign folder of the
same name goes to AddOns/.coa-addons-backup. .coa-addons.json records what the Manager
installed; update and remove touch only that. CoA_DevMenu ships with Custom Races V2, so
the separate dev menu addon is not in the catalog. Checked against the real GitHub
archives of the three small addons (ignored test).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- clear_game_cache removes Cache/WDB/<locale>/*.wdb before every Play (own server and
friend's), on by default, switch in the client card; nothing else in Cache or Data.
- The connection profile keeps the listed realm it was joined through; Play fills that
realm's saved account into GlueConfig.json every time. A host typed by hand drops it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings/restart-schedule.json (Settings, Startup) holds a local time and a countdown.
The Rust world supervisor asks the world for 'server restart <seconds>' once that time has
passed (by at most 15 minutes, for a world that ran before it), and starts the world
again when it exits with RESTART_EXIT_CODE; the database and auth keep running. While it
is under way (.state/scheduled-restart) the status says so and the Manager does not take
the down world for a crash. Extra worlds follow their server's schedule. Repacks with the
Python supervisor do not run the schedule; the card says the server needs an update.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings, Service edits Settings/mysql-custom.ini. Every start adds its name = value lines
(outside a section or in [mysqld]) to the rendered my.ini, after the defaults so they
win; the port, addresses, data and log paths, sockets and !include stay managed. Nothing
changes for a server without the file.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Settings, Startup lists every realm of the server with its name. The choice is kept in
Settings/realm-names.json of the main folder; the launcher, the realm-list setup and the
client's Config.wtf use it, and a running database gets it at once. Names are 1-32
characters without quotation marks or control characters, written as escaped SQL.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Manager 0.9.13 carries the Custom Races V2 client. Its reviewed note and the 213 notes of the upcoming
server record (Custom Races V2: subclasses, Two-Players, the new races; collected with the pipeline's own
rules from the frozen sources of candidate run 43641984449) have Russian, German, French, Spanish and
Simplified Chinese translations. Bundled server history refreshed through 0.261114.106 from
coa-server-build 3308e3a.
Checks: release-history tests 5/5, check-i18n, npm run build, cargo check --locked.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Starting a server that is open to friends adds the firewall rules for the
world ports of all realms that start together (only missing ones; a refused
Windows prompt does not undo the start).
- Settings shows one public-listing block per realm that starts together. The
main realm keeps its plain local id, so an existing listing is untouched.
- A realm that runs as an extra world is reached through that world's own
console port, so its listing reports its own state and capabilities.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Settings gets two options, one per extra realm; turning on both runs all
three realms. Each extra world keeps its own folder, configs, logs and
ports (multiworld now handles a set of worlds instead of one second world),
and Warcraft Reborn gets its own status card, realm list entry and firewall
rule.
Starting a server also sets CoA.ClassModel of the realm chosen on Overview
to exactly that realm's model, so the shipped "coa wcr" default no longer
shows two class models on a Conquest of Azeroth realm.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
- Enforce fail-closed backend resolution in LocalBackend::info (unknown ruleset = error).
- Implement strict three-space isolation (Wildcard != CoA != Reborn) across canonical store, host mappings, and collections.
- Isolate collection namespaces (wildcard:appearance, wildcard:vanity) and reject cross-ruleset collections in claim and import.
- Enforce Control Protocol v2 ruleset verification on TransferOffer, TransferCommit, and Claimed response.
- Route Direct Ingress and Relay Link dynamically according to realm world port (8085 for CoA, 8086 for Wildcard).
- Add runtime session attack rejection test suite (cross-ruleset session offers, checkpoints, owner acks, server IDs).
- Verify end-to-end Wildcard session lifecycle and documentation updates.