Compare commits

...
Author SHA1 Message Date
Дмитрий 9c40fae8d6 Localize screenshot galleries and complete visible interface translations 2026-10-23 07:42:50 +05:00
Corfirean ff09d3d056 Translate public READMEs and guides into all Manager languages (#142) 2026-10-23 06:39:11 +05:00
Дмитрий ed2b1291cb Add localized TimeIsTime module card and settings 2026-10-23 06:12:50 +05:00
Дмитрий e033cfbc92 Merge branch 'fix/online-population-counts' of C:\games\source\manager-portable-characters into integrate/manager-071-fixes 2026-10-23 06:06:39 +05:00
Дмитрий 154fdfb0e9 Separate SQUID bots from advertised online players 2026-10-23 06:04:38 +05:00
Дмитрий 79e9e85fac Fix custom races transactions with linked addons on another volume 2026-10-23 05:43:57 +05:00
Corfirean dc05b2cd3c Record reviewed Manager 0.7.1 release notes 2026-10-22 11:00:19 +05:00
Дмитрий 8d2befd7f0 Update Custom Races client package to 1.8.3 for Manager 0.7.1 2026-10-22 10:41:52 +05:00
Дмитрий 8d9dc47fed Merge published documentation and shared changelog updates for 0.7.1 2026-10-22 09:37:33 +05:00
Corfirean 2e3f36d2fd docs: keep public guides and screenshots focused on users (#139) 2026-10-22 08:12:13 +05:00
Corfirean 8f39896f0c Publish released 0.7 player guides and screenshot gallery on master (#138) 2026-10-22 08:04:59 +05:00
github-actions[bot] 103c829539 Update published Manager changelog 2026-10-22 02:53:40 +00:00
Corfirean 20fb2391ed Record every published Manager version in its own changelog (#137) 2026-10-22 07:49:15 +05:00
Corfirean 43de03eada Keep imported upstream notes separate and read historical BOM fragments (#136) 2026-10-22 00:14:25 +05:00
Corfirean cda58cdcd1 Fix collecting the next published Manager changelog from its Git tag (#135) 2026-10-22 00:04:32 +05:00
163 changed files with 2858 additions and 1020 deletions

No files matched your search

+1 -1
View File
@@ -6,7 +6,7 @@ on:
pull_request:
paths: [tools/sync_history.py, tools/test_sync_history.py, changelog/history.json, .github/workflows/changelog.yml]
release:
types: [published, released]
types: [published, prereleased, released]
workflow_run:
workflows: [release]
types: [completed]
+17
View File
@@ -31,6 +31,10 @@ Optional: one short paragraph in plain English for the reader (at most 300 chara
## Shared build and release workflow
Every published Manager version, including a clearly marked Pre-release, belongs in this repository's
CHANGELOG.md and changelog/history.json. Its GitHub release notes use the same reviewed record.
Promotion updates that entry without duplicating it; Manager and server histories remain separate.
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).
@@ -47,3 +51,16 @@ Server promotion uses the persistent Windows PC and the shared workflow's verifi
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.
## Public documentation languages
Maintain the public README and every player/server-owner guide in all six Manager languages:
English, Russian, German, French, Spanish and Simplified Chinese. English stays at `README.md`
and the player-facing `docs/*.md`; translated READMEs use `README.<locale>.md`, with guides in
`docs/<locale>/` (`ru`, `de`, `fr`, `es`, `zh-CN`). Language switches open the same page.
When changing a public guide, update its counterparts in the same change. Write naturally for
players in each language rather than translating word for word. Keep steps, feature limits and
experimental Portable Characters warnings equivalent. Use actual UI labels; retain English labels
where the released UI falls back to English. English screenshots stay in `docs/screenshots/`; localized images use its `ru`, `de`, `fr`, `es` and `zh-CN` subfolders. Keep the interface and annotation language consistent with each guide.
The public guide index is `docs/README.md`; internal protocol specifications and audits are not
player guides. Keep canonical release histories in English and link to them instead of making copies.
+34
View File
@@ -4,8 +4,42 @@ Manager releases only. Updating the Manager does not update the server.
[Server changelog](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)
Published releases and previews. Pre-release entries do not change the stable update channel.
Dates follow GitHub publication (UTC); legacy records retain their archived dates. Newest releases first.
## 0.7.1 — 2026-10-22
Close the game, then open Modules → Custom Races → Repair Client Patch to update existing patches, or Install Client Patch for a new installation. Updating the Manager does not automatically replace game files or update your server.
**Portable Characters are experimental and may contain bugs.**
- Updated Custom Races client patches to the complete 1.8.3 package.
- Race patch installation now includes the hide-armor and talent-reset addons.
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.7.1) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.7.0...v0.7.1)
[Guides and screenshots](https://github.com/Corfirean/coa-server-manager/blob/master/docs/README.md)
## 0.7.0 — 2026-10-21
Portable transfers into Warcraft Reborn are not supported yet.
**Portable Characters are experimental and may contain bugs.**
- Keep portable characters and their saved versions in the Manager, and use them on compatible realms.
- Make an existing character portable from a connected realm.
- Browse public realms and see their connection details.
- Link an existing realm account or create one on hosts that allow it.
- Switch between CoA, Wildcard and Warcraft Reborn realm profiles on supported server builds.
- Adjust creature health for different locations and enemy types in Content Scaling.
- Switch Custom Races patches faster, with visible feedback while changes are applied.
- Handle Windows requests for administrator permission when launching the game.
[Release](https://github.com/Corfirean/coa-server-manager/releases/tag/v0.7.0) · [Source changes](https://github.com/Corfirean/coa-server-manager/compare/v0.6.22...v0.7.0)
[Player guides and screenshots](https://github.com/Corfirean/coa-server-manager/tree/d22ff09ac6fd7628aac14d90ec23f547cd9b4bf1/docs)
## 0.6.22 — 2026-10-19
- Updated Custom Races client patches to 1.8.
Generated
+3 -3
View File
@@ -586,7 +586,7 @@ dependencies = [
[[package]]
name = "coa-core"
version = "0.7.0"
version = "0.7.1"
dependencies = [
"base64 0.22.1",
"chrono",
@@ -634,7 +634,7 @@ dependencies = [
[[package]]
name = "coa-release"
version = "0.7.0"
version = "0.7.1"
dependencies = [
"chrono",
"coa-core",
@@ -643,7 +643,7 @@ dependencies = [
[[package]]
name = "coa-server-manager"
version = "0.7.0"
version = "0.7.1"
dependencies = [
"coa-control-proto",
"coa-core",
+1 -1
View File
@@ -4,7 +4,7 @@ members = ["crates/coa-core", "crates/coa-release", "crates/coa-registry-proto",
exclude = ["services/coa-registry", "services/coa-registry-e2e", "services/coa-coordinator", "services/coa-relay"]
[workspace.package]
version = "0.7.0"
version = "0.7.1"
edition = "2021"
license = "AGPL-3.0-only"
+84
View File
@@ -0,0 +1,84 @@
# CoA Server Manager
[English](README.md) · [Русский](README.ru.md) · **Deutsch** · [Français](README.fr.md) · [Español](README.es.md) · [简体中文](README.zh-CN.md)
**Portable Characters sind experimentell.** Die Funktion wird noch entwickelt und kann Fehler enthalten.
Eine Windows-Anwendung, mit der du deinen eigenen **Conquest of Azeroth**-Server auf Basis von AzerothCore mit wenigen Schritten einrichtest und betreibst. Konsole, manuelle Konfigurationsdateien und separate Datenbankprogramme sind dafür nicht nötig. Entwickelt mit Tauri 2, Rust und React.
![Dein Server im Überblick](docs/screenshots/de/overview.jpg)
## Funktionen
- **Portable Characters — experimentell.** Bewahre Charaktere samt gespeicherten Versionen im Manager auf und übernimm vorhandene Charaktere von Realms, auf die du Zugriff hast. [Zur Anleitung](docs/de/PORTABLE-CHARACTERS.md).
- **Realms entdecken.** Vergleiche öffentlich gelistete Realms nach Spielmodus, Höchststufe, Raten, Modulen und Spielerzahl.
- **Einfache Einrichtung.** Der Manager lädt ein signiertes Serverpaket herunter, prüft die Dateien, richtet die Datenbank ein und erstellt dein erstes Konto. Downloads lassen sich fortsetzen; vorhandene Server kannst du ebenfalls einbinden.
- **Starten, stoppen, spielen.** Steuere Datenbank, Auth- und Weltserver gemeinsam. Status, Laufzeit und Spielerzahl siehst du direkt. Beim Spielstart wird die passende Realmlist verwendet.
- **Spielclient verwalten.** Verwende deinen vorhandenen Client oder lade ihn über den Manager herunter: etwa 43 GB, fortsetzbar und dateiweise geprüft. Verwaltete Clients erhalten Update-Hinweise; selbst veränderte Dateien werden nur mit deiner Zustimmung ersetzt.
- **Serverupdates.** Der Manager sucht beim Start und alle fünf Minuten nach Updates. Ed25519-Signaturen schützen die Pakete. Vor dem Update wird eine Sicherung erstellt; eigene Änderungen bleiben erhalten und ein Rollback ist möglich.
- **Sicherungen.** Sichere Charaktere, Konten und Einstellungen bei Bedarf oder automatisch vor Updates. Prüfen und Wiederherstellen geht direkt in der Anwendung.
- **CoA, Wildcard und Warcraft Reborn.** Wähle den Realm unter Übersicht. Die Serverversion muss den gewählten Modus unterstützen. Beim ersten Wechsel entstehen eine eigene Welt und eine leere Charakterdatenbank. Konten werden geteilt, Charaktere und Moduleinstellungen bleiben getrennt. Ein laufender Server speichert die Charaktere und startet beim Wechsel neu. Schließe vorher den Client; bei geöffnetem Client wird die Realm-Auswahl erst beim nächsten Start über den Manager übernommen. Bots sind auf Wildcard und Warcraft Reborn nicht verfügbar; andere Zusatzmodule sind dort experimentell. Sicherungen und Datenbankupdates berücksichtigen alle angelegten Realms. CoA und Wildcard können gemeinsam laufen. [Wildcard](docs/de/WILDCARD.md) · [Warcraft Reborn](docs/de/WARCRAFT-REBORN.md).
- **Begleiter-Bots.** Erstelle Bots mit passender Stufe, verfolge den Fortschritt, pausiere die Erstellung oder melde Bots ab. Entferne bei Bedarf eine bestimmte Anzahl, um den Server zu entlasten, und lege die Zahl beim Serverstart fest.
- **Realmlists wechseln.** Speichere benannte Verbindungen wie Solo oder PTR und wähle sie neben der Spiel-Schaltfläche. Die zuvor verwendete Datei wird gesichert.
- **Konten und Einstellungen.** Verwalte Namen, Passwörter und Zugriffsrechte. Für Server und Bots gibt es verständliche Optionen und Voreinstellungen, außerdem eine Serverkonsole und eine Spielerliste mit Kontoverwaltung.
- **Module.** Aktiviere Zusatzfunktionen, öffne ihre Einstellungen oder die GitHub-Seite des jeweiligen Projekts.
- **Mit Freunden spielen.** Erreichbarkeit prüfen, Firewall und UPnP einrichten und Verbindungen über LAN, direkte Adressen oder private Netze/Tailscale vorbereiten. Anleitungen und ein Paket mit Verbindungsdaten helfen deinen Freunden beim Beitritt.
- **Probleme melden.** Bereite einen GitHub-Fehlerbericht mit automatisch eingetragenen Versionsangaben vor.
- **Managerupdates.** Sie werden im Hintergrund geladen und beim Schließen installiert. Deine Server werden dabei weder angehalten noch verändert.
- **Sprachen:** Englisch, Russisch, Deutsch, Französisch, Spanisch und vereinfachtes Chinesisch.
## Screenshots und Anleitungen
| Portable Characters — experimentell | Öffentliche Realms |
|---|---|
| ![Portable Characters](docs/screenshots/de/portable.jpg) | ![Öffentliche Realms](docs/screenshots/de/realms.jpg) |
| Begleiter | Sicherungen |
|---|---|
| ![Begleiter](docs/screenshots/de/bots.jpg) | ![Sicherungen](docs/screenshots/de/backups.jpg) |
[Zur Galerie](docs/de/SCREENSHOTS.md) · [Alle Anleitungen](docs/de/README.md). Die Galerie zeigt auch Einrichtung, Module, Spielclient, Verbindungen mit Freunden und die Übernahme eines vorhandenen Charakters.
## Installation
Lade das Installationsprogramm von der [Release-Seite](https://github.com/Corfirean/coa-server-manager/releases/latest) herunter und starte es. Für den Server brauchst du etwa 10 GB freien Speicher. Der Spielclient benötigt zusätzlich etwa 43 GB: Wähle einen vorhandenen Client oder lade ihn über den Manager.
## Änderungen
[Manager-Changelog](CHANGELOG.md) · [Server-Changelog](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md). Manager und Server haben getrennte Versionsverläufe. Ein Managerupdate aktualisiert nicht den Server.
## Projektstatus
**In aktiver Entwicklung.** Fehler sind weiterhin möglich. Wenn du ein Problem findest, [erstelle bitte ein Issue](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
### Bekannte Einschränkungen
- Der Ascension-Client 3.3.5 nimmt keine Zugangsdaten über die Kommandozeile an. Gib dein Passwort selbst ein oder verknüpfe ein bestehendes Konto.
- Windows schützt vertrauliche Daten mit DPAPI (`CryptProtectData`) und zusätzlicher Entropie zur Domänentrennung. Linux/macOS verwenden Dateien mit den Zugriffsrechten `0600`.
- Eine bestehende direkte TCP-Verbindung lässt sich nicht während der Sitzung auf einen Relay umstellen. Nach einem Verbindungsabbruch wird beim nächsten Beitritt automatisch auf die Ausweichroute zurückgegriffen.
- Für sichere entfernte Importe portabler Charaktere muss `CharacterDatabase.WorkerThreads = 1` bleiben; das ist der Standardwert.
## Entwicklung
```sh
npm install
cargo test --workspace
npx tsc --noEmit
node tools/check-i18n.mjs
npx vite
cargo build -p coa-server-manager
```
Die Befehle installieren Abhängigkeiten, führen Tests aus, prüfen Typen und Übersetzungen, starten die Browseransicht mit Testdaten und bauen die native Anwendung. Der Debug-Build verwendet `http://localhost:1420`.
Die Programmlogik liegt in `crates/coa-core`, Paket- und Signaturwerkzeuge in `crates/coa-release`, native Befehle in `src-tauri` und die Oberfläche in `src`.
`cargo run -p coa-core --example scan -- <folder>` prüft eine vorhandene Installation nur lesend. Verwende für Start-/Stopp-Tests ausschließlich eine entbehrliche Testkopie: `tools/make-fixture.ps1` erstellt `C:\games\coa-fixture` aus der unveränderten Paketdatenbank mit anderen Ports. Teste niemals an einem genutzten Server. `tests/e2e/cdp.mjs` steuert das echte Fenster über WebView2 mit `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9222`.
## Lizenz
Der Manager ist freie Software unter der [GNU AGPL v3.0](LICENSE), Kennung `AGPL-3.0-only`.
- Der installierte Server basiert auf einem öffentlichen [AzerothCore-Fork](https://github.com/Corfirean/azerothcore-wotlk-coa). Für von MaNGOS übernommene Teile gilt GPL-2.0-or-later, für eigene AzerothCore-Teile AGPL-3.0. [mod-coa-playerbots](https://github.com/Corfirean/mod-coa-playerbots) steht unter AGPL-3.0. Die exakten Quellstände stehen im Paketmanifest, damit der passende Quellcode auffindbar bleibt.
- Das mitgelieferte MySQL behält seine GPL-2.0-Lizenz; der Lizenztext liegt im Paket unter `Licenses`.
- Die Spieldaten in `Data` (`dbc`, `maps`, `vmaps`, `mmaps`) stammen aus dem Client des eingestellten Ascension-Realms Conquest of Azeroth. Sie fallen **nicht** unter die Lizenz des Managers.
+84
View File
@@ -0,0 +1,84 @@
# CoA Server Manager
[English](README.md) · [Русский](README.ru.md) · [Deutsch](README.de.md) · [Français](README.fr.md) · **Español** · [简体中文](README.zh-CN.md)
**Los personajes portátiles son una función experimental.** Sigue en desarrollo y puede contener errores.
Una aplicación para Windows con la que instalar y gestionar tu propio servidor de **Conquest of Azeroth**, basado en AzerothCore, en pocos pasos. No necesitas usar la consola, editar archivos de configuración a mano ni manejar programas de bases de datos. Creada con Tauri 2, Rust y React.
![Tu servidor de un vistazo](docs/screenshots/es/overview.jpg)
## Funciones
- **Personajes portátiles — experimental.** Guarda personajes y sus distintas versiones en el Manager, o convierte en portátil un personaje que ya tengas en un reino al que puedas acceder. [Ver la guía](docs/es/PORTABLE-CHARACTERS.md).
- **Buscador de reinos.** Compara reinos públicos por modo de juego, nivel máximo, multiplicadores, módulos y población.
- **Instalación sencilla.** Descarga un paquete de servidor firmado, comprueba los archivos, prepara la base de datos y crea tu primera cuenta. Las descargas se pueden reanudar. También puedes importar un servidor existente.
- **Iniciar, detener y jugar.** Controla conjuntamente la base de datos y los servidores de autenticación y mundo. Consulta su estado, tiempo de actividad y jugadores conectados. Al abrir el juego se utiliza la realmlist correcta.
- **Cliente de juego.** Usa el que ya tengas o descárgalo desde el Manager: unos 43 GB, con descarga reanudable y verificación de archivos. Los clientes gestionados reciben avisos de actualización; los archivos que hayas modificado solo se sustituyen con tu permiso.
- **Actualizaciones del servidor.** Se buscan al iniciar y cada cinco minutos. Los paquetes se verifican mediante firmas Ed25519, se crea una copia antes de actualizar, se conservan tus cambios y es posible volver atrás.
- **Copias de seguridad.** Guarda personajes, cuentas y ajustes cuando quieras o automáticamente antes de una actualización. Comprueba y restaura las copias desde la aplicación.
- **CoA, Wildcard y Warcraft Reborn.** Elige el reino en Resumen. La versión del servidor debe admitir el modo seleccionado. El primer cambio crea un mundo independiente y una base de personajes vacía. Las cuentas son compartidas; los personajes y los ajustes de módulos se mantienen separados. Si el servidor está encendido, guarda los personajes y se reinicia al cambiar. Cierra el cliente antes del cambio; si está abierto, el nuevo reino se aplicará la próxima vez que lo abras desde el Manager. No hay bots en Wildcard ni en Warcraft Reborn; los demás módulos opcionales son experimentales allí. Las copias y las actualizaciones cubren todos los reinos creados. CoA y Wildcard pueden funcionar a la vez. [Wildcard](docs/es/WILDCARD.md) · [Warcraft Reborn](docs/es/WARCRAFT-REBORN.md).
- **Bots compañeros.** Llena el mundo con bots de nivel adecuado, sigue su creación, ponla en pausa o desconecta los bots. Elimina una cantidad concreta para reducir la carga y decide cuántos se conectan al iniciar el servidor.
- **Cambio de realmlist.** Guarda conexiones con nombres como Solo o PTR y selecciónalas junto al botón de jugar. El archivo anterior se guarda antes de sustituirlo.
- **Cuentas y ajustes.** Gestiona nombres, contraseñas y permisos. Configura el servidor y los bots con opciones explicadas y ajustes predefinidos. También tienes una consola de servidor y una lista de jugadores con herramientas de cuentas.
- **Módulos.** Activa funciones adicionales, cambia sus ajustes o abre el repositorio de sus autores desde la misma página.
- **Jugar con amigos.** Comprueba si pueden acceder, configura el cortafuegos y UPnP, y prepara conexiones por LAN, dirección directa o red privada/Tailscale. Incluye guías y un paquete con los datos de conexión para compartir.
- **Informar de problemas.** Prepara un informe para GitHub con las versiones ya rellenadas.
- **Actualizaciones del Manager.** Se descargan en segundo plano y se instalan al cerrar la aplicación. No detienen ni modifican tus servidores.
- **Idiomas:** inglés, ruso, alemán, francés, español y chino simplificado.
## Capturas y guías
| Personajes portátiles — experimental | Reinos públicos |
|---|---|
| ![Personajes portátiles](docs/screenshots/es/portable.jpg) | ![Reinos públicos](docs/screenshots/es/realms.jpg) |
| Compañeros | Copias de seguridad |
|---|---|
| ![Compañeros](docs/screenshots/es/bots.jpg) | ![Copias de seguridad](docs/screenshots/es/backups.jpg) |
[Galería completa](docs/es/SCREENSHOTS.md) · [Todas las guías](docs/es/README.md). También encontrarás la instalación, los módulos, el cliente, las conexiones con amigos y cómo convertir un personaje existente en portátil.
## Instalación
Descarga el instalador desde la [página de versiones](https://github.com/Corfirean/coa-server-manager/releases/latest) y ejecútalo. Necesitas unos 10 GB libres para el servidor. El cliente se instala por separado y ocupa unos 43 GB: indica tu carpeta existente o descárgalo con el Manager.
## Historial de cambios
[Cambios del Manager](CHANGELOG.md) · [Cambios del servidor](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md). Sus versiones se siguen por separado. Actualizar el Manager no actualiza el servidor.
## Estado del proyecto
**En desarrollo activo.** Todavía puede haber errores. Si encuentras un problema, [abre una incidencia](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
### Limitaciones conocidas
- El cliente Ascension 3.3.5 no acepta credenciales por línea de comandos. Introduce la contraseña manualmente o vincula una cuenta existente.
- En Windows, los secretos se protegen con DPAPI (`CryptProtectData`) y entropía para separar dominios. Linux/macOS usan archivos con permisos `0600`.
- Una conexión TCP directa ya establecida no puede pasar a un relé a mitad de sesión. Tras una interrupción, la ruta alternativa se selecciona automáticamente en la siguiente conexión.
- Para importar personajes portátiles de forma remota con seguridad, mantén `CharacterDatabase.WorkerThreads = 1`, su valor predeterminado.
## Desarrollo
```sh
npm install
cargo test --workspace
npx tsc --noEmit
node tools/check-i18n.mjs
npx vite
cargo build -p coa-server-manager
```
Estos comandos instalan dependencias, ejecutan pruebas, comprueban tipos y traducciones, abren la interfaz en el navegador con datos de prueba y compilan la aplicación nativa. La versión de depuración utiliza `http://localhost:1420`.
La lógica está en `crates/coa-core`, las herramientas de empaquetado y firma en `crates/coa-release`, los comandos nativos en `src-tauri` y la interfaz en `src`.
`cargo run -p coa-core --example scan -- <folder>` inspecciona una instalación sin modificarla. Para probar el inicio y la parada, usa solo una copia desechable: `tools/make-fixture.ps1` crea `C:\games\coa-fixture` a partir de la base intacta del paquete y con puertos diferentes. No hagas estas pruebas en un servidor en uso. `tests/e2e/cdp.mjs` controla la ventana real mediante WebView2 con `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9222`.
## Licencia
El Manager es software libre bajo [GNU AGPL v3.0](LICENSE), identificador `AGPL-3.0-only`.
- El servidor instalado procede de un [fork público de AzerothCore](https://github.com/Corfirean/azerothcore-wotlk-coa). Las partes heredadas de MaNGOS usan GPL-2.0-or-later y las propias de AzerothCore, AGPL-3.0. [mod-coa-playerbots](https://github.com/Corfirean/mod-coa-playerbots) utiliza AGPL-3.0. El manifiesto de cada paquete indica los commits exactos para localizar el código fuente correspondiente.
- MySQL conserva su licencia GPL-2.0; el texto se incluye en la carpeta `Licenses` del paquete.
- Los datos de juego de `Data` (`dbc`, `maps`, `vmaps`, `mmaps`) se extrajeron del cliente del antiguo reino Ascension Conquest of Azeroth. **No** están cubiertos por la licencia del Manager.
+84
View File
@@ -0,0 +1,84 @@
# CoA Server Manager
[English](README.md) · [Русский](README.ru.md) · [Deutsch](README.de.md) · **Français** · [Español](README.es.md) · [简体中文](README.zh-CN.md)
**Les personnages portables sont une fonctionnalité expérimentale.** Elle est encore en développement et peut présenter des bugs.
Une application Windows pour installer et gérer votre propre serveur **Conquest of Azeroth**, basé sur AzerothCore, en quelques étapes. Pas besoin de console, de modifier les fichiers de configuration à la main ou d'utiliser un outil de base de données. L'application utilise Tauri 2, Rust et React.
![Votre serveur en un coup d'œil](docs/screenshots/fr/overview.jpg)
## Fonctionnalités
- **Personnages portables — expérimental.** Conservez vos personnages et leurs sauvegardes dans le Manager, ou rendez portable un personnage déjà présent sur un royaume auquel vous avez accès. [Voir le guide](docs/fr/PORTABLE-CHARACTERS.md).
- **Découverte des royaumes.** Comparez les royaumes publics selon leur mode de jeu, niveau maximal, taux de progression, modules et population.
- **Installation simplifiée.** Le Manager télécharge un paquet serveur signé, vérifie les fichiers, configure la base de données et crée votre premier compte. Les téléchargements peuvent reprendre après une interruption. Vous pouvez aussi importer un serveur existant.
- **Démarrer, arrêter, jouer.** Une commande suffit pour gérer la base de données et les serveurs d'authentification et de monde. L'état, la durée de fonctionnement et les joueurs connectés restent visibles. Le lancement du jeu utilise la bonne realmlist.
- **Gestion du client de jeu.** Utilisez votre client ou téléchargez-le depuis l'application : environ 43 Go, avec reprise et vérification des fichiers. Un client géré reçoit des mises à jour ; vos fichiers modifiés ne sont remplacés qu'avec votre accord.
- **Mises à jour du serveur.** Recherche au démarrage et toutes les cinq minutes, vérification des signatures Ed25519, sauvegarde préalable, conservation des modifications personnelles et possibilité de revenir en arrière.
- **Sauvegardes.** Enregistrez personnages, comptes et paramètres à la demande ou automatiquement avant les mises à jour. Vérifiez et restaurez les sauvegardes dans l'application.
- **CoA, Wildcard et Warcraft Reborn.** Choisissez le royaume dans Vue d'ensemble. La version du serveur doit prendre en charge le mode choisi. Le premier changement crée un monde distinct et une base de personnages vide. Les comptes sont partagés, mais personnages et réglages des modules restent séparés. Un serveur en cours d'exécution sauvegarde les personnages puis redémarre lors du changement. Fermez le client avant de changer de royaume ; s'il est ouvert, le choix prendra effet au prochain lancement depuis le Manager. Les bots sont indisponibles sur Wildcard et Warcraft Reborn ; les autres modules optionnels y sont expérimentaux. Sauvegardes et mises à jour couvrent tous les royaumes créés. CoA et Wildcard peuvent fonctionner ensemble. [Wildcard](docs/fr/WILDCARD.md) · [Warcraft Reborn](docs/fr/WARCRAFT-REBORN.md).
- **Bots compagnons.** Peuplez le monde avec des bots de niveau adapté, suivez leur création, mettez-la en pause ou déconnectez les bots. Retirez un nombre choisi de bots pour alléger le serveur et réglez combien se connectent au démarrage.
- **Changement de realmlist.** Enregistrez des connexions nommées, comme Solo et PTR, et choisissez-les à côté du bouton de jeu. Le fichier précédent est sauvegardé avant remplacement.
- **Comptes et réglages.** Gérez noms, mots de passe et droits d'accès. Configurez serveur et bots avec des options expliquées et des préréglages. Une console serveur et une liste des joueurs avec gestion des comptes sont également disponibles.
- **Modules.** Activez les fonctions supplémentaires, modifiez leurs réglages ou consultez leur projet GitHub depuis une même page.
- **Jouer avec des amis.** Vérifiez l'accessibilité du serveur, configurez pare-feu et UPnP, préparez une connexion en réseau local, directe ou via un réseau privé/Tailscale. Des guides et un paquet de connexion facilitent l'arrivée des amis.
- **Signalement des problèmes.** Préparez un rapport GitHub avec les versions déjà renseignées.
- **Mises à jour du Manager.** Téléchargées en arrière-plan, elles s'installent à la fermeture. Elles n'arrêtent pas vos serveurs et ne les modifient pas.
- **Langues :** anglais, russe, allemand, français, espagnol et chinois simplifié.
## Captures et guides
| Personnages portables — expérimental | Royaumes publics |
|---|---|
| ![Personnages portables](docs/screenshots/fr/portable.jpg) | ![Royaumes publics](docs/screenshots/fr/realms.jpg) |
| Compagnons | Sauvegardes |
|---|---|
| ![Compagnons](docs/screenshots/fr/bots.jpg) | ![Sauvegardes](docs/screenshots/fr/backups.jpg) |
[Galerie complète](docs/fr/SCREENSHOTS.md) · [Tous les guides](docs/fr/README.md). La galerie présente aussi l'installation, les modules, le client, les connexions entre amis et la création d'un personnage portable.
## Installation
Téléchargez et lancez l'installateur depuis les [publications GitHub](https://github.com/Corfirean/coa-server-manager/releases/latest). Prévoyez environ 10 Go libres pour le serveur. Le client de jeu est séparé et demande environ 43 Go : indiquez un dossier existant ou téléchargez-le avec le Manager.
## Historique des versions
[Changelog du Manager](CHANGELOG.md) · [Changelog du serveur](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md). Leurs versions sont suivies séparément : mettre à jour le Manager ne met pas à jour le serveur.
## État du projet
**En développement actif.** Des bugs restent possibles. Si vous rencontrez un problème, [ouvrez une issue](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
### Limites connues
- Le client Ascension 3.3.5 n'accepte pas les identifiants en ligne de commande. Saisissez votre mot de passe ou associez un compte existant.
- Windows protège les secrets avec DPAPI (`CryptProtectData`) et une entropie de séparation de domaine. Sous Linux/macOS, ils sont conservés dans des fichiers aux permissions `0600`.
- Une connexion TCP directe déjà établie ne peut pas basculer vers un relais en cours de session. Après une coupure, le repli automatique intervient à la connexion suivante.
- Pour importer à distance des personnages portables en sécurité, conservez `CharacterDatabase.WorkerThreads = 1`, la valeur par défaut.
## Développement
```sh
npm install
cargo test --workspace
npx tsc --noEmit
node tools/check-i18n.mjs
npx vite
cargo build -p coa-server-manager
```
Ces commandes installent les dépendances, exécutent les tests, contrôlent les types et les traductions, ouvrent l'interface dans le navigateur avec des données de test, puis compilent l'application native. En mode debug, celle-ci utilise `http://localhost:1420`.
La logique se trouve dans `crates/coa-core`, les outils de paquetage et de signature dans `crates/coa-release`, les commandes natives dans `src-tauri` et l'interface dans `src`.
`cargo run -p coa-core --example scan -- <folder>` inspecte une installation sans la modifier. Pour tester démarrage et arrêt, utilisez uniquement une copie jetable : `tools/make-fixture.ps1` crée `C:\games\coa-fixture` depuis la base intacte du paquet, avec des ports distincts. Ne testez jamais sur un serveur utilisé par des joueurs. `tests/e2e/cdp.mjs` pilote la véritable fenêtre via WebView2 avec `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9222`.
## Licence
Le Manager est un logiciel libre sous [GNU AGPL v3.0](LICENSE), identifiant `AGPL-3.0-only`.
- Le serveur installé provient d'un [fork public d'AzerothCore](https://github.com/Corfirean/azerothcore-wotlk-coa). Les parties héritées de MaNGOS relèvent de GPL-2.0-or-later et les parties propres à AzerothCore d'AGPL-3.0. [mod-coa-playerbots](https://github.com/Corfirean/mod-coa-playerbots) utilise AGPL-3.0. Les commits exacts figurent dans le manifeste de chaque paquet pour retrouver les sources correspondantes.
- MySQL conserve sa licence GPL-2.0 ; son texte est fourni dans le dossier `Licenses` du paquet.
- Les données de jeu dans `Data` (`dbc`, `maps`, `vmaps`, `mmaps`) proviennent du client de l'ancien royaume Ascension Conquest of Azeroth. Elles ne sont **pas** couvertes par la licence du Manager.
+4 -2
View File
@@ -1,5 +1,7 @@
# CoA Server Manager
**English** · [Русский](README.ru.md) · [Deutsch](README.de.md) · [Français](README.fr.md) · [Español](README.es.md) · [简体中文](README.zh-CN.md)
**Portable characters are experimental.** This feature is in active development and may contain bugs.
A Windows app that installs and runs your own **Conquest of Azeroth** server (AzerothCore) with a few clicks:
@@ -29,7 +31,7 @@ no console, no config files, no database tools. Tauri 2 + Rust + React.
the change is applied on the next launch through the Manager.
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).
See [Wildcard guide](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
@@ -58,7 +60,7 @@ no console, no config files, no database tools. Tauri 2 + Rust + React.
The full gallery also covers setup, modules, game clients, playing with friends and making an existing character portable.
[Browse the screenshot gallery](docs/SCREENSHOTS.md).
[Browse the screenshot gallery](docs/SCREENSHOTS.md) · [Player and server owner guides](docs/README.md).
## Install
+84
View File
@@ -0,0 +1,84 @@
# CoA Server Manager
[English](README.md) · **Русский** · [Deutsch](README.de.md) · [Français](README.fr.md) · [Español](README.es.md) · [简体中文](README.zh-CN.md)
**Переносимые персонажи — экспериментальная функция.** Она ещё развивается и может работать с ошибками.
Приложение для Windows, с которым можно установить и запустить свой сервер **Conquest of Azeroth** на базе AzerothCore за несколько шагов. Управляйте сервером через интерфейс, без консоли, ручного редактирования конфигов и отдельных программ для базы данных. Менеджер написан на Tauri 2, Rust и React.
![Главное окно менеджера](docs/screenshots/ru/overview.jpg)
## Возможности
- **Переносимые персонажи — экспериментально.** Храните персонажей и историю сохранений в менеджере, делайте переносимыми уже существующих персонажей с доступных вам реалмов. [Как это работает](docs/ru/PORTABLE-CHARACTERS.md).
- **Каталог реалмов.** Сравнивайте публичные серверы по режиму игры, максимальному уровню, рейтам, модулям и числу игроков.
- **Простая установка.** Менеджер скачивает подписанный пакет сервера, проверяет файлы, настраивает базу данных и создаёт первый аккаунт. Прерванную загрузку можно продолжить. Можно также подключить уже установленный сервер.
- **Запуск, остановка и игра.** Управляйте базой данных и обоими серверными процессами одной кнопкой. На главном экране видны состояние, время работы и игроки онлайн. Кнопка запуска игры выбирает нужный realmlist.
- **Игровой клиент.** Подключите свой клиент или скачайте его через менеджер — около 43 ГБ, с продолжением загрузки и проверкой файлов. Для управляемого клиента доступны обновления; ваши изменения заменяются только с вашего согласия.
- **Обновления сервера.** Проверка выполняется при запуске и каждые пять минут. Пакеты защищены подписью Ed25519; перед установкой создаётся резервная копия. Пользовательские изменения сохраняются, предусмотрен откат.
- **Резервные копии.** Сохраняйте персонажей, аккаунты и настройки вручную или автоматически перед обновлениями. Проверка и восстановление доступны в приложении.
- **CoA, Wildcard и Warcraft Reborn.** Выбирайте реалм в разделе «Обзор». Нужна серверная сборка с поддержкой выбранного режима. При первом переключении создаются отдельный мир и пустая база персонажей. Аккаунты общие, персонажи и настройки модулей раздельные. Переключение работающего сервера сохраняет персонажей и перезапускает его. Закройте клиент перед переключением; если он открыт, новый реалм будет выбран при следующем запуске через менеджер. Боты недоступны в Wildcard и Warcraft Reborn, остальные дополнительные модули там экспериментальны. Копии и обновления охватывают все созданные реалмы. Одновременно можно запускать CoA и Wildcard. [Гайд по Wildcard](docs/ru/WILDCARD.md) · [Warcraft Reborn](docs/ru/WARCRAFT-REBORN.md).
- **Компаньоны-боты.** Заселяйте мир ботами подходящего уровня, следите за созданием, приостанавливайте его, отключайте ботов или удаляйте нужное количество для снижения нагрузки. Можно задать число ботов при старте сервера.
- **Список подключений.** Сохраняйте несколько realmlist с понятными названиями, например Solo и PTR, и переключайте их рядом с кнопкой игры. Предыдущий файл сохраняется.
- **Аккаунты и настройки.** Управляйте именами, паролями и уровнями доступа. Настраивайте сервер и ботов через понятные параметры и готовые наборы; доступны консоль сервера и список игроков.
- **Модули.** Включайте дополнительные возможности, меняйте их настройки и переходите в репозитории авторов с одной страницы.
- **Игра с друзьями.** Проверка доступности, настройка брандмауэра и UPnP, подключение по локальной сети, напрямую или через частную сеть/Tailscale. Внутри есть пошаговые инструкции и пакет с данными подключения для друзей.
- **Сообщения об ошибках.** Менеджер помогает подготовить issue на GitHub и подставляет версии программ.
- **Обновление менеджера.** Загружается в фоне и устанавливается при закрытии приложения. Ваши серверы при этом не останавливаются и не изменяются.
- **Языки:** английский, русский, немецкий, французский, испанский и упрощённый китайский.
## Скриншоты и гайды
| Переносимые персонажи — экспериментально | Публичные реалмы |
|---|---|
| ![Переносимые персонажи](docs/screenshots/ru/portable.jpg) | ![Публичные реалмы](docs/screenshots/ru/realms.jpg) |
| Компаньоны | Резервные копии |
|---|---|
| ![Компаньоны](docs/screenshots/ru/bots.jpg) | ![Резервные копии](docs/screenshots/ru/backups.jpg) |
[Все скриншоты](docs/ru/SCREENSHOTS.md) · [Гайды для игроков и владельцев серверов](docs/ru/README.md). В галерее также показаны установка, модули, клиент, подключение друзей и создание переносимого персонажа.
## Установка
Скачайте установщик со страницы [релизов](https://github.com/Corfirean/coa-server-manager/releases/latest) и запустите его. Для сервера нужно около 10 ГБ свободного места. Клиент устанавливается отдельно и занимает около 43 ГБ: укажите существующую папку или скачайте его через менеджер.
## Что изменилось
[Ченджлог менеджера](CHANGELOG.md) · [Ченджлог сервера](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md). Это отдельные продукты с отдельной историей версий: обновление менеджера не обновляет сервер.
## Состояние проекта
**Проект активно развивается.** Ошибки ещё возможны. Если встретили проблему, [создайте issue](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
### Известные ограничения
- Клиент Ascension 3.3.5 не принимает логин и пароль через командную строку. Введите пароль вручную или привяжите существующий аккаунт.
- В Windows секреты защищены DPAPI (`CryptProtectData`) с отдельной энтропией домена. На Linux/macOS используются файлы с правами `0600`.
- Уже открытое прямое TCP-соединение нельзя переключить на ретранслятор без разрыва. Резервный маршрут выбирается при следующем подключении.
- Для безопасного удалённого импорта переносимых персонажей оставьте `CharacterDatabase.WorkerThreads = 1` — это значение по умолчанию.
## Разработка
```sh
npm install
cargo test --workspace
npx tsc --noEmit
node tools/check-i18n.mjs
npx vite
cargo build -p coa-server-manager
```
Команды устанавливают зависимости, запускают тесты, проверяют типы и переводы, открывают браузерный интерфейс с тестовыми данными и собирают нативное приложение. В отладочном режиме оно использует `http://localhost:1420`.
`crates/coa-core` содержит основную логику, `crates/coa-release` — упаковку и подписи, `src-tauri` — команды приложения, `src` — интерфейс.
Проверить существующую сборку без изменений можно командой `cargo run -p coa-core --example scan -- <folder>`. Для проверок запуска и остановки используйте только отдельную тестовую копию: `tools/make-fixture.ps1` создаёт `C:\games\coa-fixture` из чистой базы пакета, с другими портами. Не проводите такие проверки на сервере, которым пользуются игроки. `tests/e2e/cdp.mjs` управляет настоящим окном через WebView2 с `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9222`.
## Лицензия
Менеджер — свободное ПО под [GNU AGPL v3.0](LICENSE), идентификатор `AGPL-3.0-only`.
- Устанавливаемый сервер основан на [форке AzerothCore](https://github.com/Corfirean/azerothcore-wotlk-coa): части, унаследованные от MaNGOS, используют GPL-2.0-or-later, собственные части AzerothCore — AGPL-3.0. Модуль [mod-coa-playerbots](https://github.com/Corfirean/mod-coa-playerbots) использует AGPL-3.0. Точные коммиты записываются в манифест пакета, чтобы можно было найти соответствующий исходный код.
- MySQL распространяется по собственной лицензии GPL-2.0; её текст находится в папке `Licenses` пакета.
- Данные игры в `Data` (`dbc`, `maps`, `vmaps`, `mmaps`) извлечены из клиента закрытого реалма Ascension Conquest of Azeroth. Лицензия менеджера на них **не распространяется**.
+84
View File
@@ -0,0 +1,84 @@
# CoA Server Manager
[English](README.md) · [Русский](README.ru.md) · [Deutsch](README.de.md) · [Français](README.fr.md) · [Español](README.es.md) · **简体中文**
**便携角色是一项实验性功能。** 目前仍在开发中,使用时可能遇到问题。
这是一款 Windows 应用,帮助你用几个简单步骤搭建和管理自己的 **Conquest of Azeroth** 服务器,服务端基于 AzerothCore。日常操作不需要使用控制台、手动修改配置文件或单独操作数据库。应用采用 Tauri 2、Rust 和 React 开发。
![服务器概览](docs/screenshots/zh-CN/overview.jpg)
## 主要功能
- **便携角色(实验性)。** 在管理器中保存角色及其历史存档,也可以将有权访问的服务器上的现有角色转换为便携角色。[查看使用指南](docs/zh-CN/PORTABLE-CHARACTERS.md)。
- **查找服务器。** 浏览公开服务器,对比游戏模式、等级上限、倍率、模块和在线人数。
- **轻松安装。** 下载带签名的服务端安装包,逐一校验文件,配置数据库并创建首个账号。下载支持断点续传,也可以导入已有服务器。
- **启动、停止和进入游戏。** 一处控制数据库、认证服务和世界服务,随时查看运行状态、运行时间和在线玩家。启动游戏时会自动使用对应的 realmlist。
- **管理游戏客户端。** 指定现有客户端,或通过管理器下载约 43 GB 的客户端。下载可以续传,文件会经过校验。受管理的客户端可以检查更新;自行修改的文件只有在你同意后才会被替换。
- **更新服务器。** 应用启动时及之后每五分钟检查一次更新。安装包通过 Ed25519 签名验证,更新前自动备份,保留用户修改,并支持回滚。
- **备份与恢复。** 手动备份角色、账号和设置,或在更新前自动备份。在应用中即可校验和恢复。
- **CoA、Wildcard 和 Warcraft Reborn。** 在概览中选择服务器模式,服务端版本必须支持所选模式。首次切换会创建独立的世界数据库和空的角色数据库。各模式共用账号,角色和模块设置相互独立。运行中切换会先保存角色,再重启服务器。切换前请关闭客户端;如果客户端仍开着,新选择会在下次通过管理器启动游戏时生效。Wildcard 和 Warcraft Reborn 不支持机器人,其他可选模块在这两种模式下也属于实验性支持。备份和数据库更新涵盖所有已创建的模式。目前支持 CoA 与 Wildcard 同时运行。[Wildcard 指南](docs/zh-CN/WILDCARD.md) · [Warcraft Reborn 指南](docs/zh-CN/WARCRAFT-REBORN.md)。
- **伙伴机器人。** 创建等级合适的机器人并查看进度,暂停创建、让机器人下线,或移除指定数量以减轻服务器负担。也可以设置开服时登录的机器人数量。
- **切换 realmlist。** 为不同连接保存名称,例如 Solo 和 PTR,在进入游戏按钮旁直接切换。替换前会保存原文件。
- **账号和设置。** 管理账号名称、密码和权限,通过说明清楚的选项及预设调整服务器和机器人。还提供世界服务器控制台,以及带账号管理功能的玩家列表。
- **模块管理。** 在同一页面启用可选功能、调整设置,或打开相应项目的 GitHub 页面。
- **好友联机。** 检查服务器是否可达,配置防火墙和 UPnP,支持局域网、直接连接及私有网络/Tailscale。应用提供分步说明,还能准备可分享的连接资料包。
- **报告问题。** 帮你准备 GitHub 问题报告,并自动填写版本信息。
- **管理器自身更新。** 在后台下载,关闭应用时安装。更新管理器不会停止或修改你的服务器。
- **支持语言:** 英语、俄语、德语、法语、西班牙语和简体中文。
## 截图与指南
| 便携角色(实验性) | 公开服务器 |
|---|---|
| ![便携角色](docs/screenshots/zh-CN/portable.jpg) | ![公开服务器](docs/screenshots/zh-CN/realms.jpg) |
| 伙伴机器人 | 备份 |
|---|---|
| ![伙伴机器人](docs/screenshots/zh-CN/bots.jpg) | ![备份](docs/screenshots/zh-CN/backups.jpg) |
[查看完整截图](docs/zh-CN/SCREENSHOTS.md) · [玩家与服主指南](docs/zh-CN/README.md)。图库还展示了初始设置、模块、客户端、朋友联机,以及将现有角色转换为便携角色的流程。
## 安装
从 [GitHub 发布页](https://github.com/Corfirean/coa-server-manager/releases/latest)下载安装程序并运行。服务器约需 10 GB 可用空间。游戏客户端单独安装,约占 43 GB;你可以指定已有客户端目录,也可以交给管理器下载。
## 更新记录
[管理器更新记录](CHANGELOG.md) · [服务器更新记录](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)。两者的版本和更新记录分别维护。更新管理器不会同时更新服务器。
## 项目状态
**正在积极开发中。** 仍可能存在问题。如果遇到故障,请[提交 issue](https://github.com/Corfirean/coa-server-manager/issues/new/choose)。
### 已知限制
- Ascension 3.3.5 客户端不支持通过命令行传入账号和密码。请自行输入密码,或关联现有账号。
- Windows 使用 DPAPI(`CryptProtectData`)及用于域隔离的额外熵来保护机密数据。Linux/macOS 使用权限为 `0600` 的文件。
- 已建立的直连 TCP 会话无法在不中断连接的情况下切换至中继。连接中断后,会在下一次加入服务器时自动尝试备用路径。
- 为保证远程导入便携角色的安全,请保留默认设置 `CharacterDatabase.WorkerThreads = 1`。
## 开发
```sh
npm install
cargo test --workspace
npx tsc --noEmit
node tools/check-i18n.mjs
npx vite
cargo build -p coa-server-manager
```
以上命令依次安装依赖、运行测试、检查类型与翻译、启动使用模拟数据的浏览器界面,以及编译原生应用。调试版应用连接 `http://localhost:1420`。
`crates/coa-core` 存放核心逻辑,`crates/coa-release` 提供打包和签名工具,`src-tauri` 处理原生命令,`src` 存放界面代码。
`cargo run -p coa-core --example scan -- <folder>` 可以只读检查现有安装。启动和停止测试必须使用可丢弃的独立副本:`tools/make-fixture.ps1` 会从安装包的原始数据库创建 `C:\games\coa-fixture`,并使用不同端口。不要在正在供玩家使用的服务器上进行此类测试。`tests/e2e/cdp.mjs` 可通过 WebView2 控制真实窗口,需设置 `WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS=--remote-debugging-port=9222`。
## 许可
管理器是自由软件,采用 [GNU AGPL v3.0](LICENSE),标识为 `AGPL-3.0-only`。
- 所安装的服务器来自公开的 [AzerothCore 分支](https://github.com/Corfirean/azerothcore-wotlk-coa)。继承自 MaNGOS 的部分采用 GPL-2.0-or-later,AzerothCore 自有部分采用 AGPL-3.0。[mod-coa-playerbots](https://github.com/Corfirean/mod-coa-playerbots) 采用 AGPL-3.0。每个安装包的清单都记录了准确的提交版本,便于查找对应源码。
- 随附的 MySQL 保留其 GPL-2.0 许可,许可文本位于安装包的 `Licenses` 目录。
- `Data` 中的游戏数据(`dbc`、`maps`、`vmaps`、`mmaps`)提取自已关闭的 Ascension Conquest of Azeroth 服务器客户端,**不属于**管理器许可的授权范围。
@@ -0,0 +1,7 @@
---
area: manager
type: changed
audience: players
title: Custom Races client patches now use the latest complete package
---
Install or repair Custom Races client patches from the Modules page to get the updated package, including its latest appearance fixes and login screen artwork.
@@ -0,0 +1,7 @@
---
area: manager
type: fixed
audience: players
title: More character and server browser controls now use your selected language
---
Completed missing German, French, Spanish and Simplified Chinese labels and improved Chinese font support.
@@ -0,0 +1,7 @@
---
area: manager
type: fixed
audience: admins
title: Online player counts correctly separate random bots from players
---
The server browser and overview now count SQUID random bots as bots, using the server's configured bot account prefix.
@@ -0,0 +1,7 @@
---
area: manager
type: fixed
audience: admins
title: Custom races work with shared addon folders on another drive
---
Installing, switching and removing custom races now supports linked addon folders on another drive, including recovery after an interrupted operation.
@@ -0,0 +1,7 @@
---
area: manager
type: added
audience: admins
title: Configure the day and night cycle from the module settings
---
TimeIsTime now has a module card, an on/off switch and settings translated into all six Manager languages.
+53 -1
View File
@@ -112,7 +112,15 @@
"Corfirean/coa-server-manager:20261016-preserve-core-migration-history.md",
"Corfirean/coa-server-manager:20261016-shared-auth-migration-history.md",
"Corfirean/coa-server-manager:20261016-update-compatibility-wording.md",
"Corfirean/coa-server-manager:20261018-custom-races-client.md"
"Corfirean/coa-server-manager:20261018-custom-races-client.md",
"Corfirean/coa-server-manager:20261019-portable-stop-diagnostics.md",
"Corfirean/coa-server-manager:20261019-remote-character-class-names.md",
"Corfirean/coa-server-manager:20261020-client-elevation.md",
"Corfirean/coa-server-manager:20261021-custom-races-switching.md",
"Corfirean/coa-server-manager:20261021-portable-experimental.md",
"Corfirean/coa-server-manager:20261021-scaling-health-settings.md",
"Corfirean/coa-server-manager:20261021-warcraft-reborn-realm.md",
"Corfirean/coa-server-manager:20261022-custom-races-client.md"
],
"releases": [
{
@@ -571,6 +579,50 @@
"Existing client files are preserved when installing or removing race patches"
],
"compare": "https://github.com/Corfirean/coa-server-manager/compare/v0.6.21...v0.6.22"
},
{
"tag": "v0.7.0",
"version": "0.7.0",
"date": "2026-10-21",
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.7.0",
"notes": [
"Keep portable characters and their saved versions in the Manager, and use them on compatible realms",
"Make an existing character portable from a connected realm",
"Browse public realms and see their connection details",
"Link an existing realm account or create one on hosts that allow it",
"Switch between CoA, Wildcard and Warcraft Reborn realm profiles on supported server builds",
"Adjust creature health for different locations and enemy types in Content Scaling",
"Switch Custom Races patches faster, with visible feedback while changes are applied",
"Handle Windows requests for administrator permission when launching the game"
],
"commit": "d22ff09ac6fd7628aac14d90ec23f547cd9b4bf1",
"experimentalFeatures": [
"portable-characters"
],
"compare": "https://github.com/Corfirean/coa-server-manager/compare/v0.6.22...v0.7.0",
"notice": "Portable transfers into Warcraft Reborn are not supported yet.",
"links": [
"[Player guides and screenshots](https://github.com/Corfirean/coa-server-manager/tree/d22ff09ac6fd7628aac14d90ec23f547cd9b4bf1/docs)"
]
},
{
"tag": "v0.7.1",
"version": "0.7.1",
"date": "2026-10-22",
"url": "https://github.com/Corfirean/coa-server-manager/releases/tag/v0.7.1",
"notes": [
"Updated Custom Races client patches to the complete 1.8.3 package",
"Race patch installation now includes the hide-armor and talent-reset addons"
],
"commit": "8d2befd7f08532b2cb9e0bf2f973bb631f3890e5",
"experimentalFeatures": [
"portable-characters"
],
"compare": "https://github.com/Corfirean/coa-server-manager/compare/v0.7.0...v0.7.1",
"notice": "Close the game, then open Modules → Custom Races → Repair Client Patch to update existing patches, or Install Client Patch for a new installation. Updating the Manager does not automatically replace game files or update your server.",
"links": [
"[Guides and screenshots](https://github.com/Corfirean/coa-server-manager/blob/master/docs/README.md)"
]
}
]
}
+196 -35
View File
@@ -14,25 +14,12 @@ use crate::download::Cancel;
use crate::error::{Error, Result};
use crate::fsx;
pub const CLIENT_VERSION: &str = "1.8";
pub const CLIENT_VERSION: &str = "1.8.3";
pub const MANIFEST_FILENAME: &str = "custom_races_patch_manifest.txt";
pub const ARCHIVES: &[(&str, &str)] = &[
(
"CoA-Custom-1.6-main-20261012-4dd3a4ec.zip",
"https://github.com/ilusixn/azerothcore-wotlk-coa/releases/download/coa-custom-1.6/CoA-Custom-1.6-main-20261012-4dd3a4ec.zip",
),
(
"CoA-Custom-1.6-client-part1.zip",
"https://github.com/ilusixn/azerothcore-wotlk-coa/releases/download/coa-custom-1.6/CoA-Custom-1.6-client-part1.zip",
),
(
"CoA-Custom-1.6-client-part2.zip",
"https://github.com/ilusixn/azerothcore-wotlk-coa/releases/download/coa-custom-1.6/CoA-Custom-1.6-client-part2.zip",
),
(
"CoA-Custom-1.8-Client.zip",
"https://github.com/ilusixn/azerothcore-wotlk-coa/releases/download/coa-custom-1.8/CoA-Custom-1.8-Client.zip",
),
("CoA-Custom-1.8.3-Client-1.zip", "https://github.com/ilusixn/azerothcore-wotlk-coa/releases/download/coa-custom-1.8.3/CoA-Custom-1.8.3-Client-1.zip"),
("CoA-Custom-1.8.3-Client-2.zip", "https://github.com/ilusixn/azerothcore-wotlk-coa/releases/download/coa-custom-1.8.3/CoA-Custom-1.8.3-Client-2.zip"),
("CoA-Custom-1.8.3-Client-3.zip", "https://github.com/ilusixn/azerothcore-wotlk-coa/releases/download/coa-custom-1.8.3/CoA-Custom-1.8.3-Client-3.zip"),
];
pub const RACE_MPQS: &[&str] = &[
@@ -62,11 +49,19 @@ pub const RACE_MPQS: &[&str] = &[
"patch-ZZV.MPQ",
"patch-ZZW.MPQ",
"patch-ZZZ.MPQ",
"patch-ZK.MPQ",
"patch-ZZX.MPQ",
"patch-ZZZC.MPQ",
"patch-ZZZD.MPQ",
];
pub const RACE_ADDONS: &[&str] = &[
"CoAWC2Cursor/CoAWC2Cursor.lua",
"CoAWC2Cursor/CoAWC2Cursor.toc",
"CoAHideArmor/CoAHideArmor.lua",
"CoAHideArmor/CoAHideArmor.toc",
"CoA_TalentReset/CoA_TalentReset.lua",
"CoA_TalentReset/CoA_TalentReset.toc",
];
pub const EXCLUDED_BOT_RACES_RECOMMENDED: &str =
@@ -189,6 +184,8 @@ fn patch_files(client: &Path) -> Result<Vec<PatchFile>> {
include_str!("custom_races_hashes_1_6.json")
} else if manifest.lines().any(|line| line == "# CoA Custom 1.7") {
include_str!("custom_races_hashes_1_7.json")
} else if manifest.lines().any(|line| line == "# CoA Custom 1.8") {
include_str!("custom_races_hashes_1_8.json")
} else {
include_str!("custom_races_hashes.json")
};
@@ -334,6 +331,26 @@ struct PatchTransaction<'a> {
entries: Vec<SavedFile>,
finished: bool,
}
// A shared AddOns directory can resolve onto another volume. Publish a complete,
// synced copy beside the destination before deleting the source, so the journal
// always retains recoverable bytes even if copying or publishing fails.
fn move_patch_file(source: &Path, target: &Path) -> io::Result<()> {
match fs::rename(source, target) {
Ok(()) => return Ok(()),
Err(error) if error.kind() == io::ErrorKind::CrossesDevices => {}
Err(error) => return Err(error),
}
let parent = target
.parent()
.ok_or_else(|| io::Error::other("Patch target has no parent"))?;
let temporary = tempfile::NamedTempFile::new_in(parent)?;
fs::copy(source, temporary.path())?;
temporary.as_file().sync_all()?;
temporary.persist(target).map_err(|error| error.error)?;
fs::remove_file(source)
}
impl<'a> PatchTransaction<'a> {
fn new(root: &'a Path) -> Result<Self> {
recover_patch_transaction(root)?;
@@ -365,9 +382,10 @@ impl<'a> PatchTransaction<'a> {
&self.entries,
)?;
if path.is_file() {
fs::rename(
move_patch_file(
path,
self.root
&self
.root
.join(".coa-races-transaction")
.join(index.to_string()),
)?;
@@ -404,8 +422,9 @@ impl<'a> PatchTransaction<'a> {
&self.entries,
)?;
fs::create_dir_all(target.parent().unwrap())?;
fs::rename(
self.root
move_patch_file(
&self
.root
.join(".coa-races-transaction")
.join(index.to_string()),
target,
@@ -445,7 +464,7 @@ fn recover_patch_transaction(root: &Path) -> Result<()> {
if let Some(target) = &entry.moved_to {
let target = fsx::safe_join(root, target)?;
if !saved.is_file() && target.is_file() {
fs::rename(target, &saved)?;
move_patch_file(&target, &saved)?;
}
// Persist recovery progress before restoring the source, making retries safe.
entries[index].moved_to = None;
@@ -456,7 +475,7 @@ fn recover_patch_transaction(root: &Path) -> Result<()> {
if path.is_file() {
fs::remove_file(&path)?;
}
fs::rename(saved, path)?;
move_patch_file(&saved, &path)?;
} else if !entry.existed && path.is_file() {
fs::remove_file(path)?;
}
@@ -608,17 +627,14 @@ pub fn uninstall_client_patches(client: &Path) -> Result<()> {
fn verify_archive(path: &Path, filename: &str) -> Result<()> {
let expected = match filename {
"CoA-Custom-1.6-main-20261012-4dd3a4ec.zip" => {
"dfe802ea70047c129ac2e0aaa557bab3110e3cc6926d36403b8c880a0e310ee4"
"CoA-Custom-1.8.3-Client-1.zip" => {
"a9dd51ed2d90fb048d549602f40f5429d56e2df0df5606a38781b358fa369568"
}
"CoA-Custom-1.6-client-part1.zip" => {
"1dbf1901ad5be61eba66973609df90712ffc78ef9e9b2c8549a5f3e36332bf12"
"CoA-Custom-1.8.3-Client-2.zip" => {
"ab084a55509ccbcc2977a06dd0c01fa879973a1892baaacaeb3ff52f3dfc750e"
}
"CoA-Custom-1.6-client-part2.zip" => {
"689f7f946b4180fe977dabedc7cfe642e3e7f27431600c64c4dd5b7960b1bc66"
}
"CoA-Custom-1.8-Client.zip" => {
"b0ee9275a373e4024dda7744321d02b686fb1c703603ad635b32bfb6ed9b48aa"
"CoA-Custom-1.8.3-Client-3.zip" => {
"270c7b306624bf9e5c3fe577e3bd058601221df223dd9e449ff7c25de70b9461"
}
_ => return Err(Error::Invalid("Unknown custom races archive.".into())),
};
@@ -977,12 +993,87 @@ pub fn install_client_patches(
mod tests {
use super::*;
#[cfg(windows)]
fn exercise_linked_addons(shared: &Path) {
let client = tempfile::tempdir().unwrap();
let root = client.path();
fs::create_dir(root.join("Interface")).unwrap();
let link = root.join("Interface/AddOns");
let output = std::process::Command::new("cmd")
.args(["/C", "mklink", "/J"])
.arg(link.to_string_lossy().replace('/', "\\"))
.arg(shared.to_string_lossy().replace('/', "\\"))
.output()
.unwrap();
assert!(output.status.success(), "{output:?}");
let name = "Interface/AddOns/CoAHideArmor/CoAHideArmor.lua";
let active = root.join(name);
fs::create_dir_all(active.parent().unwrap()).unwrap();
fs::write(shared.join("unrelated.lua"), b"user addon").unwrap();
let staged = root.join("staged.lua");
fs::write(&staged, b"custom").unwrap();
let mut tx = PatchTransaction::new(root).unwrap();
tx.copy(&staged, &active).unwrap();
tx.finish().unwrap();
record_files(root, &[name]);
set_client_patch_enabled(root, false).unwrap();
assert!(!active.exists());
assert_eq!(fs::read(suffix(&active, "disabled")).unwrap(), b"custom");
set_client_patch_enabled(root, true).unwrap();
assert_eq!(fs::read(&active).unwrap(), b"custom");
// Simulate process termination after a move, then recover twice.
let mut tx = PatchTransaction::new(root).unwrap();
tx.move_file(&active, &suffix(&active, "disabled")).unwrap();
std::mem::forget(tx);
recover_patch_transaction(root).unwrap();
recover_patch_transaction(root).unwrap();
assert_eq!(fs::read(&active).unwrap(), b"custom");
assert!(!suffix(&active, "disabled").exists());
// Replacement installation must preserve the old bytes on failure.
{
let mut tx = PatchTransaction::new(root).unwrap();
fs::write(&staged, b"replacement").unwrap();
tx.copy(&staged, &active).unwrap();
}
assert_eq!(fs::read(&active).unwrap(), b"custom");
uninstall_client_patches(root).unwrap();
assert!(!active.exists());
assert_eq!(
fs::read(shared.join("unrelated.lua")).unwrap(),
b"user addon"
);
assert!(fs::symlink_metadata(&link)
.unwrap()
.file_type()
.is_symlink());
fs::remove_dir(link).unwrap();
}
#[test]
#[cfg(windows)]
fn shared_addons_junction_supports_install_switch_and_rollback() {
let shared = tempfile::tempdir().unwrap();
exercise_linked_addons(shared.path());
}
#[test]
#[cfg(windows)]
#[ignore = "Set COA_TEST_OTHER_VOLUME to a writable directory on another volume"]
fn shared_addons_on_another_volume_supports_install_switch_and_rollback() {
let base = std::env::var_os("COA_TEST_OTHER_VOLUME").expect("COA_TEST_OTHER_VOLUME");
let shared = tempfile::tempdir_in(base).unwrap();
exercise_linked_addons(shared.path());
}
fn record_files(root: &Path, names: &[&str]) {
let mut manifest = format!("# CoA Custom {CLIENT_VERSION}\n");
for name in names {
let (kind, base) = name
.strip_prefix("Data/")
.map_or(("ROOT", *name), |base| ("MPQ", base));
let (kind, base) = if let Some(base) = name.strip_prefix("Interface/AddOns/") {
("ADDON", base)
} else {
name.strip_prefix("Data/")
.map_or(("ROOT", *name), |base| ("MPQ", base))
};
manifest.push_str(&format!(
"{kind}:{base}\nSHA256:{}:{name}\n",
fsx::sha256_file(&root.join(name)).unwrap()
@@ -1042,6 +1133,55 @@ mod tests {
assert_eq!(actual, expected);
}
#[test]
#[ignore = "Requires the downloaded release archives in the normal download cache"]
fn release_archives_install_toggle_and_uninstall_in_a_disposable_client() {
let temp = tempfile::tempdir().unwrap();
let root = temp.path();
fs::create_dir(root.join("Data")).unwrap();
fs::write(root.join("Ascension.exe"), b"original game executable").unwrap();
fs::write(root.join("Data/patch-T.MPQ"), b"original game patch").unwrap();
fs::write(root.join("Data/patch-user.MPQ"), b"unrelated user patch").unwrap();
install_client_patches(root, &Cancel::default(), &|_, _| {}).unwrap();
let status = client_patch_status(root);
assert_eq!(status.version.as_deref(), Some(CLIENT_VERSION));
assert_eq!(status.state, ClientPatchState::Enabled);
assert!(root.join("Data/patch-ZZZD.MPQ").is_file());
assert!(root
.join("Interface/AddOns/CoAHideArmor/CoAHideArmor.lua")
.is_file());
set_client_patch_enabled(root, false).unwrap();
assert_eq!(client_patch_status(root).state, ClientPatchState::Disabled);
assert_eq!(
fs::read(root.join("Ascension.exe")).unwrap(),
b"original game executable"
);
assert_eq!(
fs::read(root.join("Data/patch-T.MPQ")).unwrap(),
b"original game patch"
);
set_client_patch_enabled(root, true).unwrap();
assert_eq!(client_patch_status(root).state, ClientPatchState::Enabled);
uninstall_client_patches(root).unwrap();
assert_eq!(
client_patch_status(root).state,
ClientPatchState::NotInstalled
);
assert_eq!(
fs::read(root.join("Ascension.exe")).unwrap(),
b"original game executable"
);
assert_eq!(
fs::read(root.join("Data/patch-T.MPQ")).unwrap(),
b"original game patch"
);
assert_eq!(
fs::read(root.join("Data/patch-user.MPQ")).unwrap(),
b"unrelated user patch"
);
assert!(!root.join("Data/patch-ZZZD.MPQ").exists());
}
#[test]
fn legacy_installation_uses_its_own_hashes_when_preserving_originals() {
let temp = tempfile::tempdir().unwrap();
@@ -1087,6 +1227,27 @@ mod tests {
assert!(legacy.keys().all(|key| current.contains_key(key)));
}
#[test]
fn previous_appearance_release_keeps_its_hashes_and_requests_an_update() {
let temp = tempfile::tempdir().unwrap();
fs::write(temp.path().join(MANIFEST_FILENAME), "# CoA Custom 1.8\n").unwrap();
let legacy: std::collections::BTreeMap<String, String> =
serde_json::from_str(include_str!("custom_races_hashes_1_8.json")).unwrap();
let current: std::collections::BTreeMap<String, String> =
serde_json::from_str(include_str!("custom_races_hashes.json")).unwrap();
let files = patch_files(temp.path()).unwrap();
assert_eq!(files.len(), legacy.len());
for file in files {
assert_eq!(file.sha256, legacy[&file.path]);
}
assert!(legacy.keys().all(|path| current.contains_key(path)));
assert!(!legacy.contains_key("Data/patch-ZZZD.MPQ"));
assert!(current.contains_key("Data/patch-ZZZD.MPQ"));
let status = client_patch_status(temp.path());
assert_eq!(status.version.as_deref(), Some("1.8"));
assert_eq!(status.state, ClientPatchState::PartiallyInstalled);
}
#[test]
fn previous_racial_release_keeps_its_hashes_and_addon_paths_stay_inside_client() {
let temp = tempfile::tempdir().unwrap();
+10 -2
View File
@@ -16,6 +16,7 @@
"Data/patch-ZHA.MPQ": "0fc6ebeafe1d14192dc64bafc90bde3c49230df1297f98bf65900a3bcf953617",
"Data/patch-ZHM.MPQ": "317d3ae00f0bd674b358af07544976acb7804aa6d8b19d1788ad96030e8c9bf0",
"Data/patch-ZJ.MPQ": "f821e99add86ef68d108c5ec466328c97677d3ed52f7944e200f3fe38c13b4de",
"Data/patch-ZK.MPQ": "444d0ecb72c1e990509d53e3cfa5b7634c816733533e8a97e5d7f5653ee32cce",
"Data/patch-ZM.MPQ": "424ab1978986e854551633983a94bd15beba6328aabea8c02f98eaa32f6f0b61",
"Data/patch-ZVU.MPQ": "c679b85a2e97344395756b54d2cf6abefe4e80e74944cb55b6e573ad17b7d020",
"Data/patch-ZZE.MPQ": "4b1e289e12c82644cb78f50170e6b5fd53918eb2de834f9e0cebddd81873a8bb",
@@ -25,10 +26,13 @@
"Data/patch-ZZU.MPQ": "8ee1839415b56d46c6eff7eb4dfbaf6fbafc4c6b29b39380d69f4d827d02a99e",
"Data/patch-ZZV.MPQ": "8d5e61d37008abf70478e5d5f46ec7afb0490b9a643323bd75a1c70cadd63290",
"Data/patch-ZZW.MPQ": "3689c485f8ee8fccaa6dbae1d073bc9231229f9a040f79a272d80a87486d0c33",
"Data/patch-ZZX.MPQ": "4c12608089cfe356f7c8882d66db90239ed3ec8ddd980d91d7a3a488680f3c88",
"Data/patch-ZZZ.MPQ": "566aaadf501af42e29a828b1bc2edbd36d436288fb309fe423bd74b9619bf593",
"Data/patch-ZZZC.MPQ": "691a53f6325c2615a64ced0802f18bc4d96e99c62aaa606fc930f9406ee74cdf",
"Data/patch-ZZZD.MPQ": "e4ce9d8b363eb609d0d6d92627eb53454fa2e03e4dbc1795b3573a22b7d009c8",
"EsteriaAppearance.bin": "90d9cfaeaf6de10f014f1d1610ea10453ec9b240255759aea99513cac488a3ec",
"EsteriaAppearance.dll": "64564aceac38b26faefbd51dba779fa338ab5e70a2a2509f6c8f3a991ac98518",
"EsteriaAppearanceGeometry.bin": "fdc1cbba90b66c4533a66365d6d555c2d32ab01acb014fff042b4a6a9c6b6ddc",
"EsteriaAppearance.dll": "196a82f24dd287653e2b2fc4d12bfc796f8ee3f6687ca8308905a5ab528a51a9",
"EsteriaAppearanceGeometry.bin": "19de5b4b4f79778ea5316659efc2f66c6edb6b5149c46efa47c46bfa4ec6904c",
"EsteriaAppearanceMaterials.bin": "f72f027f54a55c05aa0f76b457b97b484fe0e1aedc0e068cc0e0ca53e1878cba",
"EsteriaCosmeticWings.bin": "57352c28459d073a29b3014d33b70f3b3756afa37fa9583ef6b30d503422ac3f",
"EsteriaDrakonid.bin": "95440ee9c065ef20bb7fed6158d20623d68745291cedc2726fc746ff54601f95",
@@ -57,8 +61,12 @@
"EsteriaVrykulTextures.bin": "46098750a0e235724c6e9cc8d9d4e26550aa47bef95fd5f0f82efe5e945bf296",
"EsteriaVulpera.bin": "c5434993b9af4a17d881965e4735cd2ac379e39c7142aac9844adff9528562d4",
"EsteriaVulperaTextures.bin": "1ab844e74684aced2b069f1b91cd563aade45e05bd5e23f866a6c0c301cb098e",
"Interface/AddOns/CoAHideArmor/CoAHideArmor.lua": "8c1c7403524fc9bd56c0809b4101b141da700ba163701209bf1420f2ef106aa7",
"Interface/AddOns/CoAHideArmor/CoAHideArmor.toc": "123580d92fd5ceee258e96296f42c359b7e83cdff151af49c50c6c4e2059677c",
"Interface/AddOns/CoAWC2Cursor/CoAWC2Cursor.lua": "1cf9537ff5f10b77250fea4407aea1008da690afe102ed6ed2dac21f79638cfa",
"Interface/AddOns/CoAWC2Cursor/CoAWC2Cursor.toc": "48ce695dce712b3643ebe13a77e318d623c964acc69479b8fc8cc675099801bf",
"Interface/AddOns/CoA_TalentReset/CoA_TalentReset.lua": "827d756d5948ef918fafaf8b869290b3a1faa4e4cc21b19b512a00d4509f3d41",
"Interface/AddOns/CoA_TalentReset/CoA_TalentReset.toc": "16298c04af68e68d6445e7a11f42aee525dd4145f85d2771ff434fb7c6e95a85",
"dinput8.dll": "f8de78606c241fb3911dce22faf68f5b9f9885b142b183c1e2c09ddc8f7e380c",
"wc2_human.cur": "f609736e29596bb386ef1597b157d211e01a86d32c2a929e256c581c37d71791",
"wc2_orc.cur": "baa512c9b9045762ba35b6e0d35b8f79c54b7649f35cc9c0e0cc8c168a1e5a97"
@@ -0,0 +1,65 @@
{
"Ascension.exe": "e2c347019d554a59639e5978fd68e50e906973ab313c6573cc56ca82e8e3c547",
"Data/patch-T.MPQ": "fe597138ab7f56881b5f4f27d6dc9d81bb278b483ca0d91b7207ffd4a5ae7bfd",
"Data/patch-ZE1.MPQ": "69d79dbbea54ec0312c37770debc79c7bc9ce2e21eedef99c03cd8d911955283",
"Data/patch-ZE2.MPQ": "1a41cae77ad730e9cf69e8d63fd12ae3a579418bb550d351fff469573a97ac3c",
"Data/patch-ZE3.MPQ": "b587202c21b6f580682b601b7c2e905fbfa766276e74733db55c1bddbffb7f87",
"Data/patch-ZE5.MPQ": "476b5a1fcf69f64fdb281e3b445362b936d016066ccd12f897acfcf200d6c0cf",
"Data/patch-ZE6.MPQ": "762592c9ed950b4a7b6c7d85d45050b30fa3f35d53e348ee1e1516fdbb7e5484",
"Data/patch-ZE7.MPQ": "de54b0189d242763d2872223419a259b6b8a4b380c24b50a2ef9c6fa44466248",
"Data/patch-ZE8.MPQ": "1bc5691fb84a84f3e7a0a70baaa9192a97b4ec5906ee37c85838ffe08adef934",
"Data/patch-ZE9.MPQ": "d49c94463e9548e76378ce2c0454d8f204f0745c8c0de32b6dce7f0b0fd67c4a",
"Data/patch-ZEA.MPQ": "78fd10ec5262ae2417eba9700d2172553bbc1e5cfb0b597aada8f1753ca46d9d",
"Data/patch-ZES.MPQ": "a2d9348f917f745c7aa25b2eed96efa312f7b2d2f62cb86a4f2eaabc2dfa895f",
"Data/patch-ZG.MPQ": "48979e1fda775f8deb47bffa48e0a468595d4c71286fee518f51dc5801c5ca39",
"Data/patch-ZH.MPQ": "5e1d2fe287053abba703d7af381e10096c6525ba477ffed3971c2fc4f93e919c",
"Data/patch-ZHA.MPQ": "0fc6ebeafe1d14192dc64bafc90bde3c49230df1297f98bf65900a3bcf953617",
"Data/patch-ZHM.MPQ": "317d3ae00f0bd674b358af07544976acb7804aa6d8b19d1788ad96030e8c9bf0",
"Data/patch-ZJ.MPQ": "f821e99add86ef68d108c5ec466328c97677d3ed52f7944e200f3fe38c13b4de",
"Data/patch-ZM.MPQ": "424ab1978986e854551633983a94bd15beba6328aabea8c02f98eaa32f6f0b61",
"Data/patch-ZVU.MPQ": "c679b85a2e97344395756b54d2cf6abefe4e80e74944cb55b6e573ad17b7d020",
"Data/patch-ZZE.MPQ": "4b1e289e12c82644cb78f50170e6b5fd53918eb2de834f9e0cebddd81873a8bb",
"Data/patch-ZZR.MPQ": "5a7575e592dc0c8a6913e0d946bbe06fa0ca2e4d817ef1f8548d3d13142bcbd3",
"Data/patch-ZZS.MPQ": "533fd69d5784d83e872a5a28d27301dc9ab5d0cb925f8b2116926854e4a0a5b8",
"Data/patch-ZZT.MPQ": "aef3bbe4951333d62fb55224484724fbaa9c35773a19944ffb9935e250cfb59c",
"Data/patch-ZZU.MPQ": "8ee1839415b56d46c6eff7eb4dfbaf6fbafc4c6b29b39380d69f4d827d02a99e",
"Data/patch-ZZV.MPQ": "8d5e61d37008abf70478e5d5f46ec7afb0490b9a643323bd75a1c70cadd63290",
"Data/patch-ZZW.MPQ": "3689c485f8ee8fccaa6dbae1d073bc9231229f9a040f79a272d80a87486d0c33",
"Data/patch-ZZZ.MPQ": "566aaadf501af42e29a828b1bc2edbd36d436288fb309fe423bd74b9619bf593",
"EsteriaAppearance.bin": "90d9cfaeaf6de10f014f1d1610ea10453ec9b240255759aea99513cac488a3ec",
"EsteriaAppearance.dll": "64564aceac38b26faefbd51dba779fa338ab5e70a2a2509f6c8f3a991ac98518",
"EsteriaAppearanceGeometry.bin": "fdc1cbba90b66c4533a66365d6d555c2d32ab01acb014fff042b4a6a9c6b6ddc",
"EsteriaAppearanceMaterials.bin": "f72f027f54a55c05aa0f76b457b97b484fe0e1aedc0e068cc0e0ca53e1878cba",
"EsteriaCosmeticWings.bin": "57352c28459d073a29b3014d33b70f3b3756afa37fa9583ef6b30d503422ac3f",
"EsteriaDrakonid.bin": "95440ee9c065ef20bb7fed6158d20623d68745291cedc2726fc746ff54601f95",
"EsteriaDrakonidCoverage.bin": "9cdc227f08329e1245d2b864a996e7a772c96ecdbe5d81925f4d60cdbe4fa11e",
"EsteriaDrakonidTextures.bin": "1ba9133a75dad291d98a068b2dcde01f31a897a1764cd7f3e2c316c288a8f605",
"EsteriaEarthen.bin": "8a0db93ba2d5c756b44ed84f2f7bc7c15eef13be6a7d87baf1383c6c0c624e02",
"EsteriaGnoll.bin": "cfacc8e681bb8e54a4f01ee9c12a91bf0bd23a23527bb548d4dc21ec1b33eea2",
"EsteriaGnollTextures.bin": "1ba9133a75dad291d98a068b2dcde01f31a897a1764cd7f3e2c316c288a8f605",
"EsteriaHaranir.bin": "59f31d00e372fd2646e1cf0d9d3d5d671b31edd60ff7b862f8d1ce7e53ba1f2f",
"EsteriaHaranirTextures.bin": "99948ca570be2d376f0c67e3b8088739b6fa9f9d2c73985e19f68df77689a229",
"EsteriaHighmountain.bin": "e83349252ad2687ac23fcfc5623db7401cf32e5faf47a5a7be20c2f94b014938",
"EsteriaNaga.bin": "e87547cff5d09500c294f8b06935d134cdd0bbb962e294a72de09404505bd8b3",
"EsteriaNagaTextures.bin": "57ec560f99c1d48ac1e8f6a797c156513b99e7d349e3071afe405f812d159ae3",
"EsteriaSaberon.bin": "7735c9325c807c5125760d87f323d6b7d4162fb542c1d8b5f435ea2d6b9a4daa",
"EsteriaSaberonCoverage.bin": "9cdc227f08329e1245d2b864a996e7a772c96ecdbe5d81925f4d60cdbe4fa11e",
"EsteriaSaberonTextures.bin": "1ba9133a75dad291d98a068b2dcde01f31a897a1764cd7f3e2c316c288a8f605",
"EsteriaSethrak.bin": "bd14857a8c11fdf8027128763293701586b2102f9a6539d33a727014789fd606",
"EsteriaSethrakTextures.bin": "d2b2cf58087a391f00198008fe871edd400ddf28d54a3a05674df74c5198528a",
"EsteriaTarasek.bin": "f718444d5ec36f7aff018883486ae1981151fe6e01f5b7781d68d74e9fadfa47",
"EsteriaTarasekTextures.bin": "1ba9133a75dad291d98a068b2dcde01f31a897a1764cd7f3e2c316c288a8f605",
"EsteriaThinHuman.bin": "75794d192ea0c228b3da7bf7d0bdff1119f79d3f9bfef6650cd5e1a2b5d106eb",
"EsteriaThinHumanTextures.bin": "02aeb4c05893d06125b8b58fdb7c2a56fe3d66a7d094706a44b43cb503d1731e",
"EsteriaTuskarr.bin": "ecbe7ef490ba67eca029a57639192db61238522618491549766fe38529914387",
"EsteriaTuskarrTextures.bin": "e2116c2c83adea079126fd5da765d20da24f044d4f161c4124e4368cb3d6bc71",
"EsteriaVrykul.bin": "39e2b7b4c67997dbbd34bae840bd606a59290f7f2fc82565a0ba00090335415c",
"EsteriaVrykulTextures.bin": "46098750a0e235724c6e9cc8d9d4e26550aa47bef95fd5f0f82efe5e945bf296",
"EsteriaVulpera.bin": "c5434993b9af4a17d881965e4735cd2ac379e39c7142aac9844adff9528562d4",
"EsteriaVulperaTextures.bin": "1ab844e74684aced2b069f1b91cd563aade45e05bd5e23f866a6c0c301cb098e",
"Interface/AddOns/CoAWC2Cursor/CoAWC2Cursor.lua": "1cf9537ff5f10b77250fea4407aea1008da690afe102ed6ed2dac21f79638cfa",
"Interface/AddOns/CoAWC2Cursor/CoAWC2Cursor.toc": "48ce695dce712b3643ebe13a77e318d623c964acc69479b8fc8cc675099801bf",
"dinput8.dll": "f8de78606c241fb3911dce22faf68f5b9f9885b142b183c1e2c09ddc8f7e380c",
"wc2_human.cur": "f609736e29596bb386ef1597b157d211e01a86d32c2a929e256c581c37d71791",
"wc2_orc.cur": "baa512c9b9045762ba35b6e0d35b8f79c54b7649f35cc9c0e0cc8c168a1e5a97"
}
+61 -2
View File
@@ -522,6 +522,18 @@ fn save_settings_in(
"Use the module switch to turn this module on or off.".into(),
));
}
if id == "time-is-time" {
let valid = match key.as_str() {
"TimeIsTime.Announce" => matches!(value, "0" | "1"),
"TimeIsTime.SpeedRate" => value.parse::<f32>().is_ok_and(|v| v.is_finite() && (0.0..=60.0).contains(&v)),
"TimeIsTime.TimeStart" => value.parse::<i32>().is_ok_and(|v| v >= 0),
"TimeIsTime.HourOffset" => value.parse::<f32>().is_ok_and(|v| v.is_finite() && (-24.0..=24.0).contains(&v)),
_ => true,
};
if !valid {
return Err(Error::Invalid(format!("Invalid value for {key}.")));
}
}
if id == "content-scaling" && key == "CoAContentScaling.Difficulty.DamageMultiplier" {
let multiplier = value.parse::<f32>().map_err(|_| {
Error::Invalid("Enemy damage must be a number from 0.25 to 2.0.".into())
@@ -611,6 +623,53 @@ fn save_settings_in(
mod tests {
use super::*;
#[test]
fn time_is_time_card_settings_and_backups_match_the_module() {
let temp = tempfile::tempdir().unwrap();
let root = temp.path().join("server");
let meta = temp.path().join("metadata");
fs::create_dir_all(dir(&root)).unwrap();
fs::create_dir_all(&meta).unwrap();
let cat = catalog();
assert!(!list_in(&cat, &root).iter().find(|m| m.id == "time-is-time").unwrap().installed);
let defaults = "# Keep module documentation\n[worldserver]\nTimeIsTime.Enable = 1\nTimeIsTime.Announce = 1\nTimeIsTime.SpeedRate = 1.0\nTimeIsTime.TimeStart = 0\nTimeIsTime.HourOffset = 0.0\n";
let dist = dir(&root).join("mod-time_is_time.conf.dist");
let active = dir(&root).join("mod-time_is_time.conf");
fs::write(&dist, defaults).unwrap();
let view = list_in(&cat, &root).into_iter().find(|m| m.id == "time-is-time").unwrap();
assert!(view.installed && view.enabled && view.switchable && view.has_settings);
for locale in ["en", "ru", "de", "fr", "es", "zh"] {
assert!(!view.description[locale].is_empty());
}
assert_eq!(settings_in(&cat, &root, "time-is-time").unwrap().len(), 5);
let changes = BTreeMap::from([
("TimeIsTime.SpeedRate".into(), "7.5".into()),
("TimeIsTime.TimeStart".into(), "1213963200".into()),
("TimeIsTime.HourOffset".into(), "5.5".into()),
("TimeIsTime.Announce".into(), "0".into()),
]);
assert_eq!(save_settings_in(&cat, &root, &meta, "time-is-time", &changes).unwrap().len(), 4);
let saved = fs::read(&active).unwrap();
assert!(String::from_utf8_lossy(&saved).contains("# Keep module documentation"));
assert_eq!(fs::read_to_string(&dist).unwrap(), defaults);
assert!(save_settings_in(&cat, &root, &meta, "time-is-time", &changes).unwrap().is_empty());
for (key, value) in [
("TimeIsTime.Enable", "0"), ("TimeIsTime.SpeedRate", "NaN"),
("TimeIsTime.SpeedRate", "-1"), ("TimeIsTime.SpeedRate", "61"),
("TimeIsTime.HourOffset", "inf"), ("TimeIsTime.HourOffset", "25"),
("TimeIsTime.TimeStart", "-1"), ("TimeIsTime.TimeStart", "2147483648"),
("TimeIsTime.TimeStart", "1.5"), ("TimeIsTime.Announce", "2"),
] {
assert!(save_settings_in(&cat, &root, &meta, "time-is-time", &BTreeMap::from([(key.into(), value.into())])).is_err(), "{key}={value}");
assert_eq!(fs::read(&active).unwrap(), saved);
}
set_enabled_in(&cat, &root, &meta, "time-is-time", false).unwrap();
assert_eq!(read(&active).unwrap().get("TimeIsTime.Enable"), Some("0"));
set_enabled_in(&cat, &root, &meta, "time-is-time", true).unwrap();
assert_eq!(read(&active).unwrap().get("TimeIsTime.SpeedRate"), Some("7.5"));
assert!(meta.join("backups").exists());
}
fn test_catalog() -> Vec<Entry> {
let one = |id: &str, name: &str, conf: &str, key: &str| Entry {
id: id.into(),
@@ -802,8 +861,8 @@ mod tests {
// it may be empty (modules are added to it one by one); whatever is in it must be complete
for e in &c {
assert!(
e.description.contains_key("en") && e.description.len() == 5,
"{} has all five descriptions",
["en", "ru", "de", "fr", "es"].iter().all(|locale| e.description.get(*locale).is_some_and(|text| !text.is_empty())),
"{} has the existing catalog languages (additional translations are allowed)",
e.id
);
assert!(
+127 -10
View File
@@ -51,24 +51,38 @@ fn parse_counts(out: &str) -> Result<Population> {
/// Read-only query with the game's own database account. Requires the database to be running.
pub fn query(root: &Path) -> Result<Population> {
let prefix = bot_account_prefix(root).to_uppercase();
let db = Db::from_repack(root, Account::App)?;
query_with(&db, &prefix)
query_with(
&db,
&bot_account_prefix(root),
&crate::accounts::squid_bot_prefix(root),
)
}
/// The same counts through any database handle (a realm known by its descriptor); `prefix` is the bot accounts' name prefix, upper case.
pub fn query_with(db: &Db, prefix: &str) -> Result<Population> {
if prefix.is_empty() || !prefix.chars().all(|c| c.is_ascii_alphanumeric()) {
fn counts_sql(prefix: &str, squid_prefix: &str) -> Result<String> {
if [prefix, squid_prefix]
.iter()
.any(|prefix| prefix.is_empty() || !prefix.chars().all(|c| c.is_ascii_alphanumeric()))
{
return Err(Error::Invalid(
"the bot account prefix is not a plain name".into(),
));
}
let sql = format!(
let prefix = prefix.to_ascii_uppercase();
let squid_prefix = squid_prefix.to_ascii_uppercase();
// OR counts each character once even when the two configured prefixes overlap.
let bots =
format!("(UPPER(a.username) LIKE '{prefix}%' OR UPPER(a.username) LIKE '{squid_prefix}%')");
Ok(format!(
"SELECT (SELECT COUNT(*) FROM acore_characters.characters WHERE online=1), \
(SELECT COUNT(*) FROM acore_characters.characters c JOIN acore_auth.account a ON a.id=c.account WHERE c.online=1 AND UPPER(a.username) LIKE '{prefix}%'), \
(SELECT COUNT(*) FROM acore_characters.characters c JOIN acore_auth.account a ON a.id=c.account WHERE UPPER(a.username) LIKE '{prefix}%');"
);
parse_counts(&db.query(&sql)?)
(SELECT COUNT(*) FROM acore_characters.characters c JOIN acore_auth.account a ON a.id=c.account WHERE c.online=1 AND {bots}), \
(SELECT COUNT(*) FROM acore_characters.characters c JOIN acore_auth.account a ON a.id=c.account WHERE {bots});"
))
}
/// Read both supported bot populations, including SQUID random bots, without changing realm data.
pub fn query_with(db: &Db, prefix: &str, squid_prefix: &str) -> Result<Population> {
parse_counts(&db.query(&counts_sql(prefix, squid_prefix)?)?)
}
#[derive(Debug, Clone, Serialize)]
@@ -174,6 +188,109 @@ pub fn sizes(h: &Hardware) -> Vec<SizeOption> {
mod tests {
use super::*;
// Execute the production SELECT against disposable in-memory schemas. No
// server connection or credentials are needed for these regression cases.
fn fixture_counts(
prefix: &str,
squid_prefix: &str,
accounts: &[(&str, u32, u32)],
) -> Population {
let db = rusqlite::Connection::open_in_memory().unwrap();
db.execute_batch(
"ATTACH DATABASE ':memory:' AS acore_auth;
ATTACH DATABASE ':memory:' AS acore_characters;
CREATE TABLE acore_auth.account (id INTEGER PRIMARY KEY, username TEXT);
CREATE TABLE acore_characters.characters (account INTEGER, online INTEGER);",
)
.unwrap();
for (index, (name, online, offline)) in accounts.iter().enumerate() {
db.execute(
"INSERT INTO acore_auth.account VALUES (?1, ?2)",
rusqlite::params![index as u32, name],
)
.unwrap();
for flag in std::iter::repeat_n(1, *online as usize)
.chain(std::iter::repeat_n(0, *offline as usize))
{
db.execute(
"INSERT INTO acore_characters.characters VALUES (?1, ?2)",
rusqlite::params![index as u32, flag],
)
.unwrap();
}
}
let changes = db.total_changes();
let (total, bots, all): (u32, u32, u32) = db
.query_row(&counts_sql(prefix, squid_prefix).unwrap(), [], |row| {
Ok((row.get(0)?, row.get(1)?, row.get(2)?))
})
.unwrap();
assert_eq!(
db.total_changes(),
changes,
"population queries must only read"
);
parse_counts(&format!("{total}\t{bots}\t{all}")).unwrap()
}
#[test]
fn random_bots_are_not_advertised_as_real_players() {
let p = fixture_counts(
"CoaBotHost",
"rndbot",
&[("RNDBOT1", 171, 1), ("CoaBotHost1", 2, 3), ("PLAYER", 2, 1)],
);
assert_eq!(
(
p.online_total,
p.players_online,
p.bots_online,
p.bots_total
),
(175, 2, 173, 177)
);
let empty = fixture_counts("CoaBotHost", "rndbot", &[]);
assert_eq!(
(empty.online_total, empty.bots_online, empty.bots_total),
(0, 0, 0)
);
let humans = fixture_counts("CoaBotHost", "rndbot", &[("PLAYER", 3, 1)]);
assert_eq!((humans.players_online, humans.bots_online), (3, 0));
}
#[test]
fn population_uses_both_configured_prefixes_and_counts_overlaps_once() {
let root = tempfile::tempdir().unwrap();
let configs = root.path().join("Core/configs/modules");
std::fs::create_dir_all(&configs).unwrap();
std::fs::write(
configs.join("mod_coa_playerbots.conf"),
"CoaBots.RandomSpawn.AccountPrefix = \"Companion\"\n",
)
.unwrap();
std::fs::write(
configs.join("playerbots.conf"),
"AiPlayerbot.RandomBotAccountPrefix = \"Random\"\n",
)
.unwrap();
let p = fixture_counts(
&bot_account_prefix(root.path()),
&crate::accounts::squid_bot_prefix(root.path()),
&[("COMPANION1", 2, 0), ("RANDOM1", 3, 1), ("PLAYER", 1, 0)],
);
assert_eq!((p.players_online, p.bots_online, p.bots_total), (1, 5, 6));
let p = fixture_counts(
"Bot",
"BotRandom",
&[("BOTRANDOM1", 3, 1), ("BOT1", 2, 0), ("PLAYER", 1, 0)],
);
assert_eq!((p.players_online, p.bots_online, p.bots_total), (1, 5, 6));
for unsafe_prefix in ["", "x' OR 1=1 --", "bot_", "bot%"] {
assert!(counts_sql(unsafe_prefix, "rndbot").is_err());
assert!(counts_sql("CoaBotHost", unsafe_prefix).is_err());
}
}
#[cfg(not(windows))]
#[test]
fn memory_is_read_from_proc_meminfo() {
+3 -1
View File
@@ -225,6 +225,7 @@ impl Inner {
};
// configuration-derived values do not need the realm to be running
let mut prefix = "COABOTHOST".to_string();
let mut squid_prefix = "RNDBOT".to_string();
if let Some(root) = access
.root
.as_deref()
@@ -234,12 +235,13 @@ impl Inner {
advert.modules = modules_of(root);
advert.population.capacity = capacity_of(root);
prefix = crate::population::bot_account_prefix(root).to_uppercase();
squid_prefix = crate::accounts::squid_bot_prefix(root).to_uppercase();
}
let mut caps_at = previous.as_ref().and_then(|(_, t)| *t);
if access.db_reachable() {
if let (Ok(db), Ok(mut ra)) = (access.db(), access.ra()) {
advert.running = true;
if let Ok(p) = crate::population::query_with(&db, &prefix) {
if let Ok(p) = crate::population::query_with(&db, &prefix, &squid_prefix) {
advert.population.players = p.players_online;
advert.population.bots = p.bots_online;
}
-667
View File
@@ -1,667 +0,0 @@
# CoA Server Manager — Phase 0 audit & architecture
Status: Phase 0 output. Everything under **Audit findings** was checked against the real repositories and a real
local install (`C:\games\CoA-Repack`); nothing there is invented. Everything under **Decisions** is a proposal
that the phases below implement.
---------------------------------------------------------------------------------------------------------
## 1. Audit findings (facts)
### 1.1 The repack already defines the on-disk layout
`C:\games\CoA-Repack` (RELEASE.json `mainRevision c3beca68`, `sourceRevision b8615469`, 2026-09-11):
```
Core\ authserver.exe worldserver.exe, DLLs, configs\, configs\modules\, Logs\, Crashes\
Data\ maps vmaps mmaps dbc (incl. dbc\Ascension) Cameras 3.8 GB
mysql\ MySQL 8.4.9 (mysqld, mysql, mysqladmin, mysqldump), data\ (3.3 GB), data.7z (141 MB)
Runtime\python\ embedded Python used by Scripts\
Scripts\manage.py the launcher/supervisor (604 lines) + gui_server.py (local web GUI)
Settings\ repack.json (ports, RA creds), database.json (generated DB passwords),
*.conf.template (+ .original)
BugReport\ relay.py, reports\, Logs\
Source\ server-source (2.2 GB) + zip + source-manifest.json
.state\ <name>.json = {pid, exe, created(FILETIME)} for mysql/auth/world/supervisor/relay,
control.lock, configuration.json, debug-logs.json
RELEASE.json {mainRevision, sourceRevision, binaries[{Name,SHA256,Bytes}], account, ...}
MANIFEST.json {fileCount 19382, bytes 3.2 GB, files{path:{bytes,sha256}}} <- per-file hashes
*.bat thin wrappers around Runtime\python\python.exe Scripts\manage.py <verb>
```
Consequences:
* **A per-file hash manifest already exists** (`MANIFEST.json`). It is the baseline for the file-ownership
system on imported repacks: file present in MANIFEST with the same hash → `core/repack, pristine`; present with a
different hash → `modified`; not in MANIFEST → `user`. No need to hash 3 GB to classify.
* **Generated configs are overwritten on every start.** `manage.py prepare()` renders
`Settings\*.template` → `Core\configs\{authserver,worldserver}.conf` and
`modules\mod_ascension_compat.conf` (placeholders `@DATA@ @LOGS@ @LoginDatabaseInfo@ ...`), also writes
`mysql\my.ini`, `mysql\admin-client.ini` (contains the root password) and `modules\coa_bugreport.conf`.
The README says so explicitly. **The templates, not the `.conf` files, are the source of truth** for those three
configs. Other module confs (e.g. `mod_coa_playerbots.conf`) are *not* templated and are edited in place.
* **Process identity is already solved in the repack** the way the spec demands: `{pid, exe, creation FILETIME}`
via `QueryFullProcessImageNameW` + `GetProcessTimes`; listeners via `GetExtendedTcpTable` with owning PID;
a start/stop mutex via `msvcrt.locking` on `.state\control.lock` (1 byte at offset 0 — compatible with
`LockFileEx`); graceful stop = RA `server shutdown 1s 0`, then auth terminate, then `mysqladmin shutdown`.
`stop_all` never hard-kills worldserver. Port offset support exists (`--port-offset`).
* **World is started under a supervisor** (`watch-world`) that also runs the Python bug-report relay; starting
`worldserver.exe` directly skips the relay. The relay ships reports to the maintainers.
* **Ports:** MySQL 3307 (bind 127.0.0.1), auth 3724, world 8085, RA 3443 (RA user/pass in `repack.json`).
* **DB credentials are the *same for every repack download*** (`database.json` is packaged, 48-hex passwords).
Safe only because MySQL is loopback-only. New Manager-created installs must regenerate them.
* **Readiness marker** in `Core\Logs\Server.log`:
`AzerothCore rev. <12-hex> <date> (main branch) (...) (worldserver-daemon) ready...` and
`WORLD: World Initialized In N Minutes M Seconds`. The worldserver banner also **reports its own core commit**
(12 hex) — usable to identify the core version of an imported binary when RELEASE.json is stale.
### 1.2 The reference machine is a real, customised, *running* install
* `Core\worldserver.exe` sha256 `b9aa8f36…` ≠ RELEASE.json (`715bd375…`): the owner's dev build. `Core\`
holds ~60 `worldserver.exe.pre-*` backups and `.pdb`s — **157 GB**. Import must not walk-and-hash everything;
it hashes only what it needs (exes, configs, templates, addon) and enumerates the rest by name/size.
* `mod_coa_playerbots.conf` has 71 `CoaBots.*` keys while the repo's `dist/conf/*.dist` has ~30: real configs
are ahead of the shipped template. The bot schema must therefore tolerate unknown keys (spec §10 already
demands it) and be validated against the *deployed* `.dist`, not only the repo's.
* The worldserver on this machine is **running now (pid 22080)** and the owner runs long bot experiments on it.
**Testing rule: the live install is only ever read.** Start/stop/update tests run on a disposable fixture copy
on different ports (`--port-offset`), never on `C:\games\CoA-Repack`.
* `C:` has 86 GB free (94 % full). Backup/staging code must check free space *before* writing and default
large artefacts (staging, DB dumps) to a user-selectable location.
### 1.3 mod-coa-playerbots is not a plug-in — it is a rebuilt worldserver
`Corfirean/mod-coa-playerbots` (`master`, no GitHub Releases yet) ships `dist\`:
```
bin\worldserver.exe (not in git) Install-CoaBots.ps1/.bat Uninstall-CoaBots.ps1/.bat
conf\mod_coa_playerbots.conf.dist reference\ascensionsidekick-level-builds.json (282 KB)
addon\CoABotUI\{CoABotUI.lua,.toc} sql\2026_09_15_00_ascension_character_selection.sql
release.json {builtForRepack{mainRevision, sourceRevision}, originalWorldserverSha256[], patchedWorldserverSha256[]}
```
* The module is compiled **statically into `worldserver.exe`** (`-DMODULES=static`) *and* needs three small
**core patches** (`docs/core-patches.md`: `LoginQueryHolder` moved to `WorldSession.h`,
`IWorld::AddQueryHolderCallback`, `Group::GetRolls`, plus an Ascension talent accessor). The doc says some of
these were still uncommitted in the core working tree — **must be verified before CI can build bots
from clean commits** (§6 risk R1).
* "Install bots" today = replace `Core\worldserver.exe` (backup → `.orig`), drop `.conf.dist`, create `.conf`
only if absent, copy `Core\reference\ascensionsidekick-level-builds.json`, copy the addon to
`<repack>\Client\Interface\AddOns\CoABotUI` (a `Client\` folder that the repack does not have — the client is
distributed separately), apply `dist\sql\*.sql` to the characters DB with the password read out of
`worldserver.conf` (visible on the command line).
* The installer already does **hash-gated binary replacement** (original ∈ known hashes or patched ∈ known
hashes, else refuse unless `-Force`) and refuses if worldserver is running. The Manager generalises this.
* Bots are real characters on their own accounts (`CoaBotHost*`) in `acore_characters`; no extra database.
Bot creation throttles (`BatchSize 5 / 500 ms`) exist because a 1000-bot synchronous spawn once killed the
server — presets must never lower these. (Confirmed by the owner's own incident notes.)
* The `.conf.dist` is well commented prose — usable as the source for the initial `schemas/bots.json`.
### 1.4 azerothcore-wotlk-coa (core)
* `main`, 1.1 GB, **no releases, no tags, no Windows build workflow**. Only `quality.yml` (ubuntu, source
boundaries) exists. CI for binaries must be written from scratch.
* Build: CMake ≥ out-of-source, `-DSCRIPTS=static -DMODULES=static`, C++20, Boost.PropertyTree (vcpkg
`boost-property-tree`), OpenSSL 3, MySQL client libs. Repo rules (`AGENTS.md`): never edit
`data/sql/base|archive|updates/db_*`; new SQL goes only in `data/sql/updates/pending_db_*/`; **automatic DB
updater is disabled in this project's config** (the bots doc: `AUTOUPDATER: ... disabled`). So schema
migrations are *not* applied by worldserver — the Manager must own a tracked migration runner (spec §18).
* `modules\` contains 24 in-tree modules (mod-ascension, mod-coa-*, …); bots would be the 25th.
Runtime module configs are `Core\configs\modules\*.conf` (+ `.dist`).
* Core HEAD 442cf4c9 (2026-09-30) is ahead of the repack's `mainRevision c3beca68` and the running binary
(`3567e2f8e9d5`): three different revisions are in play on one machine. The compatibility matrix must be
keyed by **exact core commit**, never by "latest".
### 1.5 Toolchain on this machine
Node 26, npm 11, git 2.55, gh (authed as Corfirean), VS 18 Insiders with MSVC 14.51 and WebView2 present.
Rust was **not** installed; `rustup` stable 1.98.1 (msvc) was installed as part of this task. cmake/pnpm absent
(npm is used; CMake is only needed by the *build* repo, on the CI runner).
---------------------------------------------------------------------------------------------------------
## 2. Decisions (architecture)
### D1. One supported layout: the "CoA Repack layout v1"
Both flows converge on the same folder shape:
* **Import** adopts an existing repack-shaped folder (classification: Healthy / Partial / Unknown-custom /
Incompatible, §5).
* **New install** downloads the *base package* (= a repack) and extracts it into staging, verifies, then moves
it into place. Every install is therefore a repack plus Manager metadata.
Result: one code path for process control, config, DB and update. "Unknown custom server" gets the restricted
mode from spec §52 (start/stop via detected exes, backups, console, no update/bots).
A `Layout` trait isolates this (`RepackLayout` now; a hypothetical `NativeLayout` later) so nothing hardcodes
`Core\worldserver.exe`; paths come from `Installation.layout`.
### D2. Manager metadata lives *next to*, not inside, the server folder
`D:\CoA-Repack` ⇒ `D:\CoA-Repack.manager\` (the example in the spec). Rationale: import stays byte-for-byte
read-only on the server folder, folder can be copied/moved without dragging Manager state, backups get a
natural home the user can redirect to another drive.
```
<install>.manager\
install.json identity + detected versions + db info (no secrets) + client path
state.json last known process state, update-transaction status pointer
ownership.sqlite (or ownership.json in v1) path → {owner, hash, version, replacePolicy, origin}
manifests\ copies of every applied release manifest
backups\<id>\ recovery points (each has backup.json + payload)
migrations\ applied-migration ledger (mirrors the DB table, see D7)
staging\ update/install staging (same volume as install → atomic rename)
logs\ manager.log (rotated 5×2 MB) ; cache\
```
A registry at `%LOCALAPPDATA%\CoAServerManager\installs.json` maps `installationId → path`, so a *moved* folder
is re-linkable (the `.manager` folder holds the id; if the path is gone the UI offers "Locate server").
Secrets (DB/RA passwords generated by the Manager) go to **Windows DPAPI-protected** files in the same
`.manager` folder (`secrets.bin`, `CryptProtectData`, user scope). Imported servers keep their own
`Settings\database.json`; the Manager reads it in memory, never displays or logs it.
### D3. Process model (Rust, `process` module)
* `ProcessIdentity {pid, exe_path, creation_time_filetime}` — identical to `.state\*.json`, so records are
interchangeable with the repack's own scripts.
* A process "belongs" to an installation iff `exe_path` is under the installation root (or equals a
configured exe) **and** creation time matches a recorded identity *or* it owns a listening socket on a
configured port. Never by image name alone; never by bare PID.
* Discovery on startup = scan running processes for the installation's exes + `GetExtendedTcpTable` owner PIDs →
rebuild state (works after a Manager crash, PC crash → stale PID dropped because creation-time/exe mismatch).
* Start/stop are serialised with the repack's `.state\control.lock` via `LockFileEx` (same byte), so Manager and
`.bat` files cannot race.
* **Driver strategy.** Phase 2 delegates start/stop to the repack's own `manage.py` through its bundled Python
(`Runtime\python\python.exe -B Scripts\manage.py start-all|stop-all`), because it already handles config
rendering, relay, RA shutdown and readiness, and because behaviour must not regress on a production install.
Observation (identity, ports, health, logs) is native from day one. A native Rust driver for the same
sequence replaces the delegate later, gated behind the same `ServerDriver` trait and validated against the
delegate by the same integration tests. Startup order/health follows spec §7–8.
* States: `Stopped | Starting | Running | Stopping | Crashed | Updating | Unknown`; overall health adds
`Ready | NeedsAttention` using: process alive → port owned by that PID → log `ready...` marker after this
start's timestamp → no `FATAL`/`ERROR` startup lines.
* Forced kill exists only as an explicit, warned last resort after graceful stop times out.
### D4. Config engine (`config` module)
* Line-preserving parser: keeps comments, blank lines, unknown keys, line endings and encoding (UTF-8, LF/CRLF
detected). A `set(key, value)` rewrites only that key's line; missing keys are appended under a
`# Added by CoA Server Manager` comment. Never re-serialises the file.
* Layered targets via the layout: for templated configs the edit is applied to `Settings\<name>.template`
(source of truth) **and** the rendered `.conf` (so the running/next state agrees without a restart of the
renderer); for `mod_coa_playerbots.conf` edit in place.
* Save = validate against schema → write `<file>.tmp` in same dir → re-parse and compare → snapshot previous
into `.manager\backups\config\` → `MoveFileEx(REPLACE_EXISTING)`.
* Merge (`.dist` v1 → v2): add keys present in new `.dist` but missing; never overwrite user values; keys
removed upstream → flagged `deprecated`, kept.
* Schemas: `schemas/bots.json`, `schemas/server.json` (curated whitelist), fields exactly per spec §10
(`key type category title description default min max options advanced restartRequired dangerous`;
`restartRequired ∈ runtime|world|full`). Presets are separate JSON diffs shown as "will change N settings".
### D5. File ownership & manifests
Every release ships `manifest.json`:
```jsonc
{
"schema": 1,
"kind": "base|update|bots",
"version": "0.4.1",
"core": { "commit": "<40 hex>" },
"bots": { "commit": "<40 hex>" | null },
"builtAt": "2026-…Z",
"minManagerVersion": "0.1.0",
"requires": { "core": ["<commit>"|"range"], "dbSchema": ">=N" },
"files": [ { "path":"Core/worldserver.exe", "sha256":"…", "size":123, "owner":"core|bots|manager",
"policy":"replace|replace-if-pristine|merge-config|create-if-missing|never-touch" } ],
"migrations": [ { "id":"2026_09_15_00_…", "db":"characters", "sha256":"…", "destructive":false } ],
"signature": { "alg":"ed25519", "keyId":"…", "sig":"…" } // verified when a public key is embedded (§54)
}
```
`ownership` table per install: `path, owner(core|bots|manager|user), sha256_at_install, installed_version,
policy, origin(imported|installed)`. Update algorithm compares **current hash vs recorded hash vs incoming
hash**: current == recorded → safe to replace; current ≠ recorded → *modified outside Manager* → prompt
(Keep / Replace / Compare / Cancel); path unknown → `user`, never touched. Import seeds the table from
`MANIFEST.json` where present (imports are read-only; hashes computed lazily and only for managed paths).
### D6. Update transaction (Prepare → Verify → Snapshot → Apply → Validate → Commit)
1. **Prepare** — fetch manifest (HTTPS only, signature checked), compatibility matrix check, disk-space check on
staging volume and backup volume.
2. **Download** to `staging\<txid>\dl\` with `.part` files, HTTP Range resume, retry/backoff, cancel, progress.
3. **Verify** — SHA-256 of every artefact; nothing is executed or extracted into the live tree before this.
4. **Snapshot** — server must be stopped (never copy over a running worldserver); create recovery point:
replaced binaries, changed managed configs, module state, full dumps of every managed realm database;
write `txn.json {state: Snapshotted}`.
5. **Apply** into `staging\<txid>\tree\`, resolve ownership conflicts, merge configs, then swap file-by-file with
same-volume atomic renames, journaling each step (`txn.json` lists done/undone operations).
6. **Migrate** — durably mark SQL as running before execution. Failure restores the full database recovery point
before restoring files. Interrupted SQL is never automatically replayed.
7. **Validate** — check database structure, start server, require ten seconds of continuous readiness with timeout.
8. **Commit** — ownership table + `install.json` version bump, mark txn `Committed`, prune staging.
Any crash before Commit leaves `txn.json` in a non-terminal state; on next launch the Manager detects it and
offers *Roll forward* or *Roll back* — the install is "recoverable" by construction.
Rollback restores files, configuration and installation metadata. Once migrations started, it also restores all
databases from the full pre-update recovery point. Failed recovery remains unfinished and blocks startup and another
update. The same journal protects Repair. Old transactions without a full recovery point cannot roll back database
changes automatically. Independent database restore remains available for other recovery points.
### D7. Database strategy (`db` module)
* Driver: talk to the repack's own `mysql.exe` / `mysqldump.exe` / `mysqladmin.exe` (bundled, 8.4.9). Passwords
are passed via a temp `--defaults-extra-file` with restrictive ACL, deleted immediately — never on argv. A
native Rust client (`mysql_async`) is used for health pings and migration ledger reads.
* Ledger: table `acore_world.coa_manager_migrations(id, db, sha256, applied_at, status, error)` (created by the
Manager, in a dedicated table — no core schema is changed) mirrored to `.manager\migrations\`.
Statuses `Applied | Pending | Failed | Running`. Each file runs in a single connection; DDL is not transactional, so
"destructive" migrations (flag in manifest, or heuristic scan for `DROP|TRUNCATE|DELETE|ALTER ... DROP`) force
a fresh DB backup first and require explicit confirmation.
* Backups: `mysqldump --single-transaction --routines --quick` per DB. Quick = characters + auth + configs +
metadata; Full adds world (large); Config-only; DB-only. Compressed with zstd. Restore is always to a
staging schema first (`…_restore`), swapped only after a row-count sanity check, with the current DB dumped
beforehand.
* Never: `DROP DATABASE` or resetting characters. Update recovery restores databases into staging schemas and
keeps the replaced tables in separate schemas. Delete/
reset lives only in **Settings → Advanced → Danger Zone**, deletes tracked files only, and refuses to remove a
directory that still contains untracked files.
* Clean install: extract `mysql\data.7z` (packaged data dir), then **rotate** root/app passwords to fresh random
values (`ALTER USER`), rewrite `Settings\database.json`/templates via the layout renderer, store copies in
DPAPI. `bind-address=127.0.0.1` enforced.
### D8. Bot install/update (needs server-side cooperation — see §4)
Compatibility matrix `compat.json` (published with releases): `[{manager, core, bots, dbSchema}]` keyed by exact
core commit. Bots install = "install the bot-enabled `worldserver.exe` built for **this** core commit" +
conf.dist + talent JSON + SQL migration + (if client attached) addon. Same hash-gated + backup-first rules as
the existing `Install-CoaBots.ps1`, executed through the D6 transaction. Force-install on unknown core =
Advanced override, snapshot first.
### D9. Client integration
The client is a separate object. By default the Manager only detects it (`Wow.exe`/`Ascension.exe` + `Data\`), reads/writes
`realmlist.wtf` after backing it up, and copies `Interface\AddOns\CoABotUI` (backing that one directory up only if
its files differ from the manifest). No touching of `WTF`, `Cache`, other AddOns, or the exe. Downloading or updating
a client is opt-in and described in section 9 (game client download); an existing client is never changed without asking.
*Reference machine note:* `C:\games\Ascension` is a heavily modified Ascension client (custom `d3d9.dll`,
renderer files, many `.bak`s) — client detection must be strictly read-only + additive.
### D10. Network / friends
Detect LAN IP and public IP (HTTPS to a small set of IP-echo endpoints, user-toggle), listening check via
outbound self-test, **CGNAT heuristic** (WAN address of router ∈ 100.64.0.0/10 or private / ≠ public IP),
UPnP/NAT-PMP later. Firewall rules created only through a separate elevated helper (UAC on demand, never whole
app as admin), fixed names `CoA Server Manager - Auth` / `- World`, idempotent (query before add), delete only
own rules. Never exposed: MySQL 3307, RA 3443, Manager control channel (Tauri IPC only, no listener). Private
network = Tailscale detection/guided enable in v1; interface `NetworkProvider` so "CoA Connect" can slot in.
Friend package contains only `realmlist`/instructions/optional addon; secrets structurally excluded (whitelist
copy, not blacklist).
### D11. Stack & code layout
```
coa-server-manager/
docs/ ARCHITECTURE.md, flows, wireframes
schemas/ bots.json, server.json, presets/, manifest.schema.json, compat.schema.json
src-tauri/src/
main.rs, commands/ thin Tauri command layer (validate → call service)
fsx/ path validation, safe join, atomic write/replace, disk space, ownership
layout/ RepackLayout, detection & classification
registry/ installs.json, .manager dir, install.json
process/ identity, listeners, lock, drivers (delegate → native)
health/ probes, log-marker scan, error translation
config/ parser, merge, schema, presets
db/ mysql tool wrapper, ledger, migrations, dump/restore
backup/ recovery points, retention
update/ manifest, download, verify, txn (journal), rollback
client/ detection, realmlist, addon
net/ ips, ports, cgnat, firewall, tailscale
errors/ error catalogue → human message + actions
diag/ diagnostics, export package (redacting)
src/ React + TS + Vite + Tailwind + shadcn/ui (presentation only)
tests/ integration fixtures (fake repack generator), failure-injection harness
coa-server-build/ (separate repo) workflows + packaging + manifest signing
```
All destructive filesystem operations exist only in `fsx`; frontend never has `fs` scope in Tauri capabilities.
Every command that mutates goes through `fsx::Transaction`-style helpers that (a) validate the path is inside a
registered installation *or* the `.manager` dir, (b) refuse symlink/junction escapes, (c) log an audit record.
### D12. Build/release repo (`coa-server-build`)
Windows runner: checkout **exact** core SHA and bots SHA from workflow inputs (refuse branch names), place bots at
`modules/mod-coa-playerbots`, verify core patches are already in the core commit (fail the build if the patch set
is not applied — never apply ad-hoc patches at build time unless they are versioned `.patch` files in the build
repo), vcpkg-cached deps, CMake Release/RelWithDebInfo static, produce **two binaries per core commit**:
`worldserver` (no bots) and `worldserver+bots`, then `authserver`, DLLs, config `.dist`s, talent JSON, addon, SQL
migrations, `RELEASE.json`, `manifest.json` (+SHA256, +ed25519 signature), zstd-compressed update package.
Base package (≈3.2 GB; Data 3.8 GB + mysql data) is split into ≤ 1.9 GB parts (GitHub release asset cap is 2 GiB)
with a parts manifest. Reproducibility: pinned runner image label, recorded compiler/vcpkg versions, source SHAs,
build timestamp written into RELEASE.json.
### D13. Linux: the servers run in Docker (experimental)
Linux has no repack launcher and no Win32 process API, and the host should need nothing but Docker. A server folder
that contains `Settings/docker.json` is a **Docker installation**; every other folder is a repack, handled by the
code above without any change. `driver::run`, `process::observe` and `layout::scan` check for the marker first and
hand over to `coa_core::docker`; nothing else needed to change for start, stop, status and the server list.
* **Containers** (`docker/lifecycle.rs`): `coa-<project>-db` (official `mysql:8.4`, data in a named volume, not
published on the host), `-world` and `-auth` (a small runtime image holding only the shared libraries; the
binaries are mounted from `Core/`, so an update replaces files and never rebuilds an image). The image tag is a
hash of its Dockerfile.
* **Why the `docker` command line and not `docker compose`**: the compose plugin is missing from some distributions'
Docker packages, and the plan is to ask for as little as possible on the host. The command line is wrapped by a
`Docker` trait (`docker/cli.rs`), so the logic is tested with an in-memory fake.
* **Same folder shape as a repack where it matters**: `Core/configs`, `Core/Logs`, `Settings/repack.json`
(ports, RA login), `Settings/database.json` and `Data/`. Configuration editing, log tailing and the RA console
therefore work as they do on Windows. The container runs as the owner of the folder and starts in `Core/`.
* **Settings forced by environment** (the core reads `AC_<KEY>` before the `.conf`): `AC_BIND_IP=0.0.0.0` (the
published address, `bindAddress`, decides who can connect), `AC_DATA_DIR`, `AC_LOGS_DIR`, `AC_RA_ENABLE`,
`AC_RA_IP`, and `AC_UPDATES_ENABLE_DATABASES=0`: the server's own database updater needs a `mysql` client program and
stops the server without one; the Manager applies database updates itself (section 1.4). The remote console is published
on `127.0.0.1` only.
* **Secrets** go to `docker` by environment (`--env NAME` without a value), never on a command line.
* **Order**: database healthy, then world listening, then auth. The auth server exits when no realm is online.
Readiness is a connection that stays open: Docker's proxy accepts connections on a published port before the server
inside listens, so a plain connect proves nothing.
* **Configuration path in the binaries**: Linux builds must use `-DCONF_DIR=configs` (see `coa-server-build`),
otherwise the core looks for module configs in a path baked in at build time.
* **Database access** (`db.rs`): for a Docker installation `Db` runs `mysql`, `mysqldump` and `mysqladmin` inside the
database container with `docker exec -i`, connecting over TCP on the container's loopback exactly as the repack's
commands do on the host (password through `MYSQL_PWD`, never on a command line). Nothing else changes: accounts,
backups, the population query, migrations and the RA service account all go through `Db`, and the host needs no
MySQL client. A repack keeps using its bundled tools.
* **Health of the database container** is a ping over TCP, like every connection the Manager makes. On a new volume the
image first runs a temporary server that answers on its socket but takes no network connection; a socket ping reported
the container healthy about four seconds before TCP worked (measured: 10 s against 14 s).
* **Main configuration files**: a package carries only `worldserver.conf.dist` and `authserver.conf.dist` (the release
tool leaves active files out). On Windows the launcher writes them at each start; on Docker `ensure_main_configs` creates
them from the templates when they are missing, at installation and at every start, and never overwrites one.
* **Installing a new server** (`docker/install.rs`, separate from `install::install_base`, which is not touched). Same
order of events: signed manifest, space and folder checks, verified download, extraction into `<dest>.installing`,
database, then one rename. The package must hold `Core/worldserver`, `Core/authserver`, the `.dist` templates,
`_migrations/` and **`Database/baseline/{auth,characters,world}.sql.zst`**. The baseline is a dump, in the format of the
Manager's backups, of databases in which **every migration of the package is already applied**; the installer imports
it, records those migrations as applied (`baseline = 1`, a few bulk statements) and creates the `acore` account, the
realm port and the console account. It is the same arrangement as a Windows package, which ships its prepared database.
The databases are **not rebuilt from the repository's SQL**: some migrations are guards generated from the maintainers'
live database (`rev_20260903_01_live_class_baseline` refuses to run unless the table holds exactly the rows it expects),
so replaying the SQL files from the base scripts fails, in any order. `coa-release export-baseline --server DIR --out DIR`
produces the dumps from a prepared server (repack or Docker). The game data stays where the person has it
(`dataDir` in `docker.json`, mounted read-only). A failure removes the containers, the volume and the staging folder.
* **Validating a release on Linux** (`docker/fixture.rs`, used by `coa-release extract-schema-base` and `schema-contract` where
there is no Windows database program): the signed base package carries the MySQL data directory of a Windows repack, and a
MySQL 8.4 container opens it as it is (`--lower-case-table-names=1`, the repack's setting). The fixture is a Docker server
folder (`docker.json` with `mysqlData`: the database container uses that directory in place of a volume; an installation
never sets it), plus a `root` account for TCP, which the repack only has for its socket. The release SQL is then applied and the
schema contract captured by the same code as on Windows, and `export-baseline` dumps the result: that is how a Linux build
produces `Database/baseline` without anyone's live database. The migration checksums recorded in the base are those of
files checked out on Windows (CRLF line endings, `core.autocrlf`): the SQL of the core, the modules and SQUID must be
checked out the same way for the checksums to match, or every applied migration looks edited.
* **In the screens** the host is asked once per command (`coa_core::platform::flavor()`: repack on Windows, Docker
elsewhere) and the Docker half lives in `src-tauri/src/docker_install.rs`; the repack arm of each install command is the
code that was there. `install_environment` tells the install screen the kind of server, the suggested folder
(`~/CoaServer`) and why Docker cannot be used, if it cannot. On Docker the screen also asks for the game data folder and
the package, and there is no default package address until a signed Linux package is published. Packages are checked with
the embedded key; only a debug build (`tauri dev`) accepts another one, named in `COA_DEV_TRUSTED_KEY`, to try the
installer on a package signed with a throwaway key.
* **Updates are refused for a Docker server, never half done.** `update::preview`, `apply` and `rollback` refuse it: the
update packages are the repack's (executables, a bundled MySQL, a launcher) and applying one would put Windows files in a
Linux folder. Found by installing a server with the screen: the update check had read the Windows channel and offered one.
* **Realm profiles (CoA / Wildcard) work on a Docker server.** What the repack's patched launcher did at each start is done
by the Docker backend: finish an interrupted switch (`realms::before_start`), name the realms in the realm list, and give
the containers the databases of the selected realm (`acore_world_wildcard` ...). The switch itself (configuration swap,
database copy, journal) is the shared code; `prepare_launcher` has nothing to patch, and Wildcard support is read from
`Core/worldserver` as it is from `Core/worldserver.exe`.
* **The game client starts under Wine on a Linux host** (`wine.rs`; `client::launch` and `client::is_running` hand over):
umu-launcher with a Proton build when `umu-run` is installed (the newest GE-Proton found for Steam, or umu's own choice),
else plain Wine; `WINEPREFIX` defaults to `~/Games/umu/coa-client`; `WINEDLLOVERRIDES=divxtac=d` is always set, because
DivxTac.dll deadlocks the world loading screen under wine-mono. `COA_PROTONPATH`, `COA_WINEPREFIX` or
`client-launch.json` in the Manager's folder (`proton_path`, `prefix`, `runner`) override the detection. Whether the client
runs is read from `/proc` (under Wine the command line holds the Windows form of the path). Output goes to `client.log`.
* **Sharing with friends** (`docker/sharing.rs`): who can reach the game is decided by the address the container ports are
published on, `bindAddress` in `docker.json`; the `BindIP` of the configuration files is forced to `0.0.0.0` inside the
containers and changes nothing. Opening and closing therefore edit `bindAddress` (and set `CoA.AllowRemoteClients`), "servers
open" and the exposure check are computed from it (the database is never published, the console only on `127.0.0.1`), and
there is no firewall row on Linux. Settings the backend fixes (`docker::FORCED_KEYS`) are not offered; a test keeps that list
equal to the variables the containers get. A world that restarts itself (exit code 2) is restarted by Docker once it has come
up. The database console shows `docker logs`, and the file-based screens read Linux locations (the desktop folder from the
user directories file, memory from `/proc/meminfo`, the distribution name for the problem report).
* **Game data folder** (`docker::game_data_dir` / `set_game_data`, Settings card): `dataDir` in `docker.json` can be changed
after the install, only while the world and auth are stopped, and only to a folder that passes the install checks. A world
that stops with "does not hold the CoA client dbc set" is reported as `GameDataMismatch` (wrong data set: the standard one,
not Conquest of Azeroth's) instead of a bare failure.
* **Not done yet**: downloading the game data, updates, port conflict detection, the firewall and exposure checks, the
Wildcard realm profiles, and the client under Wine/Proton.
### D14. Keeping Windows and Linux apart
A fix for one platform must not be able to break the other. The rules:
1. **Platform code lives in its own modules**: `coa_core::docker` for Linux and Docker; the repack code (`driver`, `process`,
`install`, `layout` and the bundled-tool half of `db`) for Windows. A new Linux feature is a new file there, not an edit
of a repack function.
2. **Shared modules hold platform-neutral logic only** (manifest, signing, download, extraction, migrations, backups,
configuration editing, the registry).
3. **The difference enters in as few places as possible**: the early `is_docker` return at the top of `driver::run`,
`process::observe`, `layout::scan` and `Db::from_repack`, and the platform checks of the Tauri layer. Everything past
that point belongs to one platform.
4. **No `cfg` in the middle of a shared algorithm.** Where one is unavoidable (file modes, a path comparison), it is small,
commented, and the other platform's branch is the code that was there before.
5. **Reuse by calling, not by editing**: a Linux feature that needs a helper from a Windows-side file makes it
`pub(crate)` and calls it (visibility only); it does not change what the helper does.
6. **Both platforms are tested on every pull request** (`check.yml`: Windows and Linux). Tests of one platform's behaviour
are marked for that platform, so they cannot fail on the other.
---------------------------------------------------------------------------------------------------------
## 3. Flows
### 3.1 First run
`Welcome → [Install new server] | [I already have a server] | (link) Manage another install`.
New: choose folder (default `C:\Games\CoA Server`; checks: free space ≥ base+backup headroom, folder empty or
absent, not a client folder, not `Documents`/system dirs, not already registered) → single progress screen
(Download → Verify → Extract → Database → Bots(optional) → Start → Health) → "Your server is ready" →
Create account → PLAY. Technical log behind "Show details" only.
### 3.2 Existing-server import (strictly read-only)
select folder → `layout::scan()` (read-only opens, `FILE_SHARE_READ|WRITE` so a live server is unaffected) →
report: core exes + hashes vs RELEASE.json/MANIFEST.json, detected core commit (RELEASE.json → else banner rev in
Server.log → else unknown), configs & modules present, DB running/reachable (ping only), bots detected (conf
present ∧ patched-hash or `CoaBots.*` keys), client detected, classification + "No files will be changed" →
**[Add server]** writes only `<folder>.manager\` and the registry entry. Import never "fixes" anything.
Verification for the fixture test: recursive (path,size,mtime) snapshot of the server folder excluding
files the running server itself changes, diffed before/after.
### 3.3 Update — see D6. Failure matrix (spec §60) is executable via a fault-injection harness: kill at step k,
disk-full at write n, network cut at byte n, migration returns error, new worldserver exits non-zero, port
taken, exe quarantined (file vanishes), folder moved, user-modified managed file, unknown config keys.
### 3.4 Rollback — restore the pre-update databases when migrations started, followed by files and metadata
The UI explains that progress after the recovery point is lost. SQL failures before startup recover automatically;
failed health checks keep the installation blocked until the owner chooses recovery. Every recovery point and staging
schema has a unique identifier, and corrupt update journals fail closed.
---------------------------------------------------------------------------------------------------------
## 4. Required changes in the two source repositories
Prefer server-side cleanliness over Manager hacks. Proposed (each is an issue/PR on the owner's side, none is
made without approval):
| # | Repo | Change | Why |
|---|------|--------|-----|
| S1 | mod-coa-playerbots | Master switch `CoaBots.Enable` (0 = module registered but inert; no login/hooks/commands) | Lets a **single** worldserver ship for everyone. "Disable bots" becomes a config flip with restart, not a binary swap; drops the 2-binary matrix and most of §D8 risk. |
| S2 | mod-coa-playerbots | Commit **all** core patches in the core repo; delete "uncommitted working-tree" state from docs | CI must build from clean SHAs (R1). |
| S3 | mod-coa-playerbots | Real Releases + `dist/release.json` replaced by the shared `manifest.json` schema; `TalentBuildsPath` default = `Core/reference/…`, remove the hard-coded dev path fallback | Manager and installer share one truth; no absolute dev paths. |
| S4 | mod-coa-playerbots | Ship a machine-readable config schema (`conf/…schema.json`) next to `.dist`, or generate it in CI from the `.dist` comments | Avoid schema drift (71 vs 30 keys today). |
| S5 | core | Windows build+release workflow (or the build repo builds it); publish `worldserver --version --json` (core commit, bots commit, DB schema id) | Reliable version detection instead of log scraping. |
| S6 | core | Health endpoint alternative: worldserver already prints `ready...`; add a stable machine line (`COA-READY {...}`) or a tiny loopback status file `Core\Logs\ready.json` | Health without regex on human text. |
| S7 | core/repack | Ship a `manager-hooks.json` in the repack describing service names, ports, exes, config templates, RA settings | Layout detection without hard-coded knowledge; unknown custom builds can opt in. |
| S8 | core | Keep the auto DB updater disabled but expose `--dry-run-updates` listing pending updates | Manager migration UI without re-implementing the updater. |
| S9 | repack | Per-download random DB passwords and `Settings\database.json` generated on first start, not packaged | Security (§1.1). Manager does it itself for new installs meanwhile. |
Everything still works without S1–S9 (Manager has fallbacks), they just remove fragility.
---------------------------------------------------------------------------------------------------------
## 5. Import classification rules
* **Healthy** — `Core\{worldserver,authserver}.exe`, `Core\configs\*.conf`, `Data\dbc`, `mysql\bin\mysqld.exe` +
`mysql\data\acore_{auth,characters,world}`, `Settings\repack.json`, `Scripts\manage.py`, all present.
* **Partial** — a repack skeleton with pieces missing (e.g. no Data\maps, DB dirs absent).
* **Unknown/custom** — has `worldserver.exe` + `authserver.exe` but not the repack scaffolding.
* **Incompatible** — not a 3.3.5 AzerothCore layout / two installations nested / client folder.
The reference install classifies as **Healthy (customised)**: repack shape, binary hash differs from RELEASE.json.
---------------------------------------------------------------------------------------------------------
## 6. Risks & open questions
* **R1 (blocking for Phase 7/6)** — are all core patches committed? Owner action: confirm/commit (S2).
* **R2** — Legal/hosting of the base package: `Data\` (maps/vmaps/mmaps/dbc) derives from the game client;
and Ascension-specific DBC. Where does the owner want to host the 3–4 GB base (GitHub Releases in the build repo,
parts ≤ 1.9 GB; or own storage)? The Manager's downloader is source-agnostic; the choice affects Phase 5–6.
* **R3** — Manager signing key: needs an Ed25519 key pair generated by the owner; public key embedded in the app,
private key in GitHub Actions secrets. Phase 6 can start with unsigned + hash-only and flip the enforcement flag.
* **R4** — Bug-report relay (Python, sends reports to maintainers) is part of the repack's world startup; Manager
keeps it (privacy note surfaced in Settings, user can disable via the existing `coa_bugreport.conf` mechanism
only if the repack supports it — currently it forces `Enable = 1` on every start; not touched by Manager).
* **R5** — Tauri updater needs a hosted, signed `latest.json`; Manager self-update is Phase 10.
* **R6** — Windows long paths / non-ASCII install paths: repack requires a Latin path (uses 8.3 short names);
new-install folder chooser enforces it.
---------------------------------------------------------------------------------------------------------
## 7. Phase plan (each phase ends: compile → tests → run against fixture → verify live install untouched → commit)
| Phase | Deliverable | Done when |
|-------|-------------|-----------|
| 1 | Tauri+Rust+React skeleton, `fsx`, registry, `.manager` layout, logging w/ rotation, manifest structs + JSON schema, error catalogue skeleton | `cargo test` green; app launches; metadata round-trips |
| 2 | Read-only scan/classify/import; process discovery; Start/Stop via delegate driver; health | Import of `C:\games\CoA-Repack` leaves it byte-identical (proved by snapshot diff); Start/Stop verified on **fixture copy, offset ports** |
| 3 | Config parser/merge/atomic save; bots+server schemas; presets; UI | Property tests: unknown keys/comments preserved; round-trip identity |
| 4 | Recovery points, DB dumps, config snapshots, restore-to-staging | Backup→restore fixture test; fails safe when disk full |
| 5 | Clean install from base package; DB bootstrap + password rotation; account creation | Fresh VM/folder install reaches "ready" |
| 6 | Build repo & workflows; signed manifests; update transaction, rollback | Fault-injection suite green (spec §60) |
| 7 | Bots install/update via txn; compat matrix; GUI settings | Install → disable → restore on fixture |
| 8 | Client detection, addon, realmlist, PLAY | Client tree hash unchanged except addon dir + realmlist |
| 9 | Friends: net diagnostics, firewall service, Tailscale | Idempotent rule add/remove test |
| 10 | Error translation, diagnostics, repair, a11y, self-update | Spec §61 checklist |
---------------------------------------------------------------------------------------------------------
## 8. Decisions recorded after owner review (2026-09-30)
* **Core changes go through our own fork.** We are not maintainers of `jealous-sound/azerothcore-wotlk-coa`, so
the bot-enabling core patches (and the S1/S5/S6/S7 style changes) live in a fork owned by the bot/manager
project; the build repo pins exact fork SHAs. Upstream is tracked as a remote and merged periodically; the
compatibility matrix is keyed by fork commit. The fork is created when Phase 6/7 needs it (nothing is pushed
before then). This supersedes S2 (no upstream commits required) and removes risk R1.
* **Base package is compressed and split.** Payloads are zstd/LZMA-compressed and cut into parts below the
2 GiB GitHub asset limit (target 1.9 GB) with a parts list in the manifest; the downloader verifies each part
and the reassembled archive. Actual ratios will be measured in Phase 5 (the packaged database already shrinks
3.3 GB -> 141 MB; `Data\` maps/vmaps/mmaps are expected to compress far less).
* **Manifest signing (R3 resolved).** Ed25519 key generated. Public key: `keys/manifest-signing.pub`, embedded
in the app (`signing::EMBEDDED_PUBLIC_KEY`). Private key: `%USERPROFILE%\.coa-manager\signing\` (outside the
repo, never committed); CI receives it as the `COA_SIGNING_KEY` secret, which the owner must add manually.
Signatures are detached (`manifest.json.sig`, over the exact manifest bytes), so the embedded `signature`
field in the manifest was removed. **Back up the private key** — losing it means shipping a new app to rotate.
### 8.1 Fork created (2026-09-30)
* Fork: `Corfirean/azerothcore-wotlk-coa` (from `jealous-sound/azerothcore-wotlk-coa`). Default branch is `coa-bots`
(a branch named `coa` is impossible: the fork inherits upstream's `coa/...` branches). `main` stays a pure mirror of upstream.
* `coa-bots` = upstream `main` + a small, reviewable patch series (audit of the owner's 38 local commits, 2026-09-30):
1. `Core/Bots` hooks: `LFGMgr::GetProposalIdForPlayer`, `PlayerScript::OnPetitionOffered`, `Guild` friend `BotMgr`.
2. Crash fixes seen under bot load: `CombatManager::PutReference`, `Unit::RemoveFromWorld` dangling delayed-visibility pointer,
`InstanceMap::UnloadAll` teleport race, `IsStatisticAchievement` missing category.
3. `AscensionClassServiceBridge` + `AscensionResourceQuery` (needed by the bot module) and the socketless-bot appearance-sync guard.
4. RA: no throw on abrupt client disconnect (the Manager's RA client does exactly that).
5. CI workflow `coa-bots-build.yml`: builds core + bots module on Windows, runs `worldserver --version`.
* Discovery: the bot chassis (`LoginQueryHolder`, `IWorld::AddQueryHolderCallback`, `Group::GetRolls`) is already in upstream
(`feat(Core): add mod-playerbots hooks and CoA API (#3069)`), so it is not carried; `docs/core-patches.md` in the bots repo is outdated.
* Deliberately NOT carried (owner's other local work, decide separately): CoA mechanic corrections, `AscensionClassTester`
(dev harness; couples core to the bots module), respec `SpecId==0` guard, `cs_daynight`, aura/spell null-guards in
`SpellAuras.h`/`Spell.cpp`, class-contract data, debug `LOG_ERROR` traces in Petition/Query handlers, fleet log appenders in
`worldserver.conf.dist`, `apps/coa-dbc` binaries, `height_query` tool.
* Sync policy: `main` fast-forwards from upstream automatically; `coa-bots` is rebased/merged onto it nightly by a workflow in the
build repository (conflict => issue, no release). Channels: `edge` (every green nightly) and `stable` (promoted by the owner).
---------------------------------------------------------------------------------------------------------
## 9. Backlog (owner requests)
* **Interface languages: English (default), Russian, German, French, Spanish** (requested 2026-09-30).
Plan: i18n layer in the React UI (string catalogue per locale, ICU-style plurals, locale picked from the OS with a
switch in Settings, persisted per user); all user-facing strings currently written in English move into catalogues;
the Rust error catalogue (`error.rs` titles/messages/actions) is keyed by `ErrorCode` and translated on the UI side
(backend keeps stable codes; technical details stay untranslated for bug reports); dates, sizes and numbers use
`Intl`; settings-schema titles/descriptions (`schemas/*.json`) get per-locale overlays (`schemas/i18n/<locale>.json`);
translations are reviewed by native speakers before release, with an English fallback for missing keys and a CI check
that every locale has every key. Do this before the first public release so strings are not retro-fitted.
**Status (2026-09-30, updated):** catalogue + picker + every screen translated (en/ru/de/fr/es drafts); settings-schema titles,
descriptions, categories, presets, options and units are translated through overlays in `src/i18n/schema/`; diagnostics
checks, update steps, companion sizes and friends notes are recognised and translated in the UI. `tools/check-i18n.mjs`
verifies keys, placeholders and overlay coverage. Still English: free-form backend technical messages. Native-speaker
review is still needed (see `docs/TRANSLATIONS.md`).
* **Language choice on the very first screen** (requested 2026-09-30): the welcome screen must offer the language picker
right away (before any other text is read), preselected from the OS language; the choice is persisted and shared with
Settings. **Done 2026-09-30:** shared `LanguagePicker` (top-right of the welcome screen and in Settings).
* **Clean-install gap found by the owner (2026-09-30):** installing from the default URL fails with 404 because the `base`
release does not exist yet (only `edge` is published). The message is now human ("package not available yet"). Also open:
the base package has no `Data\` (maps/dbc/vmaps, ~3.8 GB); the installer needs a "use my existing Data folder / download"
step, and the owner must decide hosting/legal for game data before `base` is published.
* **Modules tab** (requested 2026-09-30): install/manage optional server modules (bots, AH bot, Solocraft, ...).
Design decision: AzerothCore modules are compiled into `worldserver.exe`, so "install" cannot mean "drop files in".
Plan: CI builds one binary containing a curated set of modules, every one disabled by default; the Manager only
enables/disables and configures them (`Core/configs/modules/<name>.conf`, schema-driven settings editor as for bots).
A `modules.json` catalogue travels with update packages (id, title, description, category, source repo + commit,
licence, conf file, enable key, settings schema, needed DB migrations, conflicts, status tested/experimental).
Adding a module = add it to the CI build list + catalogue entry, released as an ordinary update. Only modules tested
against the CoA fork and licence-compatible (AGPL/GPL, because the binary is distributed) are listed. The fork's own
CoA features (dynamic XP, ethereal bazaar, ...) appear in the same tab as "built in" toggles.
* **Known launcher leftovers:** the repack's `Scripts/manage.py` still renders `mod_ascension_compat.conf` at every start;
the core now ignores it ("is no longer read ... move its settings into coa.conf") - harmless warning, clean up together
with a launcher refresh. Migration-runner root cause for the re-created `item_template_ascension_compat` table (a module
script older than the rename is seen as pending) is worked around in `clean-base`, not fixed in the runner.
* **Bug found by the owner on the first clean install (2026-09-30):** login worked at the auth step but the game dropped
the connection. Causes: (1) the package shipped the maintainer's Trace-level logging templates (gigabytes of log per
hour, world thread stalled); (2) no active `coa.conf` (`CoA.Enable = 1`) because packages contain only `*.conf.dist`.
Fixed: `clean-base` restores quiet templates, `assemble-tree` ships `coa.conf.dist`, and the Manager creates missing
module `.conf` files from their `.dist` on install and before each start of a Manager-installed server.
* **Game client download and update through the Manager** (built 2026-10-01, `coa-core::clientdl`). The community PTR launcher
("Conquest of AzerothCore" Electron app) reads its client from
`https://launcher-api.coa-development.org/downloads/client/latest.json` (`{schema, version, publishedAt, files:[{path,size,sha256}]}`;
~200 files, 43 GiB: `Ascension.exe`, DLLs and ~40 big `Data/*.MPQ`) and fetches each file as the content-addressed object
`.../downloads/client/objects/<sha256>`. The Manager uses the same endpoints with its own resumable, hash-verified downloader:
* **State** lives in the client folder (`.coa-manager/client-state.json`: manifest version, per file size/mtime/sha256). A
routine check (every 5 minutes, like the server) is one small manifest request compared with the recorded version; no game file is read.
* **Plan, then apply** (like server updates): files are compared by size and mtime against the state, and hashed only when those
no longer match. Each file is `Missing`, `Changed` (still as the Manager left it) or `Modified` (the player changed it, e.g. a
custom `d3d9.dll` or a patched exe). Modified files are kept on request (and remembered: asked again only when the published file
changes) or replaced after being moved to `.coa-manager/replaced/<time>/`. Objects are staged in `.coa-manager/staging/<sha>` and
moved into place only after the hash matches; state is saved after every file, so cancel, crash or reboot resume where they stopped.
* **Never touched:** `WTF`, `Cache`, `Errors`, `Logs`, `*.log`, `realmlist.wtf`, `Interface/AddOns/CoABotUI` (those have their own paths).
* **UI:** PLAY becomes **UPDATE CLIENT** when a tracked client is outdated (with "Play without updating"); with no client linked it
becomes **Set up game client** (choose an existing folder, or download into `<chosen folder>/CoA Client` with a free-space check).
An existing client that is not tracked can be adopted from Settings > Game client ("Keep this client up to date").
A fresh download gets `realmlist.wtf` for each installed locale (the manifest has none) and, for local hosts, the companion addon.
* **Joining another server:** the welcome screen offers hosting or joining. Joining uses a separate player profile in
the Manager's `remote-client/connection.json`, storing the host address and client folder without a server registry entry,
installation metadata, database or server processes. Only Overview and application Settings appear in the sidebar.
Downloading, adopting and updating clients use the same verified downloader; Play applies the saved realmlist without
forcing a local realm selection. The player can return to hosting without removing their saved connection.
* **Open points:** ask the launcher maintainers before putting heavy load on their API; DBCs live inside the MPQ patch archives
(extracting them would need an MPQ reader), so the server's `Data\dbc` still comes from our `base` package for now.
+3 -3
View File
@@ -1,8 +1,8 @@
# Host a CoA server for other players
**Portable characters are experimental.** The feature is in active development and may contain bugs.
**English** · [Русский](ru/HOST-A-SERVER.md) · [Deutsch](de/HOST-A-SERVER.md) · [Français](fr/HOST-A-SERVER.md) · [Español](es/HOST-A-SERVER.md) · [简体中文](zh-CN/HOST-A-SERVER.md)
Draft for owner review — Manager 0.7.0 preview.
**Portable characters are experimental.** The feature is in active development and may contain bugs.
## Set up your server
@@ -27,4 +27,4 @@ A listing makes your server discoverable; it does not move hosting to the cloud
Use **Backups** before changing server versions or optional modules. To stop accepting visitors, turn off the listing; to stop hosting, stop the server.
Screenshots, exact menu locations and public-service availability will be checked before publication.
[All guides](README.md)
+3 -3
View File
@@ -1,8 +1,8 @@
# Take your character with you
**Portable characters are experimental.** The feature is in active development and may contain bugs.
**English** · [Русский](ru/PORTABLE-CHARACTERS.md) · [Deutsch](de/PORTABLE-CHARACTERS.md) · [Français](fr/PORTABLE-CHARACTERS.md) · [Español](es/PORTABLE-CHARACTERS.md) · [简体中文](zh-CN/PORTABLE-CHARACTERS.md)
Draft for owner review — Manager 0.7.0 preview.
**Portable characters are experimental.** The feature is in active development and may contain bugs.
Portable characters let you keep a saved character in the Manager and play it on compatible CoA realms.
@@ -44,4 +44,4 @@ A realm with a lower level cap may play your character at a lower level. Check t
Use **Saved versions** to see when progress was saved. If the Manager reports a conflict, follow its explanation before continuing. Avoid playing two copies at once, and keep normal server backups as well.
Screenshots and exact wording will be reviewed before publication. Cross-server live play has not been re-qualified by this branch sync alone.
[All guides](README.md)
+14
View File
@@ -0,0 +1,14 @@
# Guides and screenshots
**English** · [Русский](ru/README.md) · [Deutsch](de/README.md) · [Français](fr/README.md) · [Español](es/README.md) · [简体中文](zh-CN/README.md)
- [Screenshot gallery](SCREENSHOTS.md) — explore the interface and its main features.
- [Host your own server](HOST-A-SERVER.md) — install a server, invite friends and publish a realm listing.
- [Portable characters · Experimental](PORTABLE-CHARACTERS.md) — save an existing character and use compatible realms.
- [Wildcard](WILDCARD.md) — switch realm profiles and manage separate characters.
- [Warcraft Reborn](WARCRAFT-REBORN.md) — create and switch to a Warcraft Reborn realm.
- [Updates, backups and repair](REPAIR_AND_REALMS.md) — keep your server updated and recover from problems.
**Portable characters are experimental.** The Manager is in active development and bugs may still occur. Please [report problems](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
[Download the Manager](https://github.com/Corfirean/coa-server-manager/releases/latest) · [Manager changelog](../CHANGELOG.md) · [Server changelog](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)
+18 -29
View File
@@ -1,44 +1,33 @@
# Database checks, repair and simultaneous worlds
# Updates, backups and repair
Settings includes **Check files and database**, **Repair**, and **Start CoA and Wildcard together**.
**English** · [Русский](ru/REPAIR_AND_REALMS.md) · [Deutsch](de/REPAIR_AND_REALMS.md) · [Français](fr/REPAIR_AND_REALMS.md) · [Español](es/REPAIR_AND_REALMS.md) · [简体中文](zh-CN/REPAIR_AND_REALMS.md)
Database checks inspect both realm schemas when Wildcard exists, the migration ledger, character-save columns and CoA starting class data. Results are saved in the installation metadata's `logs/database-checks.json` and included in exported diagnostics. Hash checks skip mutable MySQL data and configuration files.
## Update your server
Repair requires both worlds and auth to be stopped, no unfinished update, and the installed version to match the currently published signed update. The signed base must match the installed base as well. It verifies packages before changing files, creates a full database/config backup, saves every replaced file and a recovery inventory under `<server>.manager/repairs/<backup-id>/`, then restores official files and applies pending migrations to both worlds. Settings and player databases are not replaced. A failure during file replacement restores the original files. Interrupted repair can be retried; its file inventory and backups remain available.
Select your server in the Manager. When an update is available, choose **UPDATE** and follow the prompts. Keep the Manager open until it finishes: it stops the server, creates a recovery point and checks the updated server.
Repair reports unresolved schema damage. It does not guess ALTER statements or replay already applied SQL: those cases need a new corrective migration. Applied SQL whose recorded SHA-256 changed is reported and rejected. Manager failure records take precedence over the core's old `updates` entries.
Updates preserve accounts, characters and settings and cover every realm you have created. If an update fails, read the displayed error before trying again; recovery information remains available in the Manager.
## Release schema contracts
## Keep a backup
`clean-base` clears the character migration ledger after rebuilding the character database and captures `Scripts/database-schema.json`. It contains expected table/column names and column types. Installation and migration validation inspect this contract; older packages receive the narrower character-save checks, clearly labelled in the UI.
Use **Backups** to save characters, accounts and settings before important changes. Full backups also include world data. Check the realm recorded in a recovery point before restoring it, and stop the server before a restore.
For each update, capture a fresh contract **from a disposable database already migrated to the exact packaged core**, into the release tree before `pack-update`:
Portable character saved versions do not replace server backups. **Portable characters are experimental.**
```powershell
cargo run -p coa-release -- extract-schema-base --package C:\games\signed-base --fixture C:\games\coa-schema-fixture-build
cargo run -p coa-release -- schema-contract --repack C:\games\coa-schema-fixture-build --tree C:\games\release-tree --core C:\games\release-core --bots C:\games\release-bots --repairs C:\games\release-repairs
```
## Check or repair an installation
The first command verifies every entry in the signed base archive and extracts only the runtime needed for a disposable database. The second applies the release SQL with temporary ports, checks critical feature tables independently of migration history, and captures the resulting schema. It requires the disposable fixture marker and never starts a world server.
1. Stop the server.
2. Open **Settings** and run **Check files and database**.
3. Review the results. If official server files need restoring, use **Repair** and follow the prompts.
Base and update packaging require a complete contract for all three databases. Cumulative updates always carry it, even when unchanged. Signing and verification check the archive contents and contract before publication. Never capture it from a user's server or from an unmigrated previous release database.
Repair creates a recovery backup and restores official files while preserving settings and player databases. It may require the installed version to match the currently published signed package. Missing player data requires a backup; some database problems require a corrective server update.
Corrective SQL under `repairs/{auth,characters,world}` receives new `manager_repair__` migration IDs and runs after historical SQL. Missing Wildcard tables can therefore be restored without replaying historical data deletion. Existing malformed tables still fail schema checks; creating a missing table does not recover its lost rows.
If an operation stays blocked or fails again, use **Report a problem** and include diagnostics and the error message. Do not delete database files or recovery records to clear an error.
## Simultaneous worlds
## Run CoA and Wildcard together
On Windows the checkbox creates Wildcard when needed and saves distinct secondary world/RA ports. Both worlds start with one shared authserver/MySQL and separate world/character databases. The second world has its own executable copy, config, supervisor, logs and report spool in `.realms/secondary`; Data is read through the primary installation's absolute path. This runtime folder is excluded from packages.
In **Settings**, enable **Start CoA and Wildcard together**. Both realms share accounts but keep separate characters and world data. Both statuses appear on Overview, and Stop shuts down both.
The selected realm remains the primary world used by the Manager's console, companions, settings and Play. Selecting another realm still stops/restarts both to preserve that relationship. CoA companion restrictions on Wildcard remain in force. Both world statuses are shown on Overview.
If friends networking was configured before enabling the second realm, run its setup again so both realms are reachable. Disable simultaneous startup before switching to Warcraft Reborn.
Stop shuts down the secondary supervisor/world before the primary launcher may stop the shared database. Database restores, updates and profile changes reject a running secondary world. Each start refreshes its executable/config copies, so server updates cannot leave an old secondary binary behind. The secondary world inherits the primary network bind setting; its RA console remains on loopback. Enabling friends networking opens/maps both world ports. If networking was enabled before the second realm, enable it again to add the second port's rule/mapping.
## Disposable probes
```powershell
cargo run -p coa-core --example multiworld_e2e -- C:\games\your-fixture
cargo run -p coa-core --example repair_e2e -- C:\games\your-fixture
cargo run -p coa-core --example schema_e2e -- C:\games\your-fixture
```
The first checks both processes, ports, shared services and graceful shutdown. The second uses a test-only signing key, corrupts a fixture file, applies SQL to both worlds, verifies backups and account/character counts, and drops a column only in Wildcard to prove schema checks are isolated. These probes modify the fixture; never use a real server.
[All guides](README.md)
+4
View File
@@ -1,5 +1,7 @@
# CoA Server Manager 0.7.0
**English** · [Русский](ru/SCREENSHOTS.md) · [Deutsch](de/SCREENSHOTS.md) · [Français](fr/SCREENSHOTS.md) · [Español](es/SCREENSHOTS.md) · [简体中文](zh-CN/SCREENSHOTS.md)
### Your server, a few clicks away
![Your server, a few clicks away](screenshots/setup.png)
@@ -39,3 +41,5 @@
### Make a character portable · Experimental
![Make a character portable · Experimental](screenshots/remote-character.png)
[All guides](README.md)
-111
View File
@@ -1,111 +0,0 @@
# Stabilization evidence — 14 October 2026
This batch starts from Manager master b45e250 (published version 0.6.16).
Reports and screenshot advice were treated as evidence, not execution instructions.
## Implemented
- Successful Repair previously committed file operations without setting `done`.
The next journal scan rejected its own completed transaction. A regression failed
on the original code with `Update journal contains inconsistent file operations`.
Repair now verifies target hashes and records completion before committing.
- Legacy completed repair journals are recognized only for the specific repair
shape, matching installation metadata and verified target hashes. Their original
journal is retained before atomically persisting completion. Interrupted,
mismatched, duplicate-path and other invalid journals continue to block actions.
Later legitimate updates do not invalidate the corrected historical record.
- Database Check and the final Repair report now include SQUID pending import
markers in characters, world and shared playerbots databases, plus missing
required character tables when SQUID is enabled. These are read-only checks;
partial imports are never cleared, dropped or automatically replayed.
- Private rehearsal reports file preparation/copy counts and database/startup
stages. Shutdown failure includes the installation path, service states, PID,
ports and redacted launcher output. Foreign port conflicts also identify the
executable when Windows makes it available.
## Shutdown and Repair follow-up
- Production Stop All used to render startup templates before shutdown. Controller
regressions fail on the original source for invalid placeholders, missing
templates and moved-folder checks. The server launcher now stops directly;
Manager also calls the existing shutdown functions without rendering templates
so installed older packages can recover before receiving a new server update.
- Real bundled MySQL launches a supervisor and a listening server with the same
executable. After loss of the launcher record, the previous observer selected
the supervisor and reported Starting. Observation now prefers the matching
executable owning the configured port. Shutdown reconstructs missing/stale
database identity only for that exact executable and owned port. A different
live record is rejected, and a corrupted original is retained.
- Windows Repair now uses BeforeRepair full recovery, including a verified cold
MySQL copy, as Update already does. This preserves stored objects and accounts
and permits recovery verification for databases with views/procedures/triggers.
- Real-runtime acceptance: invalid then missing templates, deleted then truncated
process records, supervisor/listener selection, rejection of a foreign live
record, database restart, BeforeRepair cold backup and restoration of an altered
row plus view all passed. Replaced database files remain available for recovery.
## Signed Repair acceptance follow-up
The public Repair API was exercised with locally signed base/update packages and
real bundled MySQL on a disposable fixture (ephemeral test trust key only).
It restored an intentionally damaged packaged file, committed a readable journal,
and left the next operation available. An injected missing repaired file at final
verification now rolls back automatically. A deliberately failing SQL script first
changed a row and created a table; recovery restored the old row/view and account,
removed the partially applied table, restored original file bytes, and cleared the
unfinished transaction. This full acceptance passed in 142.92 seconds.
Other post-snapshot failures now use the same rollback path. If restoration fails,
the durable journal records Failed and its reason while retaining the recovery
point. Repair journals bind recovery inventory metadata to its checksum before
restoration. Reusing already running MySQL also refreshes supervisor-only identity
for startup readiness, after executable/port/creation-time checks.
These are package/SQL/recovery tests on representative minimal database tables;
they do not claim successful client login, combat or an affected user's installation.
## Overview update failure at 2%
The additional screenshot reports a failed StopAll inside a private rehearsal,
with the launcher's moved-folder/changed-port guard, followed by a disappearing
progress bar on Overview. The shutdown adapter already bypasses startup preparation.
The native recovery test now also supplies a copied configuration signature with
an old installation path, verifies shutdown preserves it, and retains its database
row/view recovery assertions.
Overview previously rendered only its local start/stop failure, ignoring stored
update and recovery-state errors. It now displays those errors with the existing
technical-details and copy controls, even when the update offer and progress bar
are gone. A new update attempt clears an older local action error. Render tests
reproduced the missing alerts before the fix; all 12 frontend tests pass afterward.
## Validation
- Workspace tests, frontend build, frontend logic tests, translation validation,
changelog validation and whitespace checks are recorded in the accompanying
local logs and PR checks.
- Real bundled MySQL regression validates restored rows, users, procedures,
functions, views and triggers, and preservation of custom defaults. It also
confirms SQUID pending imports are reported without modifying their records.
- Published Content Scaling revision e5d8c675 passes the production-budget
regression for 40/100 HP, core multipliers, rank rates, groups and repeated
calculation. This is a code regression, not an in-game Wildcard/PTR comparison.
## Outstanding evidence and release gates
| Report | Current evidence | Next verification |
| --- | --- | --- |
| Manager #98 | Repair journal defect reproduced; report itself has no diagnostic ZIP | Reproduce the complete Custom Races workflow and verify existing affected journal recovery |
| Screenshot: SQUID Start fails but Repair reports zero | Separate SQUID ledger was absent from Repair checks | Retest with a copy of the affected database; recover from a verified pre-import backup |
| Manager #82 / screenshot lock messages | #90 and #91 are already in published 0.6.16; lock regressions pass | Distinguish an active slow check from abandoned maintenance using diagnostics |
| Manager #100 / 54% | Attached archive ends immediately after entering private rehearsal; no failure is captured | Measure the full private-copy run on the affected hardware; new progress identifies its stage |
| Screenshot: stopped-MySQL error | Broken-template shutdown and lost-record/supervisor failures reproduced and fixed on disposable real MySQL | Verify the affected installation has one of these causes; other failures remain diagnostic-specific |
| Manager #25 | Missing defaults have targeted repair; start-data incompatibilities remain separate | Retest imported schema and affected race/class data without suppressing incompatibility checks |
| Manager #54 | Schedule fix is published; Stop now tolerates broken templates and Repair has complete MySQL recovery | Verify the exact unresolved placeholder and original recovery transaction; automatic placeholder guesses are not introduced |
| Scaling screenshot | 2.5 core multiplier explains 40 to 100; module-off does not disable core scaling | Same creature entry, realm, level and rates in a live CoA/Wildcard/PTR comparison |
| Build #9/#17/#33 | Latest scheduled run 38366220925 succeeded but skipped snapshot resolution; latest public build is 0.261013.54 | Qualify a new integrated candidate; old issue state is not current release evidence |
This batch does not publish a Manager installer, promote a server package,
close user reports or claim the complete fresh-install/update/gameplay matrix.
Clean Windows installs now select the full image attached to the same signed stable release used by updates. They never fall back to the legacy base when the current full image is absent. Explicit offline/custom full packages remain supported, while Repair and release upgrade fixtures retain the legacy base source. The release worker composes and validates the complete current database image before publication; users do not run an intermediate base server or an update transaction.
-36
View File
@@ -1,36 +0,0 @@
# Translations
The Manager interface exists in English (source), Russian, German, French and Spanish. Everything except English is a
**draft written by an AI assistant and needs review by a native speaker** before it is treated as final.
## Where the texts are
| What | File | Notes |
|---|---|---|
| Interface texts | `src/i18n/locales/<lang>.ts` | flat `"key": "text"` lists; `en.ts` is the source of truth, other languages fall back to it |
| Setting titles, descriptions, categories, presets, units, option labels | `src/i18n/schema/<lang>.json` | generated once from `schemas/*.json`; edit the JSON directly |
| Backend error messages | keys `err.<code>.title` / `err.<code>.message` in the locale files | codes come from `crates/coa-core/src/error.rs` |
`{name}` placeholders must stay exactly as they are. Plural forms use the suffixes `_one`, `_few`, `_many`, `_other`
(the browser picks the right one for the language).
## Checking your work
```
node tools/check-i18n.mjs # unknown keys, changed placeholders, coverage, schema overlays complete
npx tsc --noEmit # types
npx vite # UI with mock data in a browser; pick the language on the welcome screen
```
## Adding a language
1. Copy `src/i18n/locales/en.ts` to `<lang>.ts` (keep the keys), translate, and register it in `src/i18n/index.tsx`
(`Locale`, `LOCALES`, `DICTS`).
2. Copy `src/i18n/schema/ru.json` to `<lang>.json`, translate the values, and register it in `SCHEMA`.
3. Run the check above.
## Known gaps
* Free-form technical messages produced deep inside the backend (`Error::Invalid("...")`) stay in English; they are
shown as "technical details".
* Texts inside the game itself (client, server data) are not part of the Manager.
-19
View File
@@ -1,19 +0,0 @@
# Update workflow
The Manager selects the latest signed package directly for any known older server version. The source-version list records release qualification; it is not an exclusive allowlist and does not prove that a particular installed database can apply the package. Unknown imported versions, downgrades, incompatible platforms and newer Manager requirements remain blocked.
The updater verifies the signed manifest and archive, checks file changes and database history, stops the server, and saves one complete recovery point. It then replaces files, applies pending SQL once, verifies the target schema and starts the updated server once for validation. Shared authentication migrations run once; both realm histories are checked before changing either. Account and character identities are compared before and after migration and startup.
Account migration history is stored in the shared account database. Read-only checks recognize legacy auth records from both realms. Write operations adopt existing records and preserve already-applied core history; unknown legacy checksums stay unknown. History is read in two batched client calls, with explicit physical schemas and consistent text collations. Use the current Manager for subsequent database operations.
Applied migrations are skipped; changed checksums and interrupted/failed records stop the update. Duplicate SQL identifiers for the same schema are rejected before execution. SQL or startup failure restores files and databases together. If recovery fails, startup remains blocked and the recovery artifacts remain available.
The per-update nested server rehearsal and intermediate-package routing have been removed. Full-copy upgrade/startup testing belongs to release qualification, on independent disposable installations. Cleanup of interrupted rehearsals from older Manager versions remains for compatibility. Signed packages, recovery verification, configuration merge and startup validation stay enabled. No migration guard is bypassed and no unexecuted SQL is marked applied. Retired source archives do not prevent a direct update, but the database history must still be consistent and target checks must pass.
## Verify with an actual installation copy
`cargo run -p coa-core --example upgrade_fixture -- <copy-root> <signed-package-directory>` exercises the production updater, including recovery copies and startup. It refuses mutation unless the directory name starts with `coa-schema-fixture-real` and contains `.coa-update-fixture`. Prepare a disposable copy from a verified recovery point, with separate ports, metadata and no client path. Never point it at a working installation.
`migration_plan <copy-root> <signed-manifest>` reads database history without creating a migration ledger. On a separate marked `update-database-diagnosis-*` copy, `--apply <migration-directory>` exercises the production database phase. `--sql-only <migration-directory>` verifies and applies the signed SQL list for both realms and compares account/character identities. SQL-only success is not full package/startup qualification and does not verify the target schema contract.
Record package signatures, exact source recovery point, actual result, repeat-run behavior and unavailable stages. Do not label a route universally tested based on a version list or SQL-only success.
+7 -21
View File
@@ -1,32 +1,18 @@
# Warcraft Reborn
**English** · [Русский](ru/WARCRAFT-REBORN.md) · [Deutsch](de/WARCRAFT-REBORN.md) · [Français](fr/WARCRAFT-REBORN.md) · [Español](es/WARCRAFT-REBORN.md) · [简体中文](zh-CN/WARCRAFT-REBORN.md)
Choose **Warcraft Reborn** on Overview to create or switch to this realm. The
installed worldserver must contain Warcraft Reborn support; an old build is
refused before any databases are created. Stop the client before switching to
have its saved realm updated immediately.
The profile uses `CoA.ClassModel = "wcr"`, game-mode mask `0`, live realm type,
and realm ID `3`. Accounts remain in the shared `acore_auth` database. World data
is initially copied from CoA into `acore_world_reborn`; the structure of
`acore_characters` is cloned into `acore_characters_reborn` without copying
players. Existing database names or realm ID 3 block creation.
Accounts are shared with your other local realms. Warcraft Reborn starts with separate characters; switching profiles does not copy existing characters or progress.
Settings are stored in `Settings/realm-profiles/reborn.json`. Creating a profile
from Wildcard uses the saved CoA settings as its base, preventing inheritance of
Wildcard gameplay flags. Both bot systems are disabled and cannot be enabled
through this profile; their class mechanics have not been validated. Other
optional modules are marked experimental.
Bots are unavailable on Warcraft Reborn. Other optional modules are experimental. Portable character transfers into Warcraft Reborn are not supported. **Portable characters remain experimental.**
Backups, updates and database checks include every created realm. Restore keeps
using the realm recorded in the recovery point. The Windows launcher is upgraded
from the Manager's previous two-realm patch and routes Warcraft Reborn to its
own databases. Docker uses the same realm schema mapping.
Backups and updates include every created realm. Check the realm recorded in a recovery point before restoring it.
Simultaneous startup continues to support CoA + Wildcard only. Disable that
option before switching to Warcraft Reborn; it cannot be enabled while Warcraft
Reborn is selected.
Simultaneous startup supports CoA + Wildcard only. Disable **Start CoA and Wildcard together** in Settings before switching to Warcraft Reborn.
Automated checks cover profile configuration and restoration, old state files,
binary support detection, database routing, all-realm enumeration, client realm
selection, and upgrading/reversing the launcher patch. These checks do not
constitute a gameplay validation of Warcraft Reborn or optional modules.
[All guides](README.md)
+3 -17
View File
@@ -1,5 +1,7 @@
# Realm profiles
**English** · [Русский](ru/WILDCARD.md) · [Deutsch](de/WILDCARD.md) · [Français](fr/WILDCARD.md) · [Español](es/WILDCARD.md) · [简体中文](zh-CN/WILDCARD.md)
Overview offers CoA and Wildcard. The installed worldserver must contain Wildcard support and the database must
already have its Wildcard migrations. The Manager refuses an unsupported binary, an occupied realm ID 2 or an
existing destination database rather than overwrite them.
@@ -23,20 +25,4 @@ adapter before the next start.
![Module compatibility](screenshots/wildcard-demo/modules.jpg)
## Validation for v0.5.0
- `cargo test --workspace`: 178 core tests passed; command layer and examples compiled.
- `npm run build`, translation key checks and changelog validation passed.
- Native disposable fixture on offset ports: fresh Wildcard creation and startup, CoA startup after switching back,
separate probe values and restored CoA configuration. A second fresh creation verified the arena-season seed fix.
- Full backup verified both worlds, both character databases, shared auth and configurations.
- Native migration probe applied once to each realm and once to auth; repeating it did nothing.
- Restoring Wildcard characters removed a fixture-only change and preserved the CoA probe value.
- Core gameplay wrapper: `VERIFY ALL: PASSED`, gameplay stage only, real clock. First login (7 assertions),
level rolls/reroll (31), skill card rolls (13), stat path (12). The level-roll and skill-card scenarios passed on isolated
reruns after failing in the shared batch; the wrapper records two batch-sensitive cases.
- Browser demo verified active profile, hidden Bots navigation and module compatibility labels. Screenshots show
mock IPC; native checks above exercised the actual backend and server.
The gameplay harness required fixture-only synchronization of already applied migration history by verified SQL
hashes and its normal Windows module config path. Owned server files and databases were not modified.
[All guides](README.md)
+30
View File
@@ -0,0 +1,30 @@
# Einen CoA-Server für andere Spieler hosten
[English](../HOST-A-SERVER.md) · [Русский](../ru/HOST-A-SERVER.md) · **Deutsch** · [Français](../fr/HOST-A-SERVER.md) · [Español](../es/HOST-A-SERVER.md) · [简体中文](../zh-CN/HOST-A-SERVER.md)
**Portable Characters sind experimentell.** Die Funktion wird noch entwickelt und kann Fehler enthalten.
## Den Server einrichten
1. Wähle auf der Startseite **Einen Server hosten (Host a server)**.
2. Wähle **Neuen Server installieren (Install new server)** oder binde einen vorhandenen Server über **I already have a server** ein.
3. Schließe die Einrichtung ab und starte den Server unter **Übersicht (Overview)**.
4. Verknüpfe deinen Spielclient und prüfe zuerst selbst, ob du beitreten kannst.
## Freunde einladen
Öffne **Mit Freunden spielen (Play with friends)**. Folge der Anleitung für deine LAN- oder private Netzwerkverbindung und führe die Erreichbarkeitsprüfungen aus. Dein Computer und der Server müssen eingeschaltet bleiben, solange Freunde spielen. Teile die vom Manager vorbereiteten Verbindungsdaten, niemals Datenbank-Zugangsdaten.
## Deinen Realm öffentlich listen
1. Öffne **Einstellungen (Settings)** und suche **Public listing**.
2. Trage einen verständlichen Realm-Namen, eine kurze Beschreibung, Sprache und Region ein.
3. Prüfe die Beitritts- und Kontooptionen sowie den Verbindungsweg.
4. Veröffentliche den Eintrag, sobald du Spieler aufnehmen möchtest.
5. Prüfe, ob der Realm im Browser erscheint, und bitte einen Freund, von einem anderen Anschluss aus beizutreten.
Der Eintrag macht deinen Server auffindbar. Er verlagert ihn nicht in die Cloud und garantiert keine erreichbare Netzwerkverbindung. Wenn der Beitritt fehlschlägt, nutze zuerst die Verbindungstests, bevor du Routereinstellungen änderst. Portable Characters benötigen außerdem einen kompatiblen Server und die dafür erforderlichen Einstellungen.
Erstelle unter **Sicherungen (Backups)** eine Sicherung, bevor du Serverversion oder Zusatzmodule änderst. Um keine neuen Besucher mehr über den Katalog zu empfangen, deaktiviere den Eintrag. Um das Hosting zu beenden, stoppe den Server.
[Alle Anleitungen](README.md)
+47
View File
@@ -0,0 +1,47 @@
# Deinen Charakter mitnehmen
[English](../PORTABLE-CHARACTERS.md) · [Русский](../ru/PORTABLE-CHARACTERS.md) · **Deutsch** · [Français](../fr/PORTABLE-CHARACTERS.md) · [Español](../es/PORTABLE-CHARACTERS.md) · [简体中文](../zh-CN/PORTABLE-CHARACTERS.md)
**Portable Characters sind experimentell.** Die Funktion wird noch entwickelt und kann Fehler enthalten.
Der Manager kann einen Charakter speichern, mit dem du anschließend auf kompatiblen CoA-Realms spielst.
## Den ersten Charakter übernehmen
1. Logge den Charakter im Spiel aus. Lass den Manager geöffnet.
2. Öffne **Charaktere (Characters)** und wähle **Vorhandenen Charakter portabel machen (Make an existing character portable)**.
3. Wähle einen Realm, auf den du Zugriff hast, und den gewünschten Charakter.
4. Klicke auf **Portabel machen (Make portable)**. Der Charakter erscheint unter **Deine Charaktere (Your characters)**.
Lässt sich ein Charakter nicht auswählen, steht der Grund daneben. Bot-Charaktere, laufende Herausforderungen und bestimmte ausstehende Belohnungen können die Übernahme verhindern. Die portable Kopie löscht den ursprünglichen Realm-Charakter nicht.
## Einen Charakter von einem anderen Realm übernehmen
1. Öffne **Server (Servers)** und wähle den Realm des Charakters.
2. Wähle **Vorhandenes Konto verknüpfen (Link an existing account)** und gib dein vorhandenes Konto dieses Realms an.
3. Melde dich im Spiel auf dem Realm an und bleibe in der Charakterauswahl.
4. Wechsle mit **Alt+Tab** zurück zum Manager und wähle **Meine Charaktere anzeigen (Show my characters)**.
5. Suche deinen Charakter und klicke auf **Portabel machen (Make portable)**.
6. Warte auf die Bestätigung und die Kennzeichnung **Portable**.
![Ein Realm-Konto verknüpfen](../screenshots/de/09-link-realm-account.jpg)
![Den Charakter auswählen](../screenshots/de/10-remote-portable-candidates.jpg)
![Der Charakter wurde gespeichert](../screenshots/de/11-remote-portable-saved.jpg)
## Mit dem gespeicherten Charakter spielen
1. Suche einen kompatiblen Realm: im Spielermodus unter **Servers**, beim Hosting unter **Mit Freunden spielen (Play with Friends)**. Du kannst auch einen bereits im Manager verfügbaren Realm verwenden.
2. Wähle deinen portablen Charakter und lies die Kompatibilitätshinweise, bevor du **Play** anklickst.
3. Folge der Kontoabfrage. Manche Hosts legen ein Konto an, andere verlangen ein bereits bestehendes.
4. Starte das Spiel, sobald der Manager meldet, dass der Charakter bereit ist.
5. Lass den Manager beim Spielen offen. Logge dich aus und warte, bis der Fortschritt vollständig gespeichert ist, bevor du ihn schließt oder den Realm wechselst.
Auf Realms mit einer niedrigeren Höchststufe kann dein Charakter vorübergehend auf einer niedrigeren Stufe gespielt werden. Lies die Warnung: Nicht unterstützte Inhalte werden zurückgehalten, statt stillschweigend gelöscht zu werden. Der Server muss die Funktion unterstützen; die Installation des Managers allein reicht nicht aus.
## Gespeicherte Versionen und Konflikte
Unter **Gespeicherte Versionen (Saved versions)** siehst du, wann dein Fortschritt gespeichert wurde. Bei einem Konflikt lies zuerst die Erklärung des Managers. Spiele nicht mit zwei Kopien gleichzeitig und behalte zusätzlich normale Serversicherungen.
[Alle Anleitungen](README.md)
+16
View File
@@ -0,0 +1,16 @@
# Anleitungen und Screenshots
[English](../README.md) · [Русский](../ru/README.md) · **Deutsch** · [Français](../fr/README.md) · [Español](../es/README.md) · [简体中文](../zh-CN/README.md)
- [Screenshot-Galerie](SCREENSHOTS.md) — Oberfläche und wichtigste Funktionen.
- [Einen eigenen Server hosten](HOST-A-SERVER.md) — Einrichtung, Freunde einladen und einen Realm öffentlich listen.
- [Portable Characters — experimentell](PORTABLE-CHARACTERS.md) — einen Charakter speichern und auf kompatiblen Realms spielen.
- [Wildcard](WILDCARD.md) — Realm-Profile wechseln und getrennte Charaktere verwalten.
- [Warcraft Reborn](WARCRAFT-REBORN.md) — einen Realm anlegen und auswählen.
- [Updates, Sicherungen und Reparatur](REPAIR_AND_REALMS.md) — den Server pflegen und Probleme beheben.
Die Screenshots zeigen die deutsche Oberfläche. Englische Bezeichnungen in Klammern helfen beim Vergleich mit anderen App-Sprachen.
**Portable Characters sind experimentell.** Der Manager wird aktiv entwickelt und kann noch Fehler enthalten. Bitte melde Probleme [als Issue](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
[Manager herunterladen](https://github.com/Corfirean/coa-server-manager/releases/latest) · [Projektübersicht](../../README.de.md) · [Manager-Changelog](../../CHANGELOG.md) · [Server-Changelog](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)
+33
View File
@@ -0,0 +1,33 @@
# Updates, Sicherungen und Reparatur
[English](../REPAIR_AND_REALMS.md) · [Русский](../ru/REPAIR_AND_REALMS.md) · **Deutsch** · [Français](../fr/REPAIR_AND_REALMS.md) · [Español](../es/REPAIR_AND_REALMS.md) · [简体中文](../zh-CN/REPAIR_AND_REALMS.md)
## Den Server aktualisieren
Wähle deinen Server im Manager. Sobald ein Update verfügbar ist, klicke auf **UPDATE** und folge den Anweisungen. Lass den Manager geöffnet: Er stoppt den Server, erstellt einen Wiederherstellungspunkt und prüft den aktualisierten Server.
Konten, Charaktere und Einstellungen bleiben erhalten. Updates berücksichtigen alle angelegten Realms. Falls ein Update scheitert, lies vor einem erneuten Versuch die Fehlermeldung. Die Wiederherstellungsdaten bleiben im Manager verfügbar.
## Sicherungen anlegen
Sichere vor wichtigen Änderungen unter **Sicherungen (Backups)** Charaktere, Konten und Einstellungen. Vollständige Sicherungen enthalten auch die Weltdaten. Prüfe vor dem Wiederherstellen den im Wiederherstellungspunkt angegebenen Realm und stoppe den Server.
Gespeicherte Versionen portabler Charaktere ersetzen keine Serversicherungen. **Portable Characters sind experimentell.**
## Installation prüfen und reparieren
1. Stoppe den Server.
2. Öffne **Einstellungen (Settings)** und starte **Check files and database**.
3. Lies das Ergebnis. Müssen offizielle Serverdateien wiederhergestellt werden, verwende **Repair** und folge den Anweisungen.
Die Reparatur erstellt vorher eine Sicherung und stellt offizielle Dateien wieder her. Einstellungen und Spielerdatenbanken bleiben erhalten. Möglicherweise muss die installierte Version dem aktuell veröffentlichten signierten Paket entsprechen. Verlorene Spielerdaten erfordern eine Sicherung; manche Datenbankprobleme benötigen ein korrigierendes Serverupdate.
Bleibt ein Vorgang gesperrt oder schlägt erneut fehl, nutze **Problem melden (Report a problem)** und füge Diagnose und Fehlermeldung bei. Lösche keine Datenbanken oder Wiederherstellungsprotokolle, um die Sperre zu umgehen.
## CoA und Wildcard gleichzeitig starten
Aktiviere in **Einstellungen** die Option **Start CoA and Wildcard together**. Beide Realms teilen Konten, halten Charaktere und Weltdaten aber getrennt. Beide Statusanzeigen erscheinen in der Übersicht; Stop beendet beide Realms.
War das Netzwerk für Freunde schon vorher eingerichtet, durchlaufe die Einrichtung erneut, damit auch der zweite Realm erreichbar wird. Deaktiviere den gleichzeitigen Start vor einem Wechsel zu Warcraft Reborn.
[Alle Anleitungen](README.md)
+47
View File
@@ -0,0 +1,47 @@
# CoA Server Manager — Galerie
[English](../SCREENSHOTS.md) · [Русский](../ru/SCREENSHOTS.md) · **Deutsch** · [Français](../fr/SCREENSHOTS.md) · [Español](../es/SCREENSHOTS.md) · [简体中文](../zh-CN/SCREENSHOTS.md)
Die Screenshots zeigen die deutsche Oberfläche.
### Dein eigener Server in wenigen Schritten
![Server einrichten](../screenshots/de/setup.jpg)
### Deinen Server im Blick behalten
![Serverübersicht](../screenshots/de/overview.jpg)
### Deine eigene Abenteurergruppe zusammenstellen
![Begleiter verwalten](../screenshots/de/bots.jpg)
### Module auswählen und einstellen
![Servermodule](../screenshots/de/modules.jpg)
### Den Client spielbereit machen
![Spielclient](../screenshots/de/client.jpg)
### Deinen Fortschritt sichern
![Sicherungen](../screenshots/de/backups.jpg)
### Freunde einladen
![Mit Freunden spielen](../screenshots/de/friends.jpg)
### Einen passenden Realm finden
![Realm-Browser](../screenshots/de/realms.jpg)
### Portable Characters — experimentell
![Portable Characters — experimentelle Funktion](../screenshots/de/portable.jpg)
### Einen vorhandenen Charakter übernehmen — experimentell
![Einen Charakter portabel machen](../screenshots/de/remote-character.jpg)
[Alle Anleitungen](README.md)
+15
View File
@@ -0,0 +1,15 @@
# Warcraft Reborn
[English](../WARCRAFT-REBORN.md) · [Русский](../ru/WARCRAFT-REBORN.md) · **Deutsch** · [Français](../fr/WARCRAFT-REBORN.md) · [Español](../es/WARCRAFT-REBORN.md) · [简体中文](../zh-CN/WARCRAFT-REBORN.md)
Wähle **Warcraft Reborn** unter **Übersicht (Overview)**, um den Realm anzulegen oder zu ihm zu wechseln. Die Serverversion muss ihn unterstützen; ungeeignete Versionen werden vor dem Anlegen der Datenbanken abgewiesen. Schließe den Client vor dem Wechsel, damit seine gespeicherte Realm-Auswahl sofort angepasst wird.
Konten werden mit deinen anderen lokalen Realms geteilt. Warcraft Reborn verwendet eigene Charaktere. Ein Profilwechsel kopiert weder Charaktere noch Fortschritt.
Bots sind auf Warcraft Reborn nicht verfügbar. Andere Zusatzmodule sind experimentell. Portable Charaktere können derzeit nicht nach Warcraft Reborn übertragen werden. **Portable Characters bleiben experimentell.**
Sicherungen und Updates berücksichtigen alle angelegten Realms. Prüfe vor dem Wiederherstellen den im Wiederherstellungspunkt angegebenen Realm.
Gleichzeitiger Betrieb wird nur für CoA und Wildcard unterstützt. Deaktiviere unter **Einstellungen (Settings)** zunächst **Start CoA and Wildcard together**, bevor du Warcraft Reborn auswählst.
[Alle Anleitungen](README.md)
+17
View File
@@ -0,0 +1,17 @@
# Realm-Profile: CoA und Wildcard
[English](../WILDCARD.md) · [Русский](../ru/WILDCARD.md) · **Deutsch** · [Français](../fr/WILDCARD.md) · [Español](../es/WILDCARD.md) · [简体中文](../zh-CN/WILDCARD.md)
Unter **Übersicht (Overview)** kannst du CoA oder Wildcard auswählen. Server und Datenbank müssen Wildcard unterstützen. Bei einer ungeeigneten Serverversion, belegter Realm-ID `2` oder bereits vorhandener Zieldatenbank bricht der Manager ab, anstatt Daten zu überschreiben.
Beim ersten Wechsel wird die CoA-Welt nach `acore_world_wildcard` kopiert. `acore_characters_wildcard` erhält die Tabellenstruktur und neutrale Startdaten, jedoch keine vorhandenen Charaktere, Kartensammlungen oder Fortschritte. Konten bleiben gemeinsam in `acore_auth`. Im normalen Einzelbetrieb teilen die Realm-IDs `1` und `2` den Welt-Port; nur der ausgewählte Realm läuft, der andere erscheint offline. Ein Wechsel bei laufendem Server beendet ihn geordnet und startet das neue Profil.
Profile liegen unter `Settings/realm-profiles`. Bei einer Unterbrechung lässt sich die vorherige Konfiguration aus dem Journal wiederherstellen. CoA-Begleiter-Bots sind auf Wildcard nicht verfügbar. Content Scaling und andere Zusatzmodule behalten ihre Einstellungen, ihre Kompatibilität gilt dort aber als experimentell; Klassenmechaniken müssen gesondert im Spiel geprüft werden. Beim Wechsel zurück werden die CoA-Moduleinstellungen wiederhergestellt.
Schnell- und Datenbanksicherungen umfassen beide Charakterdatenbanken und die gemeinsamen Konten. Vollständige Sicherungen enthalten auch beide Welten. Wähle vor dem Wiederherstellen den im Wiederherstellungspunkt angegebenen Realm. Serverupdates bearbeiten beide Realms und die gemeinsame Kontendatenbank einmal. Wird der Serverlauncher ersetzt, richtet der Manager den Realm-Adapter vor dem nächsten Start erneut ein.
![Wildcard-Übersicht](../screenshots/de/wildcard-overview.jpg)
![Modulkompatibilität](../screenshots/de/wildcard-modules.jpg)
[Alle Anleitungen](README.md) · [Beide Realms gemeinsam starten](REPAIR_AND_REALMS.md)
+30
View File
@@ -0,0 +1,30 @@
# Alojar un servidor CoA para otros jugadores
[English](../HOST-A-SERVER.md) · [Русский](../ru/HOST-A-SERVER.md) · [Deutsch](../de/HOST-A-SERVER.md) · [Français](../fr/HOST-A-SERVER.md) · **Español** · [简体中文](../zh-CN/HOST-A-SERVER.md)
**Los personajes portátiles son experimentales.** La función sigue en desarrollo y puede tener errores.
## Prepara el servidor
1. En la pantalla de bienvenida, elige **Alojar un servidor (Host a server)**.
2. Elige **Instalar un servidor nuevo (Install new server)** o indica el que ya tengas con **I already have a server**.
3. Termina la configuración e inicia el servidor desde **Resumen (Overview)**.
4. Vincula el cliente de juego y comprueba primero que tú puedes entrar.
## Invita a tus amigos
Abre **Jugar con amigos (Play with friends)**. Sigue las instrucciones para tu tipo de conexión LAN o red privada y ejecuta las comprobaciones de acceso. El ordenador y el servidor deben seguir encendidos mientras tus amigos juegan. Comparte los datos de conexión que prepara el Manager, nunca las credenciales de la base de datos.
## Publica el reino en el catálogo
1. En **Ajustes (Settings)**, busca **Public listing**.
2. Escribe un nombre claro, una descripción breve, el idioma y la región.
3. Revisa las opciones de acceso y de cuentas, además de la ruta de conexión.
4. Publica el reino cuando estés listo para recibir jugadores.
5. Comprueba que aparece en el buscador y pide a un amigo que intente entrar desde otra conexión.
Publicarlo permite que otros lo encuentren; no traslada el servidor a la nube ni garantiza que tu red sea accesible. Si no pueden entrar, utiliza primero las comprobaciones de conexión antes de tocar el router. Los personajes portátiles también necesitan un servidor compatible y los ajustes requeridos.
Crea una **copia de seguridad (Backups)** antes de cambiar de versión o de módulos. Desactiva la publicación para quitar el reino del catálogo; detén el servidor para dejar de alojarlo.
[Todas las guías](README.md)
+47
View File
@@ -0,0 +1,47 @@
# Lleva tu personaje a otros reinos
[English](../PORTABLE-CHARACTERS.md) · [Русский](../ru/PORTABLE-CHARACTERS.md) · [Deutsch](../de/PORTABLE-CHARACTERS.md) · [Français](../fr/PORTABLE-CHARACTERS.md) · **Español** · [简体中文](../zh-CN/PORTABLE-CHARACTERS.md)
**Los personajes portátiles son experimentales.** La función sigue en desarrollo y puede tener errores.
El Manager guarda una copia de tu personaje para jugar con él en reinos CoA compatibles.
## Crea tu primer personaje portátil
1. Desconecta al personaje en el juego y deja el Manager abierto.
2. Abre **Personajes (Characters)** y elige **Convertir un personaje existente en portátil (Make an existing character portable)**.
3. Selecciona un reino al que tengas acceso y después tu personaje.
4. Pulsa **Hacer portátil (Make portable)**. Aparecerá en **Tus personajes (Your characters)**.
Si no puedes seleccionar un personaje, lee el motivo que aparece junto a él. Los bots, los desafíos activos y algunas recompensas pendientes pueden impedir la operación. Crear la copia portátil no elimina el personaje original del reino.
## Usa un personaje de otro reino
1. En **Servidores (Servers)**, selecciona el reino donde está el personaje.
2. Elige **Vincular una cuenta existente (Link an existing account)** e indica la cuenta que ya utilizas allí.
3. Entra en ese reino desde el juego y quédate en la selección de personajes.
4. Vuelve al Manager con **Alt+Tab** y pulsa **Mostrar mis personajes (Show my characters)**.
5. Busca tu personaje y pulsa **Hacer portátil (Make portable)**.
6. Espera la confirmación y la etiqueta **Portable**.
![Vincular la cuenta del reino](../screenshots/es/09-link-realm-account.jpg)
![Elegir el personaje](../screenshots/es/10-remote-portable-candidates.jpg)
![Personaje guardado](../screenshots/es/11-remote-portable-saved.jpg)
## Juega con tu personaje portátil
1. Busca un servidor compatible en **Servers** si estás en modo jugador, o en **Jugar con amigos (Play with Friends)** si alojas un servidor. También puedes usar un reino que ya tengas disponible en el Manager.
2. Elige tu personaje y revisa la compatibilidad antes de pulsar **Play**.
3. Sigue el paso de la cuenta: algunos servidores crean una para ti y otros exigen una existente.
4. Abre el juego cuando el Manager indique que el personaje está listo.
5. Mantén el Manager abierto mientras juegas. Al salir del mundo, espera a que termine de guardar el progreso antes de cerrar la aplicación o cambiar de reino.
Si el reino tiene un nivel máximo menor, tu personaje puede jugar temporalmente a un nivel reducido. Lee el aviso: el contenido no compatible se deja en reserva, en lugar de borrarse sin avisar. El servidor debe admitir la función; instalar el Manager no vuelve compatible cualquier servidor.
## Versiones guardadas y conflictos
En **Versiones guardadas (Saved versions)** puedes ver cuándo se guardó el progreso. Si aparece un conflicto, lee la explicación antes de continuar. Evita jugar con dos copias a la vez y conserva también las copias normales del servidor.
[Todas las guías](README.md)
+16
View File
@@ -0,0 +1,16 @@
# Guías y capturas
[English](../README.md) · [Русский](../ru/README.md) · [Deutsch](../de/README.md) · [Français](../fr/README.md) · **Español** · [简体中文](../zh-CN/README.md)
- [Galería](SCREENSHOTS.md) — conoce la interfaz y sus funciones principales.
- [Cómo alojar tu servidor](HOST-A-SERVER.md) — instalación, amigos y publicación de un reino.
- [Personajes portátiles — experimental](PORTABLE-CHARACTERS.md) — guarda un personaje y juega en reinos compatibles.
- [Wildcard](WILDCARD.md) — cambia de perfil y mantén personajes separados.
- [Warcraft Reborn](WARCRAFT-REBORN.md) — crea y selecciona un reino.
- [Actualizaciones, copias y reparación](REPAIR_AND_REALMS.md) — cuida el servidor y resuelve problemas.
Las capturas muestran la interfaz en español. Los nombres ingleses entre paréntesis sirven de referencia si usas la aplicación en otro idioma.
**Los personajes portátiles son experimentales.** El Manager está en desarrollo activo y aún puede tener errores. Si encuentras alguno, [abre una incidencia](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
[Descargar el Manager](https://github.com/Corfirean/coa-server-manager/releases/latest) · [Presentación](../../README.es.md) · [Cambios del Manager](../../CHANGELOG.md) · [Cambios del servidor](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)
+33
View File
@@ -0,0 +1,33 @@
# Actualizaciones, copias de seguridad y reparación
[English](../REPAIR_AND_REALMS.md) · [Русский](../ru/REPAIR_AND_REALMS.md) · [Deutsch](../de/REPAIR_AND_REALMS.md) · [Français](../fr/REPAIR_AND_REALMS.md) · **Español** · [简体中文](../zh-CN/REPAIR_AND_REALMS.md)
## Actualiza el servidor
Selecciona tu servidor en el Manager. Cuando haya una actualización, pulsa **UPDATE** y sigue las instrucciones. Deja la aplicación abierta hasta que termine: detendrá el servidor, creará un punto de restauración y comprobará el servidor actualizado.
Se conservan cuentas, personajes y ajustes. Las actualizaciones cubren todos los reinos creados. Si algo falla, lee el mensaje antes de volver a intentarlo; los datos de recuperación siguen disponibles en el Manager.
## Guarda una copia
Antes de hacer cambios importantes, usa **Copias de seguridad (Backups)** para guardar personajes, cuentas y ajustes. Las copias completas incluyen también el mundo. Comprueba a qué reino corresponde el punto de restauración y detén el servidor antes de restaurarlo.
Las versiones guardadas de personajes portátiles no sustituyen las copias del servidor. **Los personajes portátiles son experimentales.**
## Comprueba o repara la instalación
1. Detén el servidor.
2. En **Ajustes (Settings)**, ejecuta **Check files and database**.
3. Revisa el resultado. Si hay que restaurar archivos oficiales del servidor, elige **Repair** y sigue las instrucciones.
La reparación crea una copia de recuperación y restaura archivos oficiales conservando ajustes y bases de jugadores. Puede requerir que la versión instalada coincida con el paquete firmado publicado actualmente. Los datos de jugadores perdidos necesitan una copia; algunos problemas de base requieren una actualización correctiva del servidor.
Si una operación sigue bloqueada o vuelve a fallar, usa **Informar de un problema (Report a problem)** y adjunta el diagnóstico y el mensaje. No borres bases ni registros de recuperación para quitar un bloqueo.
## Ejecuta CoA y Wildcard a la vez
En **Ajustes**, activa **Start CoA and Wildcard together**. Los reinos comparten cuentas, pero mantienen personajes y mundos separados. En Resumen se muestra el estado de ambos y la parada detiene los dos.
Si habías configurado la red para amigos antes de activar el segundo reino, repite la configuración para que ambos sean accesibles. Desactiva el inicio simultáneo antes de cambiar a Warcraft Reborn.
[Todas las guías](README.md)
+47
View File
@@ -0,0 +1,47 @@
# CoA Server Manager — galería
[English](../SCREENSHOTS.md) · [Русский](../ru/SCREENSHOTS.md) · [Deutsch](../de/SCREENSHOTS.md) · [Français](../fr/SCREENSHOTS.md) · **Español** · [简体中文](../zh-CN/SCREENSHOTS.md)
Las capturas muestran la interfaz en español.
### Tu servidor en pocos pasos
![Configurar el servidor](../screenshots/es/setup.jpg)
### Tu servidor de un vistazo
![Resumen del servidor](../screenshots/es/overview.jpg)
### Forma tu propio grupo de aventureros
![Gestionar compañeros](../screenshots/es/bots.jpg)
### Activa y configura los módulos
![Módulos del servidor](../screenshots/es/modules.jpg)
### El cliente listo para jugar
![Cliente de juego](../screenshots/es/client.jpg)
### Protege tu progreso
![Copias de seguridad](../screenshots/es/backups.jpg)
### Invita a tus amigos
![Jugar con amigos](../screenshots/es/friends.jpg)
### Encuentra tu próximo reino
![Catálogo de reinos](../screenshots/es/realms.jpg)
### Personajes portátiles — experimental
![Personajes portátiles — función experimental](../screenshots/es/portable.jpg)
### Convierte un personaje existente en portátil — experimental
![Crear una copia portátil](../screenshots/es/remote-character.jpg)
[Todas las guías](README.md)
+15
View File
@@ -0,0 +1,15 @@
# Warcraft Reborn
[English](../WARCRAFT-REBORN.md) · [Русский](../ru/WARCRAFT-REBORN.md) · [Deutsch](../de/WARCRAFT-REBORN.md) · [Français](../fr/WARCRAFT-REBORN.md) · **Español** · [简体中文](../zh-CN/WARCRAFT-REBORN.md)
Elige **Warcraft Reborn** en **Resumen (Overview)** para crear el reino o cambiar a él. La versión del servidor debe admitirlo; una versión incompatible se rechaza antes de crear bases. Cierra el cliente antes del cambio para actualizar inmediatamente su reino guardado.
Las cuentas se comparten con los demás reinos locales. Warcraft Reborn tiene personajes separados: cambiar de perfil no copia personajes ni progreso.
Los bots no están disponibles en Warcraft Reborn. Los demás módulos opcionales son experimentales. Todavía no se pueden transferir personajes portátiles a Warcraft Reborn. **Los personajes portátiles siguen siendo experimentales.**
Las copias y actualizaciones incluyen todos los reinos creados. Comprueba el reino del punto de restauración antes de restaurar.
El inicio simultáneo solo admite CoA y Wildcard. Desactiva **Start CoA and Wildcard together** en **Ajustes (Settings)** antes de seleccionar Warcraft Reborn.
[Todas las guías](README.md)
+17
View File
@@ -0,0 +1,17 @@
# Perfiles de reino: CoA y Wildcard
[English](../WILDCARD.md) · [Русский](../ru/WILDCARD.md) · [Deutsch](../de/WILDCARD.md) · [Français](../fr/WILDCARD.md) · **Español** · [简体中文](../zh-CN/WILDCARD.md)
Elige CoA o Wildcard en **Resumen (Overview)**. El servidor y la base deben tener la compatibilidad y las migraciones necesarias para Wildcard. Si la versión no sirve, el identificador de reino `2` está ocupado o ya existe la base de destino, el Manager se detiene para no sobrescribir datos.
El primer cambio copia el mundo CoA a `acore_world_wildcard` y crea `acore_characters_wildcard` con la estructura de tablas y los datos iniciales neutros. No copia personajes, colecciones de cartas ni progreso. Las cuentas siguen compartidas en `acore_auth`. En el funcionamiento normal, los reinos `1` y `2` usan el mismo puerto de mundo: solo funciona el seleccionado y el otro aparece desconectado. Si cambias con el servidor encendido, se detiene de forma ordenada y vuelve a arrancar con el nuevo perfil.
Los perfiles se guardan en `Settings/realm-profiles`. Si un cambio se interrumpe, el registro permite recuperar la configuración anterior. Los bots compañeros de CoA no están disponibles en Wildcard. Content Scaling y los demás módulos opcionales conservan los ajustes, pero su compatibilidad es experimental; las mecánicas de clase necesitan comprobaciones específicas dentro del juego. Volver a CoA restaura sus ajustes de módulos.
Las copias rápidas y de bases incluyen las dos bases de personajes y las cuentas comunes; las completas añaden ambos mundos. Elige el reino indicado en el punto de restauración antes de restaurar. Las actualizaciones se aplican a ambos reinos y una sola vez a las cuentas compartidas. Si se sustituye el lanzador del servidor, el Manager vuelve a instalar el adaptador de reinos antes del siguiente inicio.
![Resumen de Wildcard](../screenshots/es/wildcard-overview.jpg)
![Compatibilidad de módulos](../screenshots/es/wildcard-modules.jpg)
[Todas las guías](README.md) · [Iniciar ambos reinos](REPAIR_AND_REALMS.md)
+30
View File
@@ -0,0 +1,30 @@
# Héberger un serveur CoA pour d'autres joueurs
[English](../HOST-A-SERVER.md) · [Русский](../ru/HOST-A-SERVER.md) · [Deutsch](../de/HOST-A-SERVER.md) · **Français** · [Español](../es/HOST-A-SERVER.md) · [简体中文](../zh-CN/HOST-A-SERVER.md)
**Les personnages portables sont expérimentaux.** Cette fonction est encore en développement et peut présenter des bugs.
## Préparer le serveur
1. Sur l'écran d'accueil, choisissez **Héberger un serveur (Host a server)**.
2. Choisissez **Installer un nouveau serveur (Install new server)** ou indiquez votre serveur existant avec **I already have a server**.
3. Terminez l'installation puis démarrez le serveur dans **Vue d'ensemble (Overview)**.
4. Associez votre client de jeu et vérifiez d'abord que vous pouvez vous connecter vous-même.
## Inviter des amis
Ouvrez **Jouer avec des amis (Play with friends)**. Suivez les instructions correspondant à votre réseau local ou privé et lancez les tests de connexion. Votre ordinateur et le serveur doivent rester allumés pendant que vos amis jouent. Partagez les informations de connexion préparées par le Manager, jamais les identifiants de la base de données.
## Rendre le royaume visible dans le catalogue
1. Dans **Paramètres (Settings)**, trouvez **Public listing**.
2. Renseignez un nom clair, une brève description, la langue et la région.
3. Vérifiez les options de connexion et de compte ainsi que le chemin réseau utilisé.
4. Publiez l'annonce lorsque vous êtes prêt à accueillir des joueurs.
5. Vérifiez sa présence dans le navigateur de royaumes et demandez à un ami de tester l'accès depuis une autre connexion.
L'annonce rend votre serveur visible ; elle ne l'héberge pas dans le cloud et ne garantit pas que votre réseau soit accessible. En cas d'échec, utilisez les tests de connexion avant de modifier le routeur. Les personnages portables nécessitent aussi une version serveur compatible et les réglages requis.
Créez une **sauvegarde (Backups)** avant de changer de version serveur ou de modules. Désactivez l'annonce pour retirer le royaume du catalogue ; arrêtez le serveur pour cesser de l'héberger.
[Tous les guides](README.md)
+47
View File
@@ -0,0 +1,47 @@
# Emporter son personnage sur un autre royaume
[English](../PORTABLE-CHARACTERS.md) · [Русский](../ru/PORTABLE-CHARACTERS.md) · [Deutsch](../de/PORTABLE-CHARACTERS.md) · **Français** · [Español](../es/PORTABLE-CHARACTERS.md) · [简体中文](../zh-CN/PORTABLE-CHARACTERS.md)
**Les personnages portables sont expérimentaux.** Cette fonction est encore en développement et peut présenter des bugs.
Le Manager conserve une copie sauvegardée de votre personnage, utilisable sur les royaumes CoA compatibles.
## Créer son premier personnage portable
1. Déconnectez le personnage dans le jeu. Laissez le Manager ouvert.
2. Ouvrez **Personnages (Characters)** et choisissez **Rendre un personnage existant portable (Make an existing character portable)**.
3. Sélectionnez un royaume auquel vous avez accès, puis votre personnage.
4. Cliquez sur **Rendre portable (Make portable)**. Le personnage apparaît dans **Vos personnages (Your characters)**.
Si un personnage n'est pas sélectionnable, consultez la raison affichée à côté. Les bots, les défis en cours et certaines récompenses en attente peuvent empêcher l'opération. La copie portable ne supprime pas le personnage d'origine sur son royaume.
## Récupérer un personnage d'un autre royaume
1. Dans **Serveurs (Servers)**, sélectionnez le royaume du personnage.
2. Choisissez **Associer un compte existant (Link an existing account)** et indiquez le compte que vous utilisez sur ce royaume.
3. Connectez-vous au royaume dans le jeu et restez sur l'écran de sélection des personnages.
4. Revenez au Manager avec **Alt+Tab** et cliquez sur **Afficher mes personnages (Show my characters)**.
5. Trouvez votre personnage et cliquez sur **Rendre portable (Make portable)**.
6. Attendez la confirmation et l'indication **Portable**.
![Associer le compte du royaume](../screenshots/fr/09-link-realm-account.jpg)
![Choisir un personnage](../screenshots/fr/10-remote-portable-candidates.jpg)
![Personnage enregistré](../screenshots/fr/11-remote-portable-saved.jpg)
## Jouer avec le personnage portable
1. Trouvez un serveur compatible dans **Servers** en mode joueur ou dans **Jouer avec des amis (Play with Friends)** si vous hébergez. Vous pouvez aussi utiliser un royaume déjà accessible dans le Manager.
2. Choisissez votre personnage et lisez les indications de compatibilité avant de cliquer sur **Play**.
3. Suivez l'étape concernant le compte. Certains hôtes en créent un pour vous ; d'autres demandent un compte existant.
4. Lancez le jeu lorsque le Manager indique que le personnage est prêt.
5. Gardez le Manager ouvert pendant la partie. Après déconnexion, attendez la fin de l'enregistrement du progrès avant de fermer l'application ou de changer de royaume.
Sur un royaume dont le niveau maximal est inférieur, votre personnage peut temporairement jouer à un niveau réduit. Lisez l'avertissement : les éléments non pris en charge sont mis de côté plutôt que supprimés sans vous prévenir. Le serveur doit être compatible ; installer le Manager ne suffit pas à activer cette fonction sur tous les serveurs.
## Versions sauvegardées et conflits
**Versions sauvegardées (Saved versions)** permet de voir quand le progrès a été enregistré. Si un conflit apparaît, lisez l'explication avant de continuer. Évitez de jouer avec deux copies simultanément et conservez aussi des sauvegardes classiques du serveur.
[Tous les guides](README.md)
+16
View File
@@ -0,0 +1,16 @@
# Guides et captures d'écran
[English](../README.md) · [Русский](../ru/README.md) · [Deutsch](../de/README.md) · **Français** · [Español](../es/README.md) · [简体中文](../zh-CN/README.md)
- [Galerie](SCREENSHOTS.md) — découvrir l'interface et ses fonctions principales.
- [Héberger son propre serveur](HOST-A-SERVER.md) — installer, inviter des amis et publier un royaume.
- [Personnages portables — expérimental](PORTABLE-CHARACTERS.md) — enregistrer un personnage et jouer sur des royaumes compatibles.
- [Wildcard](WILDCARD.md) — changer de profil et gérer des personnages distincts.
- [Warcraft Reborn](WARCRAFT-REBORN.md) — créer et sélectionner un royaume.
- [Mises à jour, sauvegardes et réparation](REPAIR_AND_REALMS.md) — entretenir le serveur et résoudre les problèmes.
Les captures présentent l’interface en français. Les libellés anglais entre parenthèses permettent de se repérer dans les autres langues de l’application.
**Les personnages portables sont expérimentaux.** Le Manager est en développement actif et peut encore présenter des bugs. Merci de [signaler les problèmes](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
[Télécharger le Manager](https://github.com/Corfirean/coa-server-manager/releases/latest) · [Présentation](../../README.fr.md) · [Changelog du Manager](../../CHANGELOG.md) · [Changelog du serveur](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)
+33
View File
@@ -0,0 +1,33 @@
# Mises à jour, sauvegardes et réparation
[English](../REPAIR_AND_REALMS.md) · [Русский](../ru/REPAIR_AND_REALMS.md) · [Deutsch](../de/REPAIR_AND_REALMS.md) · **Français** · [Español](../es/REPAIR_AND_REALMS.md) · [简体中文](../zh-CN/REPAIR_AND_REALMS.md)
## Mettre le serveur à jour
Sélectionnez votre serveur dans le Manager. Lorsqu'une mise à jour est proposée, cliquez sur **UPDATE** et suivez les instructions. Gardez l'application ouverte jusqu'à la fin : elle arrête le serveur, crée un point de restauration et vérifie le serveur mis à jour.
Comptes, personnages et réglages sont conservés. Tous les royaumes créés sont concernés. En cas d'échec, lisez le message avant de réessayer ; les informations de restauration restent disponibles dans le Manager.
## Prévoir une sauvegarde
Avant une modification importante, utilisez **Sauvegardes (Backups)** pour conserver personnages, comptes et paramètres. Une sauvegarde complète contient aussi les données du monde. Vérifiez le royaume indiqué sur le point de restauration et arrêtez le serveur avant de restaurer.
Les versions sauvegardées d'un personnage portable ne remplacent pas les sauvegardes du serveur. **Les personnages portables sont expérimentaux.**
## Vérifier ou réparer l'installation
1. Arrêtez le serveur.
2. Dans **Paramètres (Settings)**, lancez **Check files and database**.
3. Consultez les résultats. Si des fichiers officiels doivent être restaurés, choisissez **Repair** et suivez les instructions.
La réparation crée une sauvegarde et restaure les fichiers officiels en préservant paramètres et bases des joueurs. Elle peut exiger une version installée identique au paquet signé actuellement publié. Les données de joueurs perdues nécessitent une sauvegarde ; certains problèmes de base demandent une mise à jour corrective du serveur.
Si l'opération reste bloquée ou échoue de nouveau, utilisez **Signaler un problème (Report a problem)** et joignez diagnostic et message d'erreur. Ne supprimez pas les bases ou les journaux de restauration pour contourner un blocage.
## Faire fonctionner CoA et Wildcard ensemble
Dans **Paramètres**, activez **Start CoA and Wildcard together**. Les comptes sont communs, mais personnages et mondes restent séparés. Les deux états apparaissent dans Vue d'ensemble et l'arrêt termine les deux royaumes.
Si vous aviez configuré le réseau pour vos amis auparavant, refaites cette configuration pour rendre aussi le second royaume accessible. Désactivez le démarrage simultané avant de passer à Warcraft Reborn.
[Tous les guides](README.md)
+47
View File
@@ -0,0 +1,47 @@
# CoA Server Manager — galerie
[English](../SCREENSHOTS.md) · [Русский](../ru/SCREENSHOTS.md) · [Deutsch](../de/SCREENSHOTS.md) · **Français** · [Español](../es/SCREENSHOTS.md) · [简体中文](../zh-CN/SCREENSHOTS.md)
Les captures présentent l’interface en français.
### Votre serveur en quelques étapes
![Installer son serveur](../screenshots/fr/setup.jpg)
### Garder une vue d'ensemble
![État du serveur](../screenshots/fr/overview.jpg)
### Former votre propre groupe d'aventuriers
![Gestion des compagnons](../screenshots/fr/bots.jpg)
### Choisir et régler les modules
![Modules du serveur](../screenshots/fr/modules.jpg)
### Un client prêt à jouer
![Client de jeu](../screenshots/fr/client.jpg)
### Protéger votre progression
![Sauvegardes](../screenshots/fr/backups.jpg)
### Inviter vos amis
![Jouer avec des amis](../screenshots/fr/friends.jpg)
### Trouver votre prochain royaume
![Catalogue des royaumes](../screenshots/fr/realms.jpg)
### Personnages portables — expérimental
![Personnages portables — fonctionnalité expérimentale](../screenshots/fr/portable.jpg)
### Rendre un personnage existant portable — expérimental
![Créer une copie portable](../screenshots/fr/remote-character.jpg)
[Tous les guides](README.md)
+15
View File
@@ -0,0 +1,15 @@
# Warcraft Reborn
[English](../WARCRAFT-REBORN.md) · [Русский](../ru/WARCRAFT-REBORN.md) · [Deutsch](../de/WARCRAFT-REBORN.md) · **Français** · [Español](../es/WARCRAFT-REBORN.md) · [简体中文](../zh-CN/WARCRAFT-REBORN.md)
Choisissez **Warcraft Reborn** dans **Vue d'ensemble (Overview)** pour créer ce royaume ou y passer. Votre version serveur doit le prendre en charge ; une version incompatible est refusée avant la création des bases. Fermez le client avant de changer pour mettre immédiatement à jour son royaume enregistré.
Les comptes sont communs avec les autres royaumes locaux. Warcraft Reborn possède ses propres personnages : changer de profil ne copie ni personnages ni progression.
Les bots ne sont pas disponibles sur Warcraft Reborn. Les autres modules optionnels sont expérimentaux. Le transfert de personnages portables vers Warcraft Reborn n'est pas encore pris en charge. **Les personnages portables restent expérimentaux.**
Sauvegardes et mises à jour couvrent tous les royaumes créés. Vérifiez le royaume indiqué sur le point de restauration avant de restaurer.
Le démarrage simultané concerne uniquement CoA et Wildcard. Désactivez **Start CoA and Wildcard together** dans **Paramètres (Settings)** avant de sélectionner Warcraft Reborn.
[Tous les guides](README.md)
+17
View File
@@ -0,0 +1,17 @@
# Profils de royaume : CoA et Wildcard
[English](../WILDCARD.md) · [Русский](../ru/WILDCARD.md) · [Deutsch](../de/WILDCARD.md) · **Français** · [Español](../es/WILDCARD.md) · [简体中文](../zh-CN/WILDCARD.md)
Choisissez CoA ou Wildcard dans **Vue d'ensemble (Overview)**. Le serveur et sa base doivent disposer de la prise en charge de Wildcard. Le Manager refuse une version incompatible, un identifiant de royaume `2` déjà occupé ou une base de destination existante afin de ne rien écraser.
Au premier changement, le monde CoA est copié dans `acore_world_wildcard`. `acore_characters_wildcard` reçoit la structure des tables et les données initiales neutres, sans copier personnages, collections de cartes ou progression. Les comptes restent partagés dans `acore_auth`. En fonctionnement normal, les royaumes `1` et `2` utilisent le même port de monde : seul le royaume choisi fonctionne, l'autre est affiché hors ligne. Un changement en cours d'exécution arrête proprement le serveur puis le redémarre avec le nouveau profil.
Les réglages sont enregistrés dans `Settings/realm-profiles`. Si le changement est interrompu, le journal permet de retrouver la configuration précédente. Les bots compagnons CoA ne sont pas disponibles sur Wildcard. Content Scaling et les autres modules gardent leurs réglages mais leur compatibilité y est expérimentale ; les mécaniques de classe demandent des vérifications en jeu distinctes. Revenir à CoA restaure ses réglages de modules.
Les sauvegardes rapides et de bases incluent les deux bases de personnages et les comptes communs ; les complètes ajoutent les deux mondes. Sélectionnez le royaume indiqué sur le point de restauration avant de restaurer. Les mises à jour s'appliquent aux deux royaumes, et une seule fois aux comptes communs. Si le lanceur serveur est remplacé, le Manager réinstalle son adaptateur de royaumes avant le prochain démarrage.
![Vue d'ensemble de Wildcard](../screenshots/fr/wildcard-overview.jpg)
![Compatibilité des modules](../screenshots/fr/wildcard-modules.jpg)
[Tous les guides](README.md) · [Lancer les deux royaumes ensemble](REPAIR_AND_REALMS.md)
+30
View File
@@ -0,0 +1,30 @@
# Как открыть свой CoA-сервер для других игроков
[English](../HOST-A-SERVER.md) · **Русский** · [Deutsch](../de/HOST-A-SERVER.md) · [Français](../fr/HOST-A-SERVER.md) · [Español](../es/HOST-A-SERVER.md) · [简体中文](../zh-CN/HOST-A-SERVER.md)
**Переносимые персонажи — экспериментальная функция.** Она ещё развивается и может работать с ошибками.
## Подготовьте сервер
1. На приветственном экране выберите **«Хочу быть хостом» (Host a server)**.
2. Нажмите **«Установить новый сервер» (Install new server)** или укажите уже установленный — **I already have a server**.
3. Завершите настройку и запустите сервер в разделе **«Обзор» (Overview)**.
4. Подключите игровой клиент и сначала проверьте вход самостоятельно.
## Пригласите друзей
Откройте **«Игра с друзьями» (Play with friends)**. Выберите подходящий способ подключения и пройдите инструкции для локальной или частной сети. Запустите проверку доступности. Пока друзья играют, компьютер и сервер должны оставаться включёнными. Передавайте подготовленные менеджером данные подключения, а не логин и пароль базы данных.
## Добавьте реалм в публичный каталог
1. Откройте **«Настройки» (Settings)** и найдите **Public listing** — публикацию в каталоге.
2. Укажите понятное название, короткое описание, язык и регион.
3. Проверьте способ подключения и правила входа или создания аккаунтов.
4. Опубликуйте реалм, когда будете готовы принимать игроков.
5. Найдите его в каталоге и попросите друга проверить вход из другой сети.
Публикация помогает найти ваш сервер, но не переносит его в облако и не делает недоступную сеть доступной автоматически. Если вход не работает, начните с проверок подключения, а уже затем меняйте настройки роутера. Для переносимых персонажей также нужны совместимая серверная сборка и её необходимые настройки.
Перед обновлением сервера или изменением модулей создайте **резервную копию (Backups)**. Чтобы убрать реалм из каталога, отключите публикацию. Чтобы завершить хостинг, остановите сервер.
[Все гайды](README.md)
+47
View File
@@ -0,0 +1,47 @@
# Как сделать персонажа переносимым
[English](../PORTABLE-CHARACTERS.md) · **Русский** · [Deutsch](../de/PORTABLE-CHARACTERS.md) · [Français](../fr/PORTABLE-CHARACTERS.md) · [Español](../es/PORTABLE-CHARACTERS.md) · [简体中文](../zh-CN/PORTABLE-CHARACTERS.md)
**Переносимые персонажи — экспериментальная функция.** Она ещё развивается и может работать с ошибками.
Менеджер хранит сохранённого персонажа, с которым можно играть на совместимых CoA-реалмах.
## Первый переносимый персонаж
1. Выйдите из мира этим персонажем. Менеджер оставьте открытым.
2. Откройте **«Персонажи» (Characters)** → **«Сделать существующего персонажа переносимым» (Make an existing character portable)**.
3. Выберите доступный вам реалм, затем персонажа.
4. Нажмите **«Сделать переносимым» (Make portable)**. Персонаж появится в списке **«Ваши персонажи» (Your characters)**.
Если выбрать персонажа нельзя, рядом будет указана причина. Операцию могут блокировать персонаж-бот, активное испытание или некоторые неполученные награды. Создание переносимой копии не удаляет исходного персонажа с реалма.
## Персонаж с чужого реалма
1. В разделе **«Серверы» (Servers)** выберите реалм, на котором находится персонаж.
2. Нажмите **«Привязать существующий аккаунт» (Link an existing account)** и укажите свой аккаунт этого реалма.
3. Войдите на реалм в игре и останьтесь на экране выбора персонажа.
4. Вернитесь в менеджер через **Alt+Tab** и нажмите **Show my characters** — показать персонажей.
5. Выберите нужного персонажа и нажмите **«Сделать переносимым» (Make portable)**.
6. Дождитесь подтверждения и отметки **Portable**.
![Привязка аккаунта реалма](../screenshots/ru/09-link-realm-account.jpg)
![Выбор персонажа](../screenshots/ru/10-remote-portable-candidates.jpg)
![Персонаж сохранён](../screenshots/ru/11-remote-portable-saved.jpg)
## Как играть
1. Найдите совместимый реалм: в режиме игрока — в разделе **«Серверы»**, при хостинге — в **«Игра с друзьями»**. Можно выбрать и уже подключённый к менеджеру реалм.
2. Выберите переносимого персонажа и прочитайте сведения о совместимости перед нажатием **Play**.
3. Выполните шаг с аккаунтом. Одни серверы создают его автоматически, для других нужен существующий аккаунт.
4. Запустите игру, когда менеджер сообщит, что персонаж готов.
5. Во время игры не закрывайте менеджер. После выхода из мира дождитесь завершения сохранения и только затем закрывайте приложение или переходите на другой реалм.
Если на реалме ниже максимальный уровень, персонаж может временно играть на пониженном уровне. Читайте предупреждения: неподдерживаемое содержимое откладывается, а не удаляется без уведомления. Само наличие менеджера не делает любой сервер совместимым с переносимыми персонажами.
## Сохранённые версии и конфликты
В **«Сохранённых версиях» (Saved versions)** видно, когда сохранялся прогресс. Если менеджер сообщает о конфликте, прочитайте его пояснение перед продолжением. Не играйте двумя копиями персонажа одновременно и сохраняйте обычные резервные копии сервера.
[Все гайды](README.md)
+16
View File
@@ -0,0 +1,16 @@
# Гайды и скриншоты
[English](../README.md) · **Русский** · [Deutsch](../de/README.md) · [Français](../fr/README.md) · [Español](../es/README.md) · [简体中文](../zh-CN/README.md)
- [Галерея](SCREENSHOTS.md) — интерфейс и основные возможности.
- [Как открыть свой сервер](HOST-A-SERVER.md) — установка, друзья и публикация реалма.
- [Переносимые персонажи — экспериментально](PORTABLE-CHARACTERS.md) — сохранение персонажа и игра на совместимых реалмах.
- [Wildcard](WILDCARD.md) — переключение профилей и отдельные персонажи.
- [Warcraft Reborn](WARCRAFT-REBORN.md) — создание и выбор реалма.
- [Обновления, копии и восстановление](REPAIR_AND_REALMS.md) — обслуживание сервера и помощь при сбоях.
Скриншоты показывают русский интерфейс. Английские названия в скобках помогут свериться с другими языками приложения.
**Переносимые персонажи — экспериментальная функция.** Менеджер активно развивается, ошибки ещё возможны. О проблемах сообщайте через [issue](https://github.com/Corfirean/coa-server-manager/issues/new/choose).
[Скачать менеджер](https://github.com/Corfirean/coa-server-manager/releases/latest) · [О проекте](../../README.ru.md) · [Ченджлог менеджера](../../CHANGELOG.md) · [Ченджлог сервера](https://github.com/Corfirean/coa-server-build/blob/main/CHANGELOG.md)
+33
View File
@@ -0,0 +1,33 @@
# Обновления, резервные копии и восстановление
[English](../REPAIR_AND_REALMS.md) · **Русский** · [Deutsch](../de/REPAIR_AND_REALMS.md) · [Français](../fr/REPAIR_AND_REALMS.md) · [Español](../es/REPAIR_AND_REALMS.md) · [简体中文](../zh-CN/REPAIR_AND_REALMS.md)
## Обновление сервера
Выберите сервер в менеджере. Когда появится обновление, нажмите **UPDATE** и следуйте подсказкам. Не закрывайте менеджер до завершения: он остановит сервер, создаст точку восстановления и проверит результат обновления.
Аккаунты, персонажи и настройки сохраняются. Обновление охватывает все созданные реалмы. При ошибке сначала прочитайте сообщение; данные для восстановления остаются доступны в менеджере.
## Резервные копии
Перед важными изменениями сохраните персонажей, аккаунты и настройки в разделе **«Резервные копии» (Backups)**. Полная копия включает также данные мира. Перед восстановлением остановите сервер и проверьте, для какого реалма создана выбранная точка восстановления.
Сохранённые версии переносимого персонажа не заменяют копии сервера. **Переносимые персонажи — экспериментальная функция.**
## Проверка и восстановление установки
1. Остановите сервер.
2. В **«Настройках» (Settings)** нажмите **«Проверить файлы и БД» (Check files and database)**.
3. Прочитайте результат. Если нужно восстановить файлы серверного пакета, выберите **«Восстановить» (Repair)** и следуйте подсказкам.
Перед восстановлением создаётся резервная копия. Файлы пакета восстанавливаются с сохранением настроек и баз игроков. Иногда для этого нужна установленная версия, совпадающая с текущим опубликованным подписанным пакетом. Потерянные данные игроков восстанавливаются из резервной копии; некоторые проблемы базы требуют исправляющего обновления сервера.
Если операция остаётся заблокированной или снова завершается ошибкой, используйте **«Сообщить о проблеме» (Report a problem)** и приложите диагностику и текст ошибки. Не удаляйте базы или записи восстановления ради снятия блокировки.
## CoA и Wildcard одновременно
В **«Настройках»** включите **Start CoA and Wildcard together**. Аккаунты у реалмов общие, персонажи и данные мира раздельные. Состояние обоих видно в «Обзоре»; остановка выключает оба.
Если сеть для друзей была настроена раньше, пройдите настройку ещё раз, чтобы открыть доступ ко второму реалму. Перед переключением на Warcraft Reborn отключите одновременный запуск.
[Все гайды](README.md)
+47
View File
@@ -0,0 +1,47 @@
# CoA Server Manager — галерея
[English](../SCREENSHOTS.md) · **Русский** · [Deutsch](../de/SCREENSHOTS.md) · [Français](../fr/SCREENSHOTS.md) · [Español](../es/SCREENSHOTS.md) · [简体中文](../zh-CN/SCREENSHOTS.md)
На скриншотах показан русский интерфейс.
### Свой сервер за несколько шагов
![Настройка сервера](../screenshots/ru/setup.jpg)
### Вся информация о сервере перед глазами
![Обзор сервера](../screenshots/ru/overview.jpg)
### Соберите свою группу приключенцев
![Управление компаньонами](../screenshots/ru/bots.jpg)
### Модули и их настройки
![Управление модулями](../screenshots/ru/modules.jpg)
### Клиент готов к игре
![Игровой клиент](../screenshots/ru/client.jpg)
### Сохраните свой прогресс
![Резервные копии](../screenshots/ru/backups.jpg)
### Пригласите друзей
![Игра с друзьями](../screenshots/ru/friends.jpg)
### Найдите подходящий реалм
![Каталог реалмов](../screenshots/ru/realms.jpg)
### Переносимые персонажи — экспериментально
![Переносимые персонажи — экспериментальная функция](../screenshots/ru/portable.jpg)
### Сделайте существующего персонажа переносимым — экспериментально
![Создание переносимой копии персонажа](../screenshots/ru/remote-character.jpg)
[Все гайды](README.md)
+15
View File
@@ -0,0 +1,15 @@
# Warcraft Reborn
[English](../WARCRAFT-REBORN.md) · **Русский** · [Deutsch](../de/WARCRAFT-REBORN.md) · [Français](../fr/WARCRAFT-REBORN.md) · [Español](../es/WARCRAFT-REBORN.md) · [简体中文](../zh-CN/WARCRAFT-REBORN.md)
Выберите **Warcraft Reborn** в разделе **«Обзор» (Overview)**, чтобы создать этот реалм или переключиться на него. Нужна серверная сборка с его поддержкой: неподходящая версия будет отклонена до создания баз. Перед переключением закройте клиент, чтобы сохранённый выбор реалма обновился сразу.
Аккаунты общие с другими локальными реалмами. Персонажи Warcraft Reborn хранятся отдельно: переключение профиля не копирует персонажей или прогресс.
Боты в Warcraft Reborn недоступны, остальные дополнительные модули экспериментальны. Перенос переносимых персонажей в Warcraft Reborn пока не поддерживается. **Сама функция переносимых персонажей остаётся экспериментальной.**
Копии и обновления включают все созданные реалмы. Перед восстановлением проверьте реалм, указанный в точке восстановления.
Одновременный запуск поддерживает только CoA и Wildcard. Перед выбором Warcraft Reborn отключите **Start CoA and Wildcard together** в **«Настройках» (Settings)**.
[Все гайды](README.md)
+17
View File
@@ -0,0 +1,17 @@
# Реалмы CoA и Wildcard
[English](../WILDCARD.md) · **Русский** · [Deutsch](../de/WILDCARD.md) · [Français](../fr/WILDCARD.md) · [Español](../es/WILDCARD.md) · [简体中文](../zh-CN/WILDCARD.md)
В разделе **«Обзор» (Overview)** можно выбрать CoA или Wildcard. Сервер должен поддерживать Wildcard и иметь необходимые обновления базы. При несовместимой сборке, занятом ID реалма `2` или уже существующей целевой базе менеджер остановит создание, чтобы не перезаписать данные.
При первом переключении мир CoA копируется в `acore_world_wildcard`, а `acore_characters_wildcard` создаётся с пустым списком персонажей и начальными служебными данными. Персонажи, коллекции карт и прогресс не копируются. Аккаунты остаются общими в `acore_auth`. В обычном режиме реалмы `1` и `2` используют один игровой порт: работает выбранный реалм, второй отображается выключенным. Переключение работающего сервера корректно останавливает его и запускает выбранный профиль.
Настройки профилей хранятся в `Settings/realm-profiles`. Если переключение прервалось, журнал позволяет восстановить предыдущую конфигурацию. Компаньоны CoA недоступны в Wildcard. Content Scaling и другие дополнительные модули сохраняют свои настройки, но совместимость отмечена как экспериментальная: поведение классов требует отдельных игровых проверок. При возвращении в CoA восстанавливаются настройки его модулей.
Быстрые копии и копии баз включают обе базы персонажей и общие аккаунты; полные — также оба мира. В точке восстановления указан её реалм: выберите его перед восстановлением. Обновления применяются к обоим реалмам, а общая база аккаунтов обновляется один раз. После замены серверного лаунчера менеджер повторно настраивает маршрутизацию реалмов перед запуском.
![Обзор Wildcard](../screenshots/ru/wildcard-overview.jpg)
![Совместимость модулей](../screenshots/ru/wildcard-modules.jpg)
[Все гайды](README.md) · [Как запустить оба реалма](REPAIR_AND_REALMS.md)
Binary file not shown.

After

Width:  |  Height:  |  Size: 105 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 111 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 111 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 110 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 133 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 122 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 100 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 103 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 93 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 104 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 125 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 70 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 107 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 61 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 92 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 91 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 122 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 77 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 116 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 91 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 102 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 90 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 96 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 111 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 63 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 88 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 64 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 86 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 93 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 92 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 101 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 128 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 78 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 121 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 99 KiB

Loaded 100 of 163 files, more files were not shown because too many files have changed in this diff. Show more