Kelsidavis-WoWee/Data/expansions/tbc/expansion.json

{
  "id": "tbc",
  "name": "The Burning Crusade",
  "shortName": "TBC",
  "version": { "major": 2, "minor": 4, "patch": 3 },
  "build": 8606,
  "protocolVersion": 5,
  "maxLevel": 70,
  "races": [1, 2, 3, 4, 5, 6, 7, 8, 10, 11],
  "classes": [1, 2, 3, 4, 5, 6, 7, 8, 9, 11],
  "assetManifest": "overlay/manifest.json"

}
Add multi-expansion support with data-driven protocol layer Replace hardcoded WotLK protocol constants with a data-driven architecture supporting Classic 1.12.1, TBC 2.4.3, and WotLK 3.3.5a. Each expansion has JSON profiles for opcodes, update fields, and DBC layouts, plus C++ polymorphic packet parsers for binary format differences (movement flags, speed fields, transport data, spline format, char enum layout). Key components: - ExpansionRegistry: scans Data/expansions/*/expansion.json at startup - OpcodeTable: logical enum <-> wire values loaded from JSON - UpdateFieldTable: field indices loaded from JSON per expansion - DBCLayout: schema-driven DBC field lookups replacing magic numbers - PacketParsers: WotLK/TBC/Classic parsers with correct flag positions - Multi-manifest AssetManager: layered manifests with priority ordering - HDPackManager: overlay texture packs with expansion compatibility - Auth screen expansion picker replacing hardcoded version dropdown 2026-02-12 22:56:36 -08:00			`{`
			`"id": "tbc",`
			`"name": "The Burning Crusade",`
			`"shortName": "TBC",`
			`"version": { "major": 2, "minor": 4, "patch": 3 },`
			`"build": 8606,`
Use legacy LOGON_PROOF format for auth protocol < 8 2026-02-13 01:10:02 -08:00			`"protocolVersion": 5,`
Add multi-expansion support with data-driven protocol layer Replace hardcoded WotLK protocol constants with a data-driven architecture supporting Classic 1.12.1, TBC 2.4.3, and WotLK 3.3.5a. Each expansion has JSON profiles for opcodes, update fields, and DBC layouts, plus C++ polymorphic packet parsers for binary format differences (movement flags, speed fields, transport data, spline format, char enum layout). Key components: - ExpansionRegistry: scans Data/expansions/*/expansion.json at startup - OpcodeTable: logical enum <-> wire values loaded from JSON - UpdateFieldTable: field indices loaded from JSON per expansion - DBCLayout: schema-driven DBC field lookups replacing magic numbers - PacketParsers: WotLK/TBC/Classic parsers with correct flag positions - Multi-manifest AssetManager: layered manifests with priority ordering - HDPackManager: overlay texture packs with expansion compatibility - Auth screen expansion picker replacing hardcoded version dropdown 2026-02-12 22:56:36 -08:00			`"maxLevel": 70,`
			`"races": [1, 2, 3, 4, 5, 6, 7, 8, 10, 11],`
Add overlay extraction for multi-expansion asset deduplication Extracts each expansion's assets as a CRC-compared overlay against a base manifest, storing only files that differ. Auto-detects overlay mode when a base manifest already exists. Adds --as-overlay, --full-base flags and manifest merge for partial extractions. 2026-02-14 03:09:17 -08:00			`"classes": [1, 2, 3, 4, 5, 6, 7, 8, 9, 11],`
			`"assetManifest": "overlay/manifest.json"`

Add multi-expansion support with data-driven protocol layer Replace hardcoded WotLK protocol constants with a data-driven architecture supporting Classic 1.12.1, TBC 2.4.3, and WotLK 3.3.5a. Each expansion has JSON profiles for opcodes, update fields, and DBC layouts, plus C++ polymorphic packet parsers for binary format differences (movement flags, speed fields, transport data, spline format, char enum layout). Key components: - ExpansionRegistry: scans Data/expansions/*/expansion.json at startup - OpcodeTable: logical enum <-> wire values loaded from JSON - UpdateFieldTable: field indices loaded from JSON per expansion - DBCLayout: schema-driven DBC field lookups replacing magic numbers - PacketParsers: WotLK/TBC/Classic parsers with correct flag positions - Multi-manifest AssetManager: layered manifests with priority ordering - HDPackManager: overlay texture packs with expansion compatibility - Auth screen expansion picker replacing hardcoded version dropdown 2026-02-12 22:56:36 -08:00			`}`