Reset Password
Existing players used to logging in with their character name and moo password must signup for a website account.
- Gaijin_Guest 12s [The Drome]
- F9DFCQ 4s
- Rillem 44s
- Veleth 49s Vampires don't sparkle.
- Sivartas 5m I make the Grinch look happy.
- Enven 14s
- NightHollow 33m
- Emily 3m I lost myself, in the dark charade.
- BubbleKangaroo 49m
- Nepika 1h
j Fengshui 9m
- Komira 4h
- Vanashis 7m
a Mench 37m Doing a bit of everything.
- zxq 58m
And 26 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

How To Submit A Good @Bug
Guidelines increasing the chance your issue will be fixed

Hi everyone!

Going through the bug backlog, I've noticed a lot of issues that have insufficient information in order for me to actually address them. So, like when I worked QA many years ago, I am passing on the knowledge of what makes a successful bug report.

When submitting a bug report, I have a specific set of information I am looking for:

1. What did you do. Step by step is best but it doesn't have to be. This should include what item you were interacting with, where you were interacting with it, and so on. As many details as you can provide as possible.

2. What you were expecting to happen. If it's obvious, this isn't always necessary but it can help a lot in contrast to..

3. What *did* happen, a traceback, item dupes, so on.

Most often, the reports I'm receiving miss details on step 1. If I just get two or three, and I use the command and it works for me, I don't really have a recourse to know what to do next.

So please, please, please include as many details as possible in your bug reports.

Thank you!