Existing players used to logging in with their character name and moo password must signup for a website account.
- Fogchild1 1m
- SmokePotion 2m Right or wrong, I'm getting high.
- Raven 16m I lost myself, in the dark charade.
- Visitor_Guest 16m [Welcome to Sindome]
- Rillem 3m Make it personal.
- Archangel212168 0s
- Soltan 14m
- freezeway3k 7s
- Woeful 2m
- Sulfurado 36m
- Hivemind 13s
a Mench 54m Doing a bit of everything.
- zxq 1m Tools: https://ansicolortool.neocities.org
- PsycoticCone 8m
- xXShadowSlayerXx 46m
- JanekSembilan 13s
- Pladdicus 31s uh
- Fay 18m
- hex 17s
- Wulf 1m
- Vanashis 1m
- BlackSoul 7m
- FluffyPuff 19m
And 30 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Search Bugs
See if there is already a public bug for this?

A verb that lets you search public bugs for a string and returns a list of the bugs (with bug number) that contains that string.

This way, before submitting a bug, I can do something like '@sb market' and get a list of all bugs with 'market' in their title or description. I can then do @vb # to check the returned bugs to see if any cover what I am thinking about submitting.

At the time of this post, there are 61 unresolved public bugs. Despite this impressively short list (seriously!), I think it would be nice if I could trim it down if needed. It might also be useful for staff if they want to quickly check for other bugs that may be related to, or a duplicate of, one they are working on.

I was experimenting with passing all the bug subjects to ChatGPT and having it do a semantic analysis on them to suggest possible similar bugs when you use @bug – but it didn't work very well.

It was totally an over engineered solution. I could pretty easily make a command that does what you describe with just SQL. I'll add it to my list.