Voice data (9,555 MP3s, ~1.2 GiB) was tracked as plain git blobs,
bloating .git to 1.1 GiB per clone. Migrated to LFS so clones drop to
single-digit MiB; the actual MP3 bytes live once on Gitea LFS storage
(/srv/gitea/data/lfs on git03), fetched on demand via 'git lfs pull'.
Also marks *.mp3 export-ignore so 'git archive' (and the release
workflow's build_zip.sh) skips them — release zips will contain the
addon framework + lookup tables only, never the binary data. Voice
files distributed separately (TBD).
Re-sync after coa-ace3 9583952 backported WoWUIDev/Ace3 PR #10 which fixes
the AceDB-3.0 simple-value defaults metatable: previously falsy defaults
like ["*"] = false read back as nil because of `k2~=nil and v or nil`
short-circuiting. Now they round-trip correctly.
Re-sync after coa-ace3 3ec2009 added two CoA-compat patches:
- AceGUI-3.0/widgets/AceGUIContainer-BlizOptionsGroup.lua: parent
falls back to UIParent when InterfaceOptionsFramePanelContainer is nil
- AceConfig-3.0/AceConfigDialog-3.0: Settings.* block guarded with
fallback to InterfaceOptions_AddCategory on WotLK-era clients
Without these, every addon registering a Blizzard Interface Options
panel via AceConfigDialog errors on load on the CoA client.
Re-sync after coa-ace3 d422ad3 which converted 42 numeric FileDataIDs in
Set*Texture() calls back to string paths. Upstream Ace3 uses FDIDs which
silently fail on WoW 3.3.5 / CoA, rendering color swatches, checkboxes
and window chrome as solid-red placeholders.
Commented ll. 79 & 80 because if you run the game with LUA errors enabled it turns annoying trying to open Dungeon Caches for example, since it's not a valid QuestID for the addon. I feel they should be commented and if someone is working on the addon they can simply remove those lines as comments