I think the value here is in scene tracking, rewarding players, historical records, and managing your "to do" list.
If I log in, and I got a list of people who want my attention and how long they've been waiting for me, personally, and it's not mixed in with mail and boards, that's a great value. I've regularly read a mail and forgot about it. This stops that.
In addition, if someone sends a meeting request to my faction, we all see it and we all can respond, and we all can flag it as "done".
As Thenomain says, she's staying off MSB. She's fine, and best I know still RPing and working in her code and her next project.
Posting only in case someone is worried.
@Lisse24 yeah ok.
I like adding in @surreality's suggestion.
Personally, I'd tie the /clear command to XP gain. That'd be fun.
@tangent I was asked by a friend how easy/possible it would be to set up, and if there was any existing code base. I've never played a superhero game, so, I have not the slightest idea what they might want to do! Just doing some digging for the technically illiterate. 
I'm honestly not sure there is any such thing...
But is anyone aware of any code out there (like an existing database from an older game) that could be dropped to make a superhero game? I'm looking for something in the sheet-less, dice-less sort of realm. Background questions and a grid to RP on.
I could be way off, but I'm fairly sure it will be getting used at Fate's Harvest. The purpose, afaik, is to hold and desperate the descriptions for Changelings vs Non-Changelings. Ie, seeing mask vs mein.
It would not separate out players, but simply descs? Or I could be totally misunderstanding.
@Sunny @bladesurfer A glitch in the matrix...?
TinyMUX has a similar command (@decompile/dbref), only it doesn't start each line with Tinyfugue> and that is what the game hooks and drops into your input.
There's probably an easy workaround for this, but my brain isn't processing. Is there a way to @decompile but add some extra text into the beginning, before the information? I tried a few things, but it always puts the stuff on separate lines.
@bladesurfer I have no idea what any of that is... what is /grab supposed to do, practically speaking?
@Catsmeow not sure what you're trying to ignore. Explain more?
Updated again... Shadows of Reno, Star Wars DOD, and Arx. (Yes, finally trying non-WoD games.)
Hi All,
I have finished my Pose Order Machine, and I'd be more than happy to share it with whomever would like to use it. At present, this code is running on Fallen World MUX and Shadows Over Reno MUSH. So far, there have been no issues reported (though, admittedly, there are only a few people using it).
Overview:
The code is designed to alert players when it's their turn to pose, as well as keep track of pose order. It is entirely opt-in (as in, you need to turn your alerts on), though you can always use +poseorder to see who last posed, how long ago, etc. If a player doesn't pose for 45 minutes or leaves the room or disconnects, they will be wiped from the pose order.
Note that the alert can be set to BEEP at you. This functionality is supported by TinyMUX, but I've been told some clients will not process the beep/bell.
Code details:
This code ties into the @hook object. If your game has +poseorder, there's a good chance that this will work. Each time a pose is sent (@em, pose, ", , :, whatever) it logs the time and dbref of the poser to the local room object. Each time an additional pose is sent, it clears that player's existing pose. The hook will also process the list, decide who is 'next up' and send out an alert.
To clear out idle players, and those no longer in the room, I am using Myrddin's mushcron, and it is set up to run every minute and check for idle players.
I have attempted to make this as easy to install as possible. It's mean to go through Muxify ( http://muxify.musoapbox.net/editor.html ), with some comments being doing in block, while others are done as @@. It's likely not going to come out of muxify exactly perfect, but hopefully it's pretty close! NOTE: Muxify will not work on my Chrome or Edge. Use Firefox.
If you have any questions, if you'd like help installing, etc, etc, please just ping me here, or on Fallen World MUX as skew, or Shadows Over Reno MUSH as skew. This is the first code I've ever shared, and so I'm fairly sure I borked something up, so please don't hesitate to poke me, and please be vigilant installing it.
The code can be found here: https://github.com/skewskewskew/MUSHCode/blob/master/Pose Order Machine <POM>
Cheers!
I know you said you were avoiding suggestions on how/where to store data, but I can't really think of how to suggest without it, soooo...
We use an attribute for each stat. When we need to offset, you add that to the same attribute, after a period.
Example: _ATTRIBUTE.COMPOSURE : 5.-1
When the stat gets called, either for the sheet or the roller, it runs through a function, to get either the real, or the adjusted, and displays accordingly.
When you shift, then, it pulls from a list of offsets to apply and does that. When you shift back, it clears those.
@Volund Ahh, I thought someone had told me you'd worked on it. My mistake!
@Bobotron Thank you, but I think this idea is going to get tabled for now.
@Rook said in +poseorder and +repose:
What is wrong with just a simple OOC request that someone do a little paged playback? That was always the way it was done before...
(Am I waving my cane too much? Just say so. I can believe that's what's happening here.)
Why not hand stat sheets? Why have a desc'd grid? Why use a dice roller?
I am being absurd, of course, but yes, the long and short is "so you don't have to". It's also beautiful to be able to +repose after you just sifted through bboards, or @mail, or whatever else.
Well, my goal here with +repose is not to actually log a scene, but instead work as a tool for players in the room, who might have disconnected and missed a pose, or might have came in late, into the scene.
Right now, I can't figure out how to make what I have do what I need. Seems like having the parent room listening or something is going to be the way to do it. The idea being to store the last 10 or so poses somewhere, then have a command that can draw them back up up. After, say, 60 minutes or when the room is empty or when someone uses the /clear command, it would clear.
I just don't know how listen works yet, and I'm unsure if I want to invest the time into figuring it out.
All that said, a +log command that turns on scene logging, then outputs it into a format that can be pasted into the wiki would be super nice.
I know scenesys exists, but I cannot find whatever @Volund did to make it compatible with TinyMUX. I only see Penn stuff.
@Ashen-Shugar @Cobaltasaurus Thank you both.
Is there any conflicts between setting a parent player object and having the players themselves set attributes? Example: If I set &jobsn XX=1 on the parent, then a player sets &jobsn XX=0, would it respect the player's settings?
I have no idea how to set the default player attributes.
Some things (like, the stupid flag that makes jobs actually mark themselves 'read') need to be set as an attribute on the player bit, and I have no idea how to set it as the default. Best idea I have right now is to tie it to the landing room, so when you type "ACCEPT" to agree to our basic terms, it applies the attributes.
Any other solutions?
(Again, I'm on TinyMUX.)
I have tried 4 different MU clients on my iphone. MUDrammer is hands down the best. Like, way way way better than the others, which have some really redonkulous stuff, like constantly sending y+accent, or not allowing you to recall what you've already sent.