@faraday You know, that is actually a good idea. It could be handy to set up the exit parent to actually just note <OOC> [name] has arrived [optional: from direction]. for odrops, and <OOC> [name] has left [optional: via exit]. for osucc.
That could clear that confusion up pretty nicely, and auto-loggers designed to strip OOC comments from logs could automatically remove it as needed, provided it uses whatever the standard OOC text prefix is.
Oh fucking well.
@surreality Yeah that's what it does. I have the direction on the 'leave' because it's handy for following people around, but on entry it just says "has arrived" because the room they came from is largely irrelevant.
In the OOC nexus, knowing how the player object arrived provides a lot of context for helping newbies. Arrived from the landing pad? Hi new person! Arrived from chargen, starts asking questions, they're probably connected.
I do not feel comfortable when I don't OOCly know how a person arrived to my scene. It may not be logical, but knowing how the object entered the room grounds me to their presence. It may be a skeuomorphism thing.
@surreality said in Cultural differences between MUDs and MUSHes:
@faraday You know, that is actually a good idea. It could be handy to set up the exit parent to actually just note <OOC> [name] has arrived [optional: from direction]. for odrops, and <OOC> [name] has left [optional: via exit]. for osucc.
That could clear that confusion up pretty nicely, and auto-loggers designed to strip OOC comments from logs could automatically remove it as needed, provided it uses whatever the standard OOC text prefix is.
Hell yes.
@faraday
You'd have to edit the hardcode though wouldn't you? @odrop (at least on Penn) only covers what is after the name, as it automatically includes the name. Perhaps an @adrop that remits to the room.
Or you could just tag the <OOC> at the end.
@Sunny
Actually, I asked. At least on Penn you can set the @odrop NONAME and it won't prepend the name, so you can futz with the messages completely.
@faraday You know, that is actually a good idea. It could be handy to set up the exit parent to actually just note <OOC> [name] has arrived [optional: from direction]. for odrops, and <OOC> [name] has left [optional: via exit]. for osucc.
That could clear that confusion up pretty nicely, and auto-loggers designed to strip OOC comments from logs could automatically remove it as needed, provided it uses whatever the standard OOC text prefix is.
