My buddies and I were basically sealing the deal in a 3v3 on cataract. We got to giants first and kept locking the top left and right flags. However, something was either a) bugging out b ) there is a new v1.1 item that I am not aware of that unlocks a flag lock or c) new exploit where someone is able to remove a flag lock before 45 seconds (or possibly d) there are diminishing returns on flag locks)?! I have no idea. I'm sure most of you can imagine how excruciatingly painful it is to watch your Demigod place a flag lock, watch it leave your consumable belt so you know for certain that it has been used, then only see it instantly removed mere seconds later. It's even more painful to know that the circumstances described here lost us the game. Wtf, anyone?
P.S. I don't care if your Demigod philosophy would dictate that we shouldn't have had to use flag locks to win in the first place. That is not the issue here. There is something going on, and the forums are the place to seek solutions and to find others who have experienced similar issues.
- andpancakes
You looked at your belt. Was the flag already locked when you cast another lock?
The previous lock had just expired, which I had anticipated hence me traveling back to it to re-lock it. So, I went to re-lock it, and so mere seconds after I did, my lock was somehow removed by the approaching enemy. Even if it hadn't expired yet though as I went to apply another lock, one can re-lock an already locked flag.
There is no way to remove flag locks, so this is definitely a bug or exploit if you're certain the lock's 45 second time limit didn't expire.
EDIT: Do flag locks have health? I've heard of minions being able to attack things that DG can't, such as Oak's dead wards. In fact, I've often seen my minions attacking flags when I play as a general, despite there being no enemies around.
Not in my experience. At the very least, it doesn't seem to reset/add to the duration. I locked an already locked flag as it was about to expire, and it did expire a few seconds later.
Erub's summons tend to attack flags a lot though it does not seem to happen every match. never seen a ward destroyed before. Still wonder why it has hp. Would be nice if we could actually kill the ward.
On the capture lock thing, I played against a TB who appeared to be removing locks from flags, but i wasn't sure or not. I never saw it instantly happen. Were you against tb?
It seemed to be the Regulus that was able to do it... (I'm one of the team mates)
I don't think it was throwing mines at the already locked flag that did it. In fact, I'm not sure... I even bought some restorative scrolls (the debuff remover) and that didn't do it... I'm fairly certain it was an exploit....
I am %100 certain that the 45 seconds didn't expire before the flag lock was gone... Weird ish, definately cost us the game though. (When you have Giants on the way and you have their flags locked it should be GG, until that happens, and they remove our locks on our ports!)
This. If you lock an already locked flag, it doesn't reset the duration. You need to actually wait until the effect expires if you want to lock it for another 45s.
Are you sure, seems to me like they do stack, maybe not for 100%. But what i saw wasnt a problem with stacking locks. We didnt keep dropping them.
I methodically target Oak's Ward's with my Night Walkers, it has something to do with both wanting access to the same souls. It is not game breaking if Oak pays attention but if he doesn't notice it can leave him quite unprepared.
In any case, that wasn't the issue. The issue was that once one of our flags expired, we re-locked it only to find the lock somehow removed after 3 seconds instead of 45. My only real concern is that some people out there in the community may know of an exploit to remove freshly applied flag locks.
this.
you can't relock before the lock is gone, it will not reset the time of the lock.
People are getting off-topic here.
The OP said the previous lock had expired, so he moved to the flag, and slapped another one onto it. This was then somehow removed.
Ps, are you sure the flag wasn't going past the neutral bar at the presice momment you locked it? Cos i've seen that happen before and the flag lock becomes void.
I've had this happen to me numerous times, where your lock runs out about 2-5 seconds after you placed it, usually on portals that we are re-locking once the first lock is off. (Yes the first lock was definately off.)
From looking trough the LUA code the only thing I can see would be that the graphics are turned off after the first 45 secs, the real lock should still be active though.
# Start Can Not Capture Flag Effect AttachEffectsAtBone( params.Targets[1], EffectTemplates.Items.Consumable.DefenseOfVayikraActivate, -2 ) WaitSeconds(45)
If anyone could care to test this by casting a flaglock on an already existing one about 30 secs old and see if the graphics are removed 15 secs later. The flag should still be uncapturable though since the capture buff stacks Always
Buffs = { BuffBlueprint { Name = 'Item_Consumable_030', DisplayName = '<LOC ITEM_Consumable_0016>Capture Lock', Description = '<LOC ITEM_Consumable_0032>Cannot be captured.', BuffType = 'IUSESPRINT', Debuff = false, Stacks = 'ALWAYS', Duration = 45, Affects = { }, Icon = 'NewIcons/Gadget/DefenseofVayikra',
If you relock a flag that is already locked, the new lock dissappears when the old lock expires.
You have to wait for the older lock to dissappear before applying the new lock for it to last the full 45 seconds.
Did you read the thread? It happens after the old lock has dissapeared when you try to put a new lock on.
As in there is no lock shown on the flag, and you use a capture lock on the flag. It then dissapears after a few seconds.
I'm betting that the lock hadn't worn off yet, but your UI showed it did, so you cast another lock and then the first lock shortly wears off.
The UI lock graphic and the actual lock timer are probably not synced very well.
If by "expired" you mean that the cooldown was over in your consumable belt, that doesn't matter. You have to wait for the lock to physically disappear from the flag and cap it again. If the lock animation is still on the flag, you will indeed lose your lock that you just applied, effectively wasting it.
Aside from that, I can't think of anything else other than an exploit that could do something like that.
Well the lock graphic certainly did get removed from the flag before I cast another one. I saw the graphic fade and walked over to it and cast another on it. The graphic appeared again and an enemy walked towards me and the graphic disappeared. I'm thinking what InfiniteVengeance said is a possibility but for the sync to be off by that much is pretty unreal.(although I really wouldn't be surprised)
in short - no there is not a way to remove flag locks, so it is most likely you applied it too quickly and due to lag or whatever it got removed by the timer from the previous lock, next time wait a few seconds after the lock dissappears from the flag before applying the next flag lock
I was almost certain that flag locks could stack. I didn't realize it was such an ambiguous issue. Either way, though, I think the problem here was due most likely to crazy lag or UI bugs and less likely due to some exploit (thought an exploit wouldn't surprise me).
It'd be nice if I could use a flag lock to unlock the flag that was previously locked by the opposing team.
Disclaimer: The following is pure speculation.
Could it be possible that there is some sort of hidden debuff between same-team flag locks to prevent exactly what the OP was trying to do, which is chain-locking? I wouldn't be surprised, as it would make sense to me for the sake of game balance, but I haven't actually noticed it or tested it, so I'm just throwing it out there in case any of you know for sure there's no such thing.
You should have to buy Keys. They should cost 500.
This is actually in effect in the game apparently. Chain-locking is not possible:
That is, AbyssionX and I tested flag lock stacking and found that flags flocks do not actually stack (so, if a flag lock is about to expire, you must wait for it to fully expire before placing another lock in order to not waste the second lock). I know some of you were already aware of this, but I had such a misconception in my head that I had to test for myself. However, as I've said before, that wasn't the issue stated in my OP but nonetheless an important tidbit of information.
There are many great features available to you once you register, including:
Sign in or Create Account
