This is the full version of the HELP on BUG filing, reviewing, rating and categorisation as summarised in HELP DEVELOPMENT.

Reporting a bug is when you tell us about something in Avalon not working correctly, be it a minor typo, an ability misfiring, or something of major and gamewide importance: nothing is too small, nor too serious to merit BUG inclusion. Do not leave the task to somebody else if you know of a bug. Take the responsibility yourself. Abuse of bugs is one of the few actions in Avalon "beyond the pale" as far as the liberal gaming environment and those guilty of bug-abuse will be treated severely. Conversely, those habitual about bugfiling genuine problems in a considered and well-written fashion will find unexpected benefits popping up now and then as the Gods smile on much-appreciated diligence.

Syntax: BUG <text>.

The BUG command allows you to log the specifics of some error or malfunction in the Avalon gamesystem or an issue requiring immediate attention. Keep succint, include item numbers where possible, ALWAYS try to include a quote from text direct from Avalon to identify the issue and any commands you used exactly as you used them together with other circumstances you think relevant. Be ready to demonstrate the bug again. If it cannot be recreated, it may be better to not bugfile until it happens again - and instead talk to one of the sage/guru deities direct first.

Syntax: CATS (short for CATEGORIES).

It helps if you place your bug correctly in the category or categories it is best associated with including the profession, the skill and the aspect of Avalon best fits the issue. CATS shows you a list of all bugfile categories.

Syntax: BC <bug number> <category>/<person> and NOBC <bug#> <category/person>

Appends the specified category or the person you designate to your bugfile entry so that person shares control of the bugfile entry and the bug is in a category with others of its type. You can remove a category from a bug or a person from access to a bug using the NOBC command; the opposite of BC. Remember a bugfile entry can have many categories.

NOTE: you may block bugs from being seen by anyone save those of high rank in the associated category by BC'ing PRIVATE as one of its categories; or BC'ing SECRET to allow only the administration to see it.

REMEMBER: if you find out later a bug is not a bug, BC NOT against it and remove the other categories, or BC FIXED against it if it has been fixed.

Syntax: BUGS [<name>].

You can type BUGS at any time to see outstanding bugs reported (i..e. originating) in your name including any categories attributed. You can see the bugs filed by others and their categories too unless they are private/secret.

Syntax: FIXED.

Shows you bugs fixed under your name.

Syntax: INDEX <category> or INDEX <name>.

Shows you all the bugfile entries per that category or bugs by or including the person you name, i..e. bugs that person filed or bugs their name was added using BC as an interested party.

Syntax: EDIT <bug number> <new text>.

This command places the <new text> in place of the previous text for a bugfile entry and can only be done by the person who entered the bug, a persona listed with the bug via BC, or one of the administrative deities.

The better you write up your bug and the more accurately you list its category or categories, the faster it will be dealt with and the faster it will be ultimately fixed.