Download
(13Kb)
Download
Updated: 04-11-07 01:32 PM
Pictures
File Info
Updated:04-11-07 01:32 PM
Created:unknown
Downloads:20,289
Favorites:21
MD5:

StunWatch 2.5b(fixed)  Popular! (More than 5000 hits)

Version: 2.5b(fixed #3)
by: bentagon [More]

Update: v2.5b(fixed #3)
- Got rid of the bad path saved with the previous version. There is no path in this new version but unzip it to your WoW interface folder.
Update: v2.5b(fixed #2)
- Added code so that StunWatch only tries to initialize skills for the player's class. This should hopefully prevent some errors some players were receiving for skills their current character did not have
Update: v2.5b(fixed)
- Fixed issue with bad variable name on line 9
Update: v2.5b
- Added commands to set CombatLogRanges to increase detection range of combat log messages
- Updated English help text and set more output to both chat frame and message frame
- Fixed bug that was updating pounce duration with hibernate's duration


Update: v2.5a
- Fixed issue causing CC effect ending to not be detected
- Added new message frame and option to display calculated cc durations



This is a modification of StunWatch 2.4a by Platykurtic (original StunWatch by Vector).

v2.5 StunWatch supports both Rogue -and- Druid crowd control skills.
The game will try to update all skills but will only show the skill ranks appropriate for your class.

To install the interface, extract the zip file to your World of Warcraft's Interface\AddOns folder. Typically, WoW is installed to C:\Program Files\World of Warcraft. Look for the Interface folder there and underneath it should be an AddOns folder. Extract the zip file using Pathnames.

Usage: /sw
This will list all available options

Usage: /sw option
Options:
on : Enables StunWatch
off : Disables StunWatch
lock : Locks StunWatch bars and enables it
unlock : Unlocks StunWatch bars and allows you to move them
g : Autodetect Improved Gouge Rank"
g0 : Sets Gouge duration to default, untalented duration
g1 : Sets Gouge to Improved Gouge Rank 1 duration
g2 : Sets Gouge to Improved Gouge Rank 2 duration
g3 : Sets Gouge to Improved Gouge Rank 3 duration
k : Autodetect Kidney Shot Rank
k1 : Sets Kidney Shot to Rank 1 duration
k2 : Sets Kidney Shot to Rank 2 duration
s : Autodetect Sap Rank
s1 : Sets SAP to Rank 1 duration
s2 : Sets SAP to Rank 2 duration
s3 : Sets SAP to Rank 3 duration
b : Autodetect Bash Rank
b0 : Sets Bash duration to default, untalented duration (based on Rank)
b1 : Sets Bash duration to ranked duration plus Rank 1 Brutal Impact
b2 : Sets Bash duration to ranked duration plus Rank 2 Brutal Impact
p : Autodetect Pounce Rank
p0 : Sets Pounce duration to default, untalented duration
p1 : Sets Pounce duration to include Rank 1 Brutal Impact
p2 : Sets Pounce duration to include Rank 2 Brutal Impact
print : Prints the current configuration
invert : Invert progress bar direction
scale : Scale StunWatch, use 0.25 to 3.0
width : Set bar width, use 50 to 300
alpha : Set bar alpha, use 0 to 1
grow : Set bar growth up, down or off


Known Issues:
- If player casts cc spell at far/max range, the game does not detect the spell landing on the target and does not display a message in the combat log so StunWatch never knows that the spell landed and does not display a bar.
- Some cc effects do not display a message in the combat log when they end/break so StunWatch does not know to stop showing the bar (until the normal duration ends).
- Breaking a cc effect with a spell that adds a debuff to the target (e.g. Moonfire) is known to trick StunWatch and it doesn't know to remove the cc effect bar (until the normal duration ends).

Optional Files (0)


Post A Reply Comment Options
Unread 01-30-07, 11:43 PM  
bentagon
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 18
Uploads: 1
v2.5b uploaded. This version should resolve the issue with the default combat log detection range being too short for some messages. I've defaulted StunWatch to update the range to 50 but users can set their own desired ranges from 10 to 2000 using a new command /sw setrng <value>.
However, I wouldn't advise setting the range too high as the overhead of all the messages you'll have to process will likely tax your computer, I would imagine.

I've also fixed the bug where I accidentally saved the Pounce duration using the Hibernate duration.


Note: I'm not sure if my changes for the detection range are working of themselves as I've discovered that I've got another mod(s) installed that changes the detection ranges too. If someone could test this out and let me know, that would be great!
Last edited by bentagon : 01-30-07 at 11:45 PM.
Report comment to moderator  
Reply With Quote
Unread 01-30-07, 10:14 AM  
bentagon
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 18
Uploads: 1
Originally posted by Platykurtic

Suggestion:

Here are the variables that are used to define the combat log range:

"CombatLogRangeCreature" = "30"
"CombatLogRangeFriendlyPlayers" = "50"
"CombatLogRangeFriendlyPlayersPets" = "50"
"CombatLogRangeHostilePlayers" = "50"
"CombatLogRangeHostilePlayersPets" = "50"
"CombatLogRangeParty" = "50"
"CombatLogRangePartyPet" = "50"

Where the number is the range. You could use SetCVar to set the relevant saved variables (probably best to have this as an option that the player can select) to the maximum range that a Druid can cast - probably the Creature one. This'll be saved at log out and the issue above will go away. SetCVar is described here - http://www.wowwiki.com/API_SetCVar - and an example would be:

SetCVar("CombatLogRangeCreature", 50) - if the maximum range was 50.

Platykurtic
Platykurtic,
Thanks for the suggestion. I was digging the web and found a mention that something could be changed to increase the length but your information is exactly what I need. I'll try the changes you recommend and hopefully that solves that problem.
Last edited by bentagon : 01-30-07 at 08:07 PM.
Report comment to moderator  
Reply With Quote
Unread 01-30-07, 10:11 AM  
bentagon
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 18
Uploads: 1
Originally posted by Wachunga
One bug I found:

StunWatch_Save[STUNWATCH.PROFILE].stuns[STUNWATCH_POUNCE].LENGTH = duration;

should be (note 3rd line inside function):

StunWatch_Save[STUNWATCH.PROFILE].stuns[STUNWATCH_HIBERNATE].LENGTH = duration;
end

That was causing the duration of my pounces to appear far too long. After making that simple change, it seems to be working perfectly.
Thanks Wachunga! I had found that same bug and fixed it on my copy but was waiting to see if I could replicate Kolakhan's issue before trying to release a fix. Unfortunately, I'm not running Auctioneer (and thus Swatter) to know what error he is seeing. I may implement Platykurtic's suggested change to combat log range and then release version "b".
Report comment to moderator  
Reply With Quote
Unread 01-30-07, 04:14 AM  
Platykurtic
A Murloc Raider
AddOn Author - Click to view AddOns

Forum posts: 4
File comments: 164
Uploads: 4
- If player casts cc spell at far/max range, the game does not detect the spell landing on the target and does not display a message in the combat log so StunWatch never knows that the spell landed and does not display a bar.

Suggestion:

Here are the variables that are used to define the combat log range:

"CombatLogRangeCreature" = "30"
"CombatLogRangeFriendlyPlayers" = "50"
"CombatLogRangeFriendlyPlayersPets" = "50"
"CombatLogRangeHostilePlayers" = "50"
"CombatLogRangeHostilePlayersPets" = "50"
"CombatLogRangeParty" = "50"
"CombatLogRangePartyPet" = "50"

Where the number is the range. You could use SetCVar to set the relevant saved variables (probably best to have this as an option that the player can select) to the maximum range that a Druid can cast - probably the Creature one. This'll be saved at log out and the issue above will go away. SetCVar is described here - http://www.wowwiki.com/API_SetCVar - and an example would be:

SetCVar("CombatLogRangeCreature", 50) - if the maximum range was 50.

Platykurtic
Report comment to moderator  
Reply With Quote
Unread 01-29-07, 10:10 PM  
Wachunga
A Murloc Raider
 
Wachunga's Avatar
AddOn Author - Click to view AddOns

Forum posts: 5
File comments: 22
Uploads: 1
Great work, bentagon. Everything druid-related is working fine for me.

One bug I found:

function StunWatch_UpdateHibernate()
-- Get Hibernate Rank from Spellbook
local duration = StunWatch_GetHibernateDuration();
StunWatch_Save[STUNWATCH.PROFILE].stuns[STUNWATCH_POUNCE].LENGTH = duration;
end

should be (note 3rd line inside function):

function StunWatch_UpdateHibernate()
-- Get Hibernate Rank from Spellbook
local duration = StunWatch_GetHibernateDuration();
StunWatch_Save[STUNWATCH.PROFILE].stuns[STUNWATCH_HIBERNATE].LENGTH = duration;
end

That was causing the duration of my pounces to appear far too long. After making that simple change, it seems to be working perfectly.
Last edited by Wachunga : 01-29-07 at 10:11 PM.
Report comment to moderator  
Reply With Quote
Unread 01-29-07, 09:37 AM  
bentagon
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 18
Uploads: 1
I'll check it with my rogue when I get home tonight. Everything was working fine for my druid as of last night at 2am but I haven't tried it out on my rogue recently.

[Edit] I believe Swatter is an addon that comes with Auctioneer. What version of Auctioneer are you running? Is it their gamma version?
Last edited by bentagon : 01-29-07 at 09:49 AM.
Report comment to moderator  
Reply With Quote
Unread 01-29-07, 07:58 AM  
Kolakhan
A Deviate Faerie Dragon

Forum posts: 18
File comments: 54
Uploads: 0
I use a Rogue. D/L yesterday, on initial screen Swatter (checks for problems) threw up a SW error. When in game did not appear to work at all??? Put old version back and everything is fine. Let me know when it is fixed and I'll give it another shot.
Report comment to moderator  
Reply With Quote
Unread 01-28-07, 05:11 PM  
bentagon
A Kobold Labourer
AddOn Author - Click to view AddOns

Forum posts: 1
File comments: 18
Uploads: 1
Sorry about the other v2.5a I submitted as a patch. Still learning the system!
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: