WoW — TrinityCore 3.3.5

Field	Value
Internal ID	wow-trinitycore-335
Upstream	TrinityCore/TrinityCore
Preserved mirror	MMO-Preservation/preservation-trinitycore, full history present; local recovery bundle pending
Branch	3.3.5 — pin a full commit for every baseline
Baseline revision	d1ebb0920030ad2a3000b1c9d9228e5e6b8a23e3 for TC335-001
Manager module	gsm-mod-trinitycore (Wotlk335)
Support status	Supported
Required client	World of Warcraft 3.3.5a, build 12340
Database	MariaDB; auth, characters, and world databases
Runtime	authserver and worldserver in tmux
Default source	/opt/gsm/servers/trinitycore-335/src
Default install	/opt/gsm/servers/trinitycore-335/server
Preservation level	P0/P1 intake; source pinned, restricted client missing
Owner	Ryuu
Last documentation review	2026-07-16
Runtime verification	Not completed — #13

Preserve together

• Full TrinityCore mirror with the exact 3.3.5 commit and a dated bundle.
• WoW 3.3.5a build 12340 client snapshot metadata under the appropriate access class.
• Client-derived maps, vmaps, mmaps, dbc/data outputs and the extractor binaries used.
• Database source/version, SQL update state, configuration templates, CMake flags, compiler, and dependency versions.
• Any module/scripts installed on top of TrinityCore as separately versioned artifacts.

Manager defaults

• CMake flags: -DTOOLS=1 -DSCRIPTS=dynamic
• Databases: tc_auth_335, tc_characters_335, tc_world_335
• Tmux session: tc-335

Defaults are not a baseline. Record the full commit, database revision, extracted data hashes, and toolchain.

Known constraints and risks

• Only client build 12340 should be treated as compatible until evidence proves otherwise.
• Extracted data is derived from the client and must retain provenance.
• The 3.3.5 branch can change; preserve exact commits and database updates together.
• World database imports and updates can be large and difficult to roll back.
• Third-party modules can change schema and behavior; isolate their patch series.

Baseline verification

1. Restore and check out the pinned 3.3.5 commit.
2. Build server and extraction tools with the pinned toolchain.
3. Extract required data from the verified build-12340 client working copy.
4. Initialize auth, characters, and world databases from recorded inputs.
5. Configure DataDir, bind addresses, and loopback database access.
6. Start authserver and worldserver.
7. Use a disposable account to reach realm list, character flow, and an agreed in-world location.
8. Record hashes for extracted data, schema revision, logs, and result.

Open preservation work

• Establish a canonical build-12340 client manifest.
• Pin a first verified server/database/toolchain baseline.
• Preserve and hash all extracted data outputs.
• Document modules separately from the unmodified upstream baseline.
• Test restore from bundle plus offline client/database artifacts.

Live tracking

• First vertical baseline: Baseline TC335-001 / #13
• Mirror and bundle completion: #2