Alterac Valley - Node timers, auto quest turnins, and sync
Arathi Basin - Node timers and final score estimation
Eye of the Storm - Flag respawn timer, flag carrier display, and final score estimation
Isle of Conquest - Node timers and siege engine timer
Warsong Gulch - Flag respawn timer and flag carrier display with health percent
Wintergrasp - Start timer, wall alerts, and auto show zone map
Zone Map - Change scale, narrow, and hide border
Other - Port expiration timers, queue wait timers, scoreboard/capture bar/vehicle seat repositioning
Looking For Group - LFGStatusIcon support for LFD wait/port timers
How to use:
Show options - "/capping" or right-click on a timer bar/anchor
Toggle anchor - left-click on a timer bar or use options menu
Send time info to SAY - shift left-click on that timer bar
Send time info to BG - ctrl left-click on that timer bar
Hide timer bar (also leaves queue if related) - ctrl, shift, or alt right-click on that timer bar
Target carrier (in WSG or EotS) - left-click on the carrier's display
Send carrier info to BG - ctrl left-click on the carrier's display
Why no auto-release and auto-join?:
I try not to promote bad habits in my mods.
No auto-release because knowing when you should or should not release is a part of being a smart player in battlegrounds. For example, say there is five seconds left to capture blacksmith and you die there. Auto-release will send you to the starting area, but if you wait five seconds, you release to blacksmith graveyard.
Another reason not to use auto-release is to have time to spy on the flag carrier after a failed kill attempt.
Auto-join was useful when there were single queues and long wait time/afk time. Today is different, of course.
I'm not telling you how to play, just giving you my reasons.
Why no convenient "Incoming" and such buttons?:
The users and I had a discussion about this before when Capping was on wowace. If spoiled, the users would not type something important if there's no lazy way to do it. Am I right?.
Messages probably no mod covers:
Incoming? Well, how many? From which direction?
Incoming BS. Oh wait, they're going LM now.
Incoming BS, but we're all here already. I mean fight at the flag, they're capping.
Need help at MT...3 enemies behind
Incoming DR...3 stealth
Flag carrier going ramp side, almost dead
Flag carrier on the way up the roof, behind tree
...and so on
Don't you love seeing "INCOMING BS" "INCOMING BS" "INCOMING BS" with 2 enemies incoming and 5 people already defending? After about 5 more come to help chase these 2 kills, you get spammed "BS CLEAR".
Plenty of standalone mods that do this, so use those if needed.
Known issues:
Narrow map setting will not work if Mapster is installed. Disabling the battlemap module in Mapster will fix this.
Recently, I had some requests for donation info, so here it is. Do not feel obligated; donations (or lack of) will not determine what features I do or do not implement.
Change Log - Capping
3.3.003-4 03/16/2010:
- added special alerts to Wintergrasp timer
- sync to DBM for IoC Siege Engine timer
- added Wintergrasp alerts for walls being damaged or destroyed
3.3.002 12/12/2009:
- fix current icon mapping issues
- no longer check siege engine's buff time in Isle of Conquest
3.3.001 12/08/2009:
- toc for 3.3
- added option to change spark color
- added option to save settings per character
- added option to reset zone map position
- added option to reset all settings
3.2.006 09/29/2009:
- fix errors on zone map load on clean variables
- fix potential error with node detection
- cleanups
3.2.004 09/23/2009:
- update queue timers to support new 3.2.2 changes
- fixed mouseover highlighting for carrier targets
- clean up many unused variables
3.2.003 09/04/2009:
- organized code between files
- optimized node conflict detection code
- multiplier for Wintergrasp timer seems to be no longer necessary
- added a new layout for timer bars
- added ConfigMode support
3.2.002 08/13/2009:
- replaced event message parsing with POI landmark scanning
- removed all unnecessary node localization due to new method
- Siege Engine timer can now be retrieved by targeting it
- use map filename instead of zone name for detecting battlegrounds
3.2.001 08/04/2009:
- added timer to WSG when three minutes remain
- updated frFR and deDE localization, everyone else is outta luck
- minor tweaks and removed 3.2 compat checks
3.1.005 07/25/2009:
- many random localization changes, don't know anything got messed up
- would be nice to get some localization updates before 3.2
- sync is now auto-requested, but syncing is no longer broad casted
- attempt to sync WSG carrier names
- attempt to sync IoC siege engine timer
3.1.004 (Beta) 07/10/2009:
- beta support for 3.2 and Isle of Conquest (needs localization)
- merged all the battleground files into one
- cleaned up Wintergrasp code
- use more global strings instead of translations
- added option to make the timer bars non-interactive
3.1.003 05/22/2009:
- nil out global reference to CappingLocale
- the timer text is no longer a font size smaller and hour format changed
3.1.002 05/08/2009 - fix SetTexCoord error
3.1.001 04/14/2009:
- updated for 3.1
- now use the GetWintergraspWaitTime function
- removed chat syncing of Wintergrasp time since it's not so useful anymore
- removed showing the redundant timer bar in Wintergrasp that shows when the battle will end
- slightly improved timer bar performance
- timer bar background colors is now colored as the darkened foreground's
- sparks' height adjusted to better fit the bar's height
- added font shadow
Originally posted by bonzoid I've managed to lose my zone map. Full (shift) reset hasn't worked nor has deleting all the Capping saved variables I could find and reinstalling.
Any ideas?
Thanks.
Sorry for the late reply, this comment got buried with my other mods. Make sure your make is enabled to be shown in the first place by checking the dropdown box in the world map.
Originally posted by scarfyrre The 'You are not in a raid group" is a known bug. It's not from this add-on (since I don't have it...yet), and we've not figured out if any add-on causes it. My husband and I both play, have different add-ons, and we get it constantly.
I think it's on Blizzard's side.
It is not really a bug, you could argue about it, but
In the past any commtraffic sent to "RAID" while being in a BG, would silently fail
Nowadays you get the "you arent in a raid " message.
It's the addons that need to add a check for that currently.
You could use StopAddonMessage or YAIAP /you arent in a party fix (debug mode) to find out the addon causing this message.
I've been getting this error while running the latest version here while in various BG's. Doesn't seem to cause any problems or make Capping quit working, but here it is nonetheless.
[20:48:18] Interface\AddOns\Capping\core.lua:653: TexCoord out of range
[C]: ?
[C]: in function `SetTexCoord'
Interface\AddOns\Capping\core.lua:653: in function `SetValue'
Interface\AddOns\Capping\core.lua:586: in function `SetValue'
Interface\AddOns\Capping\core.lua:596: in function <Interface\AddOns\Capping\core.lua:588>
Originally posted by totalpackage How sure are you that Capping is doing it and not anything else?
The 'You are not in a raid group" is a known bug. It's not from this add-on (since I don't have it...yet), and we've not figured out if any add-on causes it. My husband and I both play, have different add-ons, and we get it constantly.
Originally posted by pewter77 I'm almost positive this is it, i am running the latest version downloaded here, i backed up my ui, deleted everything for a fresh wow, WTF, Interface Folders and every time i got into a bg, it would spam my chat with that.
Almost positive is negative. Make sure by running Capping by itself. That spam usually comes from unit frame mods.
I'm almost positive this is it, i am running the latest version downloaded here, i backed up my ui, deleted everything for a fresh wow, WTF, Interface Folders and every time i got into a bg, it would spam my chat with that.
Anyway, capping still seems to work, but [score/player count/flag carrier] display section looks broken (for example shows only alliance mark, and not horde one; does not show score or player count) until score changes (then it updates, and looks as it should be).
If interested - I could investigate this issue further, for example: if this issue only shows up when entering WSG before it has begun (or if it also happens when I enter WSG which is already in progress), if this happens only during first battleground entered for that WoW session, or for subsequent ones too, what happens if I disable all other addons, etc. Didn't want to double-check all those things before I get feedback here (this means before I get response that anyone here is interested in this issue )
).