WoWInterface SVN DisplacedEnergyNazi

Compare Revisions

  • This comparison shows the changes necessary to convert path 
    /trunk
    from Rev 15 to Rev 16
    ↔ Reverse comparison
  •

Rev 15 → Rev 16

DisplacedEnergyNazi/ReadMe.txt
3,49 → 3,56
 
- intended to be enabled by a "raid leader" (main tank or other critical-path
participant)
- intended to be operate while the raid is stacked during Malkorok's
"Blood Rage" phase (operates all the time, just doesn't respond to anything
except Malkorok activity)
- intended to operate while the raid is stacked during Malkorok's
"Blood Rage" phase (operates continuously while enabled, with as light a footprint
as possible, just doesn't respond to anything except Malkorok activity)
- detects when the "Displaced Energy" debuff lands on players
- detects when "Displaced Energy" does damage to a target when within roughly
a 10-yard range of other players
- detects when "Displaced Energy" does damage to the player running the addon,
when within roughly a 10-yard range of afflicted players (any of whom could
be the culprit)
- detects when "Displaced Energy" is dispelled, when the dispel target is within
roughly a 10-yard range of other players (TODO: flag when it is dispelled at
all, since some raids prefer to let it expire naturally)
- screams bloody murder, and names names, when any of this player "dysfunction"
is detected
roughly a 10-yard range of the player running the addon (TODO: flag when it
is dispelled at all, since some raids prefer to let it expire naturally)
- screams bloody murder, and names names (the person afflicted, the afflicted
player(s) who may be causing damage, and the person dispelling when the dispel
target is too close), when any of this player "dysfunction" is detected
 
Somewhat circumstantial, but something is better than nothing, and if everyone
is managing the mechanics correctly, none of these events should occur, and therefore
none should be detected.
All Displaced Energy damage reported in the combat log is attributed to Malkorok;
the afflicted player actually causing the damage cannot be positively identified.
All afflicted players close enough to be causing the damage are "blamed" collectively.
This is somewhat circumstantial, but something is better than nothing, and if
everyone is managing the mechanics correctly, none of these events should occur,
and therefore none should be detected/reported.
 
Motivation:
 
Several of my regular Siege of Orgrimmar events are having trouble with Malkorok,
caused SPECIFICALLY when those suffering from the "Displaced Energy" debuff
during the "Blood Rage" phase remain stacked with other players. Boss mods will
detect/name players affected by the debuff, but will not attempt to detect and name
those who do not leave the raid stack immediately in response to the debuff (the
debuff does damage every 3 seconds for 9 seconds, so players have 3 seconds to get
clear). Displaced Energy Nazi watches for this specific problem, and makes a lot
of noise when any of it is detected.
Several of my regular Siege of Orgrimmar groups at least occasionally have trouble
with Malkorok, caused SPECIFICALLY when those suffering from the "Displaced Energy"
debuff during the "Blood Rage" phase remain stacked with other players, or otherwise
do not move far enough away, quickly enough, to avoid damaging the rest of the raid.
Boss mods will detect/report players afflicted by the debuff, but do not attempt
to detect and name those who do not leave the raid stack immediately in response to
the debuff (the debuff does damage every 3 seconds for 9 seconds, so players have
about 3 seconds to get clear). Displaced Energy Nazi watches for this specific
problem, and makes a lot of noise when any of it is detected.
 
TODO: detect the Malkorok encounter (target the boss?); disconnect from the event
stream when encounter not active
Disclaimer: the word "Nazi" is used in the same sense the Seinfeld Show used it in
the name of the "Soup Nazi": an irascible and domineering individual, easily provoked,
who once provoked engages in verbal abuse and employs whatever institutional authority
they possess to "punish" in retaliation. Re: martinet, bully, despot, tyrant. If your
raid group is having trouble with this mechanic, you need a "nazi" to jerk your
collective leash.
 
TODO: detect the Malkorok encounter (player targets the boss?); remain disconnected
from the event stream until detection occurs, then connect, then disconnect again
when boss is dead
TODO: flag when a player is warned, to throttle event detection and avoid redundant
messaging; clear flags every 2.5 seconds or so
messaging; clear flags every 2.5 seconds or so?
TODO: options UI, allowing:
- disable the addon
- selective enable/disable of affliction warning
- selective enable/disable of damage warning
- selective enable/disable of dispel warning
- control of throttle interval (min 0.1s, max 3s, default to 2.5s)
- selective publication of warnings to any/all of:
chosen chat window(s), raid chat, raid leader chat, whisper to offending player, others?
look into LibSink for this
 
TODO: localizations (use WoWAce/CurseForge for this, since the string table is so small)
TODO: add Italian, Portuguese, and Brazilian Portuguese to the localizations
 
Thanks to the various raid groups that helped develop/debug this addon.
TODO: specifically call out Worggy/L'il, Blood Rising-Area 52, others?
\ No newline at end of file +Thanks to the various guilds and raid groups that helped develop/debug this addon. +TODO: specifically call out Worggy's Flexaholics OpenRaid group, and his Blood Rising-Area 52 guild. \ No newline at end of file