+repose

[Sponge]

Got a feature request on NPM:

I am not a coder, and thus do not know how difficult this feature is to create or enact, however, +repose was a command on a previous game I played; Star Wars: Generations of Darkness. The command essentially ignored all ooc, and just re-posted the last...10 or so poses, appended with who made them. It was an INCREDIBLE feature to help keep up with a large scene when struck by a sudden torrent of spam, and allowed very large scenes to go on without people getting lost very easily at all.

I'd LOVE a similar feature, as I think it'd help me (and a lot of people) hack their way through bigger crowd scenes and deal with channel spam at the same time. Is there any way that something like this is
possible here?

Sounds like more use of hooking than I'm interested in. Seems like it would be best implemented in client. Am I missing something?

[Coin]

@Sponge Well, I suspect it would be really useful for when you get disconnected and come back to people having posed... so it being client-based would be pointless.

[Sponge]

@Coin

It wouldn't be pointless. It would be a convenient way for others to repose to you as a courtesy.

[Coin]

@Sponge It seems far less useful and doesn't seem what to be what the person is asking for. They're asking to be able to see the last poses in a scene easily. If someone else has to give you their own pose, it's really no different than asking them for it.

The other use is cutting out OOC spam, so you can repeatedly use the command to cut through the OOC chatter. But I would find it infinitely more of use as a catch-up tool for people who disconnected and missed poses (or maybe got to the scene just a few poses after the start).

[Sponge]

@Coin

I agree that server-side repose is more useful. I assert that client-side is more useful than nothing because copy-paste is tedious and error prone.

Do you have an implementation of either?

[Misadventure]

Saving the last 5 poses would be awesome.
Or maybe the number of players present X2 or something.

[Glitch]

@Sponge said:

Sounds like more use of hooking than I'm interested in. Seems like it would be best implemented in client. Am I missing something?

I agree that server-side repose is more useful. I assert that client-side is more useful than nothing because copy-paste is tedious and error prone.

Do you have an implementation of either?

If you want code, just ask for it. It might not show up, but it's better than asking if you're missing something when you obviously understand that a MU based solution is better and just don't want to code it.

[Sponge]

@Glitch

If my desire to have an implementation was unclear, I apologize for the ambiguity.

Do you have an implementation of either?

[Tez]

Volund has a pose order tracker than handled this pretty nicely in the brief time I used it:

This may or may not be the pose tracker I played with:
https://github.com/volundmush/mushcode/blob/master/Pose Order Tracker - POT.txt

And the rest of Volund's stuff is here:
https://github.com/volundmush/mushcode

[Three-Eyed Crow]

I've played on a couple games that used similar tools to this, and it's incredibly handy. I particularly like versions of this that let you see how long it's been since the last pose. Seems to keep scenes from dragging as much if there's something to quantify beyond idle times, which can be misleading.

[Bobotron]

@Tez
Yeah, but can you actually install Volund's POT without all of the other systems? Every time I look at his code I get a headache from all of the interlinks.

[Tez]

@Bobotron
Ha. Tell me about it. I was going through his Pose Prettifier the other day. It was dependent on other systems 3 layers back. I broke down and emailed him.

The Pose Order Tracker system above definitely does seem to depend on at least one other system. When I emailed Volund (who was very quick to respond; I do suggest emailing if you try it and run into problems), he said he was working on a version of his code that is better suited to install in pieces.

I eagerly anticipate that day. In the meantime, it's at least a place to start.

[Bobotron]

@Tez
I know Volund well from MVC, where we've played together for years before I let myself time out there.

@Sponge
I may have an older POT that I should work for PennMUSH that was posted to pastebin; I've not tested it though, but it looks like it comes from the M3/SRT/etc. circuit. You could give it a whirl?
http://pastebin.com/8ALuyUab - The help file
http://pastebin.com/RWq3Uazx - The code

[Sponge]

@Bobotron
This should be adaptable though I'm somewhat @hook-averse. It will catch poses via say/pose/emit but not anything soft-coded that doesn't @force players to say/pose/emit.

Man, I wish MUX had lambdas. Having to set up a distinct soft function for things like filter() and sortby() has always felt clumsy.

[Ide]

@Sponge the poor man's MUX's lambda:

th filter([set(me, vz:mod(\%0, 2))]vz, 1 2 3 4 5)
Set.
1 3 5

edit: haha, nothing is uglier than mushcode!

[Coin]

@Sponge said:

@Coin

I agree that server-side repose is more useful. I assert that client-side is more useful than nothing because copy-paste is tedious and error prone.

Do you have an implementation of either?

Hell no, I couldn't code something if I was on CSI: Cyber.

[Templari]

KOTOR Mush had a pose tracker, lets folks know who posed in what order and when, but it also gave the last X amount of poses if you came in late.

I find that handy just to save folks in big scenes of having to set, set, reset, and set scene some more. On the other hand, it could bring back embarrassing moments or secrets.

[Misadventure]

Make it account to you when you enter a room where it is enabled, or when it is enabled, and make sure it can be turned off.

It would probably need a clear command, so you could clear your scene before logging out, and it wouldn't be a terrible idea to have it routinely locked to players who are in the log. Only a big public scene would start with /public going.

[Arkandel]

@Misadventure said:

Make it account to you when you enter a room where it is enabled, or when it is enabled, and make sure it can be turned off.

It would probably need a clear command, so you could clear your scene before logging out, and it wouldn't be a terrible idea to have it routinely locked to players who are in the log. Only a big public scene would start with /public going.

To avoid TS-related mishaps I'd say definitely clear the log as soon as a room is vacant, time it out if an hour has passed since the last pose, etc etc.

This has to be automated as well as manual or it would absolutely end up in hilarious threads right here on MSB.

[Coin]

@Arkandel said:

@Misadventure said:

Make it account to you when you enter a room where it is enabled, or when it is enabled, and make sure it can be turned off.

It would probably need a clear command, so you could clear your scene before logging out, and it wouldn't be a terrible idea to have it routinely locked to players who are in the log. Only a big public scene would start with /public going.

To avoid TS-related mishaps I'd say definitely clear the log as soon as a room is vacant, time it out if an hour has passed since the last pose, etc etc.

This has to be automated as well as manual or it would absolutely end up in hilarious threads right here on MSB.

Then again, it would absolutely end up in hilarious threads right here on MSB.