Recent Topics

Ads

Phoenix Gate scenario, biased for destro, why never fixed?

Let's talk about... everything else
User avatar
Bozzax
Posts: 2477

Re: Phoenix Gate scenario, biased for destro, why never fixed?

Post#31 » Sat Feb 27, 2021 8:34 pm

Reality is that 9/10 one of the sides side can moonwalk flag (walk toggled and backpedaling) and cap comfortably making this entire thread a waste of bytes
A reasonable RvR system that could make the majority happy http://imgur.com/HL6cgl7

Ads
Mordd
Posts: 260

Re: Phoenix Gate scenario, biased for destro, why never fixed?

Post#32 » Mon Mar 01, 2021 1:45 am

Bozzax wrote: Sat Feb 27, 2021 8:34 pm Reality is that 9/10 one of the sides side can moonwalk flag (walk toggled and backpedaling) and cap comfortably making this entire thread a waste of bytes
Actually about 1/3 of my losses is due to this. many times we pick up the flag and after destro picks it up and just runs to the bridge for the easy drop.

Sulorie
Posts: 7219

Re: Phoenix Gate scenario, biased for destro, why never fixed?

Post#33 » Mon Mar 01, 2021 2:00 am

Mordd wrote: Mon Mar 01, 2021 1:45 am
Bozzax wrote: Sat Feb 27, 2021 8:34 pm Reality is that 9/10 one of the sides side can moonwalk flag (walk toggled and backpedaling) and cap comfortably making this entire thread a waste of bytes
Actually about 1/3 of my losses is due to this. many times we pick up the flag and after destro picks it up and just runs to the bridge for the easy drop.
So your team didn't notice, that the enemy is taking your flag? If it happens, that your team picks up their flag and then one of them picks yours, someone snaring the destro flag runner would be enough to score at bridge. It should be fixed, if we have a well documented case here but in practice it shouldn't matter much, if your team knows their job.
Dying is no option.

Mordd
Posts: 260

Re: Phoenix Gate scenario, biased for destro, why never fixed?

Post#34 » Mon Mar 01, 2021 4:23 am

Sulorie wrote: Mon Mar 01, 2021 2:00 am
Mordd wrote: Mon Mar 01, 2021 1:45 am
Bozzax wrote: Sat Feb 27, 2021 8:34 pm Reality is that 9/10 one of the sides side can moonwalk flag (walk toggled and backpedaling) and cap comfortably making this entire thread a waste of bytes
Actually about 1/3 of my losses is due to this. many times we pick up the flag and after destro picks it up and just runs to the bridge for the easy drop.
So your team didn't notice, that the enemy is taking your flag? If it happens, that your team picks up their flag and then one of them picks yours, someone snaring the destro flag runner would be enough to score at bridge. It should be fixed, if we have a well documented case here but in practice it shouldn't matter much, if your team knows their job.
They havent taken the flag until after we did is the point. They can pick it up after us and easily beat order to middle. Thats the whole problem here.

User avatar
Meliannia
Posts: 276

Re: Phoenix Gate scenario, biased for destro, why never fixed?

Post#35 » Fri Mar 05, 2021 9:18 am

Correct game would be:
whomever takes flag first should get to bridge first given circumstances for both flag runners after the pick up are identical but this is the opposite of what is happening in PHoenix Gate

situation 1
order takes flag first and does not have drop off run interrupted
destro takes flag 2nd and does not have run interrupted
result: destro drops off first
correct result should be order drops off first

Situation 2.
Order picks up flag first, uses charge/flee and does not get hindered on way to flag
Destro picks up flag 2nd and doesnt use charge and doesnt get hiundred
result: destro drops off flag first
correct result should be Order drops flag first by some distance

Situation 3
order picks up flag first and flag runner is snared/KD/rooted/punted by destro
destro picks up flag second and is snared Kd/rooted/punted by order
result: destro drops of first
correct result should be order drops of first

Situation 4
Order picks up flag first and uses charge and is not hampered by destro
destro pick up flag 2nd and is snared punted rooted by order
result order drop off flag first, this is as it should be


Conclusion: only 3 in 4 situations in which order gets flag first is the this scenario playing correctly

let's also not forget ANYTIME destro picks up flag first they WILL get it to bridge regardless of what order do or when order take their flag second. this means destro get a free 50 points or they get the 1point per second tick for free all way back to their base.

Conclusion: the distances should be equal for both teams then anything that happens after pick up is down to the individual teams to to perform

There is no way a white lion who picks up the flag before destro and uses charge and flee and is not hindered by destro at all on way to bridge should be beaten to the middle point by destro black orc flag guy who picked it up afterwards

It's nonsense

worrying that an 'element' here cannot see that basic premise

No its NOT orders fault that they dont snare the destro flag guy that is a SECONDARY ISSUE, the PRIMARY issue is the flag for destro is 12 secs closer to bridge, if this is fixed then if order choose not to snare the flag guy then thats orders fault, sure, but atm this scenario is biased, unfair and broken an needs fixing so parity and equality is brought unto it.

Gromgrill crossing; Order had a 3second advantage closer to bridge, destro complained (justifiable) and gms/devs emergency fix it in 3 days
Phoenix Gate, destro have 12 second advantage closer to bridge, order complained, 3 years now, nothing done about it..... Worrying.

User avatar
GamesBond
Former Staff
Posts: 1072
Contact:

Re: Phoenix Gate scenario, biased for destro, why never fixed?

Post#36 » Fri Jul 09, 2021 5:20 pm

July 9 update:
Phoenix Gate's flag capture-point has been moved to equalize the time needed from both factions to reach and capture the flags in the middle of the map.

The scenario should be updated either in this patch or on next week's patch.

Who is online

Users browsing this forum: No registered users and 29 guests