6 replies to this topic

[Pyro699]

This is mainly for all you keener's out there who are very good at pointing out to people who don't like to read, that this is a proper way to inform the programmer that there is an error and how to fix it. First of all, the errors should always be placed in the Bug Tracker. It is a system that has been designed for the purposes of reporting bugs and letting the team deal with them. Occasionally (more often than not) they are posted in topics and new posts are made; the team is tired of closing them or pointing people to the bug tracker. So if people are not going to listen to where they should post them, they should at least post them in a manner than actually provides us with a bit of information.

The only reason to post an error that you have encountered when using our programs is to hope that we will be able to fix the issue and you will then be able to use the programs without errors. That being said, here are some examples of VERY BAD error reports (these are real and quoted properly).

Spoiler

*i could only find one, but i know there are more because ive encountered this problem way too often... feel free to link me to other bad posts and ill put them in here

copley, on 28 June 2011 - 05:18 AM, said:

It keeps showing an error to send to neotracker every time I go to open it.

That being said i am now going to create a template for people to copy/paste that will provide very good information to the developers so that they know exactly what it is they are looking for and can fix it with few questions asked to the user.

[b]Operating System:[/b] <Windows; Wine/Linux; Mac>
[b]Error Code:[/b] <Error Code; Put 'None' if there was not one>
[b]Error Message:[/b]
[quote name='error']<The copied and pasted error message>[/quote]
[b]What i was doing:[/b]
[quote name='task']<The operation you were trying to preform when the message popped up>[/quote]

This will both make my life easier as a programmer, and your life easier as someone who doesn't know how to report bugs properly Those of you that link to this post, i thank you very much If you were directed here and actually read it all and learned something, i thank you too...

~Cody

[Waser Lave]

I think the main problem is that people see a load of reports already posted and can't see anything being done about those so they figure that posting bugs in there won't result in a quick resolution.

[Pyro699]

They are not resolved quickly because they lack information. If i know exactly what is causing an error, ill go fix it immediately; but i do not want to deal with asking stupid questions to try and find the solution. Its not a guessing game.

[Neoquest]

Hehe *looks embarrassed at fail error report* I'll use this in the future, thanks Pyro.

[iargue]

Waser Lave, on 28 June 2011 - 09:04 AM, said:

I think the main problem is that people see a load of reports already posted and can't see anything being done about those so they figure that posting bugs in there won't result in a quick resolution.

I fix bugs very fast. Unless its just a network error.

[RayX00]

Operating System: <Windows>
Error Code: <Error Code; Put 'None' if there was not one>
Error Message:

error said:

<Used to receive error messages on the init function and other bits of python, but only for the first time I install the score sender.>

What i was doing:

task said:

<Says the program is running, but no new windows or icons.>

[soul__stealer]

RayX00, on 16 December 2011 - 08:46 AM, said:

Operating System: <Windows>
Error Code: <Error Code; Put 'None' if there was not one>
Error Message:

What i was doing:

Uh... Did you fail to read the first post... That was simply a template that should be posted in the relevant Bug Tracker thread.


In any case... look in the SysTray to see if the program has actually launched...