Explore the moo:

Welcome to: Cosmic rage!

By Nathan Tech!

Web view

You are in the web view for viewing help files online in your browser.
Viewing category general..
back to help list

general help: Reporting

Intro to Reporting

A MUD like Cosmic Rage runs thousands of lines of code daily, and occasionally, something goes wrong. These issues may involve code errors, descriptions, outcomes, or even behavior. Using the report command, you can contact the hosts to address any problems. This help file provides guidelines to ensure your reports include the information we need to resolve issues effectively.

General Reporting Guidelines

When submitting a report, consider these three key questions:
1. What were you doing when the issue occurred?
2. What did you expect to happen?
3. What actually happened?
These guidelines apply to most report types. Specific details for different categories are provided below.

Bug Report: I issued a command and got a traceback.

A traceback occurs when game code breaks, interrupting the action you were trying to perform. These reports go directly to the coding team and should include:
1. The command you typed when the traceback occurred.
2. The traceback ID using the reporting wizard.
3. The object related to the command, if applicable (e.g., a hammer).

Typo Report or Force RP: There's a typo or Force RP issue.

Typo reports cover misspellings or errors in descriptions, names, buy options, and similar items. Please include the following in your report:
1. A room: Submit the report from that room.
2. An object: Attach an example of the object for easier tracking.
3. A help file: Include the help file's name.
For Force RP issues, see the relevant help file for more details.

Extra Information: A help file is missing information or a command.

If a help file lacks information, include the name of the file and the missing details in your report. Your suggestions may even be used to update the file.

Harassment: I am being harassed or bullied.

The staff takes harassment reports seriously, prioritizing immediate investigation. To expedite the process, include logs with clear examples of the harassment. If reporting on someone else's behalf, logs are doubly important. For details on what constitutes harassment, refer to the associated policy.

Command: A command is producing an unhelpful message.

If a command gives an unclear response (e.g., "You can't do that right now"), submit a report. Include:
1. The command giving the issue.
2. The object you were interacting with.
3. The location where you typed the command, if relevant.

Misc: My report does not fit any of the above.

For miscellaneous issues, follow the general guidelines in the first section. If it involves:
1. An object: Attach the object.
2. A broken room: Submit the report from that room.

In Conclusion

While we won't penalize anyone for miscategorizing reports, submitting them to the correct category improves efficiency. By following these guidelines, you help us resolve issues faster and minimize back-and-forth communication. We hope this guide makes reporting smoother for everyone.

Recommended help files: rphelp Forced Role Play Forced RP,help assistin.
--------- End of file -------
Back to the top of the file
Back to help file list

Why not explore the moo!