LoseControl makes it easy to see the duration of crowd control spells by displaying them in a dedicated icon onscreen.
Features:
- Displays duration of all CC spells and abilities on your player, pet, target, targettarget, focus, focustarget, party, and arena enemy frames.
- Support PvP interrupts.
- Support BfA Raids, Mythics and Island Expeditions buffs/debuffs and WoW Classic Raids, Dungeons and Open World buffs/debuffs.
- Automatically displays the most important buffs/debuffs first.
- Integrates directly with Blizzard unit frames. Also supports SUF and Perl frames.
- Icons can be moved, resized, and made transparent.
- Compatible with OmniCC.
- Supports Masque skinning engine addon
Known issues:
- Unlocking frames does not show arena enemy frames if they are anchored to Blizzard frames (because they don't exist unless you're in an arena).
Found a Bug?
- You can report issues here.
To Do:
- Options profiles.
- Blizzard raid frame support.
- Pitbull support.
- Support all NPCs interrupts.
Additional information:
Here are some demonstration videos:
Here is a video that shows you how to edit the LUA file in order to add custom spells:
And here is a setup tutorial that shows you how to unlock the icon frames and move them around:
Any hint why the cooldown text dont work with elvui? Omnicc loaded, "Disable Omnicc support" not checked
In reply to senxs:
nevermind, found the problem
not a spell anymore:
[44572] = "CC", -- Deep Freeze
[123393] = "CC", -- Breath of Fire (Glyph of Breath of Fire)
[119392] = "CC", -- Charging Ox Wave
[105593] = "CC", -- Fist of Justice
[199740] = "CC", -- Bribe
[110913] = "Other", -- Dark Bargain
[118895] = "CC", -- Dragon Roar
[114028] = "ImmuneSpell", -- Mass Spell Reflection
[176289] = "CC", -- Siegebreaker
In reply to drty:
ty for the info, I will remove them for the next version
классический
In reply to evilsky88:
This error often occurs when you copy the configuration file (the one in the WTF folder) from another version of LoseControl (usually retail) to the classic folder.
I will change the code logic for the next version to make sure this error doesn't happen again.
Meanwhile, you can fix this error by opening your LoseControl configuration file in WTF folder (C:\Program Files (x86)\World of Warcraft\_classic_\WTF\Account\<Account_NameID>\<Realm>\<Player_Name>\SavedVariables\LoseControl.lua) with a text editor and modifying the line:
["version"] = X.Y,
X.Y are two numbers that can vary. Modify this line to indicate version 1.0:
["version"] = 1.0,
Do this whole process with the game completely closed. Open the game after making this modification and the error should have disappeared.
Although it should work, if this solution doesn't work for you, you can try to delete the configuration file directly instead of modifying it (although this will remove your current configuration from this addon). Or you can also reset the configuration in game typing the nexts commands in chat:
/lc reset
/reload
Regards
Adding masque support for this addon will make a humble WoW player from the UK's day. Hell, it would make my whole week, or even my year.
You do this for me, and I'll be there for you.
In reply to Zanak3n:
Masque support added to last versions of LoseControl classic and retail. It should work correctly, but if you find any errors don't hesitate to report it.
Hey, im trying to figure something out on the classic version of the addon...
This addon on its first startup asked me whether id like to disable parts of classicauradurations because of possible conflicts, i said no as i wanted to see what would happen and now even after deleted and re-downloading addon and deleting saved settings it still doesnt prompt me again for this (unless its on an alt character) how can i get it to ask me again?
The latest update broke like 16 of my addons and created error spam on logon, not sure why though.
In reply to Venomisto:
Are you sure it's this addon? It works well for me without any errors.
Try to download again manually the latest version from this page and restart the game completely (exit the game completely and restart it). Try to deactivate the rest of the addons and activate them one by one to make sure that it is LoseControl that causes the problem (and thus know which one it directly conflicts with).
If it still shows you an error spam, show us the error text of the message so that we can analyze it.
EDIT: nevermind, I think I have located the error and hope to upload a version with the correction soon
In reply to millanzarreta:
This should be fixed in the new LoseControl 1.03 addon version. Please, if you can, download the new addon version, check if this bug is still occurs and confirm that this bug is fixed or not.
In reply to millanzarreta:
That seems to have fixed it thanks, no errors at logon atleast.
Any chance you could either remove the Azuregos debuff or add a blacklist feature to manually configure debuffs to not show?
Love the addon but I have to disable it during Azuregos so that my character isn't permanently covered up with a 15 minute PvE debuff.
Thanks!
In reply to Zephreas:
Yeh, was a wrong debuff id in the file, in the next version the Mark of Frost debuff of Azuregos (23182) is replaced by Aura of Frost id (23186). Aura of Frost is the real stun effect (Mark of Frost only flags you susceptible to the effect).
In reply to millanzarreta:
Awesome, thank-you.
Could you add a way to specify other anchor points (center for example) and to provide precise x y offset values for the anchor?
1x LoseControl\LoseControl-1.00.lua:1073: Usage: GetPlayerInfoByGUID("playerGUID") [C]: in function `GetPlayerInfoByGUID' LoseControl\LoseControl-1.00.lua:1073: in function `?' LoseControl\LoseControl-1.00.lua:894: in function <LoseControl\LoseControl.lua:893> Locals: InCombatSkipped
In reply to Finrodi:
Ty for the report.
A big update is coming soon™ for LoseControl (classic and retail), with bugfixes (including the bugfix for this error), a lot of new spells, some new features and more!
In reply to millanzarreta:
Looking forward to it, thanks!