What's new
# Decursive 12.1 Compatibility Patch - Changelog
## v10.35
### Strict Priority Filtering
- Reworked the managed aura filtering so each Decursive priority only lights for the dispel types actually assigned to that priority.
- Removed the old fallback behavior where a protected or generally dispellable aura could incorrectly appear as Priority #1/red.
- Priority filtering now follows Decursive's actual cure assignments:
- Priority #1 only responds to dispel types mapped to Priority #1.
- Priority #2 only responds to dispel types mapped to Priority #2.
- Priority #3 follows the same model when configured.
- A protected aura that does not match a configured cure priority now remains unlit instead of defaulting to red.
- Removed the broader managed priority-curve fallback from the live color path.
- Preserved Blizzard-managed protected aura handling without adding legacy aura scanning.
- No direct reads of protected dispel type data were added.
- Priority-color behavior remains driven by Blizzard-supported managed aura filtering.
---
## v10.34
### Cure Range Fix
- Fixed the out-of-range color state not reliably appearing.
- Replaced generic `UnitInRange()`-only logic with checks based on Decursive's actual configured cure spells.
- A unit is considered out of range when the relevant cure spell cannot reach that unit.
- Raised the Decursive-owned range overlay above the managed priority fill so the out-of-range state can visibly override red/blue priority colors.
- Preserved protected aura handling and avoided modifying Blizzard-managed aura buttons.
- Default out-of-range color remains configurable through the menu.
---
## v10.33
### Yellow Out-of-Range Default
- Changed the default out-of-range overlay color from black to yellow.
- Preserved all configurable range settings.
- The reset option now restores yellow as the default out-of-range color.
- Existing saved custom colors remain unchanged until reset.
---
## v10.32
### Configurable Out-of-Range Dimming
- Added configurable out-of-range visual settings under:
- **Micro Unit Frame Settings -> Display Options**
- Added:
- **Dim MUFs when out of range**
- **Out-of-range dim amount**
- **Out-of-range overlay color**
- **Reset out-of-range color**
- Implemented the range visual using Decursive-owned overlay frames.
- Did not modify Blizzard-managed aura objects.
- Initial default used a dark overlay to preserve the underlying priority hue.
- Later changed to yellow in v10.33.
---
## v10.31
### Protected Aura Yellow
- Changed the tooltip color for:
- **Aura state protected (WoW 12.1)**
- Protected-state tooltip text now displays in yellow.
- No changes to curing, priority detection, or cooldown logic.
---
## v10.30
### Protected Aura Purple
- Changed the protected-state tooltip color from the original status color to a distinct purple/magenta.
- Used a distinct protected-state color to separate it from:
- Normal status text
- Priority colors
- This color was later changed to yellow in v10.31.
---
## v10.29
### Protected Aura Tooltip Fix
- Fixed misleading MUF tooltip behavior where WoW 12.1 protected aura states could still display:
- **Normal**
- Replaced the misleading legacy status with:
- **Aura state protected (WoW 12.1)**
- This avoids claiming a unit is normal when Blizzard's managed aura system may still be showing a dispellable protected aura.
- Left priority-color and cooldown behavior unchanged.
---
## v10.28
### Shared Priority Timer Fix
- Fixed the shared cooldown timer not appearing on other afflicted MUFs.
- Removed reliance on reading `AuraSlot:IsShown()` from Blizzard-managed aura objects.
- Reworked the shared cooldown display to use Blizzard-supported duration binding behavior.
- Added `DurationTextBinding` for the shared white countdown text.
- Continued using Blizzard engine-side priority filtering.
- Preserved the behavior where:
- The cleansed target clears its priority visual.
- The cleansed target does not keep a stale faded cooldown square.
- Other afflicted MUFs using the same priority can show the shared cooldown state.
- Different-priority MUFs remain unchanged.
- Clean MUFs remain unchanged.
---
## v10.27
### Cleanse Clear + Shared Priority Cooldown
- Changed post-cleanse behavior so the successfully cleansed target immediately clears its priority/cooldown visual.
- Removed the old stale faded-square behavior on the cleansed target.
- The cleansed target is excluded from the shared cooldown display.
- The dispel spell cooldown is tracked by Decursive priority.
- Other currently afflicted MUFs using the same priority can receive:
- A faded version of that priority color.
- A white cooldown countdown.
- Different-priority and clean MUFs remain unchanged.
---
## v10.26
### Forbidden Object Hardening
- Performed a full forbidden-object hardening pass.
- Removed unsafe shared-priority cooldown code that manipulated Blizzard-owned managed aura objects.
- Established a strict separation:
- Blizzard-managed AuraContainers/AuraButtons handle protected aura visibility and priority-color information.
- Decursive-owned frames handle dynamic cooldown/tint behavior.
- Removed unsafe dynamic calls against Blizzard-owned managed objects, including:
- `Show()`
- `Hide()`
- `SetAlpha()`
- `SetCooldownFromDurationObject()`
- `SetHideCountdownNumbers()`
- Removed forced managed `UpdateAllAuras()` calls from the dynamic cooldown path.
- Preserved working priority-color detection.
---
## v10.25
### Hybrid Shared Cooldown
- Fixed the clicked MUF cooldown timer disappearing immediately after a successful dispel.
- Added a hybrid cooldown model:
- Clicked MUF keeps an addon-owned cooldown timer.
- Other same-priority afflicted MUFs can receive a shared cooldown.
- Different-priority and clean MUFs remain unaffected.
- This approach was later replaced by stricter forbidden-object hardening.
---
## v10.24
### Shared Priority Cooldowns
- Added experimental shared cooldown behavior across afflicted MUFs using the same Decursive priority.
- Added priority-specific managed aura filtering with Blizzard's `candidateFilters.includeDispelTypes`.
- Avoided directly reading protected aura type data.
- Clean and different-priority MUFs remain unaffected.
- This version exposed additional protected-object restrictions and was later reworked.
---
## v10.23
### Forbidden Cooldown Fix
- Fixed repeated forbidden-object errors caused by manipulating Blizzard-owned managed aura objects after initialization.
- Removed unsafe live updates against managed aura descendants.
- Blizzard-managed aura buttons are used only for:
- Affliction visibility
- Priority-color display
- Cooldown timers and cooldown shading were returned to Decursive-owned frames.
- Preserved working Blizzard-managed priority-color detection.
- Restored stable per-clicked-MUF cooldown behavior.
---
# Current 12.1 Visual Model
### Priority Colors
- A MUF should only light when Blizzard's managed aura system identifies a dispellable aura that matches one of Decursive's configured curing priorities.
- There is no fallback-to-red behavior for unknown/protected aura states.
- Protected aura details are not directly inspected by addon Lua.
### Protected Aura Tooltip
When exact aura details cannot be safely inspected on WoW 12.1, the tooltip displays:
```text
Aura state protected (WoW 12.1)
```
The current default tooltip color is yellow.
### Out-of-Range State
- Out-of-range behavior is configurable in the Decursive menu.
- Default out-of-range color is yellow.
- Range detection uses Decursive's configured cure spells rather than only generic unit range.
- The range overlay is Decursive-owned and does not modify Blizzard-managed aura buttons.
---
# License and Attribution
**This project is a compatibility modification of the original Decursive addon. It is not a claim of authorship over the original Decursive project.**
- **Original project:** Decursive
- **Original author/maintainer:** Archarodim / John Wellesz
- **Original version base:** Decursive 2.8.2-2-g4a1865f
- **License:** GNU General Public License version 3 (GPLv3)
- **Modification:** World of Warcraft 12.1 compatibility and quality-of-life changes
The original copyright notices, attribution, and GPLv3 license terms should remain included in redistributed versions.
This mod has no additional files