+poseorder and +repose
-
My +poseorder code is now deployed on Fallen World, Reno, and my sekrit server.
Once I get some real stress testing and make sure it's not riddled with bugs, I'll make a new post to share.
Wooo!
-
I once built a scene logger object that was useful in place of timestop code (this was a decade+ ago) that only allowed scene participants to use (for security reasons). They could add people to the scene (which would then roll initiative for them if the scene was 'in rounds' so to speak) and that person could use the commands until they were removed. The players so added to a scene were alerted, and had to run a command to 'accept' those terms of the scene being logged (else they were not involved). It bears mentioning that this functionality/object was an offering for players, not a requirement (so that people were never forced to use them).
The point here was that the object @tel'ed to the last person to leave the room, or to the person to run the 'close scene' command. After that, only that person could run the 'regurgitate' command which output the stored poses for logging/posting purposes.
Nothing was stored on the room, the room wasn't listening, etc, was the point of using an object in the room. The room parents DID have a check for such objects, and when a new player entered the room, they saw a bright red @adesc warning on the room description.
EDIT: However, this did not have any poseorder or repose functionality.
-
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.
-
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.)
-
@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...
There's nothing wrong with that, but having an automated system just cuts down on the number of times you need to ask and page. Many people find it convenient. YMMV.
-
@faraday Yeah, and it's a bit annoying to construct them if there's OOC spam, etc in the mix.
-
@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.
-
Alright. I'm convinced. ("And yes, Rook, too much cane-waving.")
-
I have a copy of Pose Order Tracker that saves to a room; it might work to be edited to save to an object? I think it's primarily written for PennMUSH as it requires @hooks. I can link it if needed.
-
@skew
It isn't compatible with TinyMUX. It's compaible with only PennMUSH and RhostMUSH. And Rhost could use more testing.Sorry.
-
