Possible solution to the complaints

[stoutbrewdrink]

<DIV>this is a suggestion, dont take it as a rant or anything. I feel this could possbily clear up alot of hate that is being generated by the community towards soe. </DIV> <DIV> </DIV> <DIV>Fix 1 thing at a time, test it, prove it, and make sure everything is fixed in that one area. An example: fix all spell bugs in one class. Do that week by week or whenever you are able to finish it. The more you spread your fixes out, the more people you can [Removed for Content] off and disatisfy. Yes you can also spread the fixes out to everyone which is most likely your  meaning behind spreading the fixes out. But if you stick to one thing and completely finish off the bugs in it people will be more happy to see things completed. Say one month do all spell fixes, next month do all bugged encounter fixes. I just see it as an advantage doing it this way instead of spreading out the joy little piece by piece slowly and surely. Bring out the big fixing stick and knock some tasks down instead of slowly completing parts of each. </DIV> <DIV> </DIV> <DIV>Another suggestion, keep things on test server much much much much longer. Im tired of seeing a patch being brought live or new quests and stuff only to see that the servers need to come down 30 minutes later cause the NEW patch you just put in is bugged. Crown of tranix was bugged for a long while (possibly still bugged unsure on it though), i think i remember the valentines day quest being bugged and you pulled servers down to fix it right after you put it on. Basically dont think that the community wants the patches asap, we want them to work properly and take the time to test them longer. I mean patches are supposed to fix things correct? not add new problems. Honestly i dont see how some of the major bugs with the patches went through testing and made it to live servers still. The first big patch had so many problems with it along with [FAAR-NERFED!] near any other patch you have had. Test server is there for a reason, test this stuff longer and stop rushing it, you [Removed for Content] more people off by doing it this way then giving these quick snappy buggy patches.</DIV> <DIV> </DIV> <DIV>Thats all i got in words of suggestions, all i can do is pray that some DEV reads this and believes i might be correct in some way. Just FYI i thought SOE was doing horrible at release (horrible as far as running the game as a whole). But over time i see that they are trying to address the problems, i just think you guys are going at it the totally wrong way, Slow and steady wins the race. Just cause WOW is on your tail doesnt mean you have to race them, im positive eq2 is going to be popular for the long run. On that note ill leave this post as it is. Please SOE make the correct choices, slow things down, step back take a look at the ways you are fixing things.</DIV> <DIV> </DIV>

[SavinDwa]

<DIV>Unfortunately this is totally unrealistic.  It assumes that a programer is a mechanic that can be swapped onto any job without requiring any special domain knowledge or skills.  It also assumes that an unlimited number of people could work on the same section of code at the same time.  The reality is that SOE has their developers in teams.  Each of the teams are experts in particular areas,  To pull a new person into the team would take at least a month before they could be effective and probably more like 3 months.  </DIV> <DIV> </DIV> <DIV>Pretend for a moment that Everquest is a large hotel.  We have engineers, we have cooks, waiters, electrician, housekeeping, bellhops, accountants, etc, etc.  Now lets say the hotel decides that the next two hours is "bake time" because they suddenly want to make lots of apple pies.  So they get everyone in the kitchen, But ther eis not enough space.  95% of them can't cook,  They don;t where stuff is in the kitchen etc etc.  You end up with a lot of bad pies and in the mean time everything else is just going to hell....</DIV> <DIV> </DIV> <DIV> </DIV>

[pmri]

<DIV>I think the point was TEST IT WELL BEFORE DEPLOYING IT.</DIV> <DIV> </DIV> <DIV>Revamp your tesing process.  Do you actually write and execute test cases?</DIV> <DIV> </DIV> <DIV>I bet your developers are testing the code, right?</DIV> <DIV> </DIV> <DIV>Do you actually poll the users to find out what they want?  Or, do you have "brainstorming" meetings where make decisions that the users hate?</DIV> <DIV> </DIV> <DIV>BTW: the used want you to fix all P1-P3 bugs before you deploy new "features"</DIV> <P>Message Edited by pmritz on <SPAN class=date_text>02-21-2005</SPAN> <SPAN class=time_text>03:36 PM</SPAN></P><p>Message Edited by pmritz on <span class=date_text>02-21-2005</span> <span class=time_text>03:38 PM</span>