Existing players used to logging in with their character name and moo password must signup for a website account.
- fireflies 11m
- whatislove 28m reputation is whoever holds a bigger gun
- Mindhunter 7s
- Rillem 53m Make it personal.
- Wulf 27s
- PsycoticCone 45m
- Porygon 3h
- VermilionGrin 1m
- Vanashis 3h
- Mattsc 2m
- Genius_Flint 6h
- zxq 13m Tools: https://ansicolortool.neocities.org
- Euclid 21s
- Pladdicus 3s uh
- AntiqueBeast 2m White grace, hidden in the dark.
a Mench 1h Doing a bit of everything.
- Enven 1m
And 26 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Flag Gameplay Relevant @LPs

Since the other thread ended up not being related to the discussion in OOC-Chat, I'll make a separate one for this topic. It comes up occasionally that it's not always clear to players what @lp descriptions on bits are roleplay fluff and which are gameplay relevant (ie. sleeping, grappling, hiding), and I agree it's not an intuitive mechanism especially because there are common generic NPC @lps that are easily confused for something gameplay relevant until players learn what all the stock messages are through experience and memorization which is probably not ideal.

My suggestion is to distinguish important mechanical @lps with a combat label in strip_ascii mode and a colour tint otherwise. So for example:

Combat/Grappling: 1 Red

strip_ascii: (combat) %N, %N, and %N are here engaged in combat. (grapple) %N is here, locked in the grasp of %N.

Hiding: 4 Blue

strip_ascii:(hidden) %N is lurking in the shadows.

Sleeping: 8 Grey

strip_ascii: (sleeping) %N is sleeping here.

Actually that should be adding bracketed labels in when COMBAT_LABELS are enabled not when ascii_strip is, getting my accessibility options settings mixed up.
I love this option. Especially with it interacting with combat labels. A much more elegant solution that what I first proposed in another thread.

One benefit is that with something like this in place and documented, I think it would free up staff a little. If a player wants to set their @lp or @tp to something mimicking a mechanically significant message, go for it. Players will know it's RP only or maybe ICly the character pretending to do something.

The only thing I might add is that the system might need to be extended to cover other meaningful states that use @lp/@tp messages as indicators. Like sitting. Possibly diseases and medical bits. Staff would know better and, if something like this is implemented, we can catch and add such states as needed over time.

Or, possibly better, create a verb that that can be called by the game's code to set a players @lp/@tp/@sp that takes three arguments: the 'place version (lp/tp/sp), the message, and the state. Then find all code that sets lp/tp/sp messages and change it to use the new verb to set them. This might create some uniformity and catch most existing cases where using this system would be an improvement. This is just a rough idea though. DO with it what one will! :)