AB timers with a narrowed zone map (Cartographer colored icons)
WSG flag carriers with HP percent
AV and WG timers using alternate bar layout
Capping
Capping is just another battleground timer mod with some extras.
Current Features:
All battlegrounds/arenas have start timers
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 timers 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
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.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 Ruystaz I have allwasys been playing more pve than pvp so I thought it was time to get some pvp addons, like this on but only one thing I dont like, is it possible to move the flag capture thing and wintergrasp timer? Or is this coming in any later update?
Flag carriers stay with the scoreboard and the Wintergrasp timer stays with the other times. Both the scoreboard and the group of timers may be moved, however.
I have allwasys been playing more pve than pvp so I thought it was time to get some pvp addons, like this on but only one thing I dont like, is it possible to move the flag capture thing and wintergrasp timer? Or is this coming in any later update?
Problems with bg mini map in latest patch, and getting errors:
Capping-3.2.004\core.lua:270: attempt to index local 'bgopts' (a nil value)
Capping-3.2.004\core.lua:243: in function `?'
Capping-3.2.004\core.lua:124: in function <Interface\AddOns\Capping\core.lua:123>
<in C code>: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:232: in function `UIParentLoadAddOn':
Interface\FrameXML\UIParent.lua:247: in function `BattlefieldMinimap_LoadUI':
Interface\FrameXML\UIParent.lua:390: in function `ToggleBattlefieldMinimap':
<string>:"TOGGLEBATTLEFIELDMINIMAP":1: in function <[string "TOGGLEBATTLEFIELDMINIMAP"]:1>
There is an option to disable the WG timer. Also, the WG timer doesn't just disappear; it stays up and shows "0" seconds for about 2 mins after the timer ended.
Would it be possible to get an option for the WG timer that maybe changes the color or just the timer text rather than disappearing when a battle is taking place?
the buff on the siegeengine we use to determine when it will be repaired, seems to be broken. It is confirmed by a gm, that it vanishes and hasnt the full duration fo 3m.
I thought it would be "if we have two flag carriers at the same time , start timer and if one flag is dropped remove it", so we wouldnt really need localisation updates, because you could get the localised spellname from the id.
Originally posted by richerich That's odd, since i've tested every option available and this is how i get, no matter how i try:...
Capping timers are separated into two groups, battleground timers and etc timers, one on top and one on bottom of the anchor. If you want them in a single group, check "Single Group".
Quote:
Originally posted by yoshimo When both flags are held in WSG for too long, both flag carriers receive a debuff limiting their movement speed and increase damage taken....
Yea, I've been trying ways to implement reliably, but it is more complex than it seems. There are issues about when does the timer start and when it resets. Does it start when the first flag or both flags are picked up? It doesn't necessary reset when the carrier drop the flag. If you pick up the flag after it has been returned while under the debuff, the new carrier will also get the debuff...even if both flags are returned at the same time.
Anyway, it is not a critical timer to monitor, and we do get debuffs and chat notification of when it actually occurs. If it was simple, I would no doubt add it; however, it may not be worth it for the effort and added bloat (more localization is probably needed, and that's a pain to get).
