CUEmu - Thread Posts

Stakex007

Fri Jul 29, 2005 12:43 am

Tiggs wrote:

ImageAccess wrote:

Tiggs wrote:

There are many people who did not know about those guides which is why they are featured and will continue to be featured. People invested time to gather the information and create those documents. Give them credit where credit is due please.

There is no written rule on what a Friday feature has to be. Just because it isn't informative to you, doesn't mean it isn't informative to someone else.

Yet when most people believe its better suited to a tuesday tip, we feel you're insulting us badly. Most look forward to the friday feature for information. A simple search would garner the information you've posted in the past 3 weeks. Don't play symantics with us on this one. That was poor "credited" information.

Hell, when one of the original authors of one of the guides comes on and says hes not insulted and understands why people are pissed, that should say something. Yes/No?

As you yourself stated, most look forward to the friday feature for information. By posting advanced guides we supplied information that some players may not have known about. Just because it wasn't exactly what you were looking for doesn't mean it was bad for everyone.

Thats all fine and nice... but guides that are over a year old? Come on... you plain and simply had nothing else so you did a seach for a guide and posted it as a Friday Feature. Instead of letting us in on whats goign to happen in the near future, you guys would rather bore 99.7% of us. I mean come on thoes guides are easy to find for anythign who knows anything about the boards... I could see if it was a guide that wasnt on the boards or something, but not ones a very simple look through the boards would have revealed.

Thomen

Fri Jul 29, 2005 4:09 am

#93

Tiggs wrote:

You missed my response to the original post:

The excel spread sheet is used to get QA the bug information. They then enter the bugs into bug tracking software.

No flaming this time, i promise..

One of the Problems seems to be that the internal communication is somewhat borked, as stated before i believe. Also the system of assigning certain bugs to certain dev seems not to work right. Blix stumbled upon a posting about unslicable Bio Link Gear on theSmuggler board.. he sounded he never heard bout it, but it looked like he knew whatiscausing it and how to fix it.

Grab your QA guysby the balls (if they have some) and squeeze abit til they got the Bug/Issue/Content management and Team assignmentright.

Message Edited by Thomen on 07-29-2005 07:10 AM

Lawho Iwon
Master Smuggler
Smugglers Alliance Ace

Coalition of the Lost Smugglers

Capt_Obvious

Fri Jul 29, 2005 4:53 am

#94

Thomen wrote:

Tiggs wrote:

You missed my response to the original post:

The excel spread sheet is used to get QA the bug information. They then enter the bugs into bug tracking software.

No flaming this time, i promise..

One of the Problems seems to be that the internal communication is somewhat borked, as stated before i believe. Also the system of assigning certain bugs to certain dev seems not to work right. Blix stumbled upon a posting about unslicable Bio Link Gear on theSmuggler board.. he sounded he never heard bout it, but it looked like he knew whatiscausing it and how to fix it.

Grab your QA guysby the balls (if they have some) and squeeze abit til they got the Bug/Issue/Content management and Team assignmentright.

Message Edited by Thomen on 07-29-2005 07:10 AM

QFE!

The-waco kid Retired Crafter extrordinaire
The-Waco Kid-Master Pistols, Master Carbines-PERMA-CANCELLED
-Nuna- Slayer-Master Armorsmith, Master Merchant-PERMA-CANCELLED!
Hunkahunka-Master Bounty Hunter, Master Rifles-PERMA-CANCELLED!
Goodbye to all my friends and allies and enemies, may we meet on greener pastures somewhere else where the players dont get F'd over for spending the last 2 years of their lives playing a worthless POS of a game!

Simisan

Fri Jul 29, 2005 5:47 am

#95

Remember the armour break bug? TH's(iirc) response eventually was "What armour break bug?", "The one we've been reporting for 3 weeks now!". The devs were convinced there was no bug until yet another thread was started about this with, the same combat data copied from previous threads until finally, a dev could see the facts, posted in a thread.... So don't tell me that the spreadsheet is working, important bugs are not making onto that list and if they are, they aren't being prioritised properly (think chat panes resetting at every login - hardly game-breaking but very annoying to the majority of customers).

--
http://www.simantix.co.uk/swgmaps/

Jefferys

Fri Jul 29, 2005 9:12 am

#96

Tiggs wrote:

SirSpamalot wrote:
why o why put a /bug command in the game if no-one looks at them!?

/bug reports done in game go directly to the QA department and are looked over daily.

Just wondering, but what happens if QA cannot reproduce the bug. Does it get chucked into the bit bucket or do they get with the person that submitted the bug?

I would hope that they would get with the person that submitted the bug. Sometimes it is hard to put into words what is happening. And the player may be able to explain it better with direct communication.

It would be nice if there were more categories in the /bug box to select from. Sometimes the bug doesn't really fit in any of the categories listed.

Thanks,
Alen
Radiant

Felisconcolori

Fri Jul 29, 2005 11:12 am

#97

Tiggs wrote:

You missed my response to the original post:

The excel spread sheet is used to get QA the bug information. They then enter the bugs into bug tracking software.

Ahh, yes, you are quite right. I did miss that. Although I think this may still be an unnecessary step in the process. While QA is necessary and should review the bugs, I guess the point in the process in which QA steps in is up for some discussion and different development styles. I would eliminate the Excel spreadsheet portion of the process, and rather input the bugs directly into the bug tracking software. These bugs should stand out, as they would have no developer assigned and may be queued for QA to process.

I guess what I really wanted to say was, Excel is evil and you should smite it. For right now, I can always blame Bill Gates for any bugs that slip through the cracks... obviously, some rows are being obscured or forgotten because of esoteric Excel issues. (I've worked with Excel for many years now, and it never ceases to amaze me how it can take something as simple as 2+2 and mess it up for no good reason.)

Seriously, though, it is double-plus wonderful that you've let us peek in. Also lets me know how to adjust my resume when I apply

Wait... does that mean you won't respond to me now? I vaguely recall something about devs/correspondends will not reply to employment related posts... Blast! No no, what my real point is is this: Process flow is good to know, but reducing steps where possiblemakes life easier for everyone.

Gypsia d'Catman - Tough Chick with a Flamethrower
Catman Dewback - Famed Trando ex-band leader of the Wookettes
Felis Con'Colori - Bothan Spy back before there was a "Spy"
Larrana Darkewave - A Silent Dancer

All dead as of 11/30/05. We tried. Gysia's flamethrower blew up. Catman was arrested for trumped up charges of slavery. Felis grew cold in the grip of Darth SOE. Larrana finally swallowed her NDA and choked.
Hail, Hail the NGE! SWG is dead! All praise the NGE!

kAotiC_HeRo

Fri Jul 29, 2005 8:19 pm

#98

Tiggs wrote:

Ecnirp wrote:

The Experimentation bug (experimentations not updating until the item is crafted) was raised days ago, bugged on the TC and posted on the TC bug threads - yet its gone live, and to all crafters it seems.

Why did another majorly bugged publish go live?

It seems each major bug\bugs brought by each new publish is raised before it goes live and yet it still gets pushed out.

This is not what the player base wants.

Please....

1) Focus on fixing all the existing major bugs before any more publishes go out.

2) Please please, don't push out publishes you know have major bugs - do you think we really mind waiting a few days for a bug to get fixed before a publish goes live?

/sign

We agree with your wants. We are going to be focusing on smaller/cleaner publishes because quality means much more then quantity.

What about Pearl Drops? What about Force Heals not going off in a timely fashion? What about Lightsaber Speed bugging requiring removal of all pearls each time you log out? How can the force be 'broken'? Why are Characters 1 1/2 times stronger than Jedi? Why is there a LOS Bug on the Ryatt Trail to prevent Padawans from being attacked? Why am I still getting MAJOR lag issues in 'dead' cities?

Until you fix the MAJOR Underlying Issues, Don't even bother posting other fixes until you have the ones that are gamebreaking fixed? Furthermore, why don't you have an 'In-Live - Bugs Thread'?

nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn
KAOTIC HERO -[My new baby!. ]- BRITTANI

Evayy

Sat Jul 30, 2005 9:49 am

#99

True experience this week on larmark server daoc

Was working on the newbe quests for the new classic server, ran into a bug "that cannot be by passed" to gain content to a specific area.

i sent in report very detailed, within the hour i had a "yellow csr type appear in front of me in toon form"

asked me if i would mind being transported to said area and duplicate the bug for them. I did that and instead of no response and ticket deleted i got a thank you , for contributing from them.

The they said how important it was that the new be quests were working flawlessly due to the first impressions count.

To me that surprised me more then anything else. They appreicted the time i took to point out an issue and even more appreicated the time it took to duplicate it. Oh checked the known issues in the herald page next day and it appeared there. The communication through the herald page is outstanding.

Part of what frustrates the players, here, is bugs are reported, detailed, and reported on the test center that still go live.

Tihson2k4

Sat Jul 30, 2005 8:09 pm

#100

Tiggs wrote: Every day the Live, TC and Correspondent bug threads are entered into a excel spreadsheet. They are then sent on to QA to be reproduced and assigned a bug number. From there they are then prioritized and filtered out to the Leads. Members of the Dev team will not know all bugs that are happening. They are assigned bugs from their Lead and those are what they work on. So your statement is semi true, Devs are not shown all the bugs that are entered however, they are told about bugs that impact them.

&

You missed my response to the original post:

The excel spread sheet is used to get QA the bug information. They then enter the bugs into bug tracking software.

--------------------------------------------------------------------------------------------------

hmmmm, i think that the QA team need to redefine what they consider a priority or not

** edit ** damn lithium not letting me quote and damn lithium not letting me put enough html in to do my own :@

Message Edited by Tihson2k4 on 07-31-2005 04:15 AM

Coahake Eupido - CL90 Jedi

JaxMeridian

Sun Jul 31, 2005 2:33 am

#101

Once you read this, you will quickly realize that I am not a computer whiz. I do, however, have many years experience in personell management. The boss doen't have to know how to do everything that he or she has respomsibility over. All the boss needs is the ability to get their employees to do the job correctly, efficiently, and rapidly.

Thats what I do.

So try this on for size: Perhaps the problems getting bugs caught before they get in the live game, or correcting them if they do, is NOT a programming / developer / coding / or reporting rpoblem as much as it is an organisation tree problem. Perhaps the problem is that the game is so complicated and diverse that people are assigned to individual bugs, instead of being assigned to areas of the game.

By assigning Dev teams to set areas of the game, you reduce the perceived workload, manage the process, and get more done tham with a "By the Bug" assignment method.

Now, being unfamiliar with SOE's Management Structure and Developement Team Structure, all one can do is guess and suggest ( two things that I hate to do when I was assigned to go in to a location and "Fix" the crews performance), but since this is what it is, lets give it a try ( I'm not getting paid, and am only a lowly customer, so you won't pay this much attention anyway, all it will do is let me blow off steam, and dream about the good old days, lol).

Manager A is over the Ingame Correction Team. This is where the buck stops. He's the Boss when it comes to getting crap turned into gold. He/She hadthree assistants that are Managers over their own teams. One is over Bug Reporting, another over bug corrections, and the last is over testing. Now thats three develpment teams, each having DEVELOPERS as the base force. Who knows the code better than those that write it. Teams rotate, with their managers, on a monthly basis, so that team one reports bugs one month, then the next month the same team moves to correction where the reproduce the bugs by playing on one of the servers at random. This allows the teams to remain in the loop, see what players are doing, and lesten to the players without getting swamped with idiotic "Devs, please read this" posts.

This is the process that occurs: Bug is reported, goes to team one. Team one reproduces the bugs, trying to comeup with workaround to be given to CSR's till the bugs can be repaired. Bug is reproduced and is sent to the next team.

Team two gets the information from team one, they check out the information, with all the variables, and write code to repair the bug. Sends Bug report to team three.

Team three is randomly broken up and playing ontest servers, kinda like team one on the regular live servers. They test the various situations to try to reproduce the bug. If the bug cannot be reproduced, the TC players are given information about the results of the testors, and asked to try to double check the results. Players tend to have the ability to break things better that rpogrammers, so if it CAN be reproduced, the can do it.

No bug means release to live.

Just nickles worth of free advice.

Maybe I'm just an old man blowing off steam, but thanks for the areana to vent in.

Tzhar Khune
Elder Bounty Hunter,New Order Jedi
Member of CorBa
Server- Bria
"Yeah, I'm a Corellian, wanna make something of it?"

GraySeven

Sun Jul 31, 2005 10:19 am

#102

I'm simply going to sit back and be thankful that the Dev's finally heard the outcry and decided to listen to the player base and fix bugs instead of adding new ones in.

Every profession has bugs/issues that make gameplay annoying in the least. While "game-breaking" is getting thrown around a little too much, there are many bugs that lessen the enjoyment of the game. Not being able to log in is game-breaking, Krayt dragons not dropping premium pearls is not. You can still play the game using other pearls.....

I, for one, want to thank the Dev's for finally getting it. Its unfortunate that my brother quit (again) because of the lack of communication and lack of bug fixes, but maybe people quitting over these issues is what really caught the Dev's attention about them.

Whatever the reason they are doing it, I'll support the Dev's fully in this attempt to clean up the game.

My only complaint is that increasing Dev postings with inane comments is NOT increased communication. In one day my Dev Tracker had 3 pages of Dev posts/responses and yet the majority of them were nothing more than "Yada, yada, yada". If you truly wish to increase communication, then tell us something.

Vahl Arturin - Elder Ranger, Elder Bounty Hunter, Elder Rifleman
&
Vaylis Arturin - Elder Armorsmith
Starsider
"The burning is love"

Community Relations Archive

Thread: It was raised before Publish 20 went live, yet another major bug goes live.