serious gvg bug (no pve flame thank you in advance)
keli
So we(Team Chaos Theory[hent]) were playing the mAT. We had 2/2 so we had a not so low chance to get into top 16(silver cape).
But. We were playing the 5. match against Planet Unicorn [heyy]. They ran a/p omega spike while we played with nH build.
Here comes the funny thing. Around 26 we splitted to the opponents base while they were tried to gank our lord. They died at our base and did very low dmg to our lord. While we did serious damage to their lord AND EVEN KILLED IT AT 28:00. So the thing is that we did more damage and even killed the lord BUT THE F*CKING MATCH ENDED WITH A DRAW. SO "DOUBLE WIN" = DRAW
WHAT THE IS THIS ??
After this we had no chance to get the silver cape.
REGINA PLEASE COMMENT ON THIS WE ARE VERY INTRESTED.....
1.
2.http://img412.imageshack.us/img412/731/gw064.jpg
All of the 16 players agreed to let their name shown on the picture.
Please don't post huge pictures, thanks. Changed to link.
But. We were playing the 5. match against Planet Unicorn [heyy]. They ran a/p omega spike while we played with nH build.
Here comes the funny thing. Around 26 we splitted to the opponents base while they were tried to gank our lord. They died at our base and did very low dmg to our lord. While we did serious damage to their lord AND EVEN KILLED IT AT 28:00. So the thing is that we did more damage and even killed the lord BUT THE F*CKING MATCH ENDED WITH A DRAW. SO "DOUBLE WIN" = DRAW
WHAT THE IS THIS ??
After this we had no chance to get the silver cape.
REGINA PLEASE COMMENT ON THIS WE ARE VERY INTRESTED.....
1.
2.http://img412.imageshack.us/img412/731/gw064.jpg
All of the 16 players agreed to let their name shown on the picture.
Please don't post huge pictures, thanks. Changed to link.
deluxe
Did you enchant/weapon your lord a lot?
Death of lord doesn't count usually at 28:001 so all I can think of that they actually did more lord damage or you enchanted the lord a lot.
Death of lord doesn't count usually at 28:001 so all I can think of that they actually did more lord damage or you enchanted the lord a lot.
keli
Quote:
Did you enchant/weapon your lord a lot?
Death of lord doesn't count usually at 28:001 so all I can think of that they actually did more lord damage or you enchanted the lord. |
But if the lord died after 28:00 and it doesnt count, we still did more damage.
And btw there is 0 i mean 0 chance to get draw with lord damage..
Zodiac Meteor
that's a bad bug, contact support to get it fixed.
majikmajikmajik
Nothing can be done about your game now, just contact support and let them know.
FoxBat
My speculation as to what happened:
- Guild lord died at 27:59 or 28:00
- It takes a few seconds for the lord death to end the game in victory.
- Game hits 28:01, it hasn't ended, so it calls tiebreaker. Doesn't check that the Lord is dead, because it's fairly unlikely.
- Guild Lord damage is stored as a variable attached to the lord "object" - but when dead, the object (and access to related variable) are gone.
- Failsafe when the value can't be found is to declare a draw.
If it's working like above, this should be fairly easy to replicate and fix.
- Guild lord died at 27:59 or 28:00
- It takes a few seconds for the lord death to end the game in victory.
- Game hits 28:01, it hasn't ended, so it calls tiebreaker. Doesn't check that the Lord is dead, because it's fairly unlikely.
- Guild Lord damage is stored as a variable attached to the lord "object" - but when dead, the object (and access to related variable) are gone.
- Failsafe when the value can't be found is to declare a draw.
If it's working like above, this should be fairly easy to replicate and fix.
Aera
It's a one in a million thing, they won't fix it
Kaon
Quote:
My speculation as to what happened:
- Guild lord died at 27:59 or 28:00 - It takes a few seconds for the lord death to end the game in victory. - Game hits 28:01, it hasn't ended, so it calls tiebreaker. Doesn't check that the Lord is dead, because it's fairly unlikely. - Guild Lord damage is stored as a variable attached to the lord "object" - but when dead, the object (and access to related variable) are gone. - Failsafe when the value can't be found is to declare a draw. If it's working like above, this should be fairly easy to replicate and fix. |
Sucks to be you I guess, though there've been many worse things in MATs.
I'm talking:
- Midmatch bans (lol retarded)
- Errors right before match starts so you auto forfeit. This happens almost every single month to one guild, happened to my guild once as well, it really sucks.
- Matches not allowed to be replayed even if there has been cheating or serious errors.
Then again, 90% of the Anet developers don't know what a monthly tournament is, so yeah...
Sarevok Thordin
Wow you guys got gooned :/
Gforce
Quote:
My speculation as to what happened:
- Guild lord died at 27:59 or 28:00 - It takes a few seconds for the lord death to end the game in victory. - Game hits 28:01, it hasn't ended, so it calls tiebreaker. Doesn't check that the Lord is dead, because it's fairly unlikely. - Guild Lord damage is stored as a variable attached to the lord "object" - but when dead, the object (and access to related variable) are gone. - Failsafe when the value can't be found is to declare a draw. If it's working like above, this should be fairly easy to replicate and fix. |
Pretty much every victory is checked on a 3 second interval since the match starts. So the game checks if the victory condition is met on 00:03, 00:06, 00:09. I have no clue if it does another check on 28:00, but I assume it does. The lord damage win/loss triggers at 28:03. Combine that with the assumed explanation you gave would probably mean that killing the lord between 28:00 and 28:03 will result in a draw.
phan
My guess is at 28.00 mechanics scanned for victory conditions and failed to record a lord to record the damage and gave the Unicorns a draw .