This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.7
PTR
10.2.6
Beta
Recount Woes
Post Reply
Return to board index
Post by
TheReal
Crushingly, my guild failed to down HM-Madness last night, and I believe part of the problem is Recount whoring. We had a couple raiders who were more focused on padding their DPS instead of burning the targets they should have been targeting. The fiasco has led us to want to implement a "no meters" rule.
The problem is, how do we enforce the policy? Does anyone know if Recount uses an add-on communication channel (unlikely, I know)? Should I write an add-on that uses said channel and require everyone to install it (checked through feedback messages of course)? Maybe there's an add-on already available that does this and my Google Fu just fails today.
Suggestions?
Post by
550132
This post was from a user who has deleted their account.
Post by
TheReal
There just comes a point in progression where it's time to turn them off. Seriously, we put around 12 hours on HM-Madness and never did better than 10% except once (4% with a very poorly botched Congealing Bloods spawn).
In my opinion, it's a raid leader's job to whisper players who need to pick it up AND the players who are doing very well. It's like, "hey, whatever you're doing is working. Keep it up" or "hey, your DPS is well below the others, so pick it up please." I'm not against having Recount displayed while learning a fight, but once we know the mechanics and how to work inside of them, it's time to stop whoring the meters and just execute.
I'm thinking about writing an add-on exclusively for our guild (with an eventual public release) that looks for and broadcasts the presence of DPS meter add-ons and broadcasts its own presence. I could use a "one ring to rule them all" strategy to listen to the others.
Of course, having enough time to code something like that is something foreign to me right now, so I would be more than happy to install something similar and already available.
Post by
550132
This post was from a user who has deleted their account.
Post by
TheReal
I was thinking something more like this for a "client" version of a new add-on:
If event == addon_loaded and arg1 == recount or tinydps or skada or (blah blah) then
addonMessageChannel:Add(arg1)
end
...and the master version would listen for the message and let me know (a) it's installed and (b) if the user has any of the listed meters running.
Post by
Neffi
That would require:
- They install it.
- They not modify it to spoof (which would be super easy -- they could go so far as to ask how on the official forums and get an answer within minutes).
- You use IsAddOnLoaded() at PLAYER_LOGIN, not OnEvent for ADDON_LOADED, because Recount might load before your addon.
At least if you build a listener addon, you can know 100% if they actually are running it, since nobody is likely to modify Recount to remove all instances of chat spam. But that's assuming it actually does phone home.
Post by
TheReal
I plan to use it in guild raids, so requiring they install it is easy enough. I agree that it could be spoofed, but meh. I have faith that I can write a print(return) with enough mathematical complexity to make tampering obvious. Sort of like a hashing function but not really.
Thanks for that last pointer too.
Post by
550132
This post was from a user who has deleted their account.
Post by
pelf
There are pre-existing addons for watching addon spam and identifying who it comes from. You could probably leverage those as a quick measure before going to the trouble of writing your own stuff. Spamalyzer is one I've used in the past.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.