CoinFlips

v5.4.0 — Private Matches & Direct Challenges

✨ What's new

🔒 Private games (/cf private <amount> <password>)

• New command /coinflip private <amount> <password> to create a password-protected game.

Private games do not appear in the public join GUI menu — they are invisible to other players.

• To join a private game, the player must use /cf join <id> and enter the correct password.
• If the password is incorrect, an error message is sent (game.join.wrong-password).

The password is displayed to the creator in the confirmation message.

⚔️ Direct challenges (/cf challenge <player> <amount>)

• New command /coinflip challenge <player> <amount> to challenge a player online directly.
• The stake is immediately withdrawn from the challenger when the challenge is sent.

The targeted player receives an in-game notification with the commands /cf accept and /cf decline.

• Response timeout configurable via game.challenge-timeout-seconds in config.yml (default: 60 seconds).
• If the deadline expires → automatic reimbursement of the challenger, notification to both players.

If the targeted player disconnects → automatic refund from the challenger.

• If the targeted player does not have enough money to accept → challenger refund.
• A challenger can only send one challenge at a time.
• A player can only receive one challenge at a time.

Challenge matches are invisible in the public GUI (like private matches).

🆕 New orders

📝 Config files updated

config.yml

game:
  challenge-timeout-seconds: 60 # new

messages.yml — new keys added:

• game.create.private-success
• game.join.wrong-password
• game.join.not-invited
• challenge.sent
• challenge.received
• challenge. declined-challenger
• challenge.declined-target
• challenge.expired-challenger
• challenge.expired-target
• challenge.target-offline
• challenge.target-not-found
• challenge.target-busy
• challenge.target-no-money
• challenge.cannot-challenge-self
• challenge.already-sent
• challenge.no-pending