That'll happen when you wait a few months for bug fixes only to get a patch that says it fixes bugs but doesn't and actually nerfs things instead.
And then watching the official channels ****** on the ashes. It's that last part that really gets to me and takes away my hope that things will really get better.
BioWare just shot themselves in the foot.
I don't know how much the rest of you know about Dragon Age MP culture (I'm an expert), but honor and shame are huge parts of it. It's not like it is in the Mass Effect forums where you can become successful by being an *******. If you screw someone over here, you bring shame to yourself, and the only way to get rid of that shame is repentance.
What this means is the multiplayer fanbase, after hearing about this, is not going to want to play multiplayer as any character, nor will they purchase any of BioWare's games. This is HUGE. You can laugh all you want, but BioWare has alienated an entire market with this move.
BioWare, publicly apologize un-nerf the Reaver or you can kiss your business goodbye.
To say that EA is going to go out of business because of a Reaver nerf is a little presumptuous.
I have yet to see the pots bug happen again, still haven't lost a key again but I've encountered a bug that would not let me move at all, which I'm not sure if is new or not but I could not move unless I used leaping shot.
You guys have collectively lost your ****. I mean there's being disappointed, and then there's whatever the hell is happening in this thread.
It's the internets, what else did you expect?
I have yet to see the pots bug happen again, still haven't lost a key again but I've encountered a bug that would not let me move at all, which I'm not sure if is new or not but I could not move unless I used leaping shot.
That's an old bug. An annoying one at that. Renders game unplayable. No way to bypass that except leave game, and make/join another.
I'm convinced that their QA team is non-existent.
also, about the ravager nerf...WTF? because she needed to be more squishy?
were you thinking: "oh hey instead of buffing the Katari, why don't we nerf the **** out of the ravager, you know, so she'll be equally useless"
any class is "unkillable" if somebody is casting barriers on them or a tank is taunting enemies to not attack them. Either way reaver is supposed to do more damage, but its offset by the fact that he doesn't have reliable guard and dies very quickly on harder difficulties. AW has some of the best survivability and better than average dps. Its a poor comparison to look at a AW vs a damage focused class being babysit by a keeper or tank in terms of who kills faster.
You're kind of using what's exactly my point as though you're refuting it...
The game is clearly designed for teams of 4, ideally (by design) with at least one of each base class in the team.
People keep saying the AW has high survivability as though it's the "unbalancing" thing... but everyone has high survivability. It's not a design flaw if you're in a group where nobody is controlling agro, or casting barrier, or you pull agro from 4 archers standing in the open without a barrier when you're a reaver. It's also not overpowered that an AW can solo Perilous when a group of 4 can do it in half the time or less and they all get the same reward (more if they do all the rooms)
If everyone has high survivabily (in a decent team, which isn't hard to find even while PUG-ing), then is the class that does arguably the highest damage in the game, or the one that does "above average" damage likely to get nerfed first?
Personally I rate AW damage as average at best, but that's a different discussion.
The problem is what you just said, playable with HoK. Thats really helpful for those who dont have one.
I'd argue that every Rogue and Warrior class in this game needs HoK more than a Reaver does - the fact that a Reaver has Rampage and Devour actually makes it one of the few classes that doesn't need HoK, and the only class with significant heal on hit (except for the psuedo heal on hit that the AW has)
Mass effect 3's multiplayer was only good and was only worked on so much because of the massive backlash that they received for the games ending and how the mp was tied to the single player. The multiplayer would NEVER have got the proper treatment or all of that extra content had that NOT happened. I guarantee it
I think you're having some problems with causality. MP's support, QA and balance had been underway for months before EA or BioWare addressed the ending. And besides, they had all the forum and telemetry information at their fingertips to know that MP had been chugging along just fine regardless of how people felt about SP's ending.
Tell me I'm wrong.
You're wrong.
more bears and giants in wave 5
Anyways is there an ETA on the release date for the patch?
I wouldnt mind only bears and giants for a whole run 
I dont know what you are talking about, but i see a spellbinder or mage in almost every pull in waves 2-4 on threatening.
Thats not enough for a faction straight outta Tevinter. More mages rawr!
Thats not good lol i am waiting to play my ele still lol
I have noted in my thread two things lol
One why would animals work with demons of all things?
Can we get an option to turn off the dlc but still play with people who want it. Meaning in the lobby when you create a match have a check list with the dlcs and choose what ones to use because the destruction dlc is really bad. Btw i am a huge fan of Bioware and i think the destruction dlc is the worst thing they have ever made and should just be removed all together lol.
In the story demons possessed black wolves so it might work for other stuff as well.
Played a few games. Key always dropped despite fire storms and animals. Sometimes, you need to wait or open a treasure room and kill guardians there. But eventually it dropped. DC is quite timid apart from playing with hosts who did not patch yet. A big difference actually. Also, a lot of reavers were dieing out there today. I think the whole class got some disease or something. Have not seen the new map layout. Must have been fabulous. Pots mostly behaved but one in ten occasionally did not want to break to melee although ranged worked fine.
Key bug seems pretty much gone now or I was just lucky. Had a Elementalist spam firestorm the whole time for the 5 waves. No key bug. Now using my elementalist so we'll see if the bug happens.
Key bug seems pretty much gone now or I was just lucky. Had a Elementalist spam firestorm the whole time for the 5 waves. No key bug. Now using my elementalist so we'll see if the bug happens.
Actually, I think we played two or three games together today. Where is bump in the BSNers thread?
That's an old bug. An annoying one at that. Renders game unplayable. No way to bypass that except leave game, and make/join another.
You could fix if you had a team of friends and it was set to private allowing you to rejoin as that would reset the map, but you are quite correct on the part of rendering it unplayable otherwise.
I'm convinced that their QA team is non-existent.
also, about the ravager nerf...WTF? because she needed to be more squishy?
were you thinking: "oh hey instead of buffing the Katari, why don't we nerf the **** out of the ravager, you know, so she'll be equally useless"
Oh but if you listen to a certain "dev who shall not be named" (don't want another post being deleted because I just call someone out on a statement they made which was false) EAWare has one of the best QA teams in the industry. Either they meant us, the player base which would work if they actually listened, or the QA team which they had job openings for at EAWare just after the game launched, and last I checked a few days ago had openings for multiplayer game testers (cant help but wonder if said QA team got canned for some reason).
People keep saying the AW has high survivability as though it's the "unbalancing" thing... but everyone has high survivability. It's not a design flaw if you're in a group where nobody is controlling agro, or casting barrier, or you pull agro from 4 archers standing in the open without a barrier when you're a reaver.
As for the AW you would be slightly wrong, yes the AW is squishy in a sense but if you set the character up properly you don't die. I soloed the DC several times on Perilous before this "patch". Did the reaver need a nerf like this with rampage? Absolutely not. I stated before any "patches" were released and noticed the rampage bug myself that it was going to end up being like the shockwave skill on ME3MP where they attempted to fix it multiple times and finally gave up leaving the skill broken since release. Someone mentioned making dragon rage heal less than normal when rampage was up and I could see this being a viable compromise as opposed to stating in the patch notes that they addressed the issue with it not healing. This still doesn't explain why the skill still has the tool tip stating that you heal while using it (rampage). If they changed it as they did then change the bloody tool tip so people understand what it does and how it works so that they can plan accordingly.
It was quite hiralious yesterday...ALOT reavers joined my games. The fun watching them suck really made for the wipes we had 
You're kind of using what's exactly my point as though you're refuting it...
The game is clearly designed for teams of 4, ideally (by design) with at least one of each base class in the team.
People keep saying the AW has high survivability as though it's the "unbalancing" thing... but everyone has high survivability. It's not a design flaw if you're in a group where nobody is controlling agro, or casting barrier, or you pull agro from 4 archers standing in the open without a barrier when you're a reaver. It's also not overpowered that an AW can solo Perilous when a group of 4 can do it in half the time or less and they all get the same reward (more if they do all the rooms)
If everyone has high survivabily (in a decent team, which isn't hard to find even while PUG-ing), then is the class that does arguably the highest damage in the game, or the one that does "above average" damage likely to get nerfed first?
Personally I rate AW damage as average at best, but that's a different discussion.
I'd argue that every Rogue and Warrior class in this game needs HoK more than a Reaver does - the fact that a Reaver has Rampage and Devour actually makes it one of the few classes that doesn't need HoK, and the only class with significant heal on hit (except for the psuedo heal on hit that the AW has)
Are you typing this garbage with a straight face? If so Bravoooo!!
I see you must have already read my guide for AWs but here it is - http://forum.bioware...-solo-perilous/
You're kind of using what's exactly my point as though you're refuting it...
The game is clearly designed for teams of 4, ideally (by design) with at least one of each base class in the team.
People keep saying the AW has high survivability as though it's the "unbalancing" thing... but everyone has high survivability. It's not a design flaw if you're in a group where nobody is controlling agro, or casting barrier, or you pull agro from 4 archers standing in the open without a barrier when you're a reaver. It's also not overpowered that an AW can solo Perilous when a group of 4 can do it in half the time or less and they all get the same reward (more if they do all the rooms)
If everyone has high survivabily (in a decent team, which isn't hard to find even while PUG-ing), then is the class that does arguably the highest damage in the game, or the one that does "above average" damage likely to get nerfed first?
Personally I rate AW damage as average at best, but that's a different discussion.
comparing reaver and AW and focusing soloely on damage and saying reaver needs nerf is no different then if I compared AW and reaver and focused solely on survivability and said reaver needs major buffs. Other classes can help reaver and AW in both surviving more and party damage. You have to consider the entire package that the character brings to a game. Also, people die in pugs on perilous all the time, I know because I have played a lot of pugs. You can't depend on random people to barrier you every time you run in on reaver or a random tank to have counterstrike up to pull aggro off you. People will die in your party, and if you are in perilous, often times will wipe, even with a good party classes. The difference then is, if I play AW it doesn't matter what anyone else is or does. whether they are good or not, because i can just close my eyes and solo the match if they all wipe.
I have yet to see the pots bug happen again, still haven't lost a key again but I've encountered a bug that would not let me move at all, which I'm not sure if is new or not but I could not move unless I used leaping shot.
Same here. Have to do an attack first before being able to move again.
Bioware pls!
Stop deleting posts. You are ruining my entertainment!
I'd argue that every Rogue and Warrior class in this game needs HoK more than a Reaver does - the fact that a Reaver has Rampage and Devour actually makes it one of the few classes that doesn't need HoK, and the only class with significant heal on hit (except for the psuedo heal on hit that the AW has)
Except that normally you spam dragon rage, not auto attack. Having to spam auto attack when using rampage to get healed significantly lowers your damage. So you either spam dragon rage and die because the only heal you have is devour, or you spam auto attack and do terrible damage. Before the patch you would have been right, we didn't need HoK. Now we do. So if you dont have one, good luck.
As for the AW you would be slightly wrong, yes the AW is squishy in a sense but if you set the character up properly you don't die.
I think you missed the part where I said the AW is basically unkillable. I just don't care because every class is basically unkillable if you play it as part of a decent 4 player team.
comparing reaver and AW and focusing soloely on damage and saying reaver needs nerf is no different then if I compared AW and reaver and focused solely on survivability and said reaver needs major buffs.
How do you interpret my post to compare the two solely on damage? My entire post except the last couple of lines is about comparing survivability.
It seems to me the difference between the way you look at it is you focus on a team falling apart and the AW having epic survivability and the Reaver having poor survivability. While I focus on a team working well together, where a Reaver and an AW have the same survivability in the only sense that matters - they're standing next to the flag at the end of the run.
When I look at what a class bring to a team, as you sayt, I look at the actual objective of the run:
Since the ultimate objective is solely to kill everything ASAP, damage is super important, with "Utility" simply increasing the survivability of the team and buying you extra time to do all that damage.
If survivability for the team is taken care of by your class composition, skill, whatever, all that matters is damage. Your own 4 Archer perilous run supports what I'm saying - doing so much damage that everything is dead before it can kill you "takes care" of survivability.
"Balancing" is almost always dev-speak for, "We think you're getting rewards too fast". Expect more nerfs to damage dealers.
Except that normally you spam dragon rage, not auto attack. Having to spam auto attack when using rampage to get healed significantly lowers your damage. So you either spam dragon rage and die because the only heal you have is devour, or you spam auto attack and do terrible damage. Before the patch you would have been right, we didn't need HoK. Now we do. So if you dont have one, good luck.
You need HoK to spam Dragon Rage non-stop, but you don't need to mindlessly spam Dragon Rage non-stop to play Reaver... Are you actually saying you think one button is a more fun class?
Patch the patch.
itt: PR disasters, post deletions, and a pretty large outcry from the DAMP community. Most of my friends in the perilous circuit and on the leaderboards are quitting or taking a break until there is some better news.
This sentiment is simple, but poignant, and I agree. Patch the patch.
Retour en haut
