Authors CurseForge

Here's the trace:

259x Recount\Tracker.lua:1186: Usage: UnitName("unit")
[C]: ?
Recount\Tracker.lua:1186: in function `AddCurrentEvent'
Recount\Tracker.lua:1762: in function `AddDamageData'
Recount\Tracker.lua:575: in function `parsefunc'
Recount\Tracker.lua:1117: in function `?'
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:147: in function <...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0.lua:147>
[string "safecall Dispatcher[26]"]:4: in function <[string "safecall Dispatcher[26]"]:4>
[C]: ?
[string "safecall Dispatcher[26]"]:13: in function `?'
...Ons\Ace3\CallbackHandler-1.0\CallbackHandler-1.0-6.lua:92: in function `Fire'
Ace3\AceEvent-3.0\AceEvent-3.0-3.lua:120: in function <Ace3\AceEvent-3.0\AceEvent-3.0.lua:119>

Locals:
nil

Quote from sicart

I'm using the latest v4.0.9. Gonna try with an alpha, from 5 hours ago.

Hm, those should have been fixed in 4.0.9. If the alpha doesn't work, I have some ideas, but they're tedious for you and anybody else involved. :-\

Quote from sicart

i. The Target and focus power bar don't work. All power types (rage, focus, mana and energy) are colored yellow (this is for ALL units, not only these two) and when my target and focus target spend power, the power bar doesn't update, it remains full, and when I switch target and go back to the previous target, it updates to its current power but then it freezes right away and doesn't update anymore again.

What version are you using? (You should have included that information.)

Some of the recent releases had problems with power bars; either revert to a much older version, or get the absolutely latest release, potentially an alpha.

Quote from Shadowed

For people with combo point or crash issues, try the latest alpha.

The current alpha explodes at loadup, because modules/aurapoints.lua still tries to use "Combo" instead of "AuraPoints" as the table name on line 24.

Fixing that results in perfect behavior of rogue combo+Anticipation points, including the colors. Cheers!

Quote from Palladia

I'm having the same problem. I figured it out because someone else complained about it and the only addon we had in common that got information about other raid members was Recount. I turned it off and voila! no more spam!

Was seeing this even today, with 6.0.3f, in a cross-realm apexis daily raid. Persisted across /reload, had to finally disable it completely. Turned it back on after the raid, and ran several 5-player instances with zero errors.

Other than that single incident, have had no trouble (aside from some interesting default window placements).

Quote from Lichbane

Even using http://www.curse.com/addons/wow/libbodyguard-1-0? Or emulate http://www.curse.com/addons/wow/bodyguardhealth within SUF?

sUF isn't set up to look at anything other than the builtin unit types ("player", "target", "party1" through "party4", etc). If Blizzard adds "bodyguard" someday than 90% of the existing code will Just Work, and the remaining 10% will be easy to do given sUF's existing framework for exactly that purpose.

Without that, you might write a sUF plugin to kludge in lots of bodyguard-specific workarounds, but it's not going to be pretty.

Quote from Lichbane

Any chance of seeing Bodyguard as a unit?

Until and unless Blizzard adds it as a unit type, no.

Try printing tbl2[101]? Also, the builtin command "/dump" is quite helpful for these kinds of experiments, as is the WowLua addon (still works fine but you'll need to load out-of-date addons).

Quote from Farmbuyer

I just noticed that the latest alpha, v4.0.7-5-g77c3a79, has a line in its changelog about fixing combo point bars. (Actually the same line is in a few changelogs, something about how Git+Wowace accumulates entries? Dunno.)

With this version, the same behavior persists, including the incorrect colors and reuse of the same bar for both normal and anticipation points.

Bug still present with yesterday's alpha, v4.0.8-4-gb04843b. Also a slightly odd new behavior, in that the combo point blocks only stay for a short time until the total points "overflow" into Anticipation points, after which the bar remains full. That is,

0 points, attack -> 2 points, briefly
2 points returns to 0
attack -> 3 points, briefly
3 points returns to 0
eventually build to 5 combo points plus 1 Anticipation point
combo bar stays full, Anticipation bar remains empty

No need, the last file uploaded will be the "latest version" as far as the various downloader pages and tools are concerned. Leaving the older version in place allows users to revert to them in case you accidentally upload something screwy. :-)

Quote from Zurom

Wondering if I can add a question to this thread. I've been trying to find the "Version" box you speak of. I remember seeing it when I first created the project and update the file, but I no longer see this box when uploading new files. Am I missing something?

It's just the "Name" box for most manually-uploaded files. Treat that as a Version box and the results will be just as Phanx described.

Whatever you did before, do it again.

You'll have to give more information if you want any more detail than that.

Quote from jamescygnus

Until you create a new profile that option is empty.

I setup everything without knowing this and I'm trying to find a way to either copy the default setup or use it for other characters.

What are the choices under the "Existing Profiles" dropdown? I've never encountered a profile which was usable but at the same time not listed there, unless the WoD version added some new trickery.

Ah, didn't know about the new multistrike field. Thank you for that!

If I get enough caffeine tonight, I may work up the energy to post in the Blizzard UI or Bug Report forums.

jamescygnus: /suf, then "Profiles" in the top left, then look at "Copy From" about halfway down the right-hand pane.