ProVouchers

!ProVouchers

ProVouchers adds physical voucher items, redeemable codes, and a /stash menu for rewards players can claim later. You decide what a reward contains, who can use it, and how often it can be claimed.

Use it for daily rewards, vote incentives, starter kits, event prizes, temporary ranks, or one-time giveaway codes. Vouchers and codes are defined in YAML and can be reloaded without a server restart.

Documentation | Source code | Discord

How players receive rewards

• Voucher items: Players right-click an item to redeem it. Set its material, name, lore, glow, custom model, or head. Compatible custom items can come from ItemsAdder, Oraxen, Nexo, and Head Database.
• Redeemable codes: Players enter /voucher redeem <code>. Codes can be limited to a certain number of uses, restricted per player, or set to expire.
• The Stash: Queue virtual vouchers for players, including players who are offline but have joined before. They can claim their rewards through /stash, individually or with Claim all. Stash entries can expire and can notify players when they join.

The Stash can also catch voucher items that will not fit in an inventory. Set stash.overflow: stash to enable this. The default behavior is to drop overflow items.

Rewards and conditions

A voucher or code can run multiple rewards: items, XP, Vault currency, LuckPerms groups or permissions, console and player commands, messages, broadcasts, titles, action bars, sounds, and Discord webhooks. Weighted random reward pools can run alongside guaranteed rewards. Named random rolls let you reuse the same number in a reward and its announcement.

Conditions let you restrict redemption by permission, rank, world, WorldGuard region, game mode, balance, XP level, playtime, inventory contents, completed advancements, player statistics, or a PlaceholderAPI comparison. All configured conditions must pass.

Per-player cooldowns, permission-based cooldown tiers, and global or per-player usage limits are stored persistently. A shared MySQL, MariaDB, or PostgreSQL database lets multiple servers enforce the same limits. You can also set start dates, expiry dates, and optional confirmation prompts.

Physical vouchers support owner-only redemption and configurable soulbound restrictions. Non-stackable vouchers can receive a unique, persistent stamp to detect duplicate or already-used copies. Stackable vouchers do not use individual duplicate tracking.

A voucher in YAML

Create plugins/ProVouchers/vouchers/daily.yml:

display-name: "<gold>Daily Reward"
item:
  material: SUNFLOWER
  glow: true
lore:
  - "<gray>Right-click to redeem"
cooldown: 86400
rewards:
  - "item: DIAMOND 1"
  - "message: <green>Come back tomorrow!"

Run /voucher reload to load it. The player can redeem the voucher again after 24 hours, including across restarts.

Tools for server staff

/voucher fromhand saves the item you're holding as a new voucher. There are commands to give vouchers, preview rewards, reload an individual file, inspect plugin status with /voucher doctor, and reset usage records.

Moving from CrazyVouchers? /voucher import crazyvouchers reads both current and legacy voucher and code layouts. It creates ProVouchers files without overwriting your originals, and reports settings that need manual review.

ProVouchers includes English, German, French, Spanish, Polish, Danish, and Dutch. Messages can follow each player's client language, with English as a fallback. Developers can also use the public API and redemption events.

Requirements

• Server: Paper, Purpur, or Folia
• Minecraft: 26.1 or newer (tested through 26.3)
• Java: 25
• Storage: SQLite by default; MySQL, MariaDB, and PostgreSQL are supported

Vault, LuckPerms, WorldGuard, PlaceholderAPI, MiniPlaceholders, and custom item plugins are optional. Install only the integrations needed for your configuration.

For setup instructions and configuration examples, see the documentation. For bugs, use GitHub Issues. For questions and support, join Discord.