Jump to:
Assist & Report
Beta & Gamehelp
Bug & Typo

Proper Channel Usage

There are a number of different channels players can use to communicate or bring something to staff's attention. Below is an overview of the available channels, and when and how to use each.

Assist & Report

Assist

assist messages are sent to all staff who are listed as STAFF ON DUTY in the WHO list. A staff member might be on duty for a stated purpose (for example, "I am available to convert the old metal ingots to the new format"), or simply to show that a staff member is available.

If no staff is listed as being on duty, assist messages will not go through. Please use report if it is an emergency.

Report

If you feel that another player is harassing you, immediately report to alert staff to the situation. You should also log the incident and email cs@unwritten.net. A staff member will notify you if a log is unnecessary.

All uses of the report command are logged until the next reboot. If no staff are currently available, they will be able to view your message later.

Other correct usages of report include:

  1. "I have found a bug that allows me to duplicate money."
    • Why: this is serious. Staff need to know about it before anyone else knows about it. Depending on the nature of the bug, posting it may be a bad idea. When the bug is serious, do not just report a problem. When reporting a problem, always file a bug report first so it is entered indelibly into the bugtracking database.
  2. "Look at this cool roleplay that is going on right now!"
    • Why: staff can give RPAs to roleplay, but only if they're watching. This is a good thing to let them know.
  3. "I'm around for my 3pm appointment with <merchant> that we made IC previously!"
    • Why: sometimes staff forget, and sometimes people's logins get missed. This is helpful to them!
  4. "I was told to report to get my fame item!"
    • Why: if you're told to use report, use it!

Improper usages of report include:

  1. "I think there's a typo in this helpfile."
    • Why: use the typo command or post.
  2. "We just had this awesome roleplay! You should give an RPA to <player>!"
    • Why: GMs can't bonus for roleplay they don't see. Send logs to ia@unwritten.net.
  3. "Can DeSharlet do an alteration for me? I'd really love one!"
    • Why: do not use report to ask for alterations. If a merchant's being run, staff will let people know!
  4. "How do I request a fame item?"
    • Why: use the helpfiles or post on the forums.

Beta & Gamehelp

Beta and gamehelp can be turned on or off using the settings command, i.e. settings beta on/off, settings gamehelp on/off. To use them, type beta <message> or gamehelp <message>.

Beta

The beta channel is for general light socialization, discussion of matters related to beta changes or new functionality, and questions about said changes. It is not for discussing what your dog just did, that you made a typo during RP, coordinating IM chats, or conveying any IC information whatsoever. For OOC extensive socializing or commenting on current RP, use the oocwhisper command with other players in the room or take it outside of the game.

Gamehelp

The gamehelp channel is for questions about how to play the game. gamehelp should never have anything but game-related content on it. Appropriate use of gamehelp includes clarification on lore, guidance on using the chargen, and questions on syntax. It is inappropriate to ask questions that are considered IC information, such as where an item can be bought, where to find a spell, where other players currently are located, etc.

Bug & Typo

When using bug or typo, the following information is automatically provided for staff:

  1. What room you used the bug or typo command in.
  2. Who submitted the typo or bug.
  3. When the typo or bug was submitted.

Bug

The bug command should be used for things like:

  1. Skills not functioning properly.
  2. Verbs not functioning properly.
  3. Mobs behaving improperly.
  4. Items not functioning properly.

When in doubt, bug it.

When using bug, be as specific as possible. Things our coders like to see that let them solve things immediately:

  1. The exact command entered.
  2. The short description of any item involved.
  3. Any special circumstances that you think might come into play (tags, effects, etc.)

When a bug is serious, report it. Serious bugs involve those that provide item duplication, infinite exp/money/skillgain exploits, game-crashing, character/saving room corruption, and the like. Do not just report a problem. When reporting a problem, always file a bug report first so it is entered indelibly into the bugtracking database.

Bugs that are less serious and require a log or more detail than is practical to put into a bug report can be posted to the forums.

The bug queue is kept small and is tended to much more quickly and frequently than the typo queue given the more serious nature of bugs.

Typo

The typo command should be used for anything relating to creative. This includes:

  1. Typos in any description.
  2. An item mentioned not being in the room.
  3. An item not mentioned and integral to functionality being in the room.

When entering in a typo report, please make sure to input where the typo is and what the typo is. A single room can have true objects, fake objects, furniture, plants, NPCs, items, items for sale, emotes, and more.

Typoing a single sentence or word and having it only read "silvery" is not nearly as intuitive as a typo report reading, "room emote; the word silvery should be silver." This turns a simple millisecond change into a serious hunt that can take quite a while; it can be like finding a needle in a haystack.

The more detail you can provide, the more quickly staff can fix the typo and move onto the next.

The typo queue is very large and not as serious as the bug queue, so do not be surprised if it takes a while for staff to get to it.