Existing players used to logging in with their character name and moo password must signup for a website account.
- Raven 12m I lost myself, in the dark charade.
- Burgerwolf 8m PANCAKES
- zxq 14m Blackcastle was no ordinary prison.
- cata 2m
- Rillem 2m Make it personal.
- NightHollow 3s
- Jengris 14m
- BubbleKangaroo 14m
- Acupa 4s
- SmokePotion 0s Right or wrong, I'm getting high.
- Vanashis 43s
- Sivartas 16m
And 21 more hiding and/or disguised
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Bar meaningful phrases in @lp/@tps
Code in any restrictions that exist

Things may have changed but I was told by staff before that you shouldn't cheese @lp/tp/sp messages. In this case I was told that I should not set my @lp or @tp to something like 'is sleeping here.' Or to any message starting with that like 'sleeping here, snoring.'

I imagine that there may be other phrases that fall under such restrictions like 'is lurking in the shadows.' As, like with the sleeping messages, it is something that has mechanical significance. Though I am not sure if this phrase is covered or if there might be others that are covered.

My thought is that, if such phrases are not to be used in @lp/tps, why not have the game check for them when a player tries to set an @lp or @tp. If a no-no phrase is matched, the game informs the character that they can't use that @lp or @tp because of reasons.

It might be cool to make use of some of these 256 colour options we have now, alternatively tinting mechanically relevant proom @lps would make their content not as relevant. Say for example GreySilverAlt for hidden bits and BlackJet for disconnected/sleeping.
Maybe a version of bright white for a custom @lp/@tp
As long as there would be some kind of accessibility version with a tag or something. I'm not really a fan of using color or ASCII art much unless there are blind player friendly systems/alternatives for those who need it.

I'm not exactly sure how complex it is to add new alternate display options to strip_ascii but (Sleeping) and (Hidden) flags before the bit name would seem to be a possible solution.
I also worry about lumping too many things into one setting. Maybe the player has some kind of color blindness so wants tags for colored text but is fine with ASCII art and wants to see that. Granted I don't really know how color blindness works or if this is a real possibility but I figured it was worth mentioning.

Okay but the perfect is going to be the enemy of the good keey in mind, there will be any number of potential non-ideals with any given solution but if something is going to require more than 30 minutes to implement it's pretty unlikely to happen at all.
Fair enough! I think I lean more towards a system that filters out and blocks the 'bad stuff' as it doesn't rely on color and wouldn't require additional accessibility coding. But I'd take color coding @lp/sp messages that were mechanically significant too! Heck, maybe someone will have another idea we would never come up with!

I thought the issue was that players were confused by whether @lps were mechanically significant or not, not that anyone was falsely using gameplay-implying @lps.

I don't see how blocking 'lurking in the shadows' from @lp use makes it any clearer to players that 'hiding in plain sight' is only roleplay fluff.

Nevermind I thought this was related to the earlier discussion in OOC-Chat, I'll make a different thread.
It actually was but I didn't think far enough really. My thoughts extended only as far as preventing players from duplicating such messages. I think this only goes half way as new players still don't know which ones are mechanically meaningful. This is something your color system might do. I think the concept is better for a more comprehensive solution but I would prefer tags over colors. But I'll throw my thoughts onto your thread in more detail.