+RPME code idea
NOTE: THIS CODE DOES NOT EXIST.
It is a proposal to staff for a new codeset to allow for easier tracking of scenes to be played and requests for them.
I repeat, THIS CODE DOES NOT EXIST.
PROPOSAL:
This code would be in place to allow people to request scenes from one another even when they don't see one another. Having a rolling list of scenes that a person can choose will make RP much more easily available.
To request a scene:
+rpme Bob=For Dinner and Fun/Anytime CREATED: +RPME 101=Bob/For Dinner and Fun/Anytime
This would ask Bob to do a 'Dinner and Fun' style scene any time he is available. To send it to multiple people at once, it would look more like:
+rpme Bob Joanne Stacy=For Dinner and Fun/Anytime
To see your requests:
+rpme/list
And the output would look something like this:
===============+rpme Received Requests===================== Bob/101............Dinner and Fun..................Anytime Joe/134............Sphere chatter................by 5/1/23 Annie/142..........Coffee and gossip.............by 6/2/23 ===========================================================
Using the command:
+rpme Bob/101
would bring up:
========================== +rpme Request: Bob/1 ========================== BOB has requested a scene for DINNER AND FUN to be scheduled ANYTIME. INVITED: NAME NAME NAME +rpaccept Bob/101............Accept this request without a date +rpaccept Bob/101=MM/DD/YY...Accept this request and suggest a date +rpdecline Bob/101...........Decline this request without explanation +rpdecline Bob/101=reason....Decline this request with a reason +rpadd Bob/101=NAME..........Add another person, NAME, to the scene request. ==========================================================================
(Query: Is the +rpadd workable and should it force permission from the original sender to allow anyone to be added?)
You can check your sent requests with
+rpme/sent
which would bring up:
=====================+rpme Sent Requests===================== ?....To:................Reason..........................Sent Y....Bob/1..............Dinner and Fun...............04/17/23 =============================================================
Where the Y/N/? column tells the status. (Accepted - Y, Declined - N, Unanswered - ?).
The switch NAME/1 shows you which request it is, in case there is more than one from that player. The second would be NAME/2, then NAME/3, etc. I think they would have to be numbered by the player's overall requests, tbh, because I can't think of another way
OTHER POTENTIAL USEFUL ADDITIONS: +rpremove to remove a request +rpok to approve adding another person +rploc to add a location