Apparently, the LUA error reports submitted from the ingame prompt go straight to darkgod (so I've always assumed) but what about addon's that trip one? Is there some way to create a publicly visible archive of those that haven't been dealt with yet? For that matter, on occasion, some of the coders around have submitted a bug report along with code to fix the problem. Perhaps this would encourage others to submit solutions to a particular problem? (though accepting them would of course, still be at the discretion of DarkGod...)
Is this even remotely possible/feasible?
Edit: I don't know how remotely possible/feasible this would be, or how helpful it might be in quashing bugs itself, without a more formal bug report... And maybe this should have gone under the development forum in it's own right, as well?
Publicly available Lua Error archive?
Moderator: Moderator
-
Crim, The Red Thunder
- Sher'Tul Godslayer
- Posts: 2000
- Joined: Fri May 07, 2004 8:26 pm
- Location: Nahgharash
Publicly available Lua Error archive?
Currently playing under the name Aura of the Dawn 4 down, 227 to go!
Proud author of Orc Pit Restoration Project, Faction Allies, Dwarven Adventurer addons
Proud author of Orc Pit Restoration Project, Faction Allies, Dwarven Adventurer addons
SadistSquirrel wrote:DarkGod has two arms, one with an opened hand, one with a closed fist. You got the fist.
-
Hachem_Muche
- Uruivellas
- Posts: 744
- Joined: Thu Nov 18, 2010 6:42 pm
Re: Publicly available Lua Error archive?
I agree that having searchable access to in-game reported bugs would be a useful feature. Having never seen these reports myself, I assume they include other potentially useful information, such as character info, addon-info, etc.,
The game (while on-line) could also search a database of submitted bug reports to determine if a bug is new or has been previously reported by others.
"You have found a new bug! Please report it!"
Other possible improvements to in-game bug reporting:
Expand the size of the description text box for reporting the bug. The one-line space just encourages terse reports that may not contain enough detail.
Make the bug reporting prompt movable, so that you can drag it around with the mouse and see what's behind it on the game screen. It would be best if the window was detached from t-engine so that players could switch focus back to t-engine, and, where possible, review the game log, etc.
A way to trigger a bug report in-game without a lua error. So if a player sees a problem that doesn't crash the game (like "I equipped this new artifact and my quiver disappeared") they can submit an error report without going outside of the game directly to the forums.
The game (while on-line) could also search a database of submitted bug reports to determine if a bug is new or has been previously reported by others.
"You have found a new bug! Please report it!"
Other possible improvements to in-game bug reporting:
Expand the size of the description text box for reporting the bug. The one-line space just encourages terse reports that may not contain enough detail.
Make the bug reporting prompt movable, so that you can drag it around with the mouse and see what's behind it on the game screen. It would be best if the window was detached from t-engine so that players could switch focus back to t-engine, and, where possible, review the game log, etc.
A way to trigger a bug report in-game without a lua error. So if a player sees a problem that doesn't crash the game (like "I equipped this new artifact and my quiver disappeared") they can submit an error report without going outside of the game directly to the forums.