Reset Password
Existing players used to logging in with their character name and moo password must signup for a website account.
- ReeferMadness 5m May the bridges I burn light the way.
- Leudo 1m
- hex37 9m
- Amiga 2m
- LegerdemainMouse 5m always sleepy zzzzz
- adrognik 8s
- Atheran 1m
- Grig 1m
- JakeyBoy 5m
- Veleth 4m
- MrJDucky2 3m
a Mench 6m Doing a bit of everything.
- Sulfurado 4m
- SoulTune 6m
- KalopsiaTwilight 11m
- GrimButterCat 1s
- deskoft 21m
- Dystopia2102 31s
- sukebug 18s
- Baguette 9m bitchmade
- RedProtokoll 22m
- CookieJarvis 13m
- BCingyou 8s
- Wonderland 1m
- fopsy 2m
- asdronin 19h
And 30 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!