Difference between revisions of "+RPME code idea"
GingerNeko (talk | contribs) m |
GingerNeko (talk | contribs) m |
||
Line 37: | Line 37: | ||
<pre> | <pre> | ||
− | ==================== +rpme Request: Bob/1 ====================== | + | ========================== +rpme Request: Bob/1 ========================== |
BOB has requested a scene for DINNER AND FUN to be scheduled | BOB has requested a scene for DINNER AND FUN to be scheduled | ||
− | ANYTIME. | + | ANYTIME. |
− | +rpaccept Bob/1 | + | INVITED: NAME NAME NAME |
− | +rpaccept Bob/1= | + | |
− | +rpdecline Bob/1 | + | +rpaccept Bob/1............Accept this request without a date |
− | +rpdecline Bob/1=reason | + | +rpaccept Bob/1=MM/DD/YY...Accept this request and suggest a date |
− | +rpadd Bob/1=NAME | + | +rpdecline Bob/1...........Decline this request without explanation |
− | ================================================================= | + | +rpdecline Bob/1=reason....Decline this request with a reason |
+ | +rpadd Bob/1=NAME..........Add another person, NAME, to the scene request | ||
+ | ========================================================================== | ||
</pre> | </pre> | ||
Line 54: | Line 56: | ||
<pre> | <pre> | ||
− | ===================+rpme Sent Requests===================== | + | =====================+rpme Sent Requests===================== |
− | ?..To:................Reason..........................Sent | + | ?....To:................Reason..........................Sent |
− | Y..Bob/1..............Dinner and Fun...............04/17/23 | + | Y....Bob/1..............Dinner and Fun...............04/17/23 |
− | =========================================================== | + | ============================================================= |
</pre> | </pre> | ||
Where the Y/N/? column tells the status. (Accepted - Y, Declined - N, Unanswered - ?) | Where the Y/N/? column tells the status. (Accepted - Y, Declined - N, Unanswered - ?) |
Revision as of 20:55, 18 April 2023
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
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/1..............Dinner and Fun..................Anytime Joe/1..............Sphere chatter................by 5/1/23 Annie/1............Coffee and gossip.............by 6/2/23 ===========================================================
Using the command:
+rpme Bob/1
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/1............Accept this request without a date +rpaccept Bob/1=MM/DD/YY...Accept this request and suggest a date +rpdecline Bob/1...........Decline this request without explanation +rpdecline Bob/1=reason....Decline this request with a reason +rpadd Bob/1=NAME..........Add another person, NAME, to the scene request ==========================================================================
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 - ?)