07-25-2019, 11:38 PM
(This post was last modified: 09-01-2022, 01:08 AM by Fearless Community.
Edit Reason: Fixed Encoding
)
Title of Suggestion: /card Poker (deck) support
Description
Decks are required for casino games such as poker, which cannot be achieved with the current /card system as cards could be drawn twice causing clashes.
Why?
I've discussed this with Joe Joe and Forgee, and we came upon the reasonable idea with the format as so:
/deck (generates an unlimited deck, essentially the same to /card now)
/card (If no deck is generated, this will notify, but will either pick from unlimited deck or sized deck as set by...)
/deck (1-8) (Only 1 deck needed for poker, but this allows for up to 8 for blackjack, although the house should consider that card counting is made extremely easy by using this)
/pcard <player> (This privately messages from either an unlimited or sized deck. Used predominantly in poker to deal private cards. Possible second argument for how many cards to deal, AKA 2 for a poker hand)
The main reason for this is for poker games which do require a deck for obvious reasons. This should be pretty easy to implement (something similar to my example which follows the above schema) but we agreed that this is the best schema we could think of at the time for simplicity. Could do different features such as /pcard <p1> <p2> etc to send multiple players their cards at once before then printing this to the dealer as a table?
This should simplify poker RPs and keep logs on the server rather than working off of word of mouth from the croupier.
Hopefully this is of some use, largely untested code but shouldn't be *too* far off a functional system, minus some adjustment and possibly fixing of mistakes.
Thanks for reading
Description
Decks are required for casino games such as poker, which cannot be achieved with the current /card system as cards could be drawn twice causing clashes.
Why?
I've discussed this with Joe Joe and Forgee, and we came upon the reasonable idea with the format as so:
/deck (generates an unlimited deck, essentially the same to /card now)
/card (If no deck is generated, this will notify, but will either pick from unlimited deck or sized deck as set by...)
/deck (1-8) (Only 1 deck needed for poker, but this allows for up to 8 for blackjack, although the house should consider that card counting is made extremely easy by using this)
/pcard <player> (This privately messages from either an unlimited or sized deck. Used predominantly in poker to deal private cards. Possible second argument for how many cards to deal, AKA 2 for a poker hand)
The main reason for this is for poker games which do require a deck for obvious reasons. This should be pretty easy to implement (something similar to my example which follows the above schema) but we agreed that this is the best schema we could think of at the time for simplicity. Could do different features such as /pcard <p1> <p2> etc to send multiple players their cards at once before then printing this to the dealer as a table?
This should simplify poker RPs and keep logs on the server rather than working off of word of mouth from the croupier.
Hopefully this is of some use, largely untested code but shouldn't be *too* far off a functional system, minus some adjustment and possibly fixing of mistakes.
Spoiler :
Thanks for reading