Crispen_Longbow wrote: »HoloYoitsu wrote: »
2 V 1 = Zerg
3 V 2 = Zerg
4 V 3 = Zerg
8 V 6 = Zerg
16 V 14 = Zerg
24 v 24 = Zerg
48 v 36 = Zerg
Anytime outnumbered or even same numbers ESO Players will think "Zerg"
Actually, according to JDar, 5 v ~8 blues is a zerg as well, as per our 5 man group pushing a blue keep one night and 'ruining pvp'.
Was that when we got into Roe and were told that we attacked an "empty" keep with "30"?
dap_robertb16_ESO wrote: »A zerg is the number of people required to kill you, plus one.
Crispen_Longbow wrote: »HoloYoitsu wrote: »
2 V 1 = Zerg
3 V 2 = Zerg
4 V 3 = Zerg
8 V 6 = Zerg
16 V 14 = Zerg
24 v 24 = Zerg
48 v 36 = Zerg
Anytime outnumbered or even same numbers ESO Players will think "Zerg"
Actually, according to JDar, 5 v ~8 blues is a zerg as well, as per our 5 man group pushing a blue keep one night and 'ruining pvp'.
Was that when we got into Roe and were told that we attacked an "empty" keep with "30"?
Indeed. What's hilarious is that we all know there are many, many more that are challenged when it comes to counting. It might be why they rely on 10 minute long FTC parses as validation for when they die. "I fought 219 people and was zerged down!"
On the purge thing though, I wonder if it's always acted this way but no one noticed when the cap was at 20.
HoloYoitsu wrote: »
Crispen_Longbow wrote: »HoloYoitsu wrote: »
2 V 1 = Zerg
3 V 2 = Zerg
4 V 3 = Zerg
8 V 6 = Zerg
16 V 14 = Zerg
24 v 24 = Zerg
48 v 36 = Zerg
Anytime outnumbered or even same numbers ESO Players will think "Zerg"
Actually, according to JDar, 5 v ~8 blues is a zerg as well, as per our 5 man group pushing a blue keep one night and 'ruining pvp'.
Was that when we got into Roe and were told that we attacked an "empty" keep with "30"?
Indeed. What's hilarious is that we all know there are many, many more that are challenged when it comes to counting. It might be why they rely on 10 minute long FTC parses as validation for when they die. "I fought 219 people and was zerged down!"
On the purge thing though, I wonder if it's always acted this way but no one noticed when the cap was at 20.
@Satiar +102
heystreethawk wrote: »Gross. Any testing on Cleanse?
heystreethawk wrote: »Gross. Any testing on Cleanse?
HoloYoitsu wrote: »He did, he's a DK now.Astanphaeus wrote: »
ZOS_JessicaFolsom wrote: »Thanks for the detailed report and video example @Akgurd. We've sent everything over to our Dev and QA teams for investigation.
ZOS_JessicaFolsom wrote: »Thanks for the detailed report and video example @Akgurd. We've sent everything over to our Dev and QA teams for investigation.
Couldn't do this on Thursday when it was posted so that the fix could of made it into today's patch eh?
ZOS_JessicaFolsom wrote: »Thanks for the detailed report and video example @Akgurd. We've sent everything over to our Dev and QA teams for investigation.
@ZOS_JessicaFolsom Probably happening with rapids too. We've seen some issues with that but have not tested as yet.
ZOS_JessicaFolsom wrote: »@ZOS_JessicaFolsom Probably happening with rapids too. We've seen some issues with that but have not tested as yet.
Okay, thank you. We'll have the team look at Rapid Maneuver for this same call-out.