Dear visitor, welcome to Gaming Insight Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.
Alterac valley - Capture-timer doesn't update (Fixed)
When someone cap a GY/Tower etc, the timer is shown fine:
[attachment=1]<!-- ia1 -->AV1.jpg<!-- ia1 -->[/attachment]
If the GY/Tower is left undesturped for the entire 4 minutes, nothing wrong happens..
However, when the opposing faction re-cap that GY/Tower, the timer continues as nothing have happened, even though the GY/Tower is going to the otehr side.
[attachment=0]<!-- ia0 -->AV2.jpg<!-- ia0 -->[/attachment]
The icon on the map, changes color fine, it's only the timers that have the problem.
Currently using r5433, but it have happend for quite some time..
[attachment=1]<!-- ia1 -->AV1.jpg<!-- ia1 -->[/attachment]
If the GY/Tower is left undesturped for the entire 4 minutes, nothing wrong happens..
However, when the opposing faction re-cap that GY/Tower, the timer continues as nothing have happened, even though the GY/Tower is going to the otehr side.
[attachment=0]<!-- ia0 -->AV2.jpg<!-- ia0 -->[/attachment]
The icon on the map, changes color fine, it's only the timers that have the problem.
Currently using r5433, but it have happend for quite some time..
Re: Alterac valley - Capture-timer doesn't update
arta will have to look at this i really don't know. i'm guessing he figures out state from map graphic icon IDs? or the BG state system. but honestly most of that stuff is just gibberish to me so i don't know how to fix it, which is why pvp mods are almost never fixed.
Re: Alterac valley - Capture-timer doesn't update
My guess is that ChatLog is used for registering the first capture, but when next happen (and timer is still present), a new one can't be created as one with that name already exists.
A fix could be to delete any timer already existing (with the name in question) before creating a new one.
When a faction captures and the 4 minutes expire and it's re-capped after that, it works as intended, so the existing timer must be the problem.
A fix could be to delete any timer already existing (with the name in question) before creating a new one.
When a faction captures and the 4 minutes expire and it's re-capped after that, it works as intended, so the existing timer must be the problem.
Re: Alterac valley - Capture-timer doesn't update (Needs Rev
MUCH worse in r5462 
Max 2 timers at any one time (even when 6-7 locations was being captured), exchanging each others at random and sometimes disappear for no (apparant) reason...
With the amount of disappearing timers, it wasn't possible for me to determined if the initial problem is solved or not
Max 2 timers at any one time (even when 6-7 locations was being captured), exchanging each others at random and sometimes disappear for no (apparant) reason...
With the amount of disappearing timers, it wasn't possible for me to determined if the initial problem is solved or not
Re: Alterac valley - Capture-timer doesn't update (Needs Rev
ok, seems I messed something up in the function 
Time to track the new bug
Try 5463 .. missed an argument
Time to track the new bug
Try 5463 .. missed an argument
Requesting combatlogs + chatlogs (how to @ http://ninjapull.de/forumBridge/index.php?f=1&t=2691&p=31971&rb_v=viewtopic#p9577)
Re: Alterac valley - Capture-timer doesn't update (Needs Rev
Looks much better in r5463.
To be able to confirm 100%, I'll have to do a slacker-AV, where I pretty much doesn't do anything else but keep an eye on who capture what and how timers behave..
But at first glance, I had 8 or 9 timers running simultanious, and I think I saw a blue bar being exchanged by a red with a new 4min timer..
To be able to confirm 100%, I'll have to do a slacker-AV, where I pretty much doesn't do anything else but keep an eye on who capture what and how timers behave..
But at first glance, I had 8 or 9 timers running simultanious, and I think I saw a blue bar being exchanged by a red with a new 4min timer..