config.yml, so you can tune each tier independently per game without touching any permission plugin config files.
Permission nodes
The permission names are configured directly inside
config.yml under each game’s ranks block, so you can rename them freely to match your server’s existing rank structure.Three-tier model
Default
All players start here. Conservative daily limits and bet caps apply. No booster to winnings.
VIP
Assign
casinoliric.bet.vip and/or casinoliric.uses.vip (or the game-specific variant) for higher caps and an optional economy booster.Admin
Assign
casino.admin for unlimited daily uses, a $10 M max bet ceiling, and all administrative sub-commands.Per-game daily-use and max-bet limits
The table below lists the default values shipped with LiricCasino. Every row is independently editable inconfig.yml.
Roulette uses its own permission nodes (
casinoliric.roulette.vip and casinoliric.roulette.admin) instead of the shared casinoliric.uses.* nodes. Roulette also has a single flat max-bet setting rather than per-rank bet tiers, so the VIP and Admin max-bet columns do not apply to it.Economy boosters
Boosters multiply a player’s gross winnings by a configurable factor. You define the booster amount and the permission node that triggers it inside the top-levelboosters block of config.yml. Any number of booster tiers can be added.
Example config snippet
elite, legend) by following the same pattern. The permission string under permiso must match what your permission plugin assigns to those players.
Per-game limit config snippet
Below is a representative excerpt showing how daily-use and bet limits are structured. All other games follow the identical pattern.config.yml, run /casino reload to apply all changes immediately — no server restart required.