Existing players used to logging in with their character name and moo password must signup for a website account.
- Raven 4m I lost myself, in the dark charade.
- AntiqueBeast 17m White grace, hidden in the dark.
- Mattsc 41s
- Sivartas 22m
- JanekSembilan 1h
- VermilionGrin 1h
- Mikael 1m youtu.be/WM33Hr94SKw
- Sulfurado 1m
- Terrible_the_duck 52s
a Mench 1h Doing a bit of everything.
- whatislove 2h reputation is whoever holds a bigger gun
- Euclid 9s
- zxq 13m Tools: https://ansicolortool.neocities.org
- NickRosso 12h
- Fay 46m
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!