Warrior General Games

Originally posted by dahman32
OP

Roles of those involved with Bugs <--- has nothing to do with wanting something bug-free, but how the process of getting there works.

lolexplanations that sound like pandering, but it's understandable.

How come "trolls" tend to take over the topics? Sad thing is, most of the trolls are mods or "fanboys"

Hilarious

Carry on, just wanted to show how 2,000,000,000,001 can be the majority of 4,000,000,000,000.... leaving 1,999,999,999, but still... a majority was had

Originally posted by AirMcMVP
In general, bugs mods can mark as issue as a bug.
Lead bugs mods can mark items as bugs and also file items officially as bugs.
Catch has the final say.

Originally posted by EllisBell
Half of the filed bugs have been fixed, per Deathblade and AirMcMvp above and per our bugs log. We are very grateful for our Bugs Mods who help sort through bugs submissions. We have a very small group of ppl who can fix bugs, and they are extremely busy. Once a bug is filed it is up to them to fix it, the bugs mods sort of direct traffic.

If you have a concern about a filed bug or a bugs ticket that you believe hasn't been addressed, please message support, we can take a closer look and give you an update on it's status.

I believe between these two quotes you'll find the answer. Maybe not exact names of the people who fix the bugs but this is an explanation of the process.

Originally posted by Deathblade
Oh, and here I thought 38 was the majority of 72.


Technically you are correct about fixed versus filed. The only problem is that in the numbers AirMcMVP presented there are instances showing that should be considered filed and likely have not yet be addressed in some of the categories. It really was a pretty tactical approach to making a case, because people like you would not completely read it. Therefore he is able to make his case look stronger than it really is. The fact of the matter is he misled you by the things that you are able to see, and allowed you to skim over the rest of the information. Then he made sure to remind "everyone" that the 38 of the 72 information is available for all users to see just to make sure you weren't of mind to really think too hard about the information he presented. My stating that he posted information that was contrary to your statement and his agreement to that fact should really have been your first clue.

In his next post he tries to make it seem he wasn't making a case at all, "just posting the facts." Fine, as long as he admits the facts are that the points he made don't look favorable at all. Again, I called no one a liar. I did call someone out. He owned up to it.

Just a quick thought, when someone starts an argument with the phrase "just for the record," you might as well assume they are trying to pass something by you.


Originally posted by bhall43
How is anyone supposed to isolate a bug if the user doesn't give any information about what the fuck is going on? That makes absolutely no sense. Are you suggesting that for every time some user thinks there might be a bug in place that Bort piece work through that person's AI/tactics/builds/the sim itself just to come up with a solution?

Is it amateur hour at GLB? Who said the user isn't giving details on what happened to them? That is not the same thing as isolating the issue.

38 of 72 = F

Originally posted by AirMcMVP

He's going off the number of total tickets submitted, I'm sure. What he's ignoring is that the majority of the tickets that weren't filed as bugs have either been resolved (either through support or by working directly with the agent), duplicate reports, or never an issue to begin with. There may be a few submissions that I classified as insufficient information that were legitimate bugs but if we either a) can't see the replay or b) can't the reporter to provide additional information then how significant was the bug?

Uh, no. That isn't the case at all. Category

1) Support issues. Still a bug but was escalated. Uncertain where they stand now based on your information. Likely some fixed some not.
2) Duplicate, Merged. This one might be accounted for properly. However it is in fact still a separate filing and therefore should be treated as such as far as analysis goes.
3) Known issues that you were able to help the user with. if something is a known issue that has not been resolved it should technically be resolved and should be filed.
4) This one I give some leeway on but the bug may still sit out there. I agree that if you get no response on it though, it is (A) difficult to resolve and (B) probably not too important at that time to the user. It may be important to someone in the future but I can't exactly make a good argument to file that.
5) Working as intended does not mean not a bug. It does mean that the program is working as the programmer believed it should work. Some of those I am sure could be argued and debated to the end of time. Microsoft has a great number of these actually. However, they admit that many of them are still in their R&D department.

You admit the facts and make a turn about later?
Originally posted by Dub J
38 of 72 = F

LOL dub.

Which Bugs Mod is best at handling a user who keeps getting a bug up his ass?
Would the user be required to replicate the bug up his ass? (Some users are actually pretty good at that)
Do the Bug Mods use rubber gloves as they search for the bug?
Are there an female Bug Mods?

Originally posted by toobad4u_00
Is it amateur hour at GLB? Who said the user isn't giving details on what happened to them? That is not the same thing as isolating the issue.

It must be amateur hour because you aren't making any sense. What are the bugs mods asking that you believe is crazy that the user needs to provide?

If you have an issue with the Bugs system or processes, please feel free to contact me at anytime.

Originally posted by AirMcMVP
I think its safe to say that if a major issue surfaced (meaning something that affected a large portion of the user base in a significant way) resources would be moved back to get that issue fixed.

Wanted to add that this statement is very true. We are always very quick to act on issues that impact the user base in a significant way. Always have and I think most of our customers would agree that is the case.