159 réponses à ce sujet

[DJ Airsurfer]

Eric Fagnan wrote...

We will address this with next week's changes.

While you're at it, buff SubNet. This new character is inferior to the other two Vorcha in every aspect.

[Loscakes]

QA much? I mean, it's right there on the powers screen. This is seriously embarrassing.

[Airealite]

*sigh*

Good thing I didn't spend time saving up credits to try and get this guy

[Kalas Magnus]

Eric Fagnan wrote...

We will address this with next week's changes.

Can you also buff submission net so the hunter is worth playing?

[DJ Airsurfer]

Kalas321 wrote...

Eric Fagnan wrote...
We will address this with next week's changes.

Can you also buff submission net so the hunter and Batarian Sentinel are worth playing?

Fixed.

[Atheosis]

Yet more proof that Retaliation characters aren't even tested before release. This is a mistake that most veteran players on this board would've caught before playing a single game. Kind of sad really.

[Kalas Magnus]

DJ Airsurfer wrote...

Kalas321 wrote...

Eric Fagnan wrote...
We will address this with next week's changes.

Can you also buff submission net so the hunter and Batarian Sentinel are worth playing?

Fixed.

Good job. I had forgotten he was in the game.

[Elotana]

lavatsunami wrote...

How many of you idiots actually program?

No programming knowledge was required to catch this bug. Sheer laziness.

[Tipsyfresh]

mrcanada wrote...

Honestly, all the people that sit there and say they have to test things etc, here is just another reason on how these characters are simply after birth in the design department. Copy and paste skinning just sucks, Batarians receiving human voices weird charge evolution ommisions and blade armor not working properly on gold and above and now this.............You'd think that would be the first thing checked!!

Indeed. I mean i don't even know a thing about that kinda stuff but it just seems logical, esp with all the talk of "it takes time" and "you don't know how they do things"

[Liefglinde]

Tallgeese_VII wrote...

Liefglinde wrote...

WMcAlister wrote...

Liefglinde wrote...

Chealec wrote...

mrcanada wrote...

Thing is, the community catches the mistake in under 5 minutes. Says something.

Yeah - shows there are several hundred thousand of us and what, maybe 20 Devs and QA peeps at BW working on MP?

It was a simple matter of actually looking at the numbers and not copypasting and calling it a day. Of those several hundred thousand of us, how many of those do you think got the new kit in the first 5 minutes? Not nearly that many. And yet the bug was found.

More than 20.  Lots more.

Point is we're not professionals. We didn't spend a week (read: 30 seconds, as it appears) coming up with this character. We didn't design this character. And yet players found a glaring issue in a matter of minutes.

There's a difference between a gameplay bug and a bug that is sitting there and staring you in the face. There is absolutely no excuse as to why this bug was not found and corrected.

Similar thing goes to Krysae & Typhoon.
Although they were not BUGs, introducint pre-nerf Krysae after nerfing Falcon was pretty @#$@.
Typhoon with 2x damage multiplier + 1m penetration.. too good? I guess it was.

These things didn`t even realy had to be tested. They were in right front of your face asking to be fixed.

Even then there's still a difference. There's no in game number showing you that the Typhoon had those multipliers or that penetration. The Submission net's in game numbers CLEARLY show that it's the pre-buff ability. That's the problem here.

[lavatsunami]

Elotana wrote...

lavatsunami wrote...

How many of you idiots actually program?

No programming knowledge was required to catch this bug. Sheer laziness.

No, programming was required to build it.  Lol.  Daft much?

[Atheosis]

lavatsunami wrote...

Elotana wrote...

lavatsunami wrote...

How many of you idiots actually program?

No programming knowledge was required to catch this bug. Sheer laziness.

No, programming was required to build it.  Lol.  Daft much?

No programming knowledge was required to test it and see it has a pre-buff garbage power.  Come on now.

[BartoszJ91]

To those asking for immediate fix: The devs have already stated, that it's too complicated to make changes twice a week. That's also the reason why we're not getting new characters on tuesday and changes on wednesday when there is delay.

[DJ Airsurfer]

Stardusk wrote...

Great, was actually looking forward to this guy and now I have to wait a week. Brilliant. What is the point of delaying stuff and then bringing it out broken?! Seriously...

[Liefglinde]

BartoshOsiek wrote...

To those asking for immediate fix: The devs have already stated, that it's too complicated to make changes twice a week. That's also the reason why we're not getting new characters on tuesday and changes on wednesday when there is delay.

Quite frankly, I don't care how complicated it is. A glaring mistake was made, and it should be fixed.

If that sounds harsh, that's because it is. I can't understand how people find it acceptable that a company that is doing their job can mess up so much. In nearly any other profession, no one is going to accept the excuse that "oh well it's too complicated so even though i made a mistake I'll fix it in a week." So why is that accepted here?

[ASmoothCriminalx]

I'm sure the balance changes were delayed because they were working on the finishing touches of this class.. it probably wasn't that they were actually working on the things that were changing rather than preparing to release a character who had already been finished a month or two.

[lavatsunami]

Atheosis wrote...

lavatsunami wrote...

Elotana wrote...

lavatsunami wrote...

How many of you idiots actually program?

No programming knowledge was required to catch this bug. Sheer laziness.

No, programming was required to build it.  Lol.  Daft much?

No programming knowledge was required to test it and see it has a pre-buff garbage power.  Come on now.

That's not really the point.  The point is that trying to make even minor changes quickly in a programming environment causes mistakes.  Maybe when it was tested version 1.01234578787834 was used instead of 1.0224578787835.  Unless you're a programmer, unless you understand a programming environment, be quiet.  And if you are, you probably won't whine about it, because you understand how it works.  On top of that, you should probably stop whining anyway, because it's annoying.  And yes, whining about whining counts, which includes my post. 

If Bioware tried to explain even a quarter of what some of these changes entail, about 95% of people in these forums brains would explode. 

Modifié par lavatsunami, 14 novembre 2012 - 08:16 .

[xassantex]

no , they figured no one would play this character anyway so it didn't matter.

[Atheosis]

Liefglinde wrote...

BartoshOsiek wrote...

To those asking for immediate fix: The devs have already stated, that it's too complicated to make changes twice a week. That's also the reason why we're not getting new characters on tuesday and changes on wednesday when there is delay.

Quite frankly, I don't care how complicated it is. A glaring mistake was made, and it should be fixed.

If that sounds harsh, that's because it is. I can't understand how people find it acceptable that a company that is doing their job can mess up so much. In nearly any other profession, no one is going to accept the excuse that "oh well it's too complicated so even though i made a mistake I'll fix it in a week." So why is that accepted here?

Indeed.  I love ME3 MP, but since release it's been a never-ending stream of broken and buggy content that often takes months to fix.  The entire thing has felt like a beta from the start, and it's kind of sad really.

[Liefglinde]

lavatsunami wrote...

Atheosis wrote...

lavatsunami wrote...

Elotana wrote...

lavatsunami wrote...

How many of you idiots actually program?

No programming knowledge was required to catch this bug. Sheer laziness.

No, programming was required to build it.  Lol.  Daft much?

No programming knowledge was required to test it and see it has a pre-buff garbage power.  Come on now.

That's not really the point.  The point is that trying to make even minor changes quickly in a programming environment causes mistakes.  Maybe when it was tested version 1.01234578787834 was used instead of 1.0224578787835.  Unless you're a programmer, unless you understand a programming environment, be quiet.  And if you are, you probably won't whine about it, because you understand how it works.  On top of that, you should probably stop whining anyway, because it's annoying.  And yes, whining about whining counts, which includes my post. 

If Bioware tried to explain even a quarter of what some of these changes entail, about 95% of people in these forums brains would explode. 

This is all irrelevant. No amount of programming is needed to go into the game screen and see the stats for the power listed in plain sight. No magic strings of numbers of codes or starchildren are necessary to see that the stats for the power are not right. Therefore, this was never tested.

[Atheosis]

lavatsunami wrote...

Atheosis wrote...

lavatsunami wrote...

Elotana wrote...

lavatsunami wrote...

How many of you idiots actually program?

No programming knowledge was required to catch this bug. Sheer laziness.

No, programming was required to build it.  Lol.  Daft much?

No programming knowledge was required to test it and see it has a pre-buff garbage power.  Come on now.

That's not really the point.  The point is that trying to make even minor changes quickly in a programming environment causes mistakes.  Maybe when it was tested version 1.01234578787834 was used instead of 1.0224578787835.  Unless you're a programmer, unless you understand a programming environment, be quiet.  And if you are, you probably won't whine about it, because you understand how it works.  On top of that, you should probably stop whining anyway, because it's annoying.  And yes, whining about whining counts, which includes my post. 

If Bioware tried to explain even a quarter of what some of these changes entail, about 95% of people in these forums brains would explode. 

These values can actually be adjusted relatively easily in the .ini files.  You're barking up the wrong tree I'm afraid.

[DJ Airsurfer]

Atheosis wrote...

Liefglinde wrote...

BartoshOsiek wrote...

To those asking for immediate fix: The devs have already stated, that it's too complicated to make changes twice a week. That's also the reason why we're not getting new characters on tuesday and changes on wednesday when there is delay.

Quite frankly, I don't care how complicated it is. A glaring mistake was made, and it should be fixed.

If that sounds harsh, that's because it is. I can't understand how people find it acceptable that a company that is doing their job can mess up so much. In nearly any other profession, no one is going to accept the excuse that "oh well it's too complicated so even though i made a mistake I'll fix it in a week." So why is that accepted here?

Indeed.  I love ME3 MP, but since release it's been a never-ending stream of broken and buggy content that often takes months to fix.  The entire thing has felt like a beta from the start, and it's kind of sad really.

This. Not only was it delayed, but we got a broken character who had a sh*tty skillset to begin with.

[lavatsunami]

Liefglinde wrote...

lavatsunami wrote...

Atheosis wrote...

lavatsunami wrote...

Elotana wrote...

lavatsunami wrote...

How many of you idiots actually program?

No programming knowledge was required to catch this bug. Sheer laziness.

No, programming was required to build it.  Lol.  Daft much?

No programming knowledge was required to test it and see it has a pre-buff garbage power.  Come on now.

That's not really the point.  The point is that trying to make even minor changes quickly in a programming environment causes mistakes.  Maybe when it was tested version 1.01234578787834 was used instead of 1.0224578787835.  Unless you're a programmer, unless you understand a programming environment, be quiet.  And if you are, you probably won't whine about it, because you understand how it works.  On top of that, you should probably stop whining anyway, because it's annoying.  And yes, whining about whining counts, which includes my post. 

If Bioware tried to explain even a quarter of what some of these changes entail, about 95% of people in these forums brains would explode. 

This is all irrelevant. No amount of programming is needed to go into the game screen and see the stats for the power listed in plain sight. No magic strings of numbers of codes or starchildren are necessary to see that the stats for the power are not right. Therefore, this was never tested.

your one dimensional thinking fails you. 

[SaintTweeter]

All his dev complaining aside, this character was already shunned before release, but now its has been cursed forever by this mistake. Even after its fixed, people will have a very negative outlook on this and likely instakick on sight.

Death by awful first impression.

[Chealec]

I'm not saying it shouldn't have been caught - it should. All it would take would be for 1 QA professional to be on the ball... I don't know how big BioWare's current QA team is, or even if it has a dedicated team for MP - so I can understand how it might have been overlooked.

As as aside, programmers generally make poor QA testers; especially on their own programs as they tend to look for underlying problems in the code that cause bugs or glitches, they tend to know how the program functions and how to break it... they tend to miss glaringly obvious real world issues simply because they're not looking for them.

I know, I have to QA my own code but I send it out to the people that are going to be using it almost as soon as it's functional (not polished, but functional) as I've found in the past that the way I envision the program to be used isn't necessarily the way the people that are using it want to use it. Not really an option when you've got to punt everything out through XBL or PSN.