This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Baseline TC335-001 — TrinityCore 3.3.5a Build 12340

Owner: Ryuu · Last reviewed: 2026-07-16 · Tracking issue: #13

Status

P0/P1 intake state — not runnable and not claimed compatible. The source revision is pinned, but an authorized client snapshot, extracted data, database/toolchain capture, and Linux execution evidence are absent.

Component	Pinned value	Evidence state
Server	TrinityCore branch 3.3.5, commit d1ebb0920030ad2a3000b1c9d9228e5e6b8a23e3 observed 2026-07-16	Forgejo full-history mirror contains the ref; local recovery capture running
Client	WoW 3.3.5a build 12340	Requirement documented; restricted artifact not supplied
Databases	Auth, characters, world	Inputs and schema revision not captured
Toolchain	Linux/CMake/compiler/dependencies	Not pinned
Extracted data	maps, vmaps, mmaps, dbc/data outputs as required	Not generated or hashed
Runtime	authserver, worldserver	Not executed in this environment
Recovery	Git bundle + client/database/toolchain restore	Not completed

Intake gates

• Stable baseline ID and owner assigned.
• Exact server commit pinned.
• Forgejo mirror destination created.
• Authorized build-12340 client enters restricted intake with provenance and recursive hashes.
• Linux environment/toolchain is pinned and reproducible.
• Database source/revision and ordered updates are captured.
• Extractor outputs are generated from the named snapshot and hashed.
• Secret-free configuration and disposable account procedure are recorded.
• Realm, character, in-world, restart, and restore milestones pass twice from clean inputs.

Intended milestone

From a clean isolated Linux host, restore the pinned source, build server and extraction tools, derive required data from the verified build-12340 client working copy, initialize all databases, start authserver and worldserver, and use a disposable account to reach an agreed in-world location. Repeat after a clean restart and after restoring the backup set.

Why execution stops here

The workspace contains no authorized WoW client snapshot and is a Windows development host, while Game Server Manager declares Linux as its runtime target. Automatically downloading or fabricating a client artifact would violate the project’s provenance and access rules. Supply the client through Client Preservation, then resume #13.

The machine-readable intake record lives at preservation/catalog/baselines/trinitycore-335-001.yml in the main repository.