159 réponses à ce sujet

[lavatsunami]

Atheosis 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. 

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

Then change them, Mr I know the inner workings of how Bioware develops software. 

[aquamutt]

'You can and you can't-You shall and you shan't-You will and you won't-And you will be damned if you do-And you will be damned if you don't.'

no matter what you do bioware

[Chealec]

lavatsunami wrote...

Atheosis 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. 

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

Then change them, Mr I know the inner workings of how Bioware develops software. 

It's not hard to change them on the PC - but it's otherwise known as modding the lobby or hacking which is generally frowned upon for some reason

[Avl521]

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. 

That's not really the point. Even if what you are saying was right and when it was created version 1.01234578787834 was used instead of 1.0224578787835 which explains why it has pre buff stats, the fact that they didn't test it to notice the defect means they didn't fix a mistake that required NO programming skills to be noticed. One would also expect that with an extra day delay things would have been double checked.
You can make the mistake, but it's YOUR JOB to fix it. Specially if it's something as basic as getting to the build and noticing the numbers in the stats of the power are wrong. Delay it again, but don't release broken/buggy things. This goes for the Batarian as well.

[Liefglinde]

lavatsunami wrote...

Liefglinde wrote...

lavatsunami wrote...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. 

Your argument is not relevant to the discussion at hand. In addition, it appears that you are the one with the "one dimensional thinking."

This game is not just code. There is the code, which the developers see, and then the game, which is the product of the code the devlopers create. The developers simply cannot only work with the code portion; if they do that without checking the in game portions as well, they are failing to test the code they worked on. My point still stands - no amount of magic strings of numbers provides an excuse for why this issue was not found and resolved.

[aquamutt]

Avl521 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. 

That's not really the point. Even if what you are saying was right and when it was created version 1.01234578787834 was used instead of 1.0224578787835 which explains why it has pre buff stats, the fact that they didn't test it to notice the defect means they didn't fix a mistake that required NO programming skills to be noticed. One would also expect that with an extra day delay things would have been double checked.
You can make the mistake, but it's YOUR JOB to fix it. Specially if it's something as basic as getting to the build and noticing the numbers in the stats of the power are wrong. Delay it again, but don't release broken/buggy things. This goes for the Batarian as well.

and eric posted it will be addressed in next weeks balance changes

what is the problem?

[N7 ElusiveOne]

Surprisingly negative thread considering the quality of the character in question. Did anyone really want to play this character? Incinerate is good but it's on so many kits already, and Submission net is the most dodged ability in the game. Just promote your engineers and enjoy the free exp from unlocking the hunter.

[Geimhreadh]

aquamutt wrote...

Avl521 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. 

That's not really the point. Even if what you are saying was right and when it was created version 1.01234578787834 was used instead of 1.0224578787835 which explains why it has pre buff stats, the fact that they didn't test it to notice the defect means they didn't fix a mistake that required NO programming skills to be noticed. One would also expect that with an extra day delay things would have been double checked.
You can make the mistake, but it's YOUR JOB to fix it. Specially if it's something as basic as getting to the build and noticing the numbers in the stats of the power are wrong. Delay it again, but don't release broken/buggy things. This goes for the Batarian as well.

and eric posted it will be addressed in next weeks balance changes

what is the problem?

Apparently choosing to release a buggy kit now and fix it later is up there with kicking puppies and eating babies.

[Tipsyfresh]

xassantex wrote...

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

oy.  I'm surely not.

[Boog_89]

Unbelievable, what a crazy oversight
Almost a pointless balance update considering there's a glitched character and no weapon/power changes.

[MetalDeggial]

They don't even playtest or just look at these things? Geez. And the rest of the balance changes are just pointless, sans the Turian Soldier wave points fix, which drove me crazy with the notifications. No buffs to the Disciple, CSMG, CAR, Hornet and Typhoon?

I was seriously looking into the Vorcha Engineer, cuz I really dig Submission Net, but this is just unacceptable.

[lavatsunami]

Liefglinde wrote...

lavatsunami wrote...

Liefglinde wrote...

lavatsunami wrote...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. 

Your argument is not relevant to the discussion at hand. In addition, it appears that you are the one with the "one dimensional thinking."

This game is not just code. There is the code, which the developers see, and then the game, which is the product of the code the devlopers create. The developers simply cannot only work with the code portion; if they do that without checking the in game portions as well, they are failing to test the code they worked on. My point still stands - no amount of magic strings of numbers provides an excuse for why this issue was not found and resolved.

Do you program for a living? 

[Super Nothing]

ASmoothCriminalx wrote...

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.

The class was finished before the patch was ever released.  All of the power sets for the new classes were posted to the manifest soon after the patch was released.  They're not currently doing anything to the new classes, they're just waiting to add them to the store.  This error has been sitting there unnoticed this whole time.

Modifié par Super Nothing, 14 novembre 2012 - 08:49 .

[jpraelster93]

Super Nothing wrote...

ASmoothCriminalx wrote...

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.

The class was finished before the patch was ever released.  All of the power sets for the new classes were posted to the manifest soon after the patch was released.  They're not currently doing anything to the new classes, they're just waiting to add them to the store.  This error has been sitting there unnoticed this whole time.

But why

[DeadeyeCYclops]

oh well i saved my 300k and got all his appearances unlocked, and also got a CSMG upgrades to lvl 2, glad i got a weapon upgrade at least Honestly i have not looked at any spoilers for the characters and i am disappointed there are no new powers just jumbles of old powers... but at this stage of the game, really i guess expecting somethin new is a lil much....

as for putting the old subnet on him... meh its and oversight, **** happens, it sux we gotta wait an entire week b4 it gets fixed but hey at least next week we will have   a psuedo 2 new char week, since not many ppl want to play the new vorcha with his old net

Modifié par DeadeyeCYclops78, 14 novembre 2012 - 08:56 .

[lavatsunami]

For what it's worth Bioware, YOUR GAME IS AWESOME. All caps means it's true.

[Relix28]

Annomander wrote...

Well, who the jesus-f*ck was actually going to spec into submission net anyway?

Even the post buff version has huge targetting problems, does very little damage, is too easily dodged, only primes TBs if it actually incapacitates.... so can't prime armoured.... etc

Take 3 points in submission net if you must; its not worth the 21 points for tech bursts though.

Not only you are acting like a jerkbag for no apparent reason, you are also talking out of your ass. Submission Net will always prime armored targets (shielded or unshielded), and unlike most other electric primers, the prime duration will stay active for as long as the DoT lasts (7.8 seconds).

[Super Nothing]

jpraelster93 wrote...

Super Nothing wrote...

ASmoothCriminalx wrote...

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.

The class was finished before the patch was ever released.  All of the power sets for the new classes were posted to the manifest soon after the patch was released.  They're not currently doing anything to the new classes, they're just waiting to add them to the store.  This error has been sitting there unnoticed this whole time.

But why

No/Poor quality testing. 

[DJ Airsurfer]

aquamutt wrote...
and eric posted it will be addressed in next weeks balance changes

what is the problem?

1. Delayed and (somewhat mediocre update) yet broken character with already mediocre skillset.
2. Next week.

[Avl521]

DJ Airsurfer wrote...

aquamutt wrote...
and eric posted it will be addressed in next weeks balance changes

what is the problem?

1. Delayed and (somewhat mediocre update) yet broken character with already mediocre skillset.
2. Next week.

This.

[aquamutt]

Avl521 wrote...

DJ Airsurfer wrote...

aquamutt wrote...
and eric posted it will be addressed in next weeks balance changes

what is the problem?

1. Delayed and (somewhat mediocre update) yet broken character with already mediocre skillset.
2. Next week.

This.

yes next week is so far away

how will any of us survie with this 1 kit being bugged for a whole week?

[APEX KING19]

they should have gave it flamer instead of incinerate. stop them dead with sub net then burn them to death with flamer would have been a good combo to be honest

[Blike]

Eric Fagnan wrote...

We will address this with next week's changes.

youre joking, right? One thing is releasing a character with a broken power BECAUSE YOU COPIED THE WEONG ONE, another thing is waiting a full week to fixing something that simple. 
Honestly, that's disappointing.

[jpraelster93]

aquamutt wrote...

Avl521 wrote...

DJ Airsurfer wrote...

aquamutt wrote...
and eric posted it will be addressed in next weeks balance changes

what is the problem?

1. Delayed and (somewhat mediocre update) yet broken character with already mediocre skillset.
2. Next week.

This.

yes next week is so far away

how will any of us survie with this 1 kit being bugged for a whole week?

Im not even gonna wanna use it next week

[Liefglinde]

lavatsunami wrote...

Liefglinde wrote...

lavatsunami wrote...

Liefglinde wrote...

lavatsunami wrote...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. 

Your argument is not relevant to the discussion at hand. In addition, it appears that you are the one with the "one dimensional thinking."

This game is not just code. There is the code, which the developers see, and then the game, which is the product of the code the devlopers create. The developers simply cannot only work with the code portion; if they do that without checking the in game portions as well, they are failing to test the code they worked on. My point still stands - no amount of magic strings of numbers provides an excuse for why this issue was not found and resolved.

Do you program for a living? 

For the third time, that is not relevant to the point at hand.