This highly configurable mod allows players to associate buttons to unit frames. It is meant as a replacement to GroupButtons which stopped functioning with the 2.0 patch in December 2006. The mod extends the capabilities of GroupButtons by providing these additional features:
an unlimited number of buttons per unit frame
Buttons which turn on/off depending on the amount of damage a unit has
Buttons which are dimmed if a unit as that buff or a related buff applied.
Buttons which appear when a debuff is applied to a unit.
Buttons which allow you to have any type of "/" slash or macro command on a button
A variety of a modes for different activities in the game. For example, a set of buttons
for soloing, buttons for instances, buttons for raids, buttons for specific bosses (such as Baron Geddon in MC (to all priests to debuff), buttons for PvP, etc.
Assign buttons to unit frames that when clicked cast spells on different units. This feature allows, for example, buffs and heals for the player unit to appear within the target buttons to minimize the amount of mouse movement between buttons.
Works for any kind of non-casting classes; specifically warriors and rogues.
Version 1.8.2 (July 26, 2008) (by Palidindrome )
Changelog:
Code:
CHANGED: TOC for 2.4
NOTE This is a incremental releasefor the toc
CHANGED: TOC for 2.3
CHANGED: Tainting issue fix. Copied Tayedaen's combat update code
ADDED: Copied in Cosmic Cleric's UI code for additional settings
ADDED: User Guide back to release package
NOTE - other 1.9 changes are NOT copied in. This is a incremental releasefor the toc/ bug and UI
ADDED: PerfectRaid support
ADDED: Pitbull Raid Frames Raid frames appear to work - Party frames do not work well.
ADDED: Countdown for cooldowns with remaining time < 10 secs can now be displayed with decimals
To enable decimals use '/XUB showdecimals'
ADDED: BUFFx: BUFF/BUFFBLINK buttons can now blink if a buff is about to expire
By defining a BUFFx, the button will blink if the buff is x seconds away
from expiring. Examples: BUFFBLINK15, BUFF10
ADDED: Global Dim
This dims all buttons in state STATE_ENABLED while player is casting a spell
To enable GlobalDim use '/XUB useglobaldim'
(Macro buttons are not dimmed because of the possibility of /stopcast macros)
If you use 'Color coded' instead of 'Transparency' then the dimmed buttons
are colored with c_globaldim (mint at the moment).
Please note that Global Dim has quite a cost in terms of performace, since
it has to dim all ENABLED buttons if you start a cast, and undim them after.
ADDED: new Tooltip option "Show Cooldown even in Combat"
ADDED: Global cooldowns no longer start a countdown timer by default
To enable a countdown timer for global cooldowns use '/XUB showglobalcooldown'
ADDED: Garbage collection after applying a profile
CHANGED: raid/group changes are handled better (does not work while in combat !!)
CHANGED: debuff handling
Some debuffs have no debuff type. Now for these debuffs the name of
the debuff is added to the debuff list instead of the debuff type.
This allows to check for a specific debuff if necessary.
CHANGED: Display of all buttons after a party/raid change (request by Torwauki)
The duration of the display of the buttons after a raid/party change is
now 0 secs per default, the duration after a manual change is still 3 seconds.
Eventually these times will be adjustable in the future, for now they can only be changed in code.
Search in 'eXtremeUnitButtons.lua' for:
XUB_DelayTime_after_automaticProfileChange = 0;
XUB_DelayTime_after_manualProfileChange = 3;
and change the values to your liking.
CHANGED: Improved pitbull support (thx paladindrome)
CHANGED: "Hide and Disable" --> "Show as Hidden"
CHANGED: "Enable and buffed" --> "Show as Buffed"
CHANGED: "Red Cooldown/Blue Mana" --> "Color Coded"
CHANGED: "Heal Button action" --> "Heal/Buff button action"
CHANGED: Button behaviour regarding buffs
After long development discussion we agreed to implement it this way:
A button in buffed state is shown either as BUFFED or INVALID (hidden).
This is adjustable with the modified Healbutton option in the option window (see 'Heal Button action')
CHANGED: Color system
New: Red=Range,Ochre=Buffed,Purple=Cooldown,Cobalt=Mana
There are also some changes to make implementing a color selector easier later
CHANGED: OutOfRange buttons have now a separate alpha from Invalid buttons
The alpha for invalid is set to '0'.
This can be changed to 'x' with '/script XUB_INVALID_ALPHA=x (0 <= x <= 1)
CHANGED: behaviour of unusable buttons
They are no longer higlightened if mouseovered, indicating that ou can't use the button at the moment
FIXED: Spells defined as BUFFS can be debuffs on target units (fixed in hotfix1)
FIXED: fix for "XUB_UF_Apply( "PlayerPet" , "PlayerFramePetFrame" )"
FIXED: workaround for API call 'UnitClass' sometimes returning NIL
Known addon bugs:
none
Known blizzard bugs:
------------------------
'isUsableSpell' is broken, there is nothing I can do to change that.
That means: Some spells are reported 'not usable' if you target a hostile target or NPC (like 'PowerWord: Shield' for example).
NOTES:
Code:
NOTE 1: !!!! Limited Pitbull support is enabled but does not work well
- consider it experimental and unsupported!!!!
NOTE 2: The colors for 'Color coded':
STATE_OUTOFRANGE = c_range = red
STATE_COOLDOWN = c_cooldown = purple
STATE_BUFFED = c_buffed = ochre
STATE_OUTOFMANA = c_outofmana = cobalt
Dimmed button = c_globaldim = mint
These colors can be changed in eXtremUnitButtons.lua.
To do this, open the file and search for 'XUB COLOR DEFINITION BLOCK'
NOTE 3:
The correct spelling for the 4 existing debuff types are :
Magic
Poison
Curse
Disease
Please note that the first character is uppercased.
NOTE 4: The historical changes have been removed from the online
display - they are availible in the embedded Changelog_complete.txt file.
In reply to something CosmicCleric has posted in one of the subthreads:
Quote:
Originally posted by Cosmic Cleric So now, for example, if my Mage gets hit with a 'Frost' school based DoT attack, BOTH the "_FireWard" and "_FrostWard" XUB buttons will start blinking, because they are both looking for 'Magic' based debuffs. I only want ONE of the buttons to blink, the one associated with the 'Frost' based damage absorption spell, "_FrostWard".
The 11th argument to SPELL_AURA_APPLIED and SPELL_AURA_REMOVED is spellSchool
Parsing of the combatlog can be done.
But the combatlog is sometimes unreliable, mostly because of range issues.
That means we need to check UnitAura anyway to get the buff/debuff for a certain unit.
Additionally, parsing the combatloag takes more computing then calling UnitAura.
So I would not want to parse the log in a raid situation.
BUT:
I think it's a good idea, that could be implemented for the player himself.
There is no range problem concerning the player himself anyway
But my primary goal is to get a stable release first, then we can talk about enhancements
So please keep testing an posting , all of you
Changelog for 1.9 beta 13
- changed: Handling of 'Verify' for CustomButtons
- changed: spam when groupmembers had no pets
- fixed: new coordinates for groups now work without CR
- fixed: multiline-macros should work now ("\n")
- fixed: PitBull4 Raid handling
Originally posted by abinning I am pretty sure i've seen it before, but after digging through 20+ pages i can't find it.
So can anyone help a noob out and tell me how to do multi-line macros in xub?
Something like this...
Now drag that button to one of your action bars. Hover over that button and run the script:
Code:
/run local f,m=GetMouseFocus(); if f==WorldFrame or f==UIParent or not f:GetName() then m='Unnamed or unknown frame' else m=f:GetName() end; ChatFrame1:AddMessage(m)
to get the button ID
Now create a XUB macro such as
Code:
REZ_macro,macro,111,/click buttonidhere
Basically you're clicking a button that clicks another button. As long as you leave that Blizzard macro in the same spot, there shouldn't be a problem.
Originally posted by chewm1 ... I get errors when I use the duel spec options and switch to Ret and lose the Holy Shock spell.
... It doesnt seem to complain when I define a group that uses Holy Shock, only when it is defined as a custom button.
I will have a look at that.
Quote:
Originally posted by chewm1 Also,
Is there a way to comment out lines in the interface (buttons, groups, or profiles)? I sometimes try new things but dont want them to be used at all times.
I personally do not comment them out, I simply rename them.
Example: Group is called: Heal --> tHeal (I choosed 't' for 'test')
Example 2: Profile is called normal: --> tnormal
I have the following health buttons defined but now I get errors when I use the duel spec options and switch to Ret and lose the Holy Shock spell. I plan to change my profile when I change specs to one that does not use this button. Is there a way to do this or is my only option to remove the instant_heal health button? It doesnt seem to complain when I define a group that uses Holy Shock, only when it is defined as a custom button.
instant_heal,health,Holy Shock,,1000
small_heal,health,Flash of Light,,1500
big_heal,health,Holy Light,,2000
Also,
Is there a way to comment out lines in the interface (buttons, groups, or profiles)? I sometimes try new things but dont want them to be used at all times.
I am pretty sure i've seen it before, but after digging through 20+ pages i can't find it.
So can anyone help a noob out and tell me how to do multi-line macros in xub?
Something like this...
Code:
This is why I think we should start a forum. Searchable, categorized feedback =P
I have bandwidth and diskspace. ;-)
semi-colon didn't work so ill keep readin'
I copied the following from the original XUB PDF User's Guide...
Quote:
Macro Buttons
Macro buttons are custom buttons which provide access to the slash commands (/) in the game. In order to provide an icon for the button, the specification identifies a button number. This number is sequentially assigned starting at 1 according to the buttons in the /macro dialog box. Note: As long as the unit is available, a macro button will stay lit. The format is:
With macro buttons, you can also use the # symbol in the macro text. When present, the # is substituted for the party number or raid number making it possible to use macros on party members:
It seems to just pass along to the WoW client anything after the "/", so if you can figure out how to do multiple slash commands from the WoW chat window, then you've probably found the answer how to have multiple macro actions via XUB.
Last edited by Cosmic Cleric : 02-05-2009 at 06:52 PM.
It functions... but it "lights back up" when PW:S fades, NOT when Weakened Soul fades, as I would expect.
As a DISC priest, it's important for me to know when I can shield the tank again, which I can only do when Weakened Soul fades.
Or is the button just set up wrong?
Edit:
as a test, I set it to a debuff button... and the button shades back out when Weakened Soul faded. So it seems debuff is giving me more of an expected behavior than buff?
Power Word Shield has alwys had a problem )its teh same for the Pally spells that out a debuff on aswell).
I will see if there is anything that can be done - but no promises - we spent a lot of time on it a while ago.
It functions... but it "lights back up" when PW:S fades, NOT when Weakened Soul fades, as I would expect.
As a DISC priest, it's important for me to know when I can shield the tank again, which I can only do when Weakened Soul fades.
Or is the button just set up wrong?
Edit:
as a test, I set it to a debuff button... and the button shades back out when Weakened Soul faded. So it seems debuff is giving me more of an expected behavior than buff?
I was wondering how hard it would be to get XUB working with the Single party view of Praid(including player in the party).
...
I tried unsuccessfully to use the PRHeader# etc as custom party frames and it didn't work right.
...
It seems like the biggest hurdle is that 'player' isn't really a party member according to blizz api functions.
What was the problem with the custom party frames?
All we are doing is looking for someplace to hang the buttons - so we need to connect to a named frame. The association to Player, Party, Target etc. is all in teh action for the button and is independant of where the buttons are attached.
If PRaid doesnt name thier frames with a one to one relation ship to the units we can have a problem - ultimately this was the problem with PitBull support.
