| Pages: [1] 2 3 :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 5 post(s) |
|
CCP Lingorm
   |
Posted - 2007.06.28 13:49:00 -
[1]
Let me introduce myself, I am Lingorm, the Team Leader for the newly established QA Engineering Cell. We will be building better testing tools. One of the first ones we have underway is an 'upgrade' of our internal Defect Tracking System and the associated support systems (https://bugs.eve-online.com/). I am most keen to hear any suggestions that you have to improve the current site by increased functionality and/or improved usability.
Currently in development is the ability to Tag a defect to a game Category (Starbases, Missions, Science and Industry etc) this will aid us in the filtering of the bug reports and the ability to find duplicates.
What else would you like to see? What would make the site more usable?
CCP Lingorm
CCP Quality Assurance
QA Engineering Team Leader
|
|
Nisse Owned
The Order of Chivalry
|
Posted - 2007.06.28 14:04:00 -
[2]
Repost from previous thread as you posted a minute before me at most
 Originally by: Nisse Owned
I do agree on that it could be improved a bit... I used mantis not too long ago to report a bug with Garry's mod, and that i can call effective, you can create hidden bug reports that only devs can see(For exploits and so), aswell as normal bugreports can be seen by everyone and people can help add info, screenshots and repro steps aswell as was a very detailed status of bug system also, if it's new, assigned or so :)
Would be very nice if you could look at some of these features mantis has.
It's great with email notification but it seems like bughunters can't still communicate very well with the reporter, as bugreport is deleted if it needs additional info for example, leading to loads of unneeded copypasta and bother just to update info on a bug... Mostly ends with people getting a "Not enough info" reply not reporting it again 
|
Laendra
|
Posted - 2007.06.28 14:14:00 -
[3]
I would like to see a live bug tracking system, where we could see the status of current (ones we submitted and those that others have submitted) bugs, including what stage it is in (new, confirmed, in development, testing, scheduled for deployment) and the release for which the bug is scheduled to be fixed on production. Also a searchable interface, so we can search to see if a bug is already known.
-------------------
Brainstorm ideas to make EVE better:->http://eve.stormingbrains.org/index.php
|
Helison
Gallente
Times of Ancar
THE R0NIN
|
Posted - 2007.06.28 14:15:00 -
[4]
Welcome! Great to hear that you really plan to improve QA and specially the bug reporting system!
Copied (and adapted) from the old thread:
*) Make bug reporting a fully bidirectional system, where we can follow our own bugreports and can give additional info (specially if needed by BH/Devs). At the moment this is only possible by creating new BRs or by talking to BH¦s/Devs in #eve-chaos (but you can be sure, that some of the information will be lost again).
*) Automated system of "known issues". Each "public" known issue (without exploits etc.) can be seen as soon as it is confirmed by a BH/Dev. Included is a status of the issue (solved on TQ / solved internally / found / more details needed).
Another option would be to give public access to your defect tracking system, but this could be quite problematic with security.
*) Not really about bugreporting, but this would also help: Automated patchnotes for each patch, which is deployed to Sisi. Then we could test our reported bugs, if it is really fixed, when it should be fixed.
added:
*) Make it possible to see the link "Bug Reporting" under Eve Insider, even if you are not logged in. This is often confusing, when the link is simply not visible.
*) Create a better work-around for the 2MB upload-limit for attachements in bugreports. Perhaps you could even make the logserver more userfriendly. How about an option, that only the last 5(?) minutes are safed to a log-file?
*) Also not really bugreporting, but testing: Give us players hints, which changes shall be tested more intensely. Specially before larger patches like Rev2 it is difficult to track which changes are completly deployed on Sisi and should work like intended.
|
Laendra
|
Posted - 2007.06.28 14:18:00 -
[5]
Originally by: Nisse Owned
Would be very nice if you could look at some of these features mantis has.
It's great with email notification but it seems like bughunters can't still communicate very well with the reporter, as bugreport is deleted if it needs additional info for example, leading to loads of unneeded copypasta and bother just to update info on a bug... Mostly ends with people getting a "Not enough info" reply not reporting it again
I agree...would like to see the ability to edit an existing bug report to add additional information. If a response from the reporter isn't made within, say 72-96 hours, close the bug.
-------------------
Brainstorm ideas to make EVE better:->http://eve.stormingbrains.org/index.php
|
Inspiration
|
Posted - 2007.06.28 14:37:00 -
[6]
Edited by: Inspiration on 28/06/2007 14:37:26
I realy like the ideas posted above me. I have some idea's that are not explicitly related to the bug reporting site itself, so I won't polute this threat with a lengthy duplicate here. Instead you can read my take in the orignial thread instead.
|
|
CCP Lingorm
|
Posted - 2007.06.28 14:42:00 -
[7]
Edited by: CCP Lingorm on 28/06/2007 14:41:52
Somethings to consider that I have been thinking hard on.
If we make all the bugs public then EVERYONE has access to use the information contained there in for what ever purpose they can. This means that we would be 'publishing' an Exploit manual. Not something we want to do. Conversely there is some merit in people comparing notes and trying to gather more information on the bug to make it easier for us to identify and then fix.
Security by Obfuscation has never really worked but there is a difference between Obfuscation and sensible exclusion of information.
We do have more detailed bug threads on the Bug Hunter Forums, but those are closed to the general public to prevent this information being put to nefarious uses.
If you have suggestions of a happy medium that can serve both results then I am ready to hear you suggestions.
Could someone please post a URL to this Mantis that is talked about please so that I can have a look.
CCP Lingorm
CCP Quality Assurance
QA Engineering Team Leader
|
|
Nyphur
Pillowsoft
|
Posted - 2007.06.28 14:46:00 -
[8]
I'd like the ability to reply to a bug report in the same way as I would reply to a petition. I had a bug report recently turned down saying that it wasn't a bug, then I copied the bug hunter's reply, made a NEW bug report, reposted info about the bug and included the GM's reply, then refuted that reply with evidence. It took nearly a half dozen back and forths like this before the Bug Hunters actually understood what I was reporting, and it's not because I used confusing language or wasn't descriptive enough. They simply misunderstood the bug I was reporting.
I'd also like to see a way to file a bug report in-game. That's long overdue, Runescape had that implemented before Eve Online even went gold. You don't want to be outdone by Runescape... do you?
As for feedback, I am very pleased that I'm getting email replies to my bug reports saying that something is or isn't a bug. As GMs have almost no idea what the intent is behind game mechanics and Bug Hunters specialise in that area, filing a petition to ask if something is a bug or not is about as useful as shaking a magic 8-ball - It will almost certainly give you the wrong answer and will give a different one every time you ask :p. It's nice that I can bug report a bunch of things that MIGHT be bugs and get replies stating which ones are bugs and which aren't.
Eve-Tanking.com - For tanking spreadsheet and resources. |
Nisse Owned
The Order of Chivalry
|
Posted - 2007.06.28 14:53:00 -
[9]
Edited by: Nisse Owned on 28/06/2007 14:52:55
Originally by: CCP Lingorm
Edited by: CCP Lingorm on 28/06/2007 14:41:52
Somethings to consider that I have been thinking hard on.
If we make all the bugs public then EVERYONE has access to use the information contained there in for what ever purpose they can. This means that we would be 'publishing' an Exploit manual. Not something we want to do. Conversely there is some merit in people comparing notes and trying to gather more information on the bug to make it easier for us to identify and then fix.
Security by Obfuscation has never really worked but there is a difference between Obfuscation and sensible exclusion of information.
We do have more detailed bug threads on the Bug Hunter Forums, but those are closed to the general public to prevent this information being put to nefarious uses.
If you have suggestions of a happy medium that can serve both results then I am ready to hear you suggestions.
Could someone please post a URL to this Mantis that is talked about please so that I can have a look.
http://www.mantisbugtracker.com/ for main site
http://www.mantisbugtracker.com/bugs/my_view_page.php
And second link for the mantis bugreport system... kinda serves as a example on how it works and no registration needed afaik 
Oh and also, on topic of revealing exploits, you can create bugreports that only devs can see iirc
|
Ikkajo
Minmatar
Illudium Space Products
|
Posted - 2007.06.28 15:04:00 -
[10]
I'm mostly a Bugzilla person, but I've also used Mantis as well, just not as extensively. I believe that both allow you to mark things as private - both an entire bug and individual comments within a report. In addtion you can create classes of users each with their own access and modification capabilities. This should allow you to work at the level that you need to - something coming in as an exploit can be marked private and kept out of the public eye relatively easily.
Whatever step you take here to make this more public would be a wonderful capability and yet again mark CCP as being the best MMO game dev company out there. (Try getting this level of responsiveness out of SOE.) A public bug tracker will also make your lives a lot easier as people can then see whether someone has reported the same bug as them and not submit another report. It will cut down on the initial triage that the bug hunters currently have to do but a huge amount.
--
Industrialist Carebear, CEO
Illudium Space Products: Where's the KABOOM!?
LP offers by corp at the LP Store DB |
|
|
Elissen
Amarr
The Arrow Project
|
Posted - 2007.06.28 15:13:00 -
[11]
At work we are using OnTime and I like it quite a lot. Granted, it is not a free product like Mantis or Bugzilla, but since it runs on MSSQL it would probaly fit better in CCP's infrastructure since they seem to be rather MS orriented. You also have the option here to mark defects as private or public. There is also an SDK available - I would guess that you can make something around it where you can publish internal defects back to a public system if you want to link it to your current bugtracking software.
----
Weeks of programming can save you hours of planning.
Jumpplanner v2.0 - Routeplanner for all jumpcapable ships! |
Akita T
Caldari Navy Volunteer Task Force
|
Posted - 2007.06.28 16:04:00 -
[12]
Edited by: Akita T on 28/06/2007 16:11:47
Two separate approaches, both with advantages, disadvantages and arguments debunking some of the preconceptions.
1. A forum for bugreporting.
CONS:
* possible exploits become more easily available to a lot of people
* might be annoying to manually move "bugreports" from the forum to the internal tracking system
PROS:
* a lot less workload for the bughunter team in processing bugreports. With information publicly available, players will usually just add their experience regarding a specific bug
* much more likely to SEE a bugreport, some people just hate the bugreporting system. Might be less of an issue if you improve it, but nevertheless, still an issue.
* easy overview of existing bugs. Players can avoid them sooner, a lot of people encouraged to test if they have the same issue, can get good feedback on a "fix" progress or simply a statement that it's not a bug, but a feature.
However, you CAN say "this is an exploit, people caught using it will be punished" and rely on the players themselves to make reports of exploits being used.
How many non-duplicate bugreports of actual bugs do you receive out of the "1000 per month" ?
I was under the impression that you're more interested in the QUALITY and "novelty" of bugreports rather than their volume.
Overall, the "pros" heavily overweigh the "cons" for this one, and some of the "cons" are actually not "cons" at all after a harder look.
Even better, you could simply MODERATE existing "exploit" level bugreports, move them to a hidden forum where only thread originator and people that already posted in it can access it, alongside devs.
Merge "exploit level" threads together in that section if they refer to the same issue, so that only people who were already aware of them are allowed to see the progress.
2. Improving the bugreporting system
NOTE : The" list is valid only for the CURRENT implementation of the bugreporting system.
Almost every item on the list can be "solved" with improvements.
* some people hate to re-login just to post a bugreport. Why don't you use the "forum cookie" instead ?
* there's no listing of existing bugs. Duplicate bugreports must make up a huge amount of the ones you receive
* no listing of "not a bug, but a feature". You must be receiving a lot of non-bug bugreports a lot
* you can't see, edit nor delete a bugreport you made. Makes it more likely to give up writing it instead of sumbitting it
* before, we had no feedback. Now, we have simple email feedback. Still better as nothing, but hardly appropriate. see below.
* inability to PROPERLY converse with other people who spotted the same bug, or the people tasked with fixing it. Feedback levels are sluggish at best, or almost inexistant in some cases. Having a bugreport "terminated because of insufficient details" is, at best, unnerving
As already said, these would be the points to focus if you plan to improve the bugreporting site.
Basically, the ability to track your bugreport as it's being analysed or even fixed, ability to see what other people are reporting related to the same bug, ability to read about and even post extra details to an existing (non-exploit) bug, etc.
And that's about it for a realistic breakdown.
Oh, and finally...
3. Integrating bugreporting with in-game experience
The most obvious thing that could be done (and actually SHOULD be done) is to integrate the bugreport site into the game itslef, probably via a CCP-operated, IGB-compatible "auto-trusted" site that only accepts IGB requests.
Basically, it's a "merger" of points #1 and #2, combining both their strengths but really, almost none of their weaknesses (depending on how you implement it, that is).
Char creation guide | Module/Rig stacknerfing explained |
ElfeGER
Black Nova Corp
Band of Brothers
|
Posted - 2007.06.28 16:12:00 -
[13]
some nice features could be:
- mark some defects/comments as public and allow us to see those (text/some screenshots)
- allow users to vote on open defects for fixing (votes from closed ones are returned)
- custom replies from BH so no unsuiteable reply is recieved
- email notifications on bug/defect changes/comments (ie fixed, will be reworked soon anyway)
|
Laendra
|
Posted - 2007.06.28 16:18:00 -
[14]
Originally by: CCP Lingorm
Edited by: CCP Lingorm on 28/06/2007 14:41:52
Somethings to consider that I have been thinking hard on.
If we make all the bugs public then EVERYONE has access to use the information contained there in for what ever purpose they can. This means that we would be 'publishing' an Exploit manual. Not something we want to do. Conversely there is some merit in people comparing notes and trying to gather more information on the bug to make it easier for us to identify and then fix.
Security by Obfuscation has never really worked but there is a difference between Obfuscation and sensible exclusion of information.
We do have more detailed bug threads on the Bug Hunter Forums, but those are closed to the general public to prevent this information being put to nefarious uses.
If you have suggestions of a happy medium that can serve both results then I am ready to hear you suggestions.
Could someone please post a URL to this Mantis that is talked about please so that I can have a look.
One thing to consider...not everyone uses information about exploits to exploit the system. Some use that information to verify that it is gone after every patch, since they invariably seem to reappear after various iterations of patches. Also, everyone knowing what the exploits are would serve to allow us to be better education on when they are being used against us, and to not inadvertently use them by mistake because we know what they are. It also brings to light exactly what exploits are out there, so that they can be better tracked to ensure the game-breakers are taken care of in a timely manner.
Besides, there is a precedent to this. GMs announce exploits fairly frequently, stating that "such and such action is now classified as an exploit. Anyone caught utilizing such and such will be dealt with by ripping out their eyesockets!" :) Posting them makes everyone aware of them, and you no longer have ignorance as an excuse.
-------------------
Brainstorm ideas to make EVE better:->http://eve.stormingbrains.org/index.php
|
Donathan Slade
Kay Korporation
Knights Of the Southerncross
|
Posted - 2007.06.28 16:57:00 -
[15]
I'm now posting here as per the other thread referred me here. Anyway, my point is this. Not so much an 'exploit' manual, but problems that are common that you get massive amounts of bugs on the same issue. This way we know you know about the issue, and can 1) stop flooding you with bugs for it. 2) know about it so we can try to avoid it if at all possible. 3) Not all bugs are exploitable, some are but we aren't asking for all exploits to be posted unless it was something like the POS bowling with titans/motherships that was needed to be posted.
|
Kazuo Ishiguro
House of Marbles
Zzz
|
Posted - 2007.06.28 18:50:00 -
[16]
Originally by: Nisse 0wned
Originally by: CCP Lingorm
Somethings to consider that I have been thinking hard on.
If we make all the bugs public then EVERYONE has access to use the information contained there in for what ever purpose they can. This means that we would be 'publishing' an Exploit manual. Not something we want to do. Conversely there is some merit in people comparing notes and trying to gather more information on the bug to make it easier for us to identify and then fix.
Security by Obfuscation has never really worked but there is a difference between Obfuscation and sensible exclusion of information.
We do have more detailed bug threads on the Bug Hunter Forums, but those are closed to the general public to prevent this information being put to nefarious uses.
If you have suggestions of a happy medium that can serve both results then I am ready to hear you suggestions.
Could someone please post a URL to this Mantis that is talked about please so that I can have a look.
http://www.mantisbugtracker.com/ for main site
http://www.mantisbugtracker.com/bugs/my_view_page.php
And second link for the mantis bugreport system... kinda serves as a example on how it works and no registration needed afaik
Oh and also, on topic of revealing exploits, you can create bugreports that only devs can see iirc
Link-ified it for you 
The worst case scenario is that someone finds and reports an exploit that the vast majority of players are willing and able to use (item/isk duplication, for instance), and the only way to undo the damage is take TQ offline and roll back the entire database after a fix is made. But the chances are that news of such an exploit would spread very quickly even without the report being made. Where the risks are limited, it makes sense to publicly announce exploits as at present.
I don't know how many bug hunters there are, but since they're already trusted with details of exploits, it would be easy to give them the ability to censor any exploit-related reports.
In any case, based on previous patch notes, I imagine that the vast majority of bug reports are not related to exploits. I reckon that the potential gains of a public bug tracker outweigh the risks.
------
Spreadsheets: Top speed calculation - Halo Implant tanking |
Gner Dechast
Gallente
Aliastra
|
Posted - 2007.06.29 23:40:00 -
[17]
Originally by: CCP Lingorm
... I am most keen to hear any suggestions that you have to improve the current site by increased functionality and/or improved usability.
...
What else would you like to see? What would make the site more usable?
I am not sure if this is a tool improvement need or your internal process improvement...
Please make sure bug hunters will request more/new/better details if they find themselves unable to reproduce reported problem. Preferrably via flagging submitted bug report AND dropping and email to the player (giving couple of days before closing the ticket, atleast).
NOTHING is more aggrevating and irritating and silent snuffing of your bug report just because a bug hunter didn't understand the explanation or it was entered somehow incomprehensible. Grown up human being MUST be able to ASK, wouldn't you agree?
Oh, and I was positively shocked almost to the point where I wet myself not so long ago when I received an email confirmation about my submitted bug report!! Holy ******! And I gave up making bug report long long ago, since the system was a black hole. Good progress, eventually this all might compare to a professional bug tracking and management system - now atleast it has re-enabled my input with feedback and followups.
I see alot of positive improvements in this are done and it makes me happy.
|
Scorpyn
Caldari
Infinitus Odium
|
Posted - 2007.07.03 06:26:00 -
[18]
It would be nice to be able to go back and edit a bug report to add information later if you have discovered something more about it.
|
SeismicForce
Clear Horizon Industries
|
Posted - 2007.07.04 06:36:00 -
[19]
What I'd also maybe implement is that the users have a profile of their hardware/software setups saved in the bug report system (optional of course). That way it would be easier to filter out problems with specific hardware/software. (Eg. if only Ati users are having the same glitch you could quickly see that)
|
Cyan Nuevo
The Blackguard Wolves
|
Posted - 2007.07.04 18:59:00 -
[20]
Heh, I also posted in a different thread (a while ago) that you should use Mantis. Here's how I imaging it would work: we all still submit bug reports through the current form, since giving us reporter access to the bug tracker would not be a good idea.  Then the bug hunters look at each bug, decide whether it's actually a bug or just spam (this has nothing to do with confirming the bug, just a visual overview) and also whether it is sensitive information. The bug hunter then reports the bug on Mantis, selecting "private" when reporting it if it's sensitive. Meanwhile, all EVE users have view access on Mantis.
How does that sound?
---
Proud Amarr pilot.
|
|
|
Tonto Auri
Vhero' Multipurpose Corp
|
Posted - 2007.07.04 20:51:00 -
[21]
Originally by: CCP Lingorm
Edited by: CCP Lingorm on 28/06/2007 14:41:52
Somethings to consider that I have been thinking hard on.
If we make all the bugs public then EVERYONE has access to use the information contained there in for what ever purpose they can. This means that we would be 'publishing' an Exploit manual.
Not really.
Each major project I saw have two tracking systems.
One, common, to track majority of wishes, stucks, glitches and such, and second, mostly called as security tracker, to gather reports related to exploits, leaks and other security related issues.
And mentioning bughunting department work in general...
I PERSONALLY HATE SUCH RESOLUTIONS:
Quote:
Thank you for your bugreport - ID:39536 Title: Exceptions when plottong course through assets
Unfortunately, your bugreport contained insufficient information to be of any use. Please review this thread for further information on submitting bugreports.
Your bugreport has been closed.
The BugHunter Team
Report ID: 39536
Title: Exceptions when plottong course through assets
Description: Got these errors each time I set destination/add waypoint over assets.
<snip exception text>
Reproduction Steps:
1. Log in at station,
2. open assets,
3. plot course across stations in it.
Log attached
1 file(s) attached to this report.
It *STILL* happened each time I trying to set destination before undock after login. And, in fact, not depend on sourse of waypoints. Assets/P&P/whatever... Doesn't matter.
And Yes, I have tried it after clearing cache folder.
And yes, I provide log and exact description of bur reproduction steps.
what else I should to give as info? My bank account credentials?
If You continue to answer in such manner, I can set up my CRON to flood bugtracker until You get all bugs properly checked and registered. But.. does it need to be that stupid? We all wise men and can solve problem without confrontation, I think.
--
. |
Manus Stuprare
United Eve Directorate
Ground Zeero
|
Posted - 2007.07.05 11:31:00 -
[22]
Personally I would be far more likely to report bugs if I could do so in-game. I suspect this would apply to many other people also.
--------------
Poisoning the Chalice: Smartbombs as a Counter to Nos |
Hamfast
Gallente
|
Posted - 2007.07.05 17:04:00 -
[23]
Originally by: Manus Stuprare
Personally I would be far more likely to report bugs if I could do so in-game. I suspect this would apply to many other people also.
QFT...
It seems to me that if one of the Petition options was "Report Possible Bug", then many items that could help could be automatically gathered at the time of the submission...
I have tried to submit a bug report before with the petition system and was informed you all don't talk to each other that I should use the website to report the bug... (They did send a link, as I remember, it did not support the in-game browser).
None of us is as dumb as all of us...
|
Cyan Nuevo
The Blackguard Wolves
|
Posted - 2007.07.05 17:53:00 -
[24]
Why is reporting in-game an issue? Alt+tabbing is easy, actually putting good info in a bug report is hard...
---
Proud Amarr pilot.
|
Hamfast
Gallente
|
Posted - 2007.07.05 20:02:00 -
[25]
Originally by: Cyan Nuevo
Why is reporting in-game an issue? Alt+tabbing is easy, actually putting good info in a bug report is hard...
Part of my reasoning is data could be gathered at the time of making the in-game bug report that the reporter may not even know about...
The other reason for being able to make the report in-game is the likely hood of the report... I am guessing here, but I suspect most folks will leave it up to someone else to report a bug if they have to alt-tab or leave the game to make the report... make it in-game and easy and you get more bug reports... more bug reports (even if for the same bug) means more data to find the bug.
None of us is as dumb as all of us...
|
Manus Stuprare
United Eve Directorate
Ground Zeero
|
Posted - 2007.07.05 21:20:00 -
[26]
Originally by: Cyan Nuevo
Why is reporting in-game an issue? Alt+tabbing is easy, actually putting good info in a bug report is hard...
Ok, let's say I've just discovered my first bug (oh happy day!). To report it I then have to:
- Alt-tab out of the game
- Find the bug report form - there's no visible link on the main site, which means I have to search
- The built in search is crap, so I end up having to use google
- Having found the site, I need to log in
- I need to look up my client build number
- Submitting log files must be done manually
- While I'm doing all this, I'm missing chunks of any in-game conversations I'm involved in etc.
With an in-game system most of this could be automated (plus if the information I submit isn't up to scratch it would be feasible to discuss this with a member of the bug hunting team in-game).
--------------
Poisoning the Chalice: Smartbombs as a Counter to Nos |
Cyan Nuevo
The Blackguard Wolves
|
Posted - 2007.07.06 04:45:00 -
[27]
Edited by: Cyan Nuevo on 06/07/2007 04:45:03
- Alt-tab out of the game
True story.
- Find the bug report form - there's no visible link on the main site, which means I have to search
- The built in search is crap, so I end up having to use google
http://bugs.eve-online.com, it's also linked on the left navbar if you're logged in to myeve.
- Having found the site, I need to log in
Yep, lots of good reasons for this. You have to login to play the game too. I don't see you complaining about that. Admittedly, it would be nice to automatically login to bugs.eve-online.com if you're on myeve.eve-online.com, but it's not biggie.
- I need to look up my client build number
It's filled in automatically, unless you're on SiSi in which case you have to hit Esc.
- Submitting log files must be done manually
Could be automatic, yes, but again no biggie.
- While I'm doing all this, I'm missing chunks of any in-game conversations I'm involved in etc.
True.
Also, many of the above minor inconveniences can be avoided by playing in windowed mode when you want to report bugs.
All in all, I think CCP's time is better spent actually fixing the problems than on the significant amount of work involved in integrating the reporting system into the game, especially considering the very small benefits.
Edit: typo
---
Proud Amarr pilot.
|
Manus Stuprare
United Eve Directorate
Ground Zeero
|
Posted - 2007.07.06 10:16:00 -
[28]
Originally by: Cyan Nuevo
All in all, I think CCP's time is better spent actually fixing the problems than on the significant amount of work involved in integrating the reporting system into the game, especially considering the very small benefits.
And I think it's an investment of time which would quickly pay dividends with an increase in the volume and quality of bug reports. Good job we're not both on the committee eh? :p
Anyway, my main point is just that the more convenient you make it for players to report bugs, the more likely they are to do so.
--------------
Poisoning the Chalice: Smartbombs as a Counter to Nos |
Jotan Veer
HUN Corp.
HUN Reloaded
|
Posted - 2007.07.06 12:10:00 -
[29]
Edited by: Jotan Veer on 06/07/2007 12:14:24
This was already mentioned but I feel strongly about it so I gonna write it down once again....can you please make sure that every time the TQ client is patched the new release name and client build is the default selection on the bug reporting page?
For example, currently it says Revelations 2: 33752 when in fact the current build is Revelations 2.01: 34381 (I think..).
For me it is a pain in the arse having to either quit from the game to check the version number of the splash screen or find the relevant ini file.
Or hell, just get rid of the whole version number thing, just have a server selection (test or live server or whatever) and a date when the bug was last experienced then you can easily query what version was running on the server in question at that time.
Sorry, it's just one of those things that make me feel 'nah, I can't be arsed to make a bug report today' sometimes.
HUN Corp. recruitment status: frozen
|
Cyan Nuevo
The Blackguard Wolves
|
Posted - 2007.07.06 19:08:00 -
[30]
Edited by: Cyan Nuevo on 06/07/2007 19:07:44
Originally by: Manus Stuprare
Good job we're not both on the committee eh? :p
I'll agree with you there.
Originally by: Manus Stuprare
Anyway, my main point is just that the more convenient you make it for players to report bugs, the more likely they are to do so.
Well, this is the pivotal point. I have a feeling players that are too lazy to submit reports via the current system would just submit lazy (aka bad) reports via an easier one. ("omfg my ship just blew up. plz fix thx.")
Edit: Stupid smilies, should have previewed.
---
Proud Amarr pilot.
|
|
|
|
|
| |
|
| Pages: [1] 2 3 :: one page |
| First page | Previous page | Next page | Last page |