Version 0.9.16 (Manager only; no server release). Reviewed notes: the client download now comes from
the community launcher, HD graphics hint and translated Custom Races patch card, companions startup
limit creates the missing ones, weekly world restart, server log auto-cleanup. Translations in ru,
de, fr, es and zh for these five notes and for the 0.9.15 note, which the history test requires.
Bundled server history stays at 0.261115.110; notes of later server releases show in English until
a Manager refreshes and translates them.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Its body was 375 characters, so `changelog.py check` over the whole directory failed. The title is
unchanged, so the published 0.9.15 note is the same.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The weekly restart schedule and the server log auto-cleanup (previous commit) had strings only in
en and ru and no changelog fragments. Adds de/es/fr/zh for the weekday names, the weekly toggle
and the log settings, and one fragment per change.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
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 launcher owns the Standard/HD choice (Settings -> "HD graphics"; its setup
also offers it), so the Manager cannot toggle it. The client setup dialog now points players
there. The Custom Races client patch status badges, hints and Install/Repair/Uninstall
buttons were English/Russian ternaries; they are now i18n keys in all six locales.
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 module list blocked Companions on every realm but Conquest of Azeroth, so the
multi-realm bot work could not be switched on. It is allowed (as experimental) when the
world server or its bots plugin carries the standard-class bot profiles of the multi-realm
bots build; SQUID and Dungeon Clear stay CoA-only.
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>
- Subclasses/Hero Races and the /dev menu are parts of Custom Races (catalog part_of,
hidden from the grid): their switch and settings sit inside the Custom Races settings.
- The companion bots addon (CoABotUI) moves from the client facts into the addon list,
with install/update from the server package; the /dev menu addon of the V2 patch is
listed as installed by the patch, without its own buttons.
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>
mod-subclass (Subclass.Enable, the Thin Twins and Two-Headed Ogre races, two players per
character, levels) and mod-ilusixn-devmenu (DevMenu.Enable, who may use it) were shipped
with V2 but had no place in the Manager. They are catalog modules now, with translated
controls for their main settings; the rest stays under the advanced settings.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The worldserver ignores DisabledRaceIds saved against another ChrRaces catalog and with
it CoACustomRaces.Enable, so every server that had a restriction from 1.9.2 lost custom
races after the V2 update. Before a start the Manager binds the restriction to the new
catalog when every disabled race keeps its RaceID and name, judged by the server's own
snapshot (written by every save) or the table of every catalog a build has shipped
(race_catalogs.json, generated from the core history). Renamed races (1.9.1 reused 32/33)
and unknown catalogs still wait for the owner's review.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
V2 has 7,220 files. Switching rewrote the whole transaction journal with fsync after
every file (quadratic: minutes on fast disks, far longer with antivirus) and renamed
every file. Now:
- the journal is append-only JSON lines; recovery replays it, ignores a torn last
line and still reads the old journal.json of 0.9.13;
- only what the stock client loads is hidden (Data/*.MPQ, root dll/exe/bat, addons,
any file that replaced the player's own); Data/Retail, VulkanShaders and the
Esteria data stay in place, and a client disabled by 0.9.13 is recognised;
- payload hashes are remembered for the run, keyed by name, size and times.
Real V2 archives, release build: disable 1.9 s, enable 2.2 s, 224 of 7,220 files moved.
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>
A reserved or taken database port no longer fails the start after 30 seconds: the
launcher recognises Windows excluded ranges (netsh), moves MySQL to a free port and
records it in Settings/repack.json. Only the server's own services use that port.
The database connection of with_database is rebuilt after the start.
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>
The client update now takes ilusixn/CustomRacesCoa coa-custom-2.0: nine client archives plus the server
archive's client addons (subclass interface, dev menu, teleports, spell activation overlay), 76 race
archives and 7220 verified files in all, among them CoACustomRace.exe and its Vulkan renderer.
- The game starts CoACustomRace.exe when it is there; Ascension.exe is left alone, and a disabled V2
falls back to it.
- Updating from 1.9.2 retires its patched Ascension.exe and puts the player's own back (1.9.2 replaced
it; V2 does not ship one). Earlier installs keep their own hash lists, 1.9.2's included.
- Four V2 archives are byte-identical to 1.9.2's: a verified 1.9.2 copy in the cache or in Downloads
is used instead of downloading it again.
Verified: unit tests (800 passed); against the real archives, every bundled hash, a full install,
disable, enable and uninstall in a disposable client, and an update of a client that Manager 0.9.12
had put 1.9.2 on (its own Ascension.exe comes back, and again after uninstalling).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tools/test_launcher_bridge.py tested crates/coa-core/src/launcher_bridge.py,
which the Rust launcher replaced; check.yml and release.yml still ran it, so
the release build failed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A console shutdown request is sometimes lost, and the world then keeps
running until the stop times out. While the world still runs and its
console still answers after 15 s, the launcher asks again (twice at most);
asking twice is harmless. Verified on a disposable repack with the first
World::ShutdownServ call suppressed in a debugger: the second request
stopped the world.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>