Existing players used to logging in with their character name and moo password must signup for a website account.
- Acupa 2m
- Pladdicus 22m uh
- PinkFox 10m
- PainFeeler 35m
- whatislove 5s
- Sulfurado 53m
- Burgerwolf 2m PANCAKES
- VermilionGrin 14s
- AdamBlue9000 3m Rolling 526d6 damage against both of us.
- Mikael 8m A soul cant be cut.
- Rillem 8m Make it personal.
- SmokePotion 1m Right or wrong, I'm getting high.
- Raven 2h I lost myself, in the dark charade.
a Mench 6h Doing a bit of everything.
- zxq 37m Tools: https://ansicolortool.neocities.org
- Vanashis 48m
- Sivartas 1h
And 18 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

make @bug's non-yes response be no
This is very bad design

@bug should recognize everything that isn't explicitly y or yes, as no. Because at current, you can do things like, go to @bug something, see your hated rival and then BOOM, type attack rival, and still be in the bug menu. Having to type @abort to get out of type selection. There's a lot of other reasons you'd not want to have the command to proceed, but @bug very definitely should work like the following example

@bug

y/yes to the warning about other people

proceeds to bug type selection.

@bug

n/no or literally anything else,

Aborts the command instantly without proceeding to type selection.

FUCK I WROTE THAT WRONG BECAUSE I"M BAD!

Make it @ABORT! Not No.

Okay am rewriting this in full because I am very tired and trying to write @bugs is hard.

@bug should require an explicit response or @abort from the initial yes or no question.

It should not leave any room for unclarity.

Y/Yes, goes to the yes response

N/No goes to the no response

Literally anything else goes to @abort and tells you to enter an actual response and to be clear about the thing you're reporting.