Difference between revisions of "+RPME code idea"

From City of Hope MUSH
Jump to navigation Jump to search
m
 
(4 intermediate revisions by the same user not shown)
Line 11: Line 11:
 
To request a scene:
 
To request a scene:
  
<pre>+rpme Bob=For Dinner and Fun/Anytime</pre>
+
'''<pre>+rpme Bob=For Dinner and Fun/Anytime
 +
CREATED: +RPME 101=Bob/For Dinner and Fun/Anytime</pre>'''
  
 
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:  
 
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:  
  
<pre>+rpme Bob Joanne Stacy=For Dinner and Fun/Anytime</pre>
+
'''<pre>+rpme Bob Joanne Stacy=For Dinner and Fun/Anytime</pre>'''
  
 
To see your requests:
 
To see your requests:
Line 25: Line 26:
 
'''<pre>
 
'''<pre>
 
===============+rpme Received Requests=====================
 
===============+rpme Received Requests=====================
Bob/1..............Dinner and Fun..................Anytime
+
Bob/101............Dinner and Fun..................Anytime
Joe/1..............Sphere chatter................by 5/1/23
+
Joe/134............Sphere chatter................by 5/1/23
Annie/1............Coffee and gossip.............by 6/2/23
+
Annie/142..........Coffee and gossip.............by 6/2/23
 
===========================================================
 
===========================================================
 
</pre>'''
 
</pre>'''
  
 
Using the command:  
 
Using the command:  
<pre>+rpme Bob/1</pre>
+
'''<pre>+rpme Bob/101</pre>'''
  
 
would bring up:
 
would bring up:
  
<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.  
 +
 
 +
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. 
 +
==========================================================================
 +
</pre>'''
 +
 
 +
(Query: Is the +rpadd workable and should it force permission from the original sender to allow anyone to be added?)
  
+rpaccept Bob/1 - Accept this request without a date
 
+rpaccept Bob/1=4/25/23 - 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
 
=================================================================
 
</pre>
 
  
 
You can check your sent requests with  
 
You can check your sent requests with  
<pre>+rpme/sent </pre>
+
'''<pre>+rpme/sent </pre>'''
 
which would bring up:
 
which would bring up:
  
<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 - ?).
 +
 
 +
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
  
Where the Y/N/? column tells the status. (Accepted - Y, Declined - N, Unanswered - ?)
+
'''OTHER POTENTIALLY USEFUL ADDITIONS:'''
 +
* +rpremove to remove a request
 +
* +rpok to approve adding another person
 +
* +rploc to add a location
 +
* +rpnotok to reject a suggested person to add

Latest revision as of 21:09, 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
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 POTENTIALLY USEFUL ADDITIONS:

  • +rpremove to remove a request
  • +rpok to approve adding another person
  • +rploc to add a location
  • +rpnotok to reject a suggested person to add