Have the graveyard spawns in AV always been so one sided?

Let me get this straight, you think that arriving by IB choke just as 40 horde do is a better scenario for alliance than horde showing up in alliance territory with your NPC support?

Horde is not showing up at SF 20 seconds before alliance can. Stretches like this do not do you any favors.

Please name the horde that argue that aspect to not be broken. I’ll wait.

AV is still more enjoyable to lose than WSG or AB are to win.

imo

3 Likes

Strongly disagree. Even losing WSG and AB is better than losing AV because if we lose in AB/WSG, it was either a.) a premade or b.) horde group was better. Neither of those have to be true in AV to lose.

6 Likes

The thing is being down one cap in WSG or being 2/3 flags in AB is not an unrecoverable situation. Or a situation the map tries to put alliance in.

You got something that disproves this?

3 Likes

Is he still trolling?

I dont know what game you’re playing but when (or rather if) the Alliance is smart enough to take ibgy en masse, then the game for all intetns and purposes is a win for the Alliance. Taking back IBGY when fully capped in all but impossible and it doesnt matter where the spawn point is.

So yes it does seem fine because all the problems you talk about moot when IBGY is in alliance hands.

omfg… can’t you get it through your head… that none of this bs could take account of a 95-99 pct win rate? We could get ibgy but then you get sfgy and shgy… before us. by the way and you catch us on the way to ib and stop a 1/4 to a half of us in the fields between sf and ib… even if we do cap ib with a small team the other 3/4 of us are pinched in between your 20 at sh at the choke point not allowing us forward movement. which then let’s the remaining 10-20 horde who were capping sfgy to just go back and retake IB. stop being so ignorant to the facts man… you can’t not see it.

Or, you just don’t care about how broken the map is because you like winning every AV you go into because the map is in your favor. Which is understandable I guess but it’s still not right.

Another fun fact… the hunters can shoot you through the mountains near SPGY… that’s always fun, trying to LOS then getting hit because they can somehow shoot through a mountain. Mages can do this broken crap too.

7 Likes

How is taking back an objective where alliance can’t Rez at it yet and have no other graveyard that’s closer than 2 minutes away impossible for horde??

Even considering we hard cap it, we still only Rez up to 10 at a time, you Rez up to 20 at a time while fighting near it. Is math that hard?

It’s even worse in the 5 minutes to hard cap it. It has no bearing on the game if horde die, their cave rez always saves them, but alliance dying defending the IBGy soft cap will Rez at SPGY, over 90 seconds away, while you Rez with double the numbers and 20 seconds away.

Not hard to chip away, even just throwing yourselves into alliance at IBGY soft cap, kill 1-3 of us, loot insignia and those alliance won’t ever make it south.

You die, Rez at cave 20 at a time, mount up ride the 20 seconds back and rinse and repeat, after 4-6 cycles of this there won’t be any alliance left at IBGY, they would all be north trapped by the SHGY bunker choke point that horde control.

6 Likes

Wrong.

Whether it’s from the start of the game or later, over 90% of IBGY pushes end in failure. When Alliance get a soft cap on IBGY, SHGY is usually taken. With no reinforcements from Alliance, IBGY is retaken. So actually GETTING IBGY is a very rare occurance.

If Alliance caps IBGY, it’s still usually a loss. I’ve been there several times. By the time Horde are done fighting and start running around, they have soft capped IWB and often DB. SHB is already gone. So Alliance is starting a race 50 yards back from the starting line.

I’ve played matches where Horde send back cappers, and where they don’t. When Horde ignore back capping, they end with a win sooner rather than later.

I’ve been in matches where Alliance send back cappers and matches where they don’t. Of course not back capping is an automatic loss. But the ONLY time back capping has resulted in a win is when the Horde were completely brainless and allowed us to back cap SHB and IWB. These brain dead Horde will trickle in FW one by one or not have mages constantly casting blizzard on the recall spot in DB.

BTW, I’m exalted. I won four games in that entire time. Each win Alliance played like gods and the Horde played like mentally challenged squirrels. I’ve played maybe twenty matches where Alliance capped IBGY.

So I take it you were in one of those extremely rare matches with a team of comatose Horde? No other explanation for this crazy assertion.

3 Likes

That is true for both faction’s mages and hunters. :man_shrugging:
Let’s talk about possible LOS at FWGY, shall we?

Yeah. All the horde are just elite. Who knew the the choice at character creation was so impactful on the skill level of the player.

So you admit its not balanced?

Except if you’re an Alliance mage or hunter you are spawning with horde above you and no where to really retreat to, to get away from the damage coming thru the walls.

I admit the horde cave is closer to mid than the alliance cave. Whether or not thats an imbalancing factor of epic proportions is something else entirely.

Ive stated many times that Im fine with a horde cave push back.

And if you die when horde is soft capping SPGY you get the same advantage you speak about to get it back due to the cave being virtually right above it. Also, where are the LOS advantages of FWGY?

The aforementioned issue is proven by latter statement

The problem is that alliance players dont dedicate themselves to winning strategies. Taking IBGY is the beginning of win for Av for them. All you’re doing is looking for excuses for failure

The problem solely resides in the players on the Alliance side

Sock puppet off the starboard bow!!!

2 Likes

Stop making claims that aren’t true.

And the same guy telling alliance how to win

It’s all about IBGY

If Alliance players refuse to listen that is there own fault