As a software developer, I can assure you that it is MUCH more fun to add new bugs to your code than to try to track down and solve existing ones. Think about it, you come in to work for the day, and your "to do" list looks like this...
- write a working sort program for the AH, bags, etc that actually works bug free. While this is a trivial piece of code and one of the first things most students write in their first class, you can also download one on the web from some kid's homework. So nah... you can do that one later.
- fix the unstoppable bug. Well, this is ugly... someone messed with it and broke it, and no one knows how, why, or where that happened. Its like tracking down a needle in a haystack... ugg. I think I will watch a couple of utoob vids and claim I was "working on it" instead.
- add XYZ new feature. Now this sounds OK, hell with the current track record your job is in no danger if the result is bugged to death, so long as it sorta kinda works some of the time, right? Some other sucker can debug it later, serves them right, they are probably the one that broke unstoppable anyway..!
- fix some exploit. Greaaat... another needle in a haystack, first you have to figure out HOW they are doing the exploit, then you get to re-write a big chunk of confusing gibberish written by the guy that broke unstoppable so the exploit is no longer there.... joy.
As a software developer, I can assure you that it is MUCH more fun to add new bugs to your code than to try to track down and solve existing ones. Think about it, you come in to work for the day, and your "to do" list looks like this...
- write a working sort program for the AH, bags, etc that actually works bug free. While this is a trivial piece of code and one of the first things most students write in their first class, you can also download one on the web from some kid's homework. So nah... you can do that one later.
- fix the unstoppable bug. Well, this is ugly... someone messed with it and broke it, and no one knows how, why, or where that happened. Its like tracking down a needle in a haystack... ugg. I think I will watch a couple of utoob vids and claim I was "working on it" instead.
- add XYZ new feature. Now this sounds OK, hell with the current track record your job is in no danger if the result is bugged to death, so long as it sorta kinda works some of the time, right? Some other sucker can debug it later, serves them right, they are probably the one that broke unstoppable anyway..!
- fix some exploit. Greaaat... another needle in a haystack, first you have to figure out HOW they are doing the exploit, then you get to re-write a big chunk of confusing gibberish written by the guy that broke unstoppable so the exploit is no longer there.... joy.
See what I mean?
Actually thats the 1st thing i enjoyed reading on this forum.
hahah thanks for posting! sadly, i bet its how it looks like for real.
As a software developer, I can assure you that it is MUCH more fun to add new bugs to your code than to try to track down and solve existing ones. Think about it, you come in to work for the day, and your "to do" list looks like this...
- write a working sort program for the AH, bags, etc that actually works bug free. While this is a trivial piece of code and one of the first things most students write in their first class, you can also download one on the web from some kid's homework. So nah... you can do that one later.
- fix the unstoppable bug. Well, this is ugly... someone messed with it and broke it, and no one knows how, why, or where that happened. Its like tracking down a needle in a haystack... ugg. I think I will watch a couple of utoob vids and claim I was "working on it" instead.
- add XYZ new feature. Now this sounds OK, hell with the current track record your job is in no danger if the result is bugged to death, so long as it sorta kinda works some of the time, right? Some other sucker can debug it later, serves them right, they are probably the one that broke unstoppable anyway..!
- fix some exploit. Greaaat... another needle in a haystack, first you have to figure out HOW they are doing the exploit, then you get to re-write a big chunk of confusing gibberish written by the guy that broke unstoppable so the exploit is no longer there.... joy.
Shame they can't fix all bugs and exploits with the same zeal they reserve for ones that affect ZEN /cash shop in some way , if they did the game would be bug free within 24 hours or less and it would be a much more entertaining experience for it ...
I love this forum i waited until now to make a user for it. This game has one of the most negative game forums i have seen and interested in why this is so. Well from the get go it seems its because of the games failure. I will try this game out since its so called F2P we will see how far or long that lasts.
As a software developer, I can assure you that it is MUCH more fun to add new bugs to your code than to try to track down and solve existing ones. Think about it, you come in to work for the day, and your "to do" list looks like this...
- write a working sort program for the AH, bags, etc that actually works bug free. While this is a trivial piece of code and one of the first things most students write in their first class, you can also download one on the web from some kid's homework. So nah... you can do that one later.
- fix the unstoppable bug. Well, this is ugly... someone messed with it and broke it, and no one knows how, why, or where that happened. Its like tracking down a needle in a haystack... ugg. I think I will watch a couple of utoob vids and claim I was "working on it" instead.
- add XYZ new feature. Now this sounds OK, hell with the current track record your job is in no danger if the result is bugged to death, so long as it sorta kinda works some of the time, right? Some other sucker can debug it later, serves them right, they are probably the one that broke unstoppable anyway..!
- fix some exploit. Greaaat... another needle in a haystack, first you have to figure out HOW they are doing the exploit, then you get to re-write a big chunk of confusing gibberish written by the guy that broke unstoppable so the exploit is no longer there.... joy.
See what I mean?
So you mean game developers don't take any pride in their work?
As a software developer, I can assure you that it is MUCH more fun to add new bugs to your code than to try to track down and solve existing ones. Think about it, you come in to work for the day, and your "to do" list looks like this...
- write a working sort program for the AH, bags, etc that actually works bug free. While this is a trivial piece of code and one of the first things most students write in their first class, you can also download one on the web from some kid's homework. So nah... you can do that one later.
- fix the unstoppable bug. Well, this is ugly... someone messed with it and broke it, and no one knows how, why, or where that happened. Its like tracking down a needle in a haystack... ugg. I think I will watch a couple of utoob vids and claim I was "working on it" instead.
- add XYZ new feature. Now this sounds OK, hell with the current track record your job is in no danger if the result is bugged to death, so long as it sorta kinda works some of the time, right? Some other sucker can debug it later, serves them right, they are probably the one that broke unstoppable anyway..!
- fix some exploit. Greaaat... another needle in a haystack, first you have to figure out HOW they are doing the exploit, then you get to re-write a big chunk of confusing gibberish written by the guy that broke unstoppable so the exploit is no longer there.... joy.
See what I mean?
It just shows there is no QA involved in the release process. I mean "code is compiled successfully" is not the same as "code has been tested successfully". So if you try to cut corner and have someone else doing testing for you and not paying them then don't expect good result.
0
firesoul31Member, Neverwinter Beta Users, Neverwinter Hero Users, Neverwinter Knight of the Feywild UsersPosts: 34
It just shows there is no QA involved in the release process. I mean "code is compiled successfully" is not the same as "code has been tested successfully". So if you try to cut corner and have someone else doing testing for you and not paying them then don't expect good result.
Yeah this. QA is the last stop before the code goes live. Either there is too much pressure from up top to go live or there is not enough QA testing. Devs might think they have the code fixed but if it isn't tested properly the code is released with bugs still working.
I'm curious how much staff they hav and the numbers of devs and QA's.
Playing, paying & Coding - My take on Neverwinter, mods be darned
Opened up comments, because I would love to hear what everyone says, even the naysayers. http://goo.gl/TiX1kO
Yeah this. QA is the last stop before the code goes live. Either there is too much pressure from up top to go live or there is not enough QA testing. Devs might think they have the code fixed but if it isn't tested properly the code is released with bugs still working.
I'm curious how much staff they hav and the numbers of devs and QA's.
Of course, bugs can also occur after the QA testing. Sometimes, just going live can cause bugs that aren't present in the QA testing.
Is this alot of peoples first MMO? This isn't a snarky question, but genuine. There's been many games that have been much worse then here. SWTOR for example. Their first few patches and updates were so bad that you could count on them taking down the servers a couple of days after the patch to repair it. Sometimes they had to take the servers down more then once. At least here, the "breaks" haven't been bad enough that they have to take the servers down after every-single-patch.
0
sturuckusprimeMember, Neverwinter Beta Users, Neverwinter Guardian Users, Neverwinter Knight of the Feywild UsersPosts: 0Arc User
edited September 2013
Very true raath13. Which is why I'm sticking around. It just gets frustrating and I can understand people wanting to vent.
Of course, bugs can also occur after the QA testing. Sometimes, just going live can cause bugs that aren't present in the QA testing.
Is this alot of peoples first MMO? This isn't a snarky question, but genuine. There's been many games that have been much worse then here. SWTOR for example. Their first few patches and updates were so bad that you could count on them taking down the servers a couple of days after the patch to repair it. Sometimes they had to take the servers down more then once. At least here, the "breaks" haven't been bad enough that they have to take the servers down after every-single-patch.
I was mostly poking fun to lighten the mood.
But to answer... it is my first "serious" free MMO. The pay to play model games had a few minor bugs but they were quickly handled. I do not count lotro as free, though it is now its model and bug-handling are pay to play models.
Of course, bugs can also occur after the QA testing. Sometimes, just going live can cause bugs that aren't present in the QA testing.
Is this alot of peoples first MMO? This isn't a snarky question, but genuine. There's been many games that have been much worse then here. SWTOR for example. Their first few patches and updates were so bad that you could count on them taking down the servers a couple of days after the patch to repair it. Sometimes they had to take the servers down more then once. At least here, the "breaks" haven't been bad enough that they have to take the servers down after every-single-patch.
You simply do not follow the main issue that people are venting about. There are software flaws where you need to run a rather complex process/multiple levels of execution in order to see the flaw. This can be overlooked and went in production environment even thru vigorous QA process. But I do believe the issues people are venting here is the OBVIOUS.
If the gd dragon breath kills you even though you are behind its hind leg and nowhere near it then it is pretty gd obvious of a software problem don't you think.
Just a small example for you. Capiche !!!!
0
cbrowne0329Member, NW M9 PlaytestPosts: 293Arc User
If the gd dragon breath kills you even though you are behind its hind leg and nowhere near it then it is pretty gd obvious of a software problem don't you think.
Just a small example for you. Capiche !!!!
That's not a bug... That's the physics of heat. Something that is large enough to create a directional heat blast would output so much heat even being in the general vicinity could kill you. Considering that the fire generated by a dragon originates from what most believe is the abdomen... the heat near his hind quarters will be so intense that you will die from it.
But dwarves would have you believe that hiding behind a wooden or normal shield will protect you... when i nreality the only thing that can block that type of heat would be magic...
That's not a bug... That's the physics of heat. Something that is large enough to create a directional heat blast would output so much heat even being in the general vicinity could kill you. )
I sincerely hope you are trolling.....
edit: removed comment for misreading the troll
0
cbrowne0329Member, NW M9 PlaytestPosts: 293Arc User
edited September 2013
Idiot? The smiley winky face not enough... sigh... why bother... before calling people idiots learn to read context.
But to answer... it is my first "serious" free MMO. The pay to play model games had a few minor bugs but they were quickly handled. I do not count lotro as free, though it is now its model and bug-handling are pay to play models.
Oh boy...LOTRO....talk about your patches going wrong.....
The first year LOTRO was live, they released a big patch right before the American Thanksgiving holiday. Things went horribly wrong, and the servers were barely up for several days afterwards. It was so bad, that the Turbine employes got called back from their holiday!
Comments
- write a working sort program for the AH, bags, etc that actually works bug free. While this is a trivial piece of code and one of the first things most students write in their first class, you can also download one on the web from some kid's homework. So nah... you can do that one later.
- fix the unstoppable bug. Well, this is ugly... someone messed with it and broke it, and no one knows how, why, or where that happened. Its like tracking down a needle in a haystack... ugg. I think I will watch a couple of utoob vids and claim I was "working on it" instead.
- add XYZ new feature. Now this sounds OK, hell with the current track record your job is in no danger if the result is bugged to death, so long as it sorta kinda works some of the time, right? Some other sucker can debug it later, serves them right, they are probably the one that broke unstoppable anyway..!
- fix some exploit. Greaaat... another needle in a haystack, first you have to figure out HOW they are doing the exploit, then you get to re-write a big chunk of confusing gibberish written by the guy that broke unstoppable so the exploit is no longer there.... joy.
See what I mean?
Actually thats the 1st thing i enjoyed reading on this forum.
hahah thanks for posting! sadly, i bet its how it looks like for real.
Neverwinter Wonderland
Neverwinter Wet & Wild
Neverwinter 2nd Anniversary Montage
Neverwinter Anniversary Montage
Protector's Jubilee Speech
Oh the Carnage
So you mean game developers don't take any pride in their work?
It just shows there is no QA involved in the release process. I mean "code is compiled successfully" is not the same as "code has been tested successfully". So if you try to cut corner and have someone else doing testing for you and not paying them then don't expect good result.
Yeah this. QA is the last stop before the code goes live. Either there is too much pressure from up top to go live or there is not enough QA testing. Devs might think they have the code fixed but if it isn't tested properly the code is released with bugs still working.
I'm curious how much staff they hav and the numbers of devs and QA's.
Opened up comments, because I would love to hear what everyone says, even the naysayers.
http://goo.gl/TiX1kO
Of course, bugs can also occur after the QA testing. Sometimes, just going live can cause bugs that aren't present in the QA testing.
Is this alot of peoples first MMO? This isn't a snarky question, but genuine. There's been many games that have been much worse then here. SWTOR for example. Their first few patches and updates were so bad that you could count on them taking down the servers a couple of days after the patch to repair it. Sometimes they had to take the servers down more then once. At least here, the "breaks" haven't been bad enough that they have to take the servers down after every-single-patch.
I was mostly poking fun to lighten the mood.
But to answer... it is my first "serious" free MMO. The pay to play model games had a few minor bugs but they were quickly handled. I do not count lotro as free, though it is now its model and bug-handling are pay to play models.
~cough~
You simply do not follow the main issue that people are venting about. There are software flaws where you need to run a rather complex process/multiple levels of execution in order to see the flaw. This can be overlooked and went in production environment even thru vigorous QA process. But I do believe the issues people are venting here is the OBVIOUS.
If the gd dragon breath kills you even though you are behind its hind leg and nowhere near it then it is pretty gd obvious of a software problem don't you think.
Just a small example for you. Capiche !!!!
That's not a bug... That's the physics of heat. Something that is large enough to create a directional heat blast would output so much heat even being in the general vicinity could kill you. Considering that the fire generated by a dragon originates from what most believe is the abdomen... the heat near his hind quarters will be so intense that you will die from it.
But dwarves would have you believe that hiding behind a wooden or normal shield will protect you... when i nreality the only thing that can block that type of heat would be magic...
I sincerely hope you are trolling.....
edit: removed comment for misreading the troll
Oh boy...LOTRO....talk about your patches going wrong.....
The first year LOTRO was live, they released a big patch right before the American Thanksgiving holiday. Things went horribly wrong, and the servers were barely up for several days afterwards. It was so bad, that the Turbine employes got called back from their holiday!
Good times, good times.......