Epitaph Help
Categories
Concepts Creator Commands Creator Tutorials Games Innate Commands Known Commands Lord Npc Objects Playtesters Rooms Rules
Errors
Description
This command is used to manipulate the errors stored in the SQL database. The different options to the command allow different sets of errors to be selected, you can choose to see bugs, typos, ideas, all or closed (fixed and denied) reports.
'errors' by itself will show errors in the directory you are currently in, other options let you choose more specifically where to look for reports. The recursive option allows you to view bugs in subdirectories of the directory you are looking in.
Reports can be listed in order of date, filename or reporter and the offset option allows you to choose a number (in relation to the number of reports in the query, not the bug id) to start looking at. Use 0 to start at the first report.
Use 'errors mine' to find all the errors assigned to you and 'errors assigned <person> to find all the errors assigned to another person. You can also find all the reports made by a specific person with 'errors by <person>'. 'errors id <bug id>' lets you view an individual report matching the id number.
When run, the command will show the first report in the your current query results. At which time you have a lot of nice commands of which the most important is 's' which will change the status of the bug and send a reply to the person who made the bug.
If you can see the bug report has been made incorrectly and really belongs in another directory, you can forward it with the 'f' command.
Commands
f n Forward and delete error to directory n. s <status> <cat> Change the status of the bug. The basic use of this command is: s FIXED, or s DENIED, or s THANKS. This will change the status of the bug correctly and send a standard message to the recpient. You can send a custom message by going: s FIXED custom. You can send no message at all by going: s FIXED none. There are short forms for all the types used in this command, they are: f -> fixed, d -> denied, t -> thanks, n -> none, u -> custom, c -> considering, i -> fixing. So you can do: s f n, to set the status to fixed and not send a message. t <type> Update the type of the bug. This allows you to change the bug to be an IDEA, TYPO or BUG. ie: t TYPO a <person> Assign the bug to the specific person. o <category> Updates the category of the bug. The category is the thing it was attached to. eg: c ROOM i, l List the bugs in columns, similar to the web page. v Redisplay the current bug. c Comment on the bug. n/+ Next error. p/- Previous error. g Go to error. q Quit. h/? This help file.
Example
errors errors dir /d/guilds/assassins closed recursive by newest starting at 20
Syntax Forms
errorserrors recursiveerrors dir <dir>errors dir <dir> recursiveerrors {bug|typo|idea|all} open by {newest|oldest|reporter|filename} starting [at] <offset>errors {bug|typo|idea|all} open recursive by {newest|oldest|reporter|filename} starting [at] <offset>errors {bug|typo|idea|all} closed by {newest|oldest|reporter|filename|fix date newest|fix date oldest} starting [at] <offset>errors {bug|typo|idea|all} closed recursive by {newest|oldest|reporter|filename|fix date newest|fix date oldest} starting [at] <offset>errors dir <dir> {bug|typo|idea|all} open by {newest|oldest|reporter|filename} starting [at] <offset>errors dir <dir> {bug|typo|idea|all} open recursive by {newest|oldest|reporter|filename} starting [at] <offset>errors dir <dir> {bug|typo|idea|all} closed by {newest|oldest|reporter|filename|fix date newest|fix date oldest} starting [at] <offset>errors dir <dir> {bug|typo|idea|all} closed recursive by {newest|oldest|reporter|filename|fix date newest|fix date oldest} starting [at] <offset>errors hereerrors file <file>errors object <object>errors {bug|typo|idea|all} mineerrors mineerrors {bug|typo|idea|all} assigned <person>errors assigned <person>errors id <bug id>errors status <bug id> <status>errors status <bug id> <status> <reply>