Bug Reporting on Test Server

[Namdarie]

/bug any bug with as much detail as possible.
Bug reports should at least contain answers to the following: What, Where, When, How with Reproducibility steps when ever possible.

/bug will pull your present chunk, location, character name, adventuring level, class, and race. So if you have a stuck bug, or a floating rock, please /bug from that location so it is included in the report automatically.

Example: (My testers will laugh and point out our internal bug procedures to me but I won’t ask you to follow those yet )
Title: Unable to Cancel camping.

1. /camp
2. Timer Starts
3. Run forward
4. Timer never stops

Result: You camp to character select

Repeatable: Yes

Bugs such as reproducible crashes also include base hardware specs.

Petition only emergency type issues that you can not recover from.

If you follow this type of procedure it helps us to confirm your reports in a timely manner and get it out to the folks that fix these issues sooner!

An example of a bug that won't help us much:

Title: This Sword isn’t doing any damage.

No further information other then what is automatically pulled by /bug.

Out of the thousand of items this would require us pulling your character data and then tracking all swords in that characters record history. Not efficient at all, but if we get the following.

1. What is the swords name?
2. What slot was it equipped in?
3. What was the name of the NPC you where fighting against with this weapon?

With those questions answered we can look up the sword, check it out in much further detail and get the data into the hands that fix them for you!


Ed Hocking (Namdarie)
Quality Assurance Manager
Sigil Games Online