I don't memorize such things :]Lord_Sirian wrote...
LOL. You forget I've played with you...
not easy, but the easiest among all other projectilesLord_Sirian wrote...
Prime shots aren't easy to dodge at all
Modifié par sareth_65536, 08 novembre 2012 - 01:28 .
Guest_Lord_Sirian_*
ahmadsamad wrote...
Lord_Sirian wrote...
count_4 wrote...
Working as intended as far as I know.Lord_Sirian wrote...
count_4 wrote...
Well, to be honest there are only two bugs I can think of and one is more of a visual glitch. Bugginess is indeed not that much of a problem regarding the Geth.Charaxan wrote...
KalilKareem wrote...
Geth aint buggy.
Sorry, I lost you there.
Geth Hunter shooting when it shouldn't be able to bug
And I'm not saying they aren't bugged, just that (the very few) bugs are not their main problem.
Yeah, anything the dev's are too lazy to fix = working as intended.
Hunters shouldn't be able to shoot while staggered, or frozen, or in stasis, or on the floor. That's not working as intended, that's lazy dev's bucking responsibility.
And I swear if you come the 'it's because the GPS is a charge-up weapon' excuse with me I'm just going to ignore every single one of your posts from now on. Because Hunters don't just shoot WHEN they get staggered, they shoot when they get staggered, then before the animation has finished, they shoot again. I've had one shoot me while it was flying through the air after being lashed by a Cerberus Adept. (It had just flown across the map, basically)
They sure are lazy after two great patch. Stop insulting the devs
Guest_Lord_Sirian_*
sareth_65536 wrote...
I don't memorize such things :]Lord_Sirian wrote...
LOL. You forget I've played with you...not easy, but the easiest among all other projectilesLord_Sirian wrote...
Prime shots aren't easy to dodge at all
Lord_Sirian wrote...
ryanshowseason3 wrote...
You've completely misunderstood the process in which this happened.
Pre patch the combat drone was broken. It couldn't do anything. It literally floated around and wasted the prime's time by casting it... The patch fixed it so no there was not a conscious decision to "add more stunlock" they were just fixing something that was broken in the first place. It was always supposed to be like this.
I agree that geth stunlock is not enjoyable but there was no concscious decision to add more, it was a bug fix.
Then Bioware should've considered the repercussions before fixing said bug, and changed the way the Drone interacted in the same patch instead of just KNOWINGLY adding more stunlock (albeit indirectly).
Omission and action are equal in this situation.
Xeonzs wrote...
So how about you make a nice vid about this "stunlock" you mention, just a 1 or a few matches against geth?
Let's see if you can actually point it out or if you just fail okay?
Guest_Lord_Sirian_*
ryanshowseason3 wrote...
Lord_Sirian wrote...
ryanshowseason3 wrote...
You've completely misunderstood the process in which this happened.
Pre patch the combat drone was broken. It couldn't do anything. It literally floated around and wasted the prime's time by casting it... The patch fixed it so no there was not a conscious decision to "add more stunlock" they were just fixing something that was broken in the first place. It was always supposed to be like this.
I agree that geth stunlock is not enjoyable but there was no concscious decision to add more, it was a bug fix.
Then Bioware should've considered the repercussions before fixing said bug, and changed the way the Drone interacted in the same patch instead of just KNOWINGLY adding more stunlock (albeit indirectly).
Omission and action are equal in this situation.
The other option being to leave the geth prime wasting its time spawning a unit that did literally nothing?
Honestly I do not blame them.
Fixing the bug was the right thing to do. Changing the difficulty in defeating the geth is in the responsibility of balance changes. *NOT* the realm of bug fixes. Different tasks entirely. Just like adding dragoons was the job of the dlc and bringing them in line with difficulty was balance change territory.
The state of the rest of the geth is completely irrelevant to fixing bugs.
Even if the description says the drone is an attack drone, it could have been a defense drone, zapping (without stagger of course) anything coming too close to it.ryanshowseason3 wrote...
The other option being to leave the geth prime wasting its time spawning a unit that did literally nothing?
Honestly I do not blame them.
Fixing the bug was the right thing to do. Changing the difficulty in defeating the geth is in the responsibility of balance changes. *NOT* the realm of bug fixes. Different tasks entirely. Just like adding dragoons was the job of the dlc and bringing them in line with difficulty was balance change territory.
The state of the rest of the geth is completely irrelevant to fixing bugs.
Weeeeeell, you're just freezing/staggering/whatevering the Hunter, not the GPS which is basically a separate Geth unit. It's perfectly reasonable that the weapon is able to aim and fire itself if the wielder is incapacitated. All you need are some steering nozzles and a fire-by-wire trigger...Lord_Sirian wrote...
count_4 wrote...
Working as intended as far as I know.Lord_Sirian wrote...
count_4 wrote...
Well, to be honest there are only two bugs I can think of and one is more of a visual glitch. Bugginess is indeed not that much of a problem regarding the Geth.Charaxan wrote...
KalilKareem wrote...
Geth aint buggy.
Sorry, I lost you there.
Geth Hunter shooting when it shouldn't be able to bug
And I'm not saying they aren't bugged, just that (the very few) bugs are not their main problem.
Yeah, anything the dev's are too lazy to fix = working as intended.
Hunters shouldn't be able to shoot while staggered, or frozen, or in stasis, or on the floor. That's not working as intended, that's lazy dev's bucking responsibility.
And I swear if you come the 'it's because the GPS is a charge-up weapon' excuse with me I'm just going to ignore every single one of your posts from now on. Because Hunters don't just shoot WHEN they get staggered, they shoot when they get staggered, then before the animation has finished, they shoot again.
Modifié par count_4, 08 novembre 2012 - 01:41 .
Guest_Lord_Sirian_*
count_4 wrote...
Weeeeeell, you're just freezing the Hunter, not the GPS which is basically a separate Geth unit. It's perfectly reasonable that the weapon is able to aim and fire itself if the wielder is incapacitated. All you need are some steering nozzles and a fire-by-wire trigger...Lord_Sirian wrote...
count_4 wrote...
Working as intended as far as I know.Lord_Sirian wrote...
count_4 wrote...
Well, to be honest there are only two bugs I can think of and one is more of a visual glitch. Bugginess is indeed not that much of a problem regarding the Geth.Charaxan wrote...
KalilKareem wrote...
Geth aint buggy.
Sorry, I lost you there.
Geth Hunter shooting when it shouldn't be able to bug
And I'm not saying they aren't bugged, just that (the very few) bugs are not their main problem.
Yeah, anything the dev's are too lazy to fix = working as intended.
Hunters shouldn't be able to shoot while staggered, or frozen, or in stasis, or on the floor. That's not working as intended, that's lazy dev's bucking responsibility.
And I swear if you come the 'it's because the GPS is a charge-up weapon' excuse with me I'm just going to ignore every single one of your posts from now on. Because Hunters don't just shoot WHEN they get staggered, they shoot when they get staggered, then before the animation has finished, they shoot again.
<.<
>.>
:innocent:
By the way, I really like the survivability calculator in your sig... nice work on that. 
count_4 wrote...
Weeeeeell, you're just freezing the Hunter, not the GPS which is basically a separate Geth unit. It's perfectly reasonable that the weapon is able to aim and fire itself if the wielder is incapacitated. All you need are some steering nozzles and a fire-by-wire trigger...Lord_Sirian wrote...
count_4 wrote...
Working as intended as far as I know.Lord_Sirian wrote...
count_4 wrote...
Well, to be honest there are only two bugs I can think of and one is more of a visual glitch. Bugginess is indeed not that much of a problem regarding the Geth.Charaxan wrote...
KalilKareem wrote...
Geth aint buggy.
Sorry, I lost you there.
Geth Hunter shooting when it shouldn't be able to bug
And I'm not saying they aren't bugged, just that (the very few) bugs are not their main problem.
Yeah, anything the dev's are too lazy to fix = working as intended.
Hunters shouldn't be able to shoot while staggered, or frozen, or in stasis, or on the floor. That's not working as intended, that's lazy dev's bucking responsibility.
And I swear if you come the 'it's because the GPS is a charge-up weapon' excuse with me I'm just going to ignore every single one of your posts from now on. Because Hunters don't just shoot WHEN they get staggered, they shoot when they get staggered, then before the animation has finished, they shoot again.
<.<
>.>
:innocent:
Cohen le Barbare wrote...
Even if the description says the drone is an attack drone, it could have been a defense drone, zapping (without stagger of course) anything coming too close to it.ryanshowseason3 wrote...
The other option being to leave the geth prime wasting its time spawning a unit that did literally nothing?
Honestly I do not blame them.
Fixing the bug was the right thing to do. Changing the difficulty in defeating the geth is in the responsibility of balance changes. *NOT* the realm of bug fixes. Different tasks entirely. Just like adding dragoons was the job of the dlc and bringing them in line with difficulty was balance change territory.
The state of the rest of the geth is completely irrelevant to fixing bugs.
lol. I'll just left it here.Lord_Sirian wrote...
Well let's just say there was a major gap between our scores, and you scored worst when we played games against Geth IIRC.
Thanks.Lord_Sirian wrote...
Guest_Lord_Sirian_*
sareth_65536 wrote...
lol. I'll just left it here.Lord_Sirian wrote...
Well let's just say there was a major gap between our scores, and you scored worst when we played games against Geth IIRC.
If you aren't lieing how come your are whining while I'm not?
Lord_Sirian wrote...
ryanshowseason3 wrote...
Lord_Sirian wrote...
ryanshowseason3 wrote...
You've completely misunderstood the process in which this happened.
Pre patch the combat drone was broken. It couldn't do anything. It literally floated around and wasted the prime's time by casting it... The patch fixed it so no there was not a conscious decision to "add more stunlock" they were just fixing something that was broken in the first place. It was always supposed to be like this.
I agree that geth stunlock is not enjoyable but there was no concscious decision to add more, it was a bug fix.
Then Bioware should've considered the repercussions before fixing said bug, and changed the way the Drone interacted in the same patch instead of just KNOWINGLY adding more stunlock (albeit indirectly).
Omission and action are equal in this situation.
The other option being to leave the geth prime wasting its time spawning a unit that did literally nothing?
Honestly I do not blame them.
Fixing the bug was the right thing to do. Changing the difficulty in defeating the geth is in the responsibility of balance changes. *NOT* the realm of bug fixes. Different tasks entirely. Just like adding dragoons was the job of the dlc and bringing them in line with difficulty was balance change territory.
The state of the rest of the geth is completely irrelevant to fixing bugs.
But stagger/stunlock can only be reduced by way of a patch. Which SHOULD have been done during the previous patch. It's not a bug, but it can't be fixed by balance changes. So the patch team should've done it.
Whatever way you try to spin it, it doesn't look any better.
sareth_65536 wrote...
lol. I'll just left it here.
If you aren't lieing how come your are whining while I'm not?
Guest_Lord_Sirian_*
ryanshowseason3 wrote...
Lord_Sirian wrote...
ryanshowseason3 wrote...
Lord_Sirian wrote...
ryanshowseason3 wrote...
You've completely misunderstood the process in which this happened.
Pre patch the combat drone was broken. It couldn't do anything. It literally floated around and wasted the prime's time by casting it... The patch fixed it so no there was not a conscious decision to "add more stunlock" they were just fixing something that was broken in the first place. It was always supposed to be like this.
I agree that geth stunlock is not enjoyable but there was no concscious decision to add more, it was a bug fix.
Then Bioware should've considered the repercussions before fixing said bug, and changed the way the Drone interacted in the same patch instead of just KNOWINGLY adding more stunlock (albeit indirectly).
Omission and action are equal in this situation.
The other option being to leave the geth prime wasting its time spawning a unit that did literally nothing?
Honestly I do not blame them.
Fixing the bug was the right thing to do. Changing the difficulty in defeating the geth is in the responsibility of balance changes. *NOT* the realm of bug fixes. Different tasks entirely. Just like adding dragoons was the job of the dlc and bringing them in line with difficulty was balance change territory.
The state of the rest of the geth is completely irrelevant to fixing bugs.
But stagger/stunlock can only be reduced by way of a patch. Which SHOULD have been done during the previous patch. It's not a bug, but it can't be fixed by balance changes. So the patch team should've done it.
Whatever way you try to spin it, it doesn't look any better.
I don't know man I think it is not as nefarious as the way you try to spin it in the OP.
This wasn't BW consciously making the decision to just add more stunlock to the system out of spite or idiocy. Someone fixed a bug and it got rolled into the patch because it was done. I doubt balance was the main focus of this patch the focus was likely getting it through certification and fixing the vanguard glitch, everything else that was done at the time was incidental. Thats how software dev kinda goes. You make a build for a specific bug fix but the other features and fixes that are done get rolled in as well, which may or may not cause problems.
It feels more like you're spinning the story in a different way to say the devs are either incompetent or spiteful. Reads like a biased news article. At least to someone versed in how builds work and "features" like this squeak in. That may be too much to ask though. Not everyone is career software.
Then they would be REALLY stupid, because camping ( a.k.a. being in cover ) is the only way to prevent being stunned, when not on a destroyer/krogan.4ut0b4hn5child27 wrote...
not trying to support the Dev but
what if they intended to do, because of so many camping complains?
If the patch wasn't balance tested at all like your trying to make it sound, then thats pretty damm lazy work.ryanshowseason3 wrote...
This wasn't BW consciously making the decision to just add more stunlock to the system out of spite or idiocy. Someone fixed a bug and it got rolled into the patch because it was done. I doubt balance was the main focus of this patch the focus was likely getting it through certification and fixing the vanguard glitch, everything else that was done at the time was incidental. Thats how software dev kinda goes. You make a build for a specific bug fix but the other features and fixes that are done get rolled in as well, which may or may not cause problems.
Retour en haut