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 totalpackage Most likely, nope. We should not care how exact/detailed the time remaining is when it's beyond an hour. Also, 1h48 is not very standard (looks like incorrect hex), 1h 48m takes up too timer bar much space, and 1:48 can be confused with 1m 48s.
So could you just round to nearest integer when over an hour please ?
Originally posted by jakeb1138 ...How about adding the ability to right-click on the objectives in AB, EOTS, Strand etc so we can ask for help or give status through the /bg or /raid channels.
The users and I had a discussion about this before when Capping was on wowace. I should note this on the addon description, but I did mention I do not promote bad habits in my mods. If spoiled, the users would not type something important if there's no lazy way to do it.
1. Incoming? Well, how many? From which direction?
2. Incoming BS. Oh wait, they're going LM now.
3. Incoming BS, but we're all here already. I mean fight at the flag, they're capping.
4. Need help at MT...3 enemies behind
5. Incoming DR...3 stealth
6. Flag carrier going ramp side, almost dead
7. Flag carrier on the way up the roof, behind tree
8. ...and so on
An oh yea, I love seeing "INCOMING BS" "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".
Originally posted by Elisios "1.8h" is a silly representation of "1h48" or "1:48". Though I easily understand why Capping does this ATM, could you tweak it so the Wintergrasp timer became easier to read please ?...
Most likely, nope. We should not care how exact/detailed the time remaining is when it's beyond an hour. Also, 1h48 is not very standard (looks like incorrect hex), 1h 48m takes up too timer bar much space, and 1:48 can be confused with 1m 48s.
"1.8h" is a silly representation of "1h48" or "1:48". Though I easily understand why Capping does this ATM, could you tweak it so the Wintergrasp timer became easier to read please ?
I have the stacking issue. Everytime Capping starts a timer bar, there is an error message:
Capping-3.0.018\core.lua:662: attempt to perform arithmetic on field 'spacing' (a nil value)
Capping-3.0.018\core.lua:807: in function `StartBar'
Capping-3.0.018\core.lua:867: in function `?'
Capping-3.0.018\core.lua:120: in function <Interface\AddOns\Capping\core.lua:119>
Originally posted by totalpackage A screen might help. Also, does it still happen if you revert back to the previous version of Capping?
The stacking was happening for me too, reverted to .17 and everything works perfectly.
Essentially, all the bars except for the Wintergrasp timer were piling on top of each other to the top of the positioning bar; for whatever reason my Wintergrasp timer bar wasn't falling into the same stack, just sitting above the mess.
Originally posted by kroviken Since the update yesterday for this addon, I've been having an issue where timers have been overlapping eachother. I was wondering if this was just me of if other people are experiencing this.
A screen might help. Also, does it still happen if you revert back to the previous version of Capping?
Since the update yesterday for this addon, I've been having an issue where timers have been overlapping eachother. I was wondering if this was just me of if other people are experiencing this.
Re: Re: BG Queue timer and Port timer stoped working?!
Quote:
Originally posted by totalpackage
Those timers may be off-screen for you depending on where you put Capping's anchor.
This was indeed the fact. I did not know that Capping grows both upwards and downwards from its anchor. After moving the anchor down from the top of the screen I now see queue/port timers again.
Re: BG Queue timer and Port timer stoped working?!
Quote:
Originally posted by tlund Suddenly, Capping is no longer showing the Queue timer or the port time. All the other timers works fine. I upgraded to the latest version but the problem persists. I have uncheckd/checked the options to show the timers but that didn't help. Any suggestions or Ideas?
Those timers may be off-screen for you depending on where you put Capping's anchor. If that's not it, you may need to reset your variables or check for addon conflicts. If you want to try to reset, try this:
