The coa-ace3 sweep (commits 0c130e0..5ea6e44, before coa-elvui was added to
EXCLUDED_FORKS in coa-ace3 tools/sweep.py) overwrote ElvUI's customized,
-ElvUI-namespaced Ace3 libs with plain canonical ones. ElvUI registers libs
as AceLocale-3.0-ElvUI and the AceConfig-3.0-ElvUI family (plus -ElvUI
widgets that don't exist in canonical), so the clobber left them
unregistered: ElvUI failed to init (16 locale 'L' errors) and /ec would not
open. Restores ElvUI/Libraries/Ace3/AceLocale-3.0 and the
ElvUI_OptionsUI/Libraries/Ace3 stack to their pre-sweep state (5021fd1).
coa-elvui is now in EXCLUDED_FORKS, so this won't be re-clobbered.
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.
Bumps in this fork:
- LibDualSpec-1.0
Brings these libs in line with the highest version any Exiles fork currently
bundles, so LibStub resolution is predictable regardless of load order.
Aligns the unsuffixed Ace bundle with the rest of the Exiles forks
(the -ElvUI namespaced copies are intentionally left alone to keep
ElvUI's config UI isolated from any other addon's LibStub registrations).
Per-library MINOR moves:
CallbackHandler-1.0 6 → 8
AceAddon-3.0 12 → 13
AceTimer-3.0 1017 → 17 (canonical numbering — same C_Timer impl)
AceHook-3.0 8 → 9
AceDB-3.0 27 → 33
AceDBOptions-3.0 15 → 15 (unchanged)
AceComm-3.0 12 → 14
AceSerializer-3.0 3 → 5
Other Ace libs (Event, Config family, GUI, Locale, Console, Bucket) were
already at the canonical target.
The CoA client's reworked options panels may omit legacy InterfaceOptions*
status/combat/display widgets; an unguarded access aborted UnitFrames
initialisation on login. Guard every access.
* Added buff containers for vanity and consolidated buffs to match base ui feature
* use locals and don't unpack values 2x
* Moved vanity and consolidated settings to base profile instead of private per character
Fixed error: "attempt to call method 'GetUnitBattlefieldFaction' (a nil value)"
at Tags.lua:838
Changes:
- Changed E:GetUnitBattlefieldFaction(unit) to call the global API function directly
- Added nil check for GetUnitBattlefieldFaction in case it's not available
- Added fallback to UnitFactionGroup(unit) for compatibility
The issue was that the code was trying to call GetUnitBattlefieldFaction as a
method on the E object (E:GetUnitBattlefieldFaction), but this method doesn't
exist. The fix calls the WoW API function directly with a proper nil check and
fallback to ensure the tag works in all cases.
Fixes #TBD
* Missing Non-DE items
* Move Deconstruct options into seperate group
Adds blacklist functionality for general items and lockboxes
* Add translation strings
* Add LibItemSearch functionality to blacklist
* Clean up redundant variables and API calls
tina.schellander
florian.berthold
Xurkon
andrew6180
Jeremy P
ips-ux
Juggalo187
scorpzor
Anthony Narkevicius
Jake Demian
eTzmNcbkrng
fxpw