Dorandraco at 18:21, 21 September 2025

2025-09-21T18:21:09Z

← Older revision		Revision as of 18:21, 21 September 2025
Line 33:		Line 33:
	# An item mentioned not being in the room.		# An item mentioned not being in the room.
	# An item not mentioned and integral to functionality being in the room.		# An item not mentioned and integral to functionality being in the room.
			# Insensitivity towards a culture, race, or other demographic group, real or fictional.

	When entering in a <code>typo</code> 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.		When entering in a <code>typo</code> 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.
Line 40:		Line 41:
	The more detail you can provide, the more quickly staff can fix the typo and move onto the next.		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.		The typo queue is very large and mostly not as serious as the bug queue, so do not be surprised if it takes a while for staff to get to it.

Sharl: Copy/Pasted website info

2025-05-29T13:22:18Z

Copy/Pasted website info

New page

When using <code>bug</code> or <code>typo</code>, the following information is automatically provided for staff:

# What room you used the <code>bug</code> or <code>typo</code> command in.
# Who submitted the typo or bug.
# When the typo or bug was submitted.

=== Bug ===
The <code>bug</code> command should be used for things like:

# Skills not functioning properly.
# Verbs not functioning properly.
# Mobs behaving improperly.
# Items not functioning properly.

When in doubt, <code>bug</code> it.

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

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

When a bug is serious, <code>report</code> 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 <code>report</code> 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 <code>bug</code> 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 <code>typo</code> command should be used for anything relating to creative. This includes:

# Typos in any description. Things like <code>$oh</code> and <code>$adj1</code> and <code>blue|green|yellow</code> are typos, not bugs.
# An item mentioned not being in the room.
# An item not mentioned and integral to functionality being in the room.

When entering in a <code>typo</code> 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.

Bug and typo - Revision history

Dorandraco at 18:21, 21 September 2025

Sharl: Copy/Pasted website info