Combo Points Redux
Combo Points Redux is a numeric and graphical display for your combo points (and other similar mechanic abilities) based on the excellent numeric-only addon BasicComboPoints.
Slash Command
/cpr
or /cpredux
Features
- Numeric and graphical display of your combo points
- Numeric display and graphical display are independently movable
- Many icon choices for the graphical display
- Also tracks many other stacking secondary powers including
- Druids: Combo Points
- Mages: Arcane Charges
- Monks: Chi
- Paladins: Holy Power
- Rogues: Combo Points
- Warlocks: Soul Shards
Width, Height, and Scale
The new version for Legion has been updated to dynamically size the points based on your container size. This was done due to all the talents that change the number of points. Here's how this works.
- Set a Height and Width for the Point container
- Based on the maximum number of points available, the individual points will take up a proportional space
That's great... How do I get back to normal?
Here's an example of how to use the new options:
- You want 20x20 square icons and 5 pixels of spacing between them.
- Your class has six points.
- Set Height to 20 and Width to 150
- 150 = (20 * 6) + (5 * 6)
- You can then set a Scale to make this bigger or smaller too
In general:
- Set the Height to your desired Point height
- Calculate the Width
- Point Width * Max Points + Point Spacing * Max Points
Feedback
Important notice: since v3.2.6, ComboPointsRedux embeds BugGrabber, an error catching addon. Please check the error is really about ComboPointsRedux before reporting them here. I suggest installing BugSack to catch the errors.
Please report any bug or error using the WowAce bug tracker (your Curse account works there). The comments section below is not meant to report and track bugs.
Some words about submitting bug reports:
- I do not care about “it doesn’t work, fix it!” messages. I need to know how it failed and a way to reproduce the bug so I can test it and make sure I fix it.
- Bug reports are not in the “fire and forget” kind of things. I may have to ask you some details.
- Please check all existing tickets and the “known issues” section below before submitting new ones. Duplicate reports will be rejected on sight.
If you want another module for a spell please file them as tickets on WowAce. It makes my life easier!
Localization
Currently the addon will work in all locales, but the options screen is not translated on all clients. If you would like to help translate the options screen you can submit translations with the new localization tool at wowace.
I'm receiving the following error spammed at me whenever I go over 5 combo points on my Rogue. Happened a couple days ago, and is still happening as of this post's date. Playing a Subtlety rogue, and I have the lvl 45 talent "Anticipation" that allows me to have 8 combo points instead of 5.
It may be worth noting that when it happens, the combo points disappear from my UI/view completely, but come back as soon as I use a finisher and drop back below 5. Also possibly worth noting, my Warlock seems completely fine. I'm only seeing this on my Rogue when I go over 5 CPs.
Error spammed in chat says: "[Error 00000202A87E37D0] captured, click the link for more information."
When I click the link, I get all this code gibberish. Screenshot here: http://i.imgur.com/WwauIcI.png
Thanks for the report, I should be able to get this fixed over the weekend.
Not sure if this is the place to post this but im using king kong UI hider to hide frames on certain conditions. It seems to work fine hiding the player frame but it cant 'save' frames that are unnamed so the settings get reset when i log out. the CPR frame is just called <noname> and i dont know how to rename it or if thats possible, not sure if this is a cpr problem or a king kong ui hider problem so maybe someone could help me out.
Heres a picture of what i mean if that helps.
http://imgur.com/MFH9ouQ
That is a CPR problem. I've been using anonymous frames since the beginning. From a programming perspective, the thought was why create unnecessary global variables.
It should be an easy change to help support that add on though. I'll see what I can do.
Thanks for the fast reply! Great work with this addon.
Jus wanted to say thanks for all the hard work on keeping things up to date! I've used these combo points for years now on multiple classes! Thanks man!
Absolutely does not work for demo warlock. Sometimes it turns on but show only 4 shards instead of 5. But in 99% of cases it does not work and spam endless errors in chat. When it will be fixed?
Fixed in 4.0.5. Should be up on Curse in a couple minutes.
Thank you for this correction. Now 5 soul shards displayed correctly. But here is one more problem. Combo points do not appear on the screen automatically after entering the game. Each time it is necessary to open addon config & turn off/on soul shards graphics button. This is the only way to enable soul shards combo points in game.
I should be able to fix that tonight. I think there is some old code limiting Soul Shards to Affliction that needs to be removed for Legion.
Was working Fine till last update, now it wont go to 6 combo points only 5 and it gives me a lua error every time i hit 6 combo points and the bar disappears till I use my cp's on my Rogue
Who gave you guys six points?! That's just silly!
4.0.3 should fix that.
I can not open to config even with the latest update.
What class are you?
It's fixed
Think I figured this one out, 4.0.3 should fix.
Feral Druid. I just updated. I still get no response with /cpr or /cpredux.
Okay, it was some old options for the removed Lacerate module. 4.0.4 should fix it.
Hey there! I love this addon and have been using it for a while now, but I'm running into an issue with the newest updates for 7.0. I'm not receiving any lua errors, however I am having issues with functionality. It seems like my combo points only update when I update my target selection. So either when I change targets or drop my target does the addon display actually update. I've tried doing fresh installs of the addon to see if maybe some old code was hanging around messing with things, but to no avail. If there's any other info that could help, let me know and I'll get it to you. Again, I love this addon and would love to keep it in my stable =)
That problem should have been fixed in Beta4, and shouldn't be a problem in the release.
Do you have the release installed? Can you try completely closing WoW, uninstalling the addon and deleting the saved variables, then reinstalling?
I'll take another look tonight, but I swear it was working for me and another user last night.