CLOK BBS

From the help file: The bugcheck command may be used to view the status of recent bug reports that you submitted. You may specify an optional numeric argument to show a specific number of bugs (It will show 10 by default), up to 50. Example: bugcheck 20 - shows the last 20 bug reports submitted.

You may use this to check bugs that you have submitted. This is a trial run of the command. Any use of it to pester, rage at, or otherwise annoy GMs will mean that either you lose access to it, or everybody does.

Any person to use the command to say, "I submitted a bug report X days ago and it's still open" or anything similar will lose all access to this command.

Please remember that bugs and errors are prioritized and not necessarily addressed in chronological order. Sometimes things fall through the cracks, and sometimes typos happen while closing bugs (which would mean the wrong bug got closed). If it has been months since you submitted a bug report, you could try sending a report or posting something on the boards. And now, you can refer to the bug by number when you do that. Please do not resend the bug report.

Thanks to Jirato for making this and all the other commands that make tracking bugs possible.

I tried this out today and got "Invalid command. (You may type help commands to get a list of all available commands.)" I'm not sure if this already got zapped or if I don't have sufficiently recent bug reports for it to work.

The help bugcheck does seem to function properly, though I'd like to request a brief sentence about not harassing GMs be added there as well. Some players may find out about the bugcheck command via 'help commands' before properly reading the warning on this board.

About the invalid command thing, sorry, my bad. This is basically an (extremely) stripped down version of a GM-only tool, and I forgot to remove the check that prevents non-GMs from using it. It should work fine now.

Awesome, it does indeed work now. Thank you for this nifty command.

I had thought I had submitted a bug report to the effect that crafted rigid leather armors are unwearable (red message only when I tried to wear them).

Does the absence of any mention of this on my bugcheck list mean I forgot to submit the report or else the report got lost somewhere, and thus either way I need to (re) submit it?

Did you make sure to use bugcheck 50 to view the maximum number of past bug reports?

Kent wrote:I had thought I had submitted a bug report to the effect that crafted rigid leather armors are unwearable (red message only when I tried to wear them).

Does the absence of any mention of this on my bugcheck list mean I forgot to submit the report or else the report got lost somewhere, and thus either way I need to (re) submit it?

When in doubt, re-submit.

We decided to limit the list to 50 for players for various reasons, but I can tell you that none of your 247 bug reports have the word 'rigid' in them.

Jirato wrote:

Kent wrote:I had thought I had submitted a bug report to the effect that crafted rigid leather armors are unwearable (red message only when I tried to wear them).

Does the absence of any mention of this on my bugcheck list mean I forgot to submit the report or else the report got lost somewhere, and thus either way I need to (re) submit it?

When in doubt, re-submit.

Ok thanks for the answer. It seems the bug has in fact been fixed, perhaps due to the bug report of another player, otherwise I would re-submit it. I can wear the rigid armor I just made.

Okay, I have a suggestions the GM's will probably love.

Could the Bug command require a minimum of, say, four words in order to be processed as a bug report?

For example, we have sometimes mistakenly typed in Bug Check instead of Bugcheck and it submitted the one-word report 'check'. Also today I meant to type in 'Help Bug' and typed 'Bug Help' instead to similar result.

So under my suggestion, a report with too few words will not submit a report but rather a message to the effect that that's too short a report.

I do love the suggestion, so: implemented!