• 0

    posted a message on X-Perl Thread
    Quote from lotddragon
    I am having a problem when I try to use focus on any target. The error says that it is taint forced, here is a screenshot of what it fully says. I have XPerl 3.0.8 and WoW 3.3.2.

    http://i15.photobucket.com/albums/a370/LOTDDragon/WoWScrnShot_020710_232706.jpg


    Read the whole thread before posting. Blizzard bug. Use /focus.
    Posted in: Unit Frames
  • 0

    posted a message on Recount
    Quote from Elsia
    In the latest alpha, partial blocks in offensive details are annotated. This means that hits which had part of the damage blocked will appear as "Hit (Blocked)" in the details.

    Also the Scarab brooch proc has been added to the absorbed effects in RecountGuessedAbsorbs.


    Thanks Elsia.
    Posted in: General AddOns
  • 0

    posted a message on Recount
    I don't think anyone wants Recount to change. Quite the contrary. By reporting what the Combat Log says, it highlights discrepancies between what we know and expect and what actually happens. This is what happened here.

    The reason there's a link between Recount and the attack table is that there are only so many possible outcomes for a melee attack. And that's how they're labeled in Recount: hit, miss, crit, glancing hit, parry, dodge, block. What else could you call them? That's their name. The attack table and Recount are linked by definition.

    I don't think offense and defense are cleanly separated, otherwise there wouldn't be partial xxxx mechanics in WoW. Heck, Resilience is a perfect example of a defensive mechanic affecting offense.

    Anyway, not trying to argue here. It was just a suggestion to add partial stuff. It's also a testament to Recount that people rely on it for verifying known theories. If you think it can be a module, then that's cool. I think people were trying to let you know about it, more than "asking for a fix". I suggested something because you brought up how they were handled. Either way, I'll know to test from behind dummies in the future. :P (though that's not necessarily possible, which is why this was done from the front)
    Posted in: General AddOns
  • 0

    posted a message on Recount
    They weren't looking at tanks. They were looking at white damage only, and the breakdown of that white damage (that is, how much of it is hit, crit, glance, miss... etc). Hence the use of the detailed view, to isolate melee attacks only.

    As to partial blocks, they are considered blocks as far as the Blizzard attack table is concerned, even though they do damage. At least that's my understanding of it. So I would think they should be included with full blocks. Of course, as you say, where would the damage done by these partial blocks go? Would it be possible to add another category that's just for partial blocks and includes the damage done? Sort of best of both worlds?

    Those who did those tests were crit-capped and were seeing hits show up on Recount anyway. I guess now we know those were partial blocks. But it led many to believe that there was some hidden conversion of crits into hits. That's actually been going on since LK came out, but it hadn't mattered much until recently since the gear wasn't available to be crit-capped. Once that gear became available, people re-tested this and were able to more closely observe that phenomenon.
    Posted in: General AddOns
  • 0

    posted a message on Recount
    Quote from cremor
    I just read a post on EJ that says Recount is counting blocked hits as normal hits.
    Could you maybe have a look on that?
    http://elitistjerks.com/f31/t76785-crit_depression_combat_table/p3/#post1548433


    More accurately, it's partial blocks that are being counted as hits, not full blocks. And the slightly more relevant post is:
    http://elitistjerks.com/f31/t76785-crit_depression_combat_table/p3/#post1548389
    Posted in: General AddOns
  • 0

    posted a message on BigWigs
    Consider your audience with those tips. First off, here's an example of one: "You shouldn't be quick to blow off a timmy in game, we were all once timmies and they may become the next main tank in your guild."

    I happen to know that means "noobs" in some parts of the world but I guarantee you not everyone does. Localize more.

    Also, THIS is the kind of tips in there? I thought this was a boss addon, not a new player how-to-play guide. I looked through the tips, many of them are general "noob" tips that, while useful to a certain population, don't belong in a raid addon. Focus on raiding tips, not one that reminds people to not get too drunk during a run (yeah that one's in there). That's a social problem and has absolutely nothing to do with Big Wigs and what the addon is about. Turning tips off next time I log on...
    Posted in: Raid AddOns
  • 0

    posted a message on X-Perl Thread
    Update. Role icons have been in X-Perl for a month now. v3.0.8 has it, if you don't want to use alpha versions.
    Posted in: Unit Frames
  • 0

    posted a message on New RSS feeds on the Armory and Privacy Concerns
    Quote from Xinhuan
    You haven't seen the 51 page thread no the WoW forums that filled up in hours have you? And the number of people that have quit wow over it (supposedly by people posting in the thread).


    I have seen it. And I believe that 95% of the people who say they quit WoW never really go through with it.

    The fact remains (and that goes for what mojosdoj said) that unless you specifically mention it, nobody knows who you are in real-life. I fail to see how your privacy is compromised when someone cannot link a toon's name to a real life identity.

    If someone had an unhealthy interest in you, they could already watch your armory profile closely, see your achievements evolve over time, see the statistics change, see your gear evolve... etc. It's pretty easy to see a pattern and figure out when someone raids for example, without the RSS feed. Not to mention websites that track characters on realms...

    The fact that this adds the time of the day is just one extra detail. Everyone's acting as if a pile of info has suddenly become public. That's not the case. Only the time is new and it's now provided in the form of a feed for easy integration into feed readers. So great... you don't have to write an armory parser to get the dates for achievements, statistics... etc. Big deal... there are tons of websites tracking achievements, guild progression by checking individual achievements and the like. Did everyone suddenly realize this was out there?

    It reminds me of the ilvl situation. Now that it's been made more visible by Blizz, all those GearScore-like addons have come out of the woodwork, even though ilvl isn't a new concept. Same thing here. All they added is the time, the rest was already there and anyone dedicated enough could already know quite a lot about you. Everyone needs to relax and needs to learn to keep their real-life identity separate from their online characters' names. If you don't, you're not being careful enough about security. Your privacy is NOT the same thing as your toon's privacy.

    Finally, I still question this concern over the time. People who play when they shouldn't are playing with fire anyway. It's only a matter of time before they got caught anyway, whether they do it at work, or home when they're not supposed to... etc.
    Posted in: General Chat
  • 0

    posted a message on New RSS feeds on the Armory and Privacy Concerns
    Quote from Xinhuan
    Achievements doesn't go down to "hours and minutes" detail, i.e inspecting an achievement doesn't reveal that you play at 3pm-6pm everyday, but the armory reveals that.


    And the difference matters why? They still both provide info about what you do in the game, even if one has more info than the others.

    If the concern is truly the time, then a lot of people are playing when they shouldn't be. And they should probably address that instead of worrying about privacy concerns over a character name that's not linked to any real life information unless THE PLAYERS provide that link THEMSELVES.
    Posted in: General Chat
  • 0

    posted a message on New RSS feeds on the Armory and Privacy Concerns
    Are you aware you can inspect someone else's achievements in-game? Should they take that out too?

    It's your toon, not your real life. I don't get the privacy concerns. If you're playing more than your should (parents, playing at work... etc) and don't want anyone to find out, well... quit playing so much. That's one of the concerns I saw posted around other forums.
    Posted in: General Chat
  • 0

    posted a message on BigWigs
    This seems related:

    17x BigWigs_Ulduar-r7011\Leviathan.lua:56: bad argument #1 to 'band' (number expected, got string)
    BigWigs_Ulduar-r7011\Leviathan.lua:56: in function `?'
    BigWigs_Core-r7011\BossPrototype.lua:102: in function `?'
    CallbackHandler-1.0-5:146: in function <...ron\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
    <string>:"safecall Dispatcher[14]":4: in function <[string "safecall Dispatcher[14]"]:4>
    <in C code>: ?
    <string>:"safecall Dispatcher[14]":13: in function `?'
    CallbackHandler-1.0-5:91: in function `Fire'
    AceEvent-3.0-3 (Acheron):119: in function <...ce\AddOns\Acheron\Libs\AceEvent-3.0\AceEvent-3.0.lua:118>
    
      ---


    Running BigWigs r7011
    Posted in: Raid AddOns
  • 0

    posted a message on Recount
    Totally unrelated, but I just got this:

    2x Recount-1115\GUI_Main.lua:1253: attempt to index field 'TimeData' (a nil value)
    Recount-1115\GUI_Main.lua:1271: in function `AddAllToGraph'
    Recount-1115\GUI_Graph.lua:1249: in function <Recount\GUI_Graph.lua:1249>
    
    Locals:
    self = <table> {
     SetMainWindowModeByLabel = <function> @ Recount\Recount_Modes.lua:592:
     ResetData = <function> @ Recount\Recount.lua:851:
     ResetPositionAllWindows = <function> @ Recount\WindowOrder.lua:111:
     modules = <table> {}
     FormatLongNums = <function> @ Recount\GUI_Main.lua:55:
     srcRetention = true
     SpellBuildingDamage = <function> @ Recount\Tracker.lua:234:
     FlagSync = <function> @ Recount\LazySync.lua:492:
     UnregisterTracking = <function> @ Recount\Tracker.lua:1803:
     CheckPartyCombatWithPets = <function> @ Recount\roster.lua:14:
     InitFightData = <function> @ Recount\Recount.lua:986:
     RequestVersion = <function> @ Recount\LazySync.lua:539:
     UpdateZoneGroupFilter = <function> @ Recount\zonefilters.lua:69:
     FightDropDownOpen = <function> @ Recount\GUI_Main.lua:988:
     ScheduleTimer = <function> @ Acheron\Libs\AceTimer-3.0\AceTimer-3.0.lua:270:
     SetStrataAndClamp = <function> @ Recount\WindowOrder.lua:145:
     ShortNumber = <function> @ Recount\GUI_Main.lua:27:
     FreeTableRecurse = <function> @ Recount\Recount.lua:2063:
     FreeComm = <function> @ Recount\LazySync.lua:488:
     db = <table> {}
     SetZoneGroupFilter = <function> @ Recount\zonefilters.lua:48:
     UnregisterAllComm = <function> @ TomTom\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:202:
     SetEnabledState = <function> @ Acheron\Libs\AceAddon-3.0\AceAddon-3.0.lua:430:
     ReportVersions = <function> @ Recount\Recount.lua:825:
     ResetFightData = <function> @ Recount\Recount.lua:925:
     SpellMissed = <function> @ Recount\Tracker.lua:322:
     FightingWho = "Ley-Guardian Eregos"
     SetDeathLogDetails = <function> @ Recount\GUI_Detail.lua:447:
     FindTargetedUnit = <function> @ Recount\roster.lua:91:
     NewModule = <function> @ Acheron\Libs\AceAddon-3.0\AceAddon-3.0.lua:247:
     IsBoss = <function> @ Recount\Tracker.lua:178:
     GetLazySyncAmount = <function> @ Recount\LazySync.lua:560:
     CreateFilterWeights = <function> @ Recount\Recount.lua:1535:
     UpdateSummaryMode = <function> @ Recount\GUI_Detail.lua:1269:
     SpellEnergize = <function> @ Recount\TrackerModules\TrackerModule_PowerGains.lua:58:
     AddGain = <function> @ Recount\TrackerModules\TrackerModule_PowerGains.lua:68:
     Deserialize = <function> @ DataStore\libs\AceSerializer-3.0\AceSerializer-3.0.lua:236:
     AddDispelData = <function> @ Recount\TrackerModules\TrackerModule_Dispels.lua:42:
     CheckFontStringLength = <function> @ Recount\GUI_Graph.lua:734:
     GetPetPrefixUnit = <function> @ Recount\roster.lua:67:
     GetName = <function> @ Acheron\Libs\AceAddon-3.0\AceAddon-3.0.lua:290:
     SetActive = <function> @ Recount\Tracker.lua:650:
     name = "Recount"
     CreateRealtimeWindow = <function> @ Recount\GUI_Realtime.lua:319:
     GetLazySyncTouched = <function> @ Recount\LazySync.lua:567:
     Print = <function> @ AckisRecipeList\libs\AceConsole-3.0\AceConsole-3.0.lua:54:
     SpellCastStartSuccess = <function> @ Recount\Tracker.lua:402:
     SpellAuraDispelFailed = <function> @ Recount\Tracker.lua:1755:
     GuardianOwnerGUIDs = <table> {}
     DeleteGuardianOwnerByGUID = <function> @ Recount\Recount.lua:1252:
     HideRealtimeWindows = <function> defined @Recount\Win
      ---


    I clicked on the + button in the graph window for my character. It was after a random 5-man and there was data available.
    Posted in: General AddOns
  • 0

    posted a message on Recount
    Re: The memory thing.

    Ok, so last time was before the changes to RecountDeathTrack. It was a log of 7 boss kills, with few deaths, zero wipes. Ended up at 35 MB with the results posted previously. WoW crashed on /reloadui, then it couldn't load the SV next time WoW started.

    This time, using RecountDeathTrack r31. Made sure to reset the data before raid of course. Only 3 boss kills, but a bajillion more deaths and wipes (Icecrown Citadel), so several attempts on bosses. 10 attempts recorded by Recount altogether. Actually, only 2 bosses since apparently the Gunship Battle isn't recorded by Recount. Some people might ask you for it, though I personally don't think it matters for such a gimmicky fight. Anyway, log file: 20 MB.

    So clearly, a lot of data has disappeared with the changes to RecountDeathTrack, since not only do we have more bosses attempts this time around, but we also have a ton more deaths.

    So I did a /reloadui again... WoW crashed. Same error as previously again (the memory thing. Exact message is in my previous posts). Now I had WoW running for several hours by then, had switched toons, done things other than raiding... etc. I need to restart WoW, maybe even reboot before a raid next time, because I really think they have memory management issues.

    But... and here's the good part: relogging after the crash, this time, the SV loaded properly. All I did was reboot technically: raid was last night, I didn't log back in until tonight after the crash. So I have last night's data still available.

    So thanks Elsia, looks like you solved your side of the issue. At least so far. Now it seems like Blizzard needs to look at their code.

    Hope that helps.
    Posted in: General AddOns
  • 0

    posted a message on Recount
    Quote from Elsia
    Committed a new RecountDeathTrack version that no longer stores information in SV. Note that this does NOT affect standard death data as stored by Recount proper. It means that the extra death track window will for now not show a persistent view through reloadui's, DCs and relogs, but at the same time the accumulation of SV file size should be drastically reduced for any combat situations where recorded deaths occur frequently.


    Interesting. Thanks for looking into that plugin after all. I'll be sure to let you know, though it could be a few days.
    Posted in: General AddOns
  • 0

    posted a message on Recount
    Quote from Elsia
    We really shouldn't be micro-comparing very different cases. A farm BT run where as much trash is avoided, noone ever dies etc can be far smaller than a wipe night where no boss ever goes down. There is no real way for me to judge relative file sizes in detail. I can just to be ranges with fairly large tolerances.


    Agree with this, though I picked last night because we didn't wipe and there's no trash in ToC (the Ulduar part for the weekly raid quest involved vehicle trash and I'm not 100% sure Recount works well with that or even sees the data anyway).

    Regarding what's suggested above, that's kinda why I brought up the DeathTrack plugin. Should it have its own SV? Also, since I was never clear on it, doesn't Recount track some sort of death info without the plugin anyway? I'm not even sure of the differences.
    Posted in: General AddOns
  • To post a comment, please or register a new account.