mirror of
https://github.com/Corfirean/coa-server-manager.git
synced 2026-11-18 19:25:56 +00:00
Compare commits
176
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
0e62be5097 | ||
|
|
19791edb94 | ||
|
|
4537b2a826 | ||
|
|
4a88f696a0 | ||
|
|
e3fbb2e4b6 | ||
|
|
a7b56d6aed | ||
|
|
cda7875a9a | ||
|
|
f53c7cb221 | ||
|
|
ca6bcf0052 | ||
|
|
d6a6384f9c | ||
|
|
21ddc1e7d8 | ||
|
|
16396407ad | ||
|
|
093dbfcadc | ||
|
|
dc323df681 | ||
|
|
46785f7978 | ||
|
|
97c024d95c | ||
|
|
52b80232fa | ||
|
|
be2f252593 | ||
|
|
24d593d787 | ||
|
|
4a9760b864 | ||
|
|
482bbfcdfd | ||
|
|
b45e2502ec | ||
|
|
6a955bd670 | ||
|
|
d5f441de0c | ||
|
|
4efc02e768 | ||
|
|
be9641254a | ||
|
|
c18daac228 | ||
|
|
89c62abf80 | ||
|
|
a6471d79d0 | ||
|
|
fd0eaafda2 | ||
|
|
fb1cc38773 | ||
|
|
7a950f234b | ||
|
|
2f1df13b7a | ||
|
|
be705329c1 | ||
|
|
7e70409ca0 | ||
|
|
9e6a650d13 | ||
|
|
0398a5a6f9 | ||
|
|
dd23e81dd4 | ||
|
|
ca2a555d7c | ||
|
|
8269a53db7 | ||
|
|
b97f86fc00 | ||
|
|
1a71f18def | ||
|
|
358f9f4f2b | ||
|
|
0c0d2db368 | ||
|
|
7d7bc530ec | ||
|
|
acd04fae2f | ||
|
|
106a532092 | ||
|
|
d86a1676fe | ||
|
|
53a05820c8 | ||
|
|
58c976a388 | ||
|
|
35c4d03bdc | ||
|
|
c45f962d02 | ||
|
|
f52bd8ba5f | ||
|
|
247159e56c | ||
|
|
cdd5be2365 | ||
|
|
7e170744bf | ||
|
|
10daa9b74d | ||
|
|
51ef88101e | ||
|
|
ed7bf7262b | ||
|
|
7c866b116d | ||
|
|
4d8ca00e46 | ||
|
|
36bfc6d31e | ||
|
|
3fb4ee39c6 | ||
|
|
0250b61c62 | ||
|
|
dfd8a50975 | ||
|
|
90c308615b | ||
|
|
cfea54e203 | ||
|
|
57aa97da8a | ||
|
|
b9f89a4ae4 | ||
|
|
6fd2130fc4 | ||
|
|
346d97ee89 | ||
|
|
10a6744192 | ||
|
|
7557b347c5 | ||
|
|
2abd64dfe2 | ||
|
|
9ae5fb471b | ||
|
|
59036867d7 | ||
|
|
949614f11a | ||
|
|
9ee0e9f6af | ||
|
|
3405c89fe8 | ||
|
|
4c4d39f1de | ||
|
|
b101c79e96 | ||
|
|
3b7f77d92e | ||
|
|
0589722e71 | ||
|
|
a3717c08bb | ||
|
|
dc2bffc57e | ||
|
|
e34ab45443 | ||
|
|
40f9feab84 | ||
|
|
5b16842720 | ||
|
|
02843bb6d1 | ||
|
|
a9ab7ced7e | ||
|
|
77318895ae | ||
|
|
115c57f54e | ||
|
|
94fd5fb5b9 | ||
|
|
94d4ade1c7 | ||
|
|
376f1dbb46 | ||
|
|
b0951dbee7 | ||
|
|
374a3f9c23 | ||
|
|
d20d5a6410 | ||
|
|
1228807eaf | ||
|
|
ee59708fbf | ||
|
|
3ed9c5dacd | ||
|
|
9099168927 | ||
|
|
a27e0eb6ab | ||
|
|
c46edd2feb | ||
|
|
f934bef303 | ||
|
|
c882a21334 | ||
|
|
a625b065cf | ||
|
|
5c3a9def0c | ||
|
|
25098b5a63 | ||
|
|
45a699d2ca | ||
|
|
be68eb4341 | ||
|
|
06ca748e80 | ||
|
|
58c1e1aee0 | ||
|
|
ad69fb0401 | ||
|
|
7540527d30 | ||
|
|
5328709826 | ||
|
|
478ea8a960 | ||
|
|
c8a0f6872f | ||
|
|
c3791f80f1 | ||
|
|
1acbcc2bb5 | ||
|
|
838cc07e73 | ||
|
|
4c4f8bbb3e | ||
|
|
d85d86a3dc | ||
|
|
0a050a40a2 | ||
|
|
017b977bfa | ||
|
|
337418afe0 | ||
|
|
f920ff8a59 | ||
|
|
072a657649 | ||
|
|
c6e8a34509 | ||
|
|
3f98ba3add | ||
|
|
7a3fefaafd | ||
|
|
fac6ce469a | ||
|
|
f22cedd963 | ||
|
|
0b5f12941c | ||
|
|
f3fc14b55a | ||
|
|
beaec7d27e | ||
|
|
8490dc9983 | ||
|
|
3f8abcbbe8 | ||
|
|
b3c50a7b39 | ||
|
|
bbdad37e40 | ||
|
|
0ed4d5e268 | ||
|
|
b13ee55bb9 | ||
|
|
51a45db8cb | ||
|
|
3f700ee8f4 | ||
|
|
277ebba847 | ||
|
|
9a0b815937 | ||
|
|
78b84e11c2 | ||
|
|
6aea9011f9 | ||
|
|
171d9a2bf8 | ||
|
|
0d6d8a0db8 | ||
|
|
3940506987 | ||
|
|
654b7cddd3 | ||
|
|
f8301d7394 | ||
|
|
cd3a963f70 | ||
|
|
6c771fae20 | ||
|
|
cfe0889a4f | ||
|
|
f25a1d425d | ||
|
|
b5e4a38d7d | ||
|
|
07ec22798f | ||
|
|
5d865fcaea | ||
|
|
a67d51804b | ||
|
|
7c096a4844 | ||
|
|
b90b377fc3 | ||
|
|
a02130f587 | ||
|
|
f4e36f21eb | ||
|
|
65c9945626 | ||
|
|
f13398bbd7 | ||
|
|
f05f94ba01 | ||
|
|
c39a7a0ac7 | ||
|
|
e8367354ef | ||
|
|
461fa035d0 | ||
|
|
3edc600f97 | ||
|
|
c3d87e1ff2 | ||
|
|
d2496603e7 | ||
|
|
2eea0e117c | ||
|
|
58b5ddeb07 |
No files matched your search
@@ -0,0 +1,14 @@
|
||||
name: changelog-fragments
|
||||
# Checks the changelog.d/ fragment files with the shared rules (https://github.com/Corfirean/coa-server-build/blob/main/changelog/GUIDE.md).
|
||||
on:
|
||||
push:
|
||||
paths: ['changelog.d/**']
|
||||
pull_request:
|
||||
paths: ['changelog.d/**']
|
||||
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
check:
|
||||
uses: Corfirean/coa-server-build/.github/workflows/changelog-check.yml@main
|
||||
@@ -1,14 +1,47 @@
|
||||
name: changelog
|
||||
# Checks the changelog.d/ fragment files with the shared rules (https://github.com/Corfirean/coa-server-build/blob/main/changelog/GUIDE.md).
|
||||
on:
|
||||
push:
|
||||
paths: ['changelog.d/**']
|
||||
branches: [master]
|
||||
paths: [tools/sync_history.py, changelog/history.json, .github/workflows/changelog.yml]
|
||||
pull_request:
|
||||
paths: ['changelog.d/**']
|
||||
|
||||
paths: [tools/sync_history.py, tools/test_sync_history.py, changelog/history.json, .github/workflows/changelog.yml]
|
||||
release:
|
||||
types: [published, released]
|
||||
workflow_run:
|
||||
workflows: [release]
|
||||
types: [completed]
|
||||
workflow_dispatch:
|
||||
permissions:
|
||||
contents: read
|
||||
|
||||
contents: write
|
||||
concurrency:
|
||||
group: component-changelog
|
||||
cancel-in-progress: false
|
||||
jobs:
|
||||
check:
|
||||
uses: Corfirean/coa-server-build/.github/workflows/changelog-check.yml@main
|
||||
test:
|
||||
runs-on: ubuntu-latest
|
||||
permissions:
|
||||
contents: read
|
||||
steps:
|
||||
- uses: actions/checkout@v7
|
||||
- run: python3 -m unittest discover -s tools -p test_sync_history.py
|
||||
sync:
|
||||
needs: test
|
||||
if: github.event_name != 'pull_request' && (github.event_name != 'workflow_run' || github.event.workflow_run.conclusion == 'success')
|
||||
runs-on: ubuntu-latest
|
||||
env:
|
||||
GH_TOKEN: ${{ github.token }}
|
||||
steps:
|
||||
- uses: actions/checkout@v7
|
||||
with:
|
||||
ref: ${{ github.event.repository.default_branch }}
|
||||
fetch-depth: 0
|
||||
- name: Synchronize this component from published immutable sources
|
||||
run: python3 tools/sync_history.py --sync-release-notes
|
||||
- name: Commit updated history
|
||||
run: |
|
||||
git config user.name 'github-actions[bot]'
|
||||
git config user.email '41898282+github-actions[bot]@users.noreply.github.com'
|
||||
git add CHANGELOG.md changelog/history.json
|
||||
if git diff --cached --quiet; then exit 0; fi
|
||||
git commit -m 'Update published Manager changelog'
|
||||
git push origin HEAD:"${{ github.event.repository.default_branch }}"
|
||||
@@ -4,3 +4,5 @@ dist
|
||||
*.log
|
||||
.env
|
||||
src-tauri/gen
|
||||
# Disposable database fixtures and private recovery data
|
||||
.cache/
|
||||
@@ -3,8 +3,7 @@
|
||||
<!-- changelog:start (managed by coa-server-build/changelog/changelog.py sync-instructions) -->
|
||||
## Changelog (shared by all CoA repositories)
|
||||
|
||||
Every CoA project (server fork, bots, Content Scaling, Manager, renderer) feeds **one** changelog that is posted to the
|
||||
community. When you finish a change that a **player** or a **server owner** would notice (a new feature, a changed
|
||||
Every CoA project (server fork, bots, Content Scaling, Manager, renderer) uses the same fragment format. **Manager and server release histories are separate**; each repository publishes only its own shipped component changes. When you finish a change that a **player** or a **server owner** would notice (a new feature, a changed
|
||||
behaviour, a fix for something people ran into, a removed feature, a known issue), add **one small file to
|
||||
`changelog.d/` in the same commit**. Do not add one for internal work (refactors, tests, CI, documentation).
|
||||
|
||||
@@ -29,3 +28,22 @@ Optional: one short paragraph in plain English for the reader (at most 300 chara
|
||||
`python changelog.py new --area bots --type fixed --audience players --title "..."`.
|
||||
- Full guide with examples: https://github.com/Corfirean/coa-server-build/blob/main/changelog/GUIDE.md
|
||||
<!-- changelog:end -->
|
||||
|
||||
## Shared build and release workflow
|
||||
|
||||
Before preparing or publishing a Manager/server release, read the maintained
|
||||
[release runbook](https://github.com/Corfirean/coa-server-build/blob/main/docs/server-release.md)
|
||||
and [build agent instructions](https://github.com/Corfirean/coa-server-build/blob/main/AGENTS.md).
|
||||
Use the local build checkout when available; otherwise retrieve the current files from GitHub.
|
||||
|
||||
Recover the exact prepared run, source commit, version, hashes and artifact expiry before rebuilding.
|
||||
Prepare-only is not publication permission. A normal owner command to release the identified candidate
|
||||
includes its required stable promotion; do not stop at a server Pre-release or ask twice for the same action.
|
||||
Reuse signed prepared Manager installers after verifying their source metadata, SHA-256, updater JSON
|
||||
and signature against the matching source's updater public key. Do not rerun compilation just to upload
|
||||
already verified assets, or overwrite a published version with different bytes.
|
||||
|
||||
Server promotion uses the persistent Windows PC and the shared workflow's verified caches. Preserve
|
||||
production databases; run applicable local acceptance in disposable fixtures. Record the actual passed,
|
||||
failed and unrun checks. Verify both GitHub Latest and the public signed stable pointer before reporting
|
||||
that users can update. Leave the durable handoff described in the runbook for the next agent.
|
||||
+290
-15
@@ -1,25 +1,300 @@
|
||||
# CoA Server Manager changelog
|
||||
|
||||
Manager releases only. Updating the Manager does not update the server.
|
||||
|
||||
[Server changelog](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)
|
||||
|
||||
Dates follow GitHub publication (UTC); legacy records retain their archived dates. Newest releases first.
|
||||
|
||||
## 0.6.22 — 2026-10-19
|
||||
|
||||
- Updated Custom Races client patches to 1.8.
|
||||
- Included the updated race appearance and cursor addons.
|
||||
- Existing client files are preserved when installing or removing race patches.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.22) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.21...v0.6.22)
|
||||
|
||||
## 0.6.21 — 2026-10-16
|
||||
|
||||
- Server updates apply migrations once after saving a recovery point.
|
||||
- Older server versions update directly without installing intermediate packages.
|
||||
- Update validation recognizes an already stopped server.
|
||||
- Recorded core SQL stays applied after old history tables are cleaned up.
|
||||
- Switching realms no longer repeats shared account database updates.
|
||||
- Update offers distinguish version support from database validation.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.21) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.19...v0.6.21)
|
||||
|
||||
## 0.6.19 — 2026-10-16
|
||||
|
||||
- Update checks no longer download a server archive to compare its launcher.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.19) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.18...v0.6.19)
|
||||
|
||||
## 0.6.18 — 2026-10-16
|
||||
|
||||
- Older servers find a tested intermediate update instead of being blocked.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.18) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.17...v0.6.18)
|
||||
|
||||
## 0.6.17 — 2026-10-15
|
||||
|
||||
- Already running MySQL is recognized before startup readiness checks.
|
||||
- New servers install the current stable build directly.
|
||||
- Install the matching client patches for Grummle.
|
||||
- Failed repairs restore the previous server after final verification errors.
|
||||
- Failed server updates show an error on the Overview screen.
|
||||
- Private update checks show preparation stages and stop failure details.
|
||||
- Repair recovery copies preserve all bundled database objects and accounts.
|
||||
- Server checks report interrupted SQUID database imports.
|
||||
- Shutdown remains available when startup templates or database records are damaged.
|
||||
- Successful server repairs no longer block later server actions.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.17) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.16...v0.6.17)
|
||||
|
||||
## 0.6.16 — 2026-10-13
|
||||
|
||||
- Linux Docker servers follow Settings, sharing and backups (experimental).
|
||||
- Local hosts can connect while sharing a server online.
|
||||
- Custom race client installation follows the current upstream release.
|
||||
- Docker friend mode requests a restart when remote client support changes.
|
||||
- Module cards show installed server revisions and the client race patch version.
|
||||
- Server updates accept long Windows paths inside the private test server.
|
||||
- Diagnostics record blocked startup requests and maintenance owner information.
|
||||
- Client race patches can be repaired and removed while preserving original files.
|
||||
- Checking an already installed server update no longer reports incompatibility.
|
||||
- Failed server startup shows service errors even when the launcher reported ready.
|
||||
- Starting the server waits for update checks and identifies ongoing maintenance.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.16) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.15...v0.6.16)
|
||||
|
||||
## 0.6.15 — 2026-10-11
|
||||
|
||||
- Large server updates no longer repeatedly rewrite the recovery journal.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.15) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.14...v0.6.15)
|
||||
|
||||
## 0.6.14 — 2026-10-11
|
||||
|
||||
- Fixed server update checks failing with long Windows paths.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.14) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.13...v0.6.14)
|
||||
|
||||
## 0.6.13 — 2026-10-11
|
||||
|
||||
- Failed server startup after an update automatically restores the previous version.
|
||||
- Windows update recovery preserves database procedures triggers and views.
|
||||
- Custom races bot setting synchronizes Playerbots excluded race lists.
|
||||
- Blocked updates identify database objects that prevent automatic recovery.
|
||||
- Updates can follow signed channels that select a complete server release.
|
||||
- Server updates check startup privately before allowing players to connect.
|
||||
- Updates repair missing database defaults from the verified release schema.
|
||||
- Server updates no longer replay module installation scripts on existing databases.
|
||||
- Windows server updates are tested on a private copy before changing your installation.
|
||||
- Server updates can require a tested combination of platform and installed version.
|
||||
- Failed database checks keep a complete report after rollback.
|
||||
- Players can install custom race patches when connecting to a friend.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.13) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.12...v0.6.13)
|
||||
|
||||
## 0.6.12 — 2026-10-10
|
||||
|
||||
- Background world servers no longer stop because the local console is closed.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.12) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.11...v0.6.12)
|
||||
|
||||
## 0.6.11 — 2026-10-10
|
||||
|
||||
- Server and Bots settings open without a blank window.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.11) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.10...v0.6.11)
|
||||
|
||||
## 0.6.10 — 2026-10-10
|
||||
|
||||
- Custom race client patches update to the latest races and appearances.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.10) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.9...v0.6.10)
|
||||
|
||||
## 0.6.9 — 2026-10-10
|
||||
|
||||
- Custom races can be enabled and their client patches installed from Modules.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.9) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.8...v0.6.9)
|
||||
|
||||
## 0.6.8 — 2026-10-10
|
||||
|
||||
- Linux: install from the install screen, play with Wine or Proton (experimental).
|
||||
- A failing database update is no longer reported as "database not running.
|
||||
- Unsaved settings are protected and crashed servers can restart automatically.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.8) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.7...v0.6.8)
|
||||
|
||||
## 0.6.7 — 2026-10-08
|
||||
|
||||
- Choose where backups are stored, for example on another drive.
|
||||
- Bot settings with a fixed list of values show a drop-down.
|
||||
- The bot dashboard loads completely and can be opened in the browser.
|
||||
- Accounts of the SQUID bots are hidden from the Accounts list.
|
||||
- A Dashboard tab shows what the SQUID bots are doing.
|
||||
- A stopped server stays stopped after an update, unless you ask it to start.
|
||||
- Checking for updates no longer fails with "Something went wrong" after a crash.
|
||||
- Server updates no longer stop with "has a different checksum" on the Wildcard repair.
|
||||
- A world server started from the coa-bots folder is recognised.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.7) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.6...v0.6.7)
|
||||
|
||||
## 0.6.6 — 2026-10-07
|
||||
|
||||
- Install a server from a package on Linux, running in Docker (experimental).
|
||||
- The Auction House Bot card no longer asks for a character GUID.
|
||||
- Choose and remember the local network address friends use to connect.
|
||||
- The NPC Enchanter card explains how to place and remove the NPC.
|
||||
- Diagnostic files with database checks stay readable after secrets are removed.
|
||||
- One button collects all diagnostics, including crashes and Windows crash records.
|
||||
- Problem reports go to the right project.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.6) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.5...v0.6.6)
|
||||
|
||||
## 0.6.5 — 2026-10-06
|
||||
|
||||
- Imported SquidBots servers warn before replacing their original binary.
|
||||
- SquidBots settings follow the options shipped by the module.
|
||||
- SquidBots shows its bundled release and includes it in problem reports.
|
||||
- Server updates accept verified published migration variants without rerunning them.
|
||||
- Server updates replace older launchers adapted by the Manager for Wildcard.
|
||||
- Older server packages cannot replace a newer installation.
|
||||
- Checking again no longer offers an already installed launcher update.
|
||||
- Large SQUID database imports have more time to finish on first startup.
|
||||
- Update history conflicts are detected before server files change.
|
||||
- Pending database updates remain visible when the server version matches.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.5) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.4...v0.6.5)
|
||||
|
||||
## 0.6.4 — 2026-10-05
|
||||
|
||||
- Start your installed server or client without downloading an available update.
|
||||
- Finish a server update that was blocked by a startup failure.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.4) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.3...v0.6.4)
|
||||
|
||||
## 0.6.3 — 2026-10-04
|
||||
|
||||
- Configure partial dungeon parties and open-world life steal in module settings.
|
||||
- Download and update the game client without installing a server.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.3) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.2...v0.6.3)
|
||||
|
||||
## 0.6.2 — 2026-10-04
|
||||
|
||||
- Choose which item types the auction bot sells.
|
||||
- Module settings now offer translated controls and an enemy damage slider.
|
||||
- Failed server updates restore databases and files together.
|
||||
- Configure SQUID Playerbots and prevent conflicting bot systems.
|
||||
- Server packages must include a complete database schema check.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.2) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.1...v0.6.2)
|
||||
|
||||
## 0.6.1 — 2026-10-04
|
||||
|
||||
- PLAY launches only the client with the selected realmlist; starting the local server remains a separate action.
|
||||
- Server multipliers accept decimals typed with a dot or comma. Talent and rested experience descriptions now explain their actual behavior.
|
||||
- Added database and file checks, and Repair with backups and signed package verification. Unresolved schema damage is reported instead of guessed repairs.
|
||||
- Fixed character database rebuilds retaining migration history that could skip required SQL. Applied migration hash changes are now rejected.
|
||||
- Added optional simultaneous CoA and Wildcard worlds on Windows, with separate processes, ports and status indicators.
|
||||
- Server multipliers now accept decimals typed with a dot or comma.
|
||||
- Play launches only the game client without starting your local server.
|
||||
- Check database structure and repair server files with a safety backup.
|
||||
- Start CoA and Wildcard together from Settings.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.1) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.0...v0.6.1)
|
||||
|
||||
## 0.6.0 — 2026-10-03
|
||||
|
||||
- Added Simplified Chinese for the interface and all server and bot settings.
|
||||
- The closed game client now follows the selected CoA or Wildcard realm. Play checks the saved realm before launching; existing settings are preserved and backed up.
|
||||
- Fixed GitHub reports opening Windows Explorer instead of the default browser. Long reports use the clipboard fallback.
|
||||
- Fixed configuration snapshots created in the same millisecond overwriting each other during restore.
|
||||
- Added experimental Linux startup: persistent state uses the XDG data folder, Tailscale detection supports Linux, and a Wayland rendering workaround respects existing user settings.
|
||||
- Added experimental start, stop and status controls for manually prepared Docker servers, with private database networking and a remote console bound to localhost.
|
||||
- Linux extraction restores executable permissions for ELF binaries and scripts, and paths retain case-sensitive filesystem semantics.
|
||||
- The game client follows the realm selected in the Manager.
|
||||
- Configuration snapshots no longer overwrite each other.
|
||||
- Experimental Linux startup and Docker server controls.
|
||||
- Problem reports open in the default browser.
|
||||
- Simplified Chinese is available in the Manager.
|
||||
|
||||
### Availability
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.0) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.5.0...v0.6.0)
|
||||
|
||||
This release ships the Windows installer and signed updater assets. Linux support is a development preview, not a one-click installation flow. Docker installation/database setup, SQL operations and backups, updates, Wildcard realm profiles, and Wine/Proton client launching remain unfinished. Servers must be prepared manually and use Linux binaries built with the packaged configuration layout.
|
||||
## 0.5.0 — 2026-10-03
|
||||
|
||||
Server shutdown and starting-zone scaling issues require separate server releases and are not fixed by updating the Manager alone.
|
||||
- Imported servers get the module config files they lack.
|
||||
- Modules marked Soon stay greyed out.
|
||||
- The Bots page is hidden when the module is not on the server.
|
||||
- Updating the game client shows a progress bar on its button.
|
||||
- Switch between CoA and Wildcard while keeping separate characters and module settings.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.5.0) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.4.0...v0.5.0)
|
||||
|
||||
## 0.4.0 — 2026-10-02
|
||||
|
||||
- Added module cards with switches and settings.
|
||||
- Added searchable server settings and appearance and collection controls.
|
||||
- Added account deletion with confirmation.
|
||||
- Fixed update checks offering an already installed version.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.4.0) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.3.1...v0.4.0)
|
||||
|
||||
## 0.3.1 — 2026-10-01
|
||||
|
||||
- Added named realmlists and a switcher beside Play.
|
||||
- Added account management and a prefilled GitHub problem-report form.
|
||||
- Server updates continue when leaving the settings page.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.3.1) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.3.0...v0.3.1)
|
||||
|
||||
## 0.3.0 — 2026-10-01
|
||||
|
||||
- Download and update the game client through the Manager while preserving custom files.
|
||||
- Server updates are checked automatically and offered on Overview.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.3.0) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.2.0...v0.3.0)
|
||||
|
||||
## 0.2.0 — 2026-10-01
|
||||
|
||||
- Added companion creation progress and controls to stop creation, take bots offline or remove them.
|
||||
- Choose how many bots log in when the server starts.
|
||||
- Added a control to log out a chosen number of bots and reduce server load.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.2.0) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.1.6...v0.2.0)
|
||||
|
||||
## 0.1.6 — 2026-09-30
|
||||
|
||||
- Overview shows world speed.
|
||||
- Improved companion setup, including requests made while the server is stopped.
|
||||
- Expanded translated settings and connection guides.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.6) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.1.4...v0.1.6)
|
||||
|
||||
## 0.1.4 — 2026-09-30
|
||||
|
||||
- Sharing settings are reapplied before server startup.
|
||||
- Added a restart shortcut after enabling play with friends.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.4) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.1.3...v0.1.4)
|
||||
|
||||
## 0.1.3 — 2026-09-30
|
||||
|
||||
- The interface scales with the window.
|
||||
- Each friend connection mode shows the realmlist line to use.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.3) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.1.2...v0.1.3)
|
||||
|
||||
## 0.1.2 — 2026-09-30
|
||||
|
||||
- Manager updates download in the background and install when the app closes.
|
||||
- Missing module configuration files are created from the supplied defaults.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.2) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.1.1...v0.1.2)
|
||||
|
||||
## 0.1.1 — 2026-09-30
|
||||
|
||||
- Added translations throughout setup, server updates, backups, diagnostics and settings.
|
||||
- Added clearer errors when server packages are unavailable or a server cannot be reached.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.1) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.1.0...v0.1.1)
|
||||
|
||||
## 0.1.0 — 2026-09-30
|
||||
|
||||
- Initial Windows release: install or import a server and manage startup from one app.
|
||||
- Configure server and bot settings, manage accounts, create backups and restore saved data.
|
||||
- Launch the game client, set up sharing with friends and collect diagnostics.
|
||||
|
||||
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.0)
|
||||
Generated
+14
-3
@@ -491,7 +491,7 @@ dependencies = [
|
||||
|
||||
[[package]]
|
||||
name = "coa-core"
|
||||
version = "0.6.1"
|
||||
version = "0.6.21"
|
||||
dependencies = [
|
||||
"base64 0.22.1",
|
||||
"chrono",
|
||||
@@ -499,6 +499,7 @@ dependencies = [
|
||||
"ed25519-dalek",
|
||||
"fs4",
|
||||
"hex",
|
||||
"if-addrs",
|
||||
"num-bigint",
|
||||
"rand_core",
|
||||
"reqwest 0.12.28",
|
||||
@@ -519,7 +520,7 @@ dependencies = [
|
||||
|
||||
[[package]]
|
||||
name = "coa-release"
|
||||
version = "0.6.1"
|
||||
version = "0.6.21"
|
||||
dependencies = [
|
||||
"chrono",
|
||||
"coa-core",
|
||||
@@ -528,7 +529,7 @@ dependencies = [
|
||||
|
||||
[[package]]
|
||||
name = "coa-server-manager"
|
||||
version = "0.6.1"
|
||||
version = "0.6.21"
|
||||
dependencies = [
|
||||
"coa-core",
|
||||
"serde",
|
||||
@@ -1913,6 +1914,16 @@ dependencies = [
|
||||
"icu_properties",
|
||||
]
|
||||
|
||||
[[package]]
|
||||
name = "if-addrs"
|
||||
version = "0.15.0"
|
||||
source = "registry+https://github.com/rust-lang/crates.io-index"
|
||||
checksum = "c0a05c691e1fae256cf7013d99dad472dc52d5543322761f83ec8d47eab40d2b"
|
||||
dependencies = [
|
||||
"libc",
|
||||
"windows-sys 0.61.2",
|
||||
]
|
||||
|
||||
[[package]]
|
||||
name = "indexmap"
|
||||
version = "1.9.3"
|
||||
|
||||
+1
-1
@@ -3,7 +3,7 @@ resolver = "2"
|
||||
members = ["crates/coa-core", "crates/coa-release", "src-tauri"]
|
||||
|
||||
[workspace.package]
|
||||
version = "0.6.1"
|
||||
version = "0.6.21"
|
||||
edition = "2021"
|
||||
license = "AGPL-3.0-only"
|
||||
|
||||
|
||||
@@ -0,0 +1,104 @@
|
||||
# Urgent update hotfix
|
||||
|
||||
Deadline: 2026-10-06. This checkout starts at the exact v0.6.4 tag, commit
|
||||
6c771fa, and excludes the ongoing isolated-trial/recovery redesign.
|
||||
|
||||
The client accepts checksum compatibility only from a verified signed manifest and only
|
||||
for an Applied migration. It never updates the historical checksum, reruns historical
|
||||
SQL, or excuses a Running/Failed ledger row. A server package must explicitly list the
|
||||
verified published variants and append corrections under new migration IDs.
|
||||
|
||||
Current local evidence: the locked workspace tests passed, including 252 core tests
|
||||
run serially. Six frontend logic tests and the frontend production build passed.
|
||||
The hotfix runtime was tested against the exact signed candidate manifest on the marked
|
||||
CoA/Wildcard fixture. Both published repair checksums were accepted independently in
|
||||
both worlds, with zero migration executions, unchanged historical checksums, and unchanged
|
||||
account, character and inventory counts. The original ledger rows were restored after
|
||||
the test, and all fixture processes were stopped. A real Running or Failed repair row in
|
||||
either world was rejected before staging or creating a transaction, with unchanged world
|
||||
executable and installation metadata. Tests use independent hotfix metadata so experimental
|
||||
transaction formats are not confused with the 0.6.4 upgrade path. Windows journal writes also use flushed
|
||||
atomic replacement with long-path support. Changelog validation passed.
|
||||
|
||||
Additional guards implemented:
|
||||
|
||||
- Read migration history without creating its ledger before downloading or replacing files.
|
||||
- Reject missing journals, invalid identities, paths, hashes and inconsistent operations.
|
||||
Durable completed-cleanup markers distinguish interrupted pruning from a lost journal.
|
||||
- Preserve all backups while an update is unfinished or its journal is damaged.
|
||||
- Verify saved-file hashes and the complete database/configuration recovery point before
|
||||
stopping services or changing files/databases. New snapshots include configuration hashes;
|
||||
update journals bind their backup metadata to a hash.
|
||||
- Surface state-reading errors in Settings and disable applying until the disk state is
|
||||
successfully read. Checking again refreshes that state.
|
||||
- Verify every extracted SQL artifact before taking the update snapshot or replacing
|
||||
server files; missing files, invalid IDs, duplicate migrations and checksum disagreements
|
||||
reject the update early. SQL application repeats the integrity check immediately before use.
|
||||
- Count unapplied migrations in the active and secondary realms, counting shared auth once.
|
||||
Matching versions and files do not hide remaining database work. Preview reads history
|
||||
under the installation lock; a stopped database is temporarily started for inspection
|
||||
and stopped again when no game services are running.
|
||||
- Reread the disk state after every update/recovery attempt, including failed attempts and
|
||||
background updates. Unfinished or unreadable state blocks another application in the UI.
|
||||
- Acquire the installation lock before checking and deleting a backup.
|
||||
|
||||
Latest real-runtime test used the independently copied, doubly marked fixture
|
||||
`C:\games\coa-schema-fixture-chaos-20261005-v1` and signed candidate `0.261005.24`, manifest SHA-256
|
||||
`1284b1273815209c9621b6d173a2211bae316f33462ccbe8b578e53b8d26fb5b`.
|
||||
All 1748 SQL artifacts passed verification after authenticated archive extraction.
|
||||
Removing one repair record separately in CoA and Wildcard increased the pending count
|
||||
by exactly one; restoring its original record restored the original count. No migrations
|
||||
were executed, player counts were preserved and fixture services were stopped afterward.
|
||||
The source checkout remains uncommitted; these results are not an installer acceptance report.
|
||||
|
||||
Additional acceptance on 2026-10-06: a new independent installation/database copy at
|
||||
`C:\games\coa-schema-fixture-chaos-064-transition-20261006` received the authenticated
|
||||
published `0.261005.22` program files, original CRLF repair checksum, and a deliberately
|
||||
missing Wildcard table in both realms. The production hotfix update pipeline committed
|
||||
signed candidate `0.261005.24`, repaired both realms, passed schema checks and actual
|
||||
bundled-Python server startup, and preserved the selected account, character, item and
|
||||
inventory fields byte-for-byte. The fixture was stopped afterward. The harness explicitly
|
||||
instruments the launcher to prevent relay submissions and bind to localhost; this is not
|
||||
proof of packaged UI behavior or operating-system network containment.
|
||||
|
||||
Local installer `C:\games\source\manager-065-local-installer-20261006\CoA Server Manager_0.6.5_x64-setup.exe`
|
||||
has SHA-256 `520ee0391d923b92da0a20591e30006c048cdb60156275d7a829918bf1b77491`.
|
||||
Its updater signature and the published 0.6.4 installer's signature passed independent
|
||||
verification with the configured updater public key. Both executables extracted from
|
||||
their exact NSIS packages started, created responsive windows, and were stopped using
|
||||
an independent application/WebView profile. No installer was executed over a user's
|
||||
installation, and no UI update operation was exercised.
|
||||
|
||||
Legacy limitation: old 0.6.4 transaction copies and configuration snapshots without recorded
|
||||
hashes can be checked for presence and declared database hashes, but their original file
|
||||
contents cannot be authenticated retroactively. Missing copies block restoration. This
|
||||
hotfix does not claim that old unchecksummed copies received full integrity verification.
|
||||
|
||||
Remaining release requirements: reproduce the existing-user failures through the published
|
||||
0.6.4 interface, verify legacy unfinished transaction handling on real-runtime fixtures,
|
||||
and execute the exact installer over 0.6.4 in an isolated Windows environment with UI
|
||||
state/settings/server-list verification. Windows native UI automation is unavailable in
|
||||
this session. Packaged startup and signature checks do not satisfy that installer gate.
|
||||
No public release has been made.
|
||||
|
||||
The user subsequently exercised the packaged UI: candidate 0.261005.24 committed and
|
||||
both CoA and Wildcard were shown running. Repeat-check/restart acceptance is still pending.
|
||||
The screenshots exposed an older published package being offered after the local candidate
|
||||
was installed. Follow-up changes reject older packages before preview/database inspection
|
||||
and application and clear a cached offer after a failed recheck. All 253 core tests and
|
||||
seven frontend tests passed. The earlier installer hash above does not include this follow-up;
|
||||
a separately recorded revision is required. Native UI control was subsequently initialized
|
||||
through the deferred node_repl tool, then the user stopped automation with Escape and
|
||||
performed the UI check manually.
|
||||
|
||||
Another user repeat-check exposed the already installed launcher being offered again.
|
||||
The preview now verifies canonical launcher bytes against the current signed package,
|
||||
caches those bytes by SHA-256, and compares only recognized Manager transformations.
|
||||
The actual disposable fixture's repeat preview passed with all 104 files skipped and
|
||||
zero pending SQL. User edits, recorded custom content, and a package with different
|
||||
launcher bytes are not mistaken for that integration. All 254 core tests passed;
|
||||
the strengthened regression test and seven frontend tests also passed. The first
|
||||
preview of a managed launcher may download/extract its authenticated package to build
|
||||
the optional canonical cache. Earlier installer revisions do not include this fix.
|
||||
|
||||
Do not recommend deleting an installation or replacing its player databases.
|
||||
@@ -18,14 +18,14 @@ no console, no config files, no database tools. Tauri 2 + Rust + React.
|
||||
into **UPDATE**. Updates are authenticated (Ed25519), back up first, keep files you changed and can be rolled back.
|
||||
* **Backups.** Characters, accounts and settings on demand, automatically before every update; verify and restore
|
||||
from the app.
|
||||
* **CoA / Wildcard realms.** Choose the active realm on Overview. A server build with Wildcard support is required;
|
||||
* **CoA / Wildcard / Warcraft Reborn realms.** Choose the active realm on Overview. A server build supporting the selected realm is required;
|
||||
the first switch copies world data and creates an empty character database. Accounts are shared, characters and
|
||||
module settings are separate, and only one world runs. Switching a running server saves characters and restarts it.
|
||||
The closed client's saved realm follows this selection and is checked again before PLAY. If the client is open,
|
||||
the change is applied on the next launch through the Manager.
|
||||
CoA companions are unavailable on Wildcard; other optional modules are experimental. Backups include both realms,
|
||||
and database updates apply to both.
|
||||
See [realm profiles and validation](docs/WILDCARD.md).
|
||||
Bots are unavailable on Wildcard and Warcraft Reborn; other optional modules are experimental. Backups and
|
||||
database updates include every created realm. Simultaneous startup supports CoA + Wildcard only.
|
||||
See [realm profiles and validation](docs/WILDCARD.md) and [Warcraft Reborn](docs/WARCRAFT-REBORN.md).
|
||||
* **Companions (bots).** Fill the world with level-appropriate bots, see progress, stop spawning, take them offline,
|
||||
despawn N to relieve the server, and choose how many log in at server start.
|
||||
* **Realmlist switcher.** Keep named realmlists (for example *Solo* and *PTR*) and switch the game client between them from a
|
||||
@@ -57,6 +57,11 @@ Download the installer from the [Releases](https://github.com/Corfirean/coa-serv
|
||||
and run it. You need about 10 GB of free disk space for the server. The game client (about 43 GB) is separate: point the
|
||||
Manager at the one you have, or let it download one for you.
|
||||
|
||||
## Changelog
|
||||
|
||||
[Manager release history](CHANGELOG.md) · [Server release history](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md).
|
||||
Manager and server updates have separate version histories.
|
||||
|
||||
## Status
|
||||
|
||||
Phases 0–10 of the plan in [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) are done: foundation, import, start/stop,
|
||||
|
||||
@@ -0,0 +1,29 @@
|
||||
# TODO
|
||||
|
||||
## UI / UX
|
||||
- [x] **Предупреждение о несохранённых изменениях при переходе между вкладками (Unsaved Changes Guard / Modal)**:
|
||||
- Если у пользователя есть несохранённые изменения в настройках (`ModulesPage`, `SettingsPage` — сервер, боты и др.) и он переходит на другую вкладку (в боковом меню `Shell.tsx` или кнопками навигации), показывать pop-up диалог подтверждения.
|
||||
- Опции в диалоге:
|
||||
- **Сохранить (Save)** — сохранить внесённые изменения и перейти на выбранную страницу.
|
||||
- **Сбросить (Discard)** — отменить несохранённые изменения и перейти на выбранную страницу.
|
||||
- **Отмена (Cancel)** — остаться на текущей странице с сохранением введённых данных.
|
||||
- *Контекст:* Предотвратит случайную потерю настроек, когда пользователь меняет параметры модуля/сервера и сразу уходит на вкладку Overview для запуска сервера (см. [Issue #45](https://github.com/Corfirean/coa-server-manager/issues/45)).
|
||||
|
||||
## Сервер и стабильность
|
||||
- [x] **Автоподнятие сервера при падении (Auto-restart on crash) со счётчиком и расшифровкой крашей**:
|
||||
- **Настройка:** Чекбокс «Автоматически перезапускать сервер при падении» в настройках сервера / менеджера.
|
||||
- **Поведение автоподнятия:**
|
||||
- Перезапускать процесс сервера только если падение произошло внезапно (процесс завершился с ненулевым exit code, крашем или без команды от менеджера).
|
||||
- Если пользователь нажал кнопку «Стоп» (Stop Server), сервер останавливается полностью, автоподнятие не срабатывает.
|
||||
- Защита от бесконечного цикла крашей (Crash Loop Protection): если за короткий интервал (например, 2-3 минуты) сервер падает более 3-5 раз, автоподнятие временно прекращается, а в UI выводится критическое оповещение.
|
||||
- **Счётчик падений в интерфейсе:**
|
||||
- Рядом со статусом сервера (или в шапке/панели состояния) показывать бейдж со счётчиком крашей с момента старта (например: `Крашей: 2`).
|
||||
- При клике на счётчик открывать окно / модалку со списком последних падений с точным временем.
|
||||
- **Расшифровка причин краша (Crash Explanation Engine):**
|
||||
- *Как парсить и определять причину:*
|
||||
1. Читать свежий текстовый файл из `Core/Crashes/<hash>_worldserver.exe_[date].txt`.
|
||||
2. Смотреть `Exception code` (например, `C0000005` — нарушение доступа к памяти/access violation, `C0000420` — сработавший assert ядра, `C00000FD` — переполнение стека, `E06D7363` — исключение C++ / std::bad_alloc).
|
||||
3. При `C0000420` парсить блок `ASSERTION FAILED` (`Location`, `Function`, `Condition`).
|
||||
4. Анализировать последние строки `Core/Logs/Server.log` и `Errors.log` на критические маркеры (потеря соединения с MySQL, нехватка RAM/OOM, ошибка бинда портов).
|
||||
5. Проверять по встроенному словарю известных сигнатур (паттерны частых крашей с понятным описанием, например: «Сбой удаления объекта из сетки карты», «Ошибка запроса к базе данных», «Нехватка оперативной памяти»).
|
||||
- *Fallback:* Если сигнатура не опознана в словаре известных проблем, показывать краткую техническую выжимку (код исключения + сработавший ассерт или вершина Call Stack) и кнопку разворота полного текста крашлога / копирования.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Choose which item types the auction bot sells
|
||||
---
|
||||
Switch 15 item categories on or off and adjust listing frequency by quality. Labels and descriptions are translated into all six languages. Changes affect new listings; existing auctions remain.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Module settings now offer translated controls and an enemy damage slider
|
||||
---
|
||||
Configure scaling, auctions and enchantments with translated controls. Module switches no longer appear twice. Modules without settings hide their settings button; short lists need no search. New server builds support dungeon and raid damage from 25% to 200%.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Failed server updates restore databases and files together
|
||||
---
|
||||
Updates save a full backup and recover databases and files together. Interrupted SQL is not replayed. Checks cover Wildcard tables and every supported race/class pair, including existing characters. Unfinished updates block startup until recovered.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Configure partial dungeon parties and open-world life steal in module settings
|
||||
---
|
||||
Choose whether Dungeon Finder enters with the current party and enable open-world life steal with a healing percentage from 0 to 100. Available on server builds that support these options.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Configure SQUID Playerbots and prevent conflicting bot systems
|
||||
---
|
||||
The Bots tab shows translated settings for the active bot system. Bot module cards keep enable switches without duplicate settings. Enable one bot system at a time; the Manager checks manual config changes before starting the server. Recovery points also include the SQUID database when installed.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: players
|
||||
title: Download and update the game client without installing a server
|
||||
---
|
||||
Choose to host a server or connect to someone else's. Players joining a friend can download, update and launch the client, save the host's address and use the Manager without installing a local server.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Imported SquidBots servers warn before replacing their original binary
|
||||
---
|
||||
Imports explain that the original launcher and updater check the server binary hash. Updating that binary requires an explicit choice to keep or replace it.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: players
|
||||
title: Start your installed server or client without downloading an available update
|
||||
---
|
||||
Choose to update later and keep playing with your installed version. Interrupted server updates still require recovery before startup.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Install a server from a package on Linux, running in Docker (experimental)
|
||||
---
|
||||
Experimental. The Manager creates the database, imports the packaged baseline and starts the server in Docker containers. It needs a Linux server package and your own game data folder.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Linux Docker servers follow Settings, sharing and backups (experimental)
|
||||
---
|
||||
Experimental. Settings the Docker backend fixes are hidden, friends sharing and logs work, the game data folder can be changed, and the realm no longer shows offline after a start.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Linux: install from the install screen, play with Wine or Proton (experimental)
|
||||
---
|
||||
Experimental. The install screen offers Docker installs on Linux, realm profiles and the Play button work on a Docker server, and updates are not offered for it.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Finish a server update that was blocked by a startup failure
|
||||
---
|
||||
The Manager repairs the launcher import path and lets you retry startup for an already applied update. Successful validation finishes the update without replaying SQL or restoring old databases. Failure details are preserved and rollback remains available.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: SquidBots settings follow the options shipped by the module
|
||||
---
|
||||
New settings use the module's descriptions, groups, defaults and value limits while retaining existing translations. Unknown formats or invalid fields use built-in controls so the settings page remains available.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: SquidBots shows its bundled release and includes it in problem reports
|
||||
---
|
||||
The Bots and Modules pages and problem reports include the release identifiers. Imported repacks use their recorded bot revision; empty tags are hidden. The settings file's source commit is not presented as the build revision.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server updates accept verified published migration variants without rerunning them
|
||||
---
|
||||
Signed updates can recognise known published checksums without changing your migration history. Interrupted or failed SQL still requires recovery before retrying.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server updates replace older launchers adapted by the Manager for Wildcard
|
||||
---
|
||||
Updates recognize the Manager’s own realm and import adjustments even when older metadata still records the original launcher. New server binaries receive their matching launcher; genuine custom edits still require your decision.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server packages must include a complete database schema check
|
||||
---
|
||||
Release tools generate the expected database structure on an isolated copy of the signed base, verify all archive files and refuse packages without the schema check. Corrective SQL can restore missing Wildcard tables without replaying old updates.
|
||||
@@ -0,0 +1,8 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: The Auction House Bot card no longer asks for a character GUID
|
||||
---
|
||||
Turning the module and the seller on is enough: a server build with the automatic auction character creates its own account and character. The GUID field moved to the advanced settings.
|
||||
The buyer option hint no longer says it spends the auction character's gold.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Choose and remember the local network address friends use to connect
|
||||
---
|
||||
Select an adapter or custom IPv4 address when sharing on LAN. Your choice survives restarts and mode changes; unavailable addresses show a warning instead of silently switching adapters.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: The NPC Enchanter card explains how to place and remove the NPC
|
||||
---
|
||||
The card now shows the two commands: `.npc add 601015` where you stand, and `.npc delete` on the targeted NPC.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Older server packages cannot replace a newer installation
|
||||
---
|
||||
Update checks stop offering stale packages after an update. To undo an update, use its recovery point instead of applying an older server package.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Checking again no longer offers an already installed launcher update
|
||||
---
|
||||
The Manager recognizes its own launcher integration while still detecting user edits and changes in newer signed packages.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Large SQUID database imports have more time to finish on first startup
|
||||
---
|
||||
The Manager allows up to 45 minutes when SQUID Playerbots is enabled, covering its initial database import and bot creation. Ordinary server startup and shutdown keep their existing deadlines.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Update history conflicts are detected before server files change
|
||||
---
|
||||
Damaged update records block changes and remain visible. Recovery checks saved copies before restoring, and unfinished updates protect backups from deletion and cleanup.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Pending database updates remain visible when the server version matches
|
||||
---
|
||||
SQL files are checked before replacing server files. Update and recovery attempts refresh their saved status, including errors. Backup deletion cannot race with an update.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Diagnostic files with database checks stay readable after secrets are removed
|
||||
---
|
||||
Removing a line that mentioned a secret could break the JSON files in a diagnostic package. Secret values are now replaced instead, so the files stay valid.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: One button collects all diagnostics, including crashes and Windows crash records
|
||||
---
|
||||
Report a problem collects logs, crash reports and small dumps, Windows crash records, update journals and the running server programs in one file, then shows its folder. Crashes without a server crash report are no longer missing.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Problem reports go to the right project
|
||||
---
|
||||
Choose what the problem is about: Manager and other modules, CoA Companions, or SQUID Playerbots. The report opens in that project's GitHub page with the versions filled in. The bot system that is switched on is preselected.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Choose where backups are stored, for example on another drive
|
||||
---
|
||||
Backups can now live in any folder outside the server folder. Existing backups stay listed. A backups folder that you moved and linked from the old place also works again for updates.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Bot settings with a fixed list of values show a drop-down
|
||||
---
|
||||
SQUID bots 1.9 describes the chat language as a list of languages. The Manager shows it as a drop-down with names instead of a bare number.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: The bot dashboard loads completely and can be opened in the browser
|
||||
---
|
||||
The dashboard no longer fails on large pages, starts again after a crash left its history files empty, and its Open in the browser button works. With both realms started together the realm drop-down is hidden.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: A failing database update is no longer reported as "database not running"
|
||||
---
|
||||
An SQL error whose message contained the number 2003, such as an out-of-range value, was shown as "The database is not running". The real error is now shown.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Accounts of the SQUID bots are hidden from the Accounts list
|
||||
---
|
||||
The RNDBOT accounts that hold the random bots no longer fill the Accounts tab, and they cannot be renamed or deleted from there.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: A Dashboard tab shows what the SQUID bots are doing
|
||||
---
|
||||
With SQUID Playerbots on, the Dashboard tab downloads the dashboard release that matches your bots, starts it on this computer and shows it inside the Manager.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: A stopped server stays stopped after an update, unless you ask it to start
|
||||
---
|
||||
Updating no longer leaves a server running that was stopped before. Settings has a switch to start it afterwards, and the client card has one to open the game after a client update.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Checking for updates no longer fails with "Something went wrong" after a crash
|
||||
---
|
||||
A crash or power loss could leave a damaged status file that made every database start fail. The Manager now removes such files itself, still compares the files when the database is unavailable, and shows the real reason.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server updates no longer stop with "has a different checksum" on the Wildcard repair
|
||||
---
|
||||
Servers that applied one of the two published versions of the Wildcard table repair can now update to the other. Nothing in the database changes.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: A world server started from the coa-bots folder is recognised
|
||||
---
|
||||
The Manager no longer reports a port conflict when the world server runs from the coa-bots folder inside the server folder, and a failed update now says that undoing it can take several minutes.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Failed server startup after an update automatically restores the previous version
|
||||
---
|
||||
The Manager restores server files and databases, then checks the recovered server. If recovery cannot be confirmed, it preserves the recovery point and blocks further startup until the problem is resolved.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Windows update recovery preserves database procedures triggers and views
|
||||
---
|
||||
A verified copy of stopped MySQL restores all databases and accounts together. Interrupted restoration can be retried, and the replaced database directory is retained.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Custom races bot setting synchronizes Playerbots excluded race lists
|
||||
---
|
||||
The "Bots can be custom races" setting now configures AiPlayerbot.ExcludedBotRaces in playerbots.conf. Off excludes all added races (recommended), while on allows stable added races (experimental).
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Custom race client patches update to the latest races and appearances
|
||||
---
|
||||
The module card offers an upgrade for older patches. Archive downloads are verified before installation.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Custom races can be enabled and their client patches installed from Modules
|
||||
---
|
||||
Install the custom race client assets from the module card, then enable the module and restart the server.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Blocked updates identify database objects that prevent automatic recovery
|
||||
---
|
||||
Diagnostics include the complete list of unsupported database objects across the recovery point, helping resolve update failures without removing user data.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Background world servers no longer stop because the local console is closed
|
||||
---
|
||||
The Manager automatically disables the local interactive console before starting the world server. Its remote console remains available, and no manual configuration changes are needed.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Updates can follow signed channels that select a complete server release
|
||||
---
|
||||
The Manager checks the channel signature and downloads every package part from the same release. Existing installations continue using the previous download source until the new channel is published.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server updates check startup privately before allowing players to connect
|
||||
---
|
||||
Startup checks use temporary local ports. Original settings are restored before opening the server, and interrupted checks retain a recovery journal.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Local hosts can connect while sharing a server online
|
||||
---
|
||||
The Manager no longer replaces the realm's local address with its public address when Friends mode is enabled.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Updates repair missing database defaults from the verified release schema
|
||||
---
|
||||
Only missing literal defaults are restored when column properties match. Existing rows, custom defaults, types and nullability are preserved; unresolved incompatibilities still block the update.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server updates no longer replay module installation scripts on existing databases
|
||||
---
|
||||
Update packages contain incremental SQL only. Module table initialization and seed scripts remain available when preparing a clean installation, preventing existing content from being reset during updates.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Windows server updates are tested on a private copy before changing your installation
|
||||
---
|
||||
The Manager tests migrations and server startup using your databases and configurations. A failed rehearsal leaves the installed server unchanged and preserves a diagnostic report.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Server updates can require a tested combination of platform and installed version
|
||||
---
|
||||
Signed release metadata identifies core and module revisions, supported starting versions and database contracts. Incompatible packages are rejected before shutdown; changed schema contracts and incompatible databases block installation before migration.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Failed database checks keep a complete report after rollback
|
||||
---
|
||||
Schema errors show readable default values and save every detected difference for troubleshooting, including after the server is restored.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server and Bots settings open without a blank window
|
||||
---
|
||||
Opening settings no longer crashes the interface after loading. Unsaved changes can still be saved or discarded before leaving the page.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Unsaved settings are protected and crashed servers can restart automatically
|
||||
---
|
||||
The Manager asks before leaving unsaved settings. Optional automatic restart pauses after repeated crashes, and crash history explains common failures.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: players
|
||||
title: Players can install custom race patches when connecting to a friend
|
||||
---
|
||||
Install the custom race client patch directly from the Game client section without hosting a server.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Large server updates no longer repeatedly rewrite the recovery journal
|
||||
---
|
||||
Updates containing rebuilt navigation data now prepare all recovery copies before replacing files. Interrupted updates remain recoverable without rewriting the full journal for every file.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Normalize rehearsal server roots to prevent Windows path prefix errors
|
||||
---
|
||||
Server update rehearsals now canonicalize the installation root before collecting files, resolving a "prefix not found" error during rehearsal preparation on Windows.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: client
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Custom race client installation follows the current upstream release
|
||||
---
|
||||
The installer verifies the current race archives and includes the two additional MPQs. Legacy patch hashes remain available so upgrading never mistakes the old custom executable for an original launcher file.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Docker friend mode requests a restart when remote client support changes
|
||||
---
|
||||
Enabling remote CoA clients now requests a world restart even when the game ports were already open. Repeating the same unchanged setting does not request another restart.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Module cards show installed server revisions and the client race patch version
|
||||
---
|
||||
Module revisions come from the currently installed release metadata. The race card shows the client patch version separately; missing version metadata is reported honestly instead of showing a download version as installed.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server updates accept long Windows paths inside the private test server
|
||||
---
|
||||
Long SQL file paths no longer fail the folder safety check during update rehearsals. Files outside the server folder remain blocked.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Diagnostics record blocked startup requests and maintenance owner information
|
||||
---
|
||||
A start refused before the launcher runs is now logged with its reason. Exported diagnostics include the last recorded maintenance owner, while clearly distinguishing old metadata from a currently held operating-system lock.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Client race patches can be repaired and removed while preserving original files
|
||||
---
|
||||
Every overwritten client file gets an original backup. Switching preserves newer launcher files; checksums detect missing or replaced assets. Repair and removal are always available, with rollback if a file operation fails.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Checking an already installed server update no longer reports incompatibility
|
||||
---
|
||||
The installed release can be checked again even when its compatibility list only names earlier releases. Platform checks and protection against downgrades still apply.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Failed server startup shows service errors even when the launcher reported ready
|
||||
---
|
||||
Update rehearsal and startup failures include recent world, authentication and database error lines. Missing tables and late startup failures are visible directly in the error details, with secrets redacted.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: bots
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Disabling custom races for SQUID bots now excludes all nonstandard races
|
||||
---
|
||||
The standard-races preset keeps only the ten original playable races. High elves, worgen and other custom race IDs are excluded, and the displayed setting reads complete race IDs rather than matching number substrings.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Starting the server waits for update checks and identifies ongoing maintenance
|
||||
---
|
||||
Downloading an update manifest no longer blocks startup. A start waits up to 30 seconds for a check to finish; other active maintenance still blocks it safely and shows its operation, process and start time.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: bots
|
||||
type: changed
|
||||
audience: admins
|
||||
title: The experimental SQUID race preset follows the current race release
|
||||
---
|
||||
Custom-race bots now use the upstream supported-race preset, excluding Test Race, Skyborne and Darkfallen. The standard-races preset continues to exclude all custom races.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Already running MySQL is recognized before startup readiness checks
|
||||
---
|
||||
A verified MySQL listener replaces a stale or supervisor-only launcher record before startup. Existing databases are reused instead of waiting for a port owned by a different process from the same executable.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: New servers install the current stable build directly
|
||||
---
|
||||
A clean installation downloads the complete package of the selected stable release, including its prepared database. It no longer installs an old base and asks for a separate update. Missing or mismatched full packages stop installation before changing the destination.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: players
|
||||
title: Install the matching client patches for Grummle
|
||||
---
|
||||
Custom race installation includes the new Grummle appearance and voices while retaining the existing race assets. Older installations can still be safely switched off or removed.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Failed repairs restore the previous server after final verification errors
|
||||
---
|
||||
Errors after file replacement now undo the repair using its verified recovery point, including final file or database check errors. If recovery fails, the journal retains the cause and further server actions remain blocked.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Failed server updates show an error on the Overview screen
|
||||
---
|
||||
The error stays visible after the progress bar disappears, with technical details and a copy button. Recovery-state errors are shown there too.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Private update checks show preparation stages and stop failure details
|
||||
---
|
||||
Private-copy preparation reports checked and copied file counts, database tests and startup stages. Failed shutdown reports the server folder, remaining processes and launcher reason. Port conflicts identify the owning process and executable.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Repair recovery copies preserve all bundled database objects and accounts
|
||||
---
|
||||
Windows repairs now save a verified copy of stopped MySQL before changing server files or SQL. Recovery preserves procedures, triggers, views and database accounts as well as player rows.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Server checks report interrupted SQUID database imports
|
||||
---
|
||||
Check and Repair now report SQUID pending imports and missing bot character tables separately from package migrations. Interrupted imports retain their records and require verified database recovery.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Shutdown remains available when startup templates or database records are damaged
|
||||
---
|
||||
Stop uses existing shutdown settings instead of rendering startup templates. Missing or stale MySQL records are recovered only from the exact installed executable and its owned port; foreign processes are never adopted.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Successful server repairs no longer block later server actions
|
||||
---
|
||||
Repair verifies restored files before completing its recovery record. Older completed repair records are accepted only when every repaired file still matches its expected content.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Server updates apply migrations once after saving a recovery point
|
||||
---
|
||||
Updates no longer build and start a second full server copy. The Manager checks both realms, saves recovery, applies pending SQL once and verifies startup. Failed SQL or startup restores the recovery point. Full-copy upgrade testing remains a release task.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: changed
|
||||
audience: admins
|
||||
title: Older server versions update directly without installing intermediate packages
|
||||
---
|
||||
The Manager checks database history and applies missing SQL from the latest signed package. A version missing from the release test list no longer blocks the update. Unknown versions, interrupted migrations and downgrades remain blocked.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Update validation recognizes an already stopped server
|
||||
---
|
||||
Validation uses the same complete-server stop check as recovery instead of issuing redundant unconditional shutdown commands.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Older servers find a tested intermediate update instead of being blocked
|
||||
---
|
||||
When the latest release cannot update an older server directly, Manager offers a signed intermediate release from its compatibility matrix and explains how to continue to the latest version.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Update checks no longer download a server archive to compare its launcher
|
||||
---
|
||||
Manager recognizes its supported launcher edits against the signed file hash locally. Overlapping checks wait briefly for one another, and the private update copy checks combined program and database space before copying.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Recorded core SQL stays applied after old history tables are cleaned up
|
||||
---
|
||||
Existing core migration records are preserved in Manager history. Unknown legacy checksums remain explicitly unknown, and interrupted or changed migrations are still rejected.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Switching realms no longer repeats shared account database updates
|
||||
---
|
||||
Solo and Wildcard use one migration history for their shared account database. Previously applied records from either realm are recognized without running their SQL again.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: fixed
|
||||
audience: admins
|
||||
title: Update offers distinguish version support from database validation
|
||||
---
|
||||
An available version sequence no longer claims that every database state has been tested. Database compatibility is checked during the update.
|
||||
@@ -0,0 +1,7 @@
|
||||
---
|
||||
area: manager
|
||||
type: added
|
||||
audience: admins
|
||||
title: Warcraft Reborn can now be created and selected as a separate realm
|
||||
---
|
||||
Warcraft Reborn has separate characters and settings, shares accounts, and is included in backups, updates and database checks. A server build with Warcraft Reborn support is required.
|
||||
@@ -1,7 +1,6 @@
|
||||
# changelog.d
|
||||
|
||||
One small Markdown file per change that a player or a server owner would notice. They are collected from every CoA
|
||||
repository when a release is made. The rules and the file format are in `AGENTS.md` (section "Changelog") and, in full,
|
||||
One small Markdown file per change that a player or a server owner would notice. Server and Manager releases collect only their own shipped changes from immutable sources; their public histories are separate. The rules and the file format are in `AGENTS.md` (section "Changelog") and, in full,
|
||||
in https://github.com/Corfirean/coa-server-build/blob/main/changelog/GUIDE.md
|
||||
|
||||
This README is ignored by the collector.
|
||||
@@ -0,0 +1,200 @@
|
||||
[
|
||||
{
|
||||
"tag": "v0.6.22",
|
||||
"date": "2026-10-19T07:49:11Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.22",
|
||||
"body": "## Manager\r\n- Updated Custom Races client patches to 1.8, including Drakkin, Drakonid and updated racial abilities\r\n- Added updated race appearances and cursor addons\r\n- Existing client files are preserved when installing or removing race patches\r\n\r\nPrepared from commit 65df6604846d5492e40a6b08a797199478666e24. Installer and updater signature were verified before publication.\r\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.21",
|
||||
"date": "2026-10-16T12:11:35Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.21",
|
||||
"body": "## Manager\n- Older server versions update directly to the latest signed package without installing intermediate releases.\n- The published source-version list records release test coverage; a missing entry no longer blocks an older installation by itself.\n- Apply only missing database migrations, preserving recorded AzerothCore history and sharing account migration history between Solo and Wildcard.\n- Save one complete recovery point, apply SQL once and check the database schema, startup, account and character identities. Restore files and databases on failure.\n- Keep unknown imported versions, interrupted migrations, changed SQL checksums, downgrades and incompatible packages blocked.\n- Remove the nested per-update server rehearsal and recursive intermediate-package lookup.\n\nInstalling this Manager does not update your server automatically. Unknown third-party repacks still require a verified starting state; this release does not guess which unrecorded SQL was applied manually.\r\n\nValidation: 11 package-based scenarios passed against Server 0.261015.58, including the earliest base and a repeated current-version check. A separate direct 800006 -> 58 upgrade on an isolated copy preserved all 133 account and 3123 character identities. No client login or gameplay acceptance was performed.\n\r\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.19",
|
||||
"date": "2026-10-16T02:37:16Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.19",
|
||||
"body": "## Manager\n- Update checks no longer download a full server package just to verify the launcher\n- Concurrent update checks wait briefly for the current check instead of immediately reporting another operation\n- Update rehearsals check the combined space required for program files and databases before creating the private copy\n\nIncludes the signed intermediate upgrade path from v0.6.18 for older server installations.\n\nThis release updates the Manager only. Existing server files and databases are not changed by installing it.\r\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.18",
|
||||
"date": "2026-10-16T00:33:21Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.18",
|
||||
"body": "## CoA Server Manager 0.6.18\n\n- Fixed update checks blocking older server versions when a tested intermediate release is available\n- Manager now offers the required intermediate update automatically and explains how to continue to the latest stable version\n- Intermediate packages must match the signatures and manifest hashes recorded in the target release's compatibility matrix\n- Unsupported source errors now identify the installed version, target version and directly supported versions\n\nFor servers on **0.261011.800006**, Manager offers **0.261013.54** first. After it completes, check for updates again to install **0.261015.58**. Clear any manually entered Advanced package source to use automatic selection.\n\nThe server package and stable channel have not changed. Existing data follows the normal backup and verified update process.\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.17",
|
||||
"date": "2026-10-15T16:51:52Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.17",
|
||||
"body": "## CoA Server Manager 0.6.17 / Server 0.261015.58\n\n### Manager\n\n- New servers now install the current stable build directly, without installing 2.0 first\n- Fixed completed repairs leaving the server stuck in a maintenance state\n- Servers can now stop even when startup templates or MySQL process records are damaged\n- Repair now preserves database accounts, views, procedures and triggers, with improved rollback after failures\n- Interrupted SQUID database imports are now reported by Check and Repair\n- Update errors remain visible on Overview, with technical details and a copy button\n- Improved update preparation progress and diagnostics for shutdown failures and port conflicts\n- Updated Custom Races client patches to 1.7 while preserving existing race assets\n\n### Server\n\n- Integrated 34 CoA upstream commits\n- Updated Custom Races to 1.7, adding playable Grummle and their racial abilities\n- Updated SQUID Playerbots to 2.3.1\n- Added complete installation packages for the current server release\n- Improved shutdown recovery and startup configuration errors\n\n### Content scaling\n\n- Creature health settings are now respected while Content Scaling is enabled\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.16",
|
||||
"date": "2026-10-13T12:39:15Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.16",
|
||||
"body": "**Manager** (for server owners)\n- Added: Linux Docker servers follow Settings, sharing and backups (experimental). Experimental. Settings the Docker backend fixes are hidden, friends sharing and logs work, the game data folder can be changed, and the realm no longer shows offline after a start.\n- Added: Updates can follow signed channels that select a complete server release. The Manager checks the channel signature and downloads every package part from the same release. Existing installations continue using the previous download source until the new channel is published.\n- Added: Windows server updates are tested on a private copy before changing your installation. The Manager tests migrations and server startup using your databases and configurations. A failed rehearsal leaves the installed server unchanged and preserves a diagnostic report.\n- Added: Server updates can require a tested combination of platform and installed version. Signed release metadata identifies core and module revisions, supported starting versions and database contracts. Incompatible packages are rejected before shutdown; changed schema contracts and incompatible databases block installation before migration.\n- Added: Module cards show installed server revisions and the client race patch version. Module revisions come from the currently installed release metadata. The race card shows the client patch version separately; missing version metadata is reported honestly instead of showing a download version as installed.\n- Changed: Failed server startup after an update automatically restores the previous version. The Manager restores server files and databases, then checks the recovered server. If recovery cannot be confirmed, it preserves the recovery point and blocks further startup until the problem is resolved.\n\n----- next message -----\n\n**Manager** (for server owners) (cont.)\n- Fixed: Windows update recovery preserves database procedures triggers and views. A verified copy of stopped MySQL restores all databases and accounts together. Interrupted restoration can be retried, and the replaced database directory is retained.\n- Fixed: Custom races bot setting synchronizes Playerbots excluded race lists. The \"Bots can be custom races\" setting now configures AiPlayerbot.ExcludedBotRaces in playerbots.conf. Off excludes all added races (recommended), while on allows stable added races (experimental).\n- Fixed: Blocked updates identify database objects that prevent automatic recovery. Diagnostics include the complete list of unsupported database objects across the recovery point, helping resolve update failures without removing user data.\n- Fixed: Server updates check startup privately before allowing players to connect. Startup checks use temporary local ports. Original settings are restored before opening the server, and interrupted checks retain a recovery journal.\n- Fixed: Local hosts can connect while sharing a server online. The Manager no longer replaces the realm's local address with its public address when Friends mode is enabled.\n- Fixed: Updates repair missing database defaults from the verified release schema. Only missing literal defaults are restored when column properties match. Existing rows, custom defaults, types and nullability are preserved; unresolved incompatibilities still block the update.\n- Fixed: Server updates no longer replay module installation scripts on existing databases. Update packages contain incremental SQL only. Module table initialization and seed scripts remain available when preparing a clean installation, preventing existing content from being reset during updates.\n\n----- next message -----\n\n**Manager** (for server owners) (cont.)\n- Fixed: Failed database checks keep a complete report after rollback. Schema errors show readable default values and save every detected difference for troubleshooting, including after the server is restored.\n- Fixed: Large server updates no longer repeatedly rewrite the recovery journal. Updates containing rebuilt navigation data now prepare all recovery copies before replacing files. Interrupted updates remain recoverable without rewriting the full journal for every file.\n- Fixed: Normalize rehearsal server roots to prevent Windows path prefix errors. Server update rehearsals now canonicalize the installation root before collecting files, resolving a \"prefix not found\" error during rehearsal preparation on Windows.\n- Fixed: SQUID imports character tables first and reports slow database imports. SQUID prepares character tables before its large travel data. Startup shows each base import and identifies a failed import without starting the world server or replaying an incomplete migration.\n- Fixed: Docker friend mode requests a restart when remote client support changes. Enabling remote CoA clients now requests a world restart even when the game ports were already open. Repeating the same unchanged setting does not request another Line truncated
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.15",
|
||||
"date": "2026-10-11T23:10:59Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.15",
|
||||
"body": "## Fixes\n\n- Large server updates, including rebuilt maps, vmaps and mmaps, no longer rewrite the complete recovery journal for every file.\n- All recovery copies are prepared before replacing any server file. Interrupted updates still restore the previous files and remove newly created files only when their content matches the update.\n\nValidated by Windows and Linux CI, the full Manager test suite, and a regression covering power loss during file replacement and incomplete recovery-copy preparation.\n\nUpdate the Manager before installing the navigation refresh. Portable Characters and Portable Session Bridge are not included."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.14",
|
||||
"date": "2026-10-11T21:14:34Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.14",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.13",
|
||||
"date": "2026-10-11T14:03:44Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.13",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.12",
|
||||
"date": "2026-10-10T03:10:14Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.12",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.11",
|
||||
"date": "2026-10-10T03:05:20Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.11",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.10",
|
||||
"date": "2026-10-10T02:07:18Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.10",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.9",
|
||||
"date": "2026-10-10T01:50:51Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.9",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.8",
|
||||
"date": "2026-10-10T01:05:56Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.8",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.7",
|
||||
"date": "2026-10-08T04:59:31Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.7",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.6",
|
||||
"date": "2026-10-07T05:47:46Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.6",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.5",
|
||||
"date": "2026-10-06T06:17:21Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.5",
|
||||
"body": "# CoA Server Manager 0.6.5 / Server 0.261006.1\n\nUpdate CoA Server Manager to 0.6.5 first, then update the server. This server package requires Manager 0.6.5.\n\n## Server updates and recovery\n\n- Recognize known, signed historical migration checksums without rewriting migration history or replaying applied SQL.\n- Check migration history and SQL files before replacing server files. Interrupted or failed migrations still require recovery.\n- Preserve damaged update records and protect recovery points belonging to unfinished updates. Check saved copies before restoring them.\n- Refresh saved update status after update and recovery attempts, including failures.\n- Recognize launcher adjustments made by the Manager, including older Wildcard launchers. Custom edits still require a choice.\n- Stop offering an already installed launcher update after checking again.\n- Reject older server packages. Use the update's recovery point to undo an update.\n- Restore missing Wildcard card and specialization-cache tables through a new corrective migration, preserving existing tables and data.\n- Fix launcher integration imports when using the server's isolated Python runtime.\n\n## SQUID Playerbots\n\n- Include SQUID Playerbots v1.8.1 together with the matching core, launcher and Manager integration.\n- Provide translated bot settings, release information and controls for the active bot system. Prevent conflicting bot systems from starting together.\n- Include the SQUID database in recovery points when installed.\n- Keep servers with SQUID disabled independent of its database startup hooks.\n- Detect unfinished initial database imports instead of treating partially imported tables as complete.\n- Allow more time for large SQL imports and initial bot creation. The Manager startup deadline is up to 45 minutes when SQUID is enabled; ordinary startup deadlines are unchanged.\n- Preserve historical SQL files and migration history. Only new migrations are applied.\n- Require an explicit keep-or-replace decision when updating imported server binaries protected by their original launcher or updater.\n\n## Local candidate validation\n\nThe signed final package passed an update and startup of both CoA and Wildcard on a marked disposable installation. Selected account, character and inventory fields were preserved, historical migrations were skipped, and a repeated update check was clean. Fresh SQUID database import and repeated startup were checked using the same native binaries and SQL as the final package.\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.4",
|
||||
"date": "2026-10-05T09:22:40Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.4",
|
||||
"body": "Fixes server updates that failed to start with the repack's bundled Python runtime.\n\nIf an update is waiting for recovery, open Settings → Server updates and choose **Retry server startup**. Successful validation finishes the already applied update without replaying database migrations. Rollback remains available if validation fails.\n\n**Start without updating** and **Play without updating** let you use the installed server or client when a newer version is available. Interrupted server updates still require recovery.\n\n[Shared changelog](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.3",
|
||||
"date": "2026-10-04T22:41:10Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.3",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.2",
|
||||
"date": "2026-10-04T21:54:32Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.2",
|
||||
"body": "## Manager 0.6.2\n\n- Server Update and Repair now back up databases before changes and recover databases, files and version metadata together after a failed update.\n- Database checks detect missing Wildcard tables even when migration history says the SQL ran. New server packages include the expected full database schema.\n- Interrupted or failed SQL is not blindly replayed; unresolved recovery is reported before another update or server start.\n- Checks cover race/class starting data and existing character visibility.\n- Adds the bot and module settings included in the reviewed dependency, including SQUID settings and translated controls.\n- Includes the latest Docker database-access changes.\n\nInstall/update Manager first, then update the server package. Run Settings → Check files and database if an existing installation reports database problems. Already lost database rows require a backup; restoring table structure cannot recreate them.\n\nValidation: 233 core tests passed locally after merging current master; workspace check and frontend build passed. Release package verification used disposable MySQL and a signed server package.\r\n\n\nShared release changelog: https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md\n\r\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.1",
|
||||
"date": "2026-10-04T10:58:56Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.1",
|
||||
"body": "## Changes\n\n- PLAY launches only the game client with the selected realmlist. Use START SERVER separately for your local server.\n- Decimal server multipliers can be typed with either a dot or a comma.\n- Talent settings explain that the standard AzerothCore multiplier does not affect CoA talent points; rested experience settings describe accumulation correctly.\n- Added file/database checks and Repair with backups, verified official packages and reports of unresolved schema damage.\n- Fixed stale character migration history after rebuilding a character database and reject changed hashes of already applied migrations.\n- Added optional simultaneous CoA and Wildcard worlds on Windows, with separate processes, ports, logs and status indicators.\n\n## Notes\n\nRepair requires a stopped server and matching currently published packages. It preserves player data and settings; unsupported schema repairs are reported for corrective migrations.\n\nSimultaneous worlds require a compatible Wildcard server build. Existing Linux/Docker support remains experimental; simultaneous worlds are Windows-only.\n\nDownload the Windows installer below, or let an existing Manager installation update automatically. Server packages are updated separately.\r\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.6.0",
|
||||
"date": "2026-10-03T18:06:31Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.6.0",
|
||||
"body": "# CoA Server Manager changelog\r\n\r\n## 0.6.0 — 2026-10-03\r\n\r\n- Added Simplified Chinese for the interface and all server and bot settings.\r\n- The closed game client now follows the selected CoA or Wildcard realm. Play checks the saved realm before launching; existing settings are preserved and backed up.\r\n- Fixed GitHub reports opening Windows Explorer instead of the default browser. Long reports use the clipboard fallback.\r\n- Fixed configuration snapshots created in the same millisecond overwriting each other during restore.\r\n- Added experimental Linux startup: persistent state uses the XDG data folder, Tailscale detection supports Linux, and a Wayland rendering workaround respects existing user settings.\r\n- Added experimental start, stop and status controls for manually prepared Docker servers, with private database networking and a remote console bound to localhost.\r\n- Linux extraction restores executable permissions for ELF binaries and scripts, and paths retain case-sensitive filesystem semantics.\r\n\r\n### Availability\r\n\r\nThis release ships the Windows installer and signed updater assets. Linux support is a development preview, not a one-click installation flow. Docker installation/database setup, SQL operations and backups, updates, Wildcard realm profiles, and Wine/Proton client launching remain unfinished. Servers must be prepared manually and use Linux binaries built with the packaged configuration layout.\r\n\r\nServer shutdown and starting-zone scaling issues require separate server releases and are not fixed by updating the Manager alone.\r\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.5.0",
|
||||
"date": "2026-10-03T06:26:08Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.5.0",
|
||||
"body": "## CoA and Wildcard realm profiles\n\nChoose CoA or Wildcard on Overview. The first Wildcard switch creates a separate world and empty character database; accounts are shared. Only one world runs at a time. Switching a running server saves characters and restarts it, and returning to CoA restores its module settings.\n\n- Requires a server build and database migrations with Wildcard support. Existing destination databases or realm ID 2 are preserved and block automatic creation.\n- CoA companion bots are unavailable on Wildcard. Content Scaling and other optional modules remain experimental there.\n- Backups cover both realms; restores identify their realm. Server migrations update both realms and shared auth once.\n- Configuration switches support recovery after interruption.\n\nValidation: 178 Rust tests, frontend build and translation checks, native isolated-fixture creation/start/switch, full backup, restore and migration checks. Final real-clock Wildcard gameplay verification: four scenarios passed with zero failures and zero isolated reruns (first login, level rolls, skill-card rolls, stats). Module gameplay compatibility beyond those scenarios remains unverified.\n\nDownload the Windows installer below. Existing Manager installations receive the signed update automatically. [Details and demo](https://github.com/Corfirean/coa-server-manager/blob/v0.5.0/docs/WILDCARD.md).\r\n\r\n"
|
||||
},
|
||||
{
|
||||
"tag": "v0.4.0",
|
||||
"date": "2026-10-02T16:51:50Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.4.0",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.3.1",
|
||||
"date": "2026-10-01T11:44:28Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.3.1",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.3.0",
|
||||
"date": "2026-10-01T03:13:59Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.3.0",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.2.0",
|
||||
"date": "2026-10-01T00:58:01Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.2.0",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.1.6",
|
||||
"date": "2026-09-30T18:16:06Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.6",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.1.4",
|
||||
"date": "2026-09-30T15:04:30Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.4",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.1.3",
|
||||
"date": "2026-09-30T14:55:17Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.3",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.1.2",
|
||||
"date": "2026-09-30T11:06:53Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.2",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.1.1",
|
||||
"date": "2026-09-30T07:40:42Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.1",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
},
|
||||
{
|
||||
"tag": "v0.1.0",
|
||||
"date": "2026-09-30T07:03:22Z",
|
||||
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.1.0",
|
||||
"body": "See the assets to download the installer. Existing installations update themselves."
|
||||
}
|
||||
]
|
||||
Loaded 100 of 241 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user