I hope you can understand that this isn't really helpful. What would be helpful is telling us what the error message says, and at what point, exactly, it crops up. Do you get the error message when you load the page, or is it when you select Scopa, or is it when you search for pre-existing bug reports of the same issue (which I hope you are doing), or when you click on "Create a new report", or when you actually submit the report?
I'm the dev of Twilight Imperium and have over 1300 unique error codes which pinpoint specific cases that should not happen, in case they ever occur.
Well they've never helped nor have I ever paid attention to them. If I'm on a phone repair line or something and the person on the other end asks me "can I get the error number", in my mind it tells me they have no clue and aren't really interested in helping.
I can only speak as one developer, but they have been incredibly helpful for me. Knowing a short error code instantly shows me the part of the program that produced it. Just knowing the behavior and context is not as helpful, and much more effort for the reporter than telling me the code is "735".tbhp wrote: ↑23 October 2026, 20:30Well they've never helped nor have I ever paid attention to them. If I'm on a phone repair line or something and the person on the other end asks me "can I get the error number", in my mind it tells me they have no clue and aren't really interested in helping.
I think the nature of the bug should be its own source for diagnosis, not some error message the computer automatically puts out.
I am a software engineer and yes, I believe it is possible for error messages to give relevant information. It obviously depends on them being well placed and well written, and I don't have a huge amount of confidence in that being the case here. But it should still be a standard part of any bug report or help request.
The error message is supposed to be the diagnosis! And yes, in fact, the reason I want to know the error message is because it can tell you how to solve the issue! We users may or may not be able to solve it, but the error message (along with the sequence of events leading up to it) is the first step in a solution.
Well then, you don't know what you are talking about. Error numbers frequently only originate in one place in the code, or at least a very small number that should be practically identical. Knowing the error number tells you exactly where and when things went wrong.
And what, pray tell, is the "nature of the bug" when a web page doesn't load? There are probably fifty different things that could have gone wrong to make that result; how do you know what the problem is?
