Private Server Preservation & Modernization

This wiki is the shared memory of the PrivateServer-RS ecosystem. It documents the servers we can run, the clients they require, the artifacts we preserve, what we have learned while repairing them, and how to reproduce a clean working environment years from now.

The project has two equally important goals:

1. Preservation — retain source history, release files, client snapshots, documentation, dependencies, configuration knowledge, and checksums before they disappear.
2. Modernization — make preserved systems safer and easier to install, test, operate, diagnose, and repair without erasing their original behavior.

Start here

Area	Purpose
Preservation Status	Live evidence dashboard, owners, blockers, and next actions.
Compatibility Matrix	Exact server revision ↔ client snapshot ↔ test relationships.
Vision and Scope	What belongs in this ecosystem and what “preserved” means.
Server Catalog	Current server implementations and their required clients.
Client Preservation	How to capture clean client snapshots and derived runnable copies.
Archive Layout	Canonical folder structure for mirrors, artifacts, metadata, and working copies.
Repository Mirroring	How upstream repositories are mirrored, bundled, verified, and recovered.
Mirror Inventory	Actual upstream and Forgejo mirrors, captured refs, bundle checksums, and gaps.
Ecosystem Map	How evidence flows from acquisition to a tested, recoverable baseline.
Reverse-Engineering Workflow	Evidence-driven workflow for understanding and fixing compatibility failures.
Findings Log	Confirmed facts, hypotheses, experiments, and unresolved questions.
Bug Tracker	Known defects and the Forgejo issue workflow.
Toolbox	Tools that help with preservation, diagnosis, and modernization.
Reproducible Baselines	Definition and verification of a ready-to-use clean state.
Operational Runbooks	Installation, upgrade, database, client, incident, and Forgejo recovery procedures.
Backup and Recovery	Copies, integrity checks, restore drills, and disaster recovery.
Contributing	How to add a server, client, finding, tool, or mirror safely.

Current ecosystem

Game	Server implementation	Client compatibility	Project status
Final Fantasy XI	LandSandBoat	Matching FFXI data	Supported module
Final Fantasy XIV 1.x	Project Meteor	1.23b, 2012.09.19.0001	Supported legacy module
Final Fantasy XIV	Sapphire	Snapshot matching the configured SqPack/data version	Supported module
World of Warcraft	TrinityCore 3.3.5	3.3.5a, build 12340	Supported module
World of Warcraft	TrinityCore master	Retail build matching the selected revision	Supported moving target
Aura Kingdom	Aura Kingdom legacy server	Release-specific legacy client/server assets	Experimental preservation module
X-Legend legacy collection	Eight primary server releases plus specialized profiles	Profile-specific; several clients/authentication sets remain missing	Experimental preservation module; archive/layout/schema smoke tests passed

See the Preservation Status Dashboard before relying on a profile. “Supported module” describes manager coverage, not a verified server/client baseline.

Live work

• Forgejo Issues track preservation gaps, findings, modernization, and destructive/security risks.
• Milestones track the preservation foundation, first TrinityCore baseline, and restore drill.
• Baseline TC335-001 records the first vertical baseline without concealing its missing restricted client and Linux execution evidence.

Ground rules

• Never put passwords, access tokens, private keys, personal data, or confidential packet captures in this public wiki.
• Preserve originals as read-only; apply fixes only to derived working copies.
• Every stored artifact needs provenance, a cryptographic checksum, acquisition date, and access classification.
• Record exact revisions and versions. “Latest” is not a reproducible version.
• A server is not considered preserved merely because its source code compiles. Its matching client, database, configuration, dependencies, and verification procedure matter too.
• Use Forgejo Issues for active bugs and work items. Use the wiki for durable knowledge and summaries.

Repository of record

The manager source lives in MMO-Preservation/PrivateServer-RS. This wiki is a separate Git repository named PrivateServer-RS.wiki.git, so it must be included explicitly in backup jobs.