Forums » Bugs
verbose
Ray,
For us that do not regularly deal in this language, could you please explain the verbose command and what circumstances we would use /verbose 9, /verbose 5 or /verbose 3 to generate error logs for different types of problems?
For us that do not regularly deal in this language, could you please explain the verbose command and what circumstances we would use /verbose 9, /verbose 5 or /verbose 3 to generate error logs for different types of problems?
You missed /verbose 8. I was assuming that the different numbers stood for how detailed the log would be written in terms of in-game events, because verbose literally means wordy. But now that I think about it maybe each number may correspond with the graphics activity, network activity, sound activity, etc.
/me pokes Raybondo for a better explanation
/me pokes Raybondo for a better explanation
And another question...what is the 'ending' command for /verbose # ? Is it /endverbose # or what?
/verbose 0
That sets it to "normal" responces only.
That sets it to "normal" responces only.
/verbose # sets the verboseness of the error messages. Setting it to 0 basically 'turns it off'.
1 is some, 2 is more, 3 is even more, etc... I think we really only have up to level 5 and setting it higher doesn't matter. There are still a lot of msgs that should be generated at higher levels but it's a matter of us adding the msgs and we tend to add msgs for only certain actions.
They're mainly used to make sure the client received certain events from the server during debugging.
1 is some, 2 is more, 3 is even more, etc... I think we really only have up to level 5 and setting it higher doesn't matter. There are still a lot of msgs that should be generated at higher levels but it's a matter of us adding the msgs and we tend to add msgs for only certain actions.
They're mainly used to make sure the client received certain events from the server during debugging.
Woohoo, I guessed right!
Understood...thx!
Should we routinely use the verbose command if we are trying to reproduce a bug or, are there circumstances where you don't want that information or our errors.log file?
Also, if the file is required, should we clear it with a text editor before using verbose to make it easier on you?
Should we routinely use the verbose command if we are trying to reproduce a bug or, are there circumstances where you don't want that information or our errors.log file?
Also, if the file is required, should we clear it with a text editor before using verbose to make it easier on you?
Yes, if you are trying to reproduce a bug, then the verbose messages are helpful; at worst, they don't do any harm. It's just hard to see what's going on with all that stuff scrolling (although I bet in MultiLog it's pretty inconsequential).
Generally speaking, no, don't clear it.. just be sure to gzip it or something before sending. :P It's helpful to get the whole sequence of events starting from the initial log on. It helps if, right at the time you do reproduce the bug, you say something identifying in the log.. perhaps if you /msg yourself something and point out to us what it is. We can then synchronize your log with the server logs.
Generally speaking, no, don't clear it.. just be sure to gzip it or something before sending. :P It's helpful to get the whole sequence of events starting from the initial log on. It helps if, right at the time you do reproduce the bug, you say something identifying in the log.. perhaps if you /msg yourself something and point out to us what it is. We can then synchronize your log with the server logs.
Good idea, a1...gee, you're tho thmart!