CrateForge

WHY CRATEFORGE

• Twelve animations, not one. A case opening, a roulette, a wheel, a slot machine, a war, a cascade, an auction, a mystery box, a portal, fireworks and more — chosen per crate, so your legendary crate does not open like your daily one
• Bad luck has a limit. After a number of opens you set without a prize of a given tier, the next one is guaranteed at that tier. Tracked per player and per crate, so a streak of nothing does not become a refund request
• Keys survive everything. Renaming in an anvil, splitting a stack, being given by a command — a key stays a key, because it is not identified by the text written on it
• Rewards are weighted and previewable. Players can see every prize and its chance before spending a key, which is the difference between a crate and a scam
• Tokens give the leftovers value. Duplicate and low-tier prizes turn into a currency with its own shop, so the fortieth common reward still means something

WHAT YOU GET

• 12 reveal animations — fully styled, chosen per crate, running server-side with nothing installed on the client
• Physical crates — anchored anywhere in the world, with a hologram and an ambient effect above them
• Durable keys — immune to renames, stack splits and transfers
• Weighted rewards — any item, command or amount of money, with the odds you choose
• Reward preview — every prize and its chance, in game, before opening
• Pity system — a guaranteed tier after N unlucky opens, per player and per crate
• Token economy — several token types with a built-in shop to spend them in
• Key drops from mobs — optional, by mob type and chance
• Staff tools — hand keys to a player, anchor or move a crate, reload without a restart
• Custom-model support — rewards can use items from your model or resource-pack plugin
• PlaceholderAPI — keys held, crates opened and token balance, for scoreboards, TAB or chat
• An API for your own plugins — give keys and open crates from your own code
• English and Spanish included, and every string a player reads lives in messages.yml in MiniMessage format

HOW IT WORKS IN PLAY

You anchor a crate at spawn and set it to the case-opening animation. A player votes, gets a key, right-clicks the crate and watches the reel slow down in front of them. It stops on a duplicate — but the tokens it pays go into the shop, and their pity counter moves one closer to a guaranteed rare. Somebody else renames their key "lucky" in an anvil and it still works, because it was never the name that made it a key.

CONFIGURATION

• crates/ — one file per crate: its animation, its rewards and their weights, its key, its hologram and its pity threshold
• config.yml — token types, mob key drops, the shop and which integrations are on, every key with a comment beside it
• messages.yml — every string a player reads, so you can reword or re-colour the plugin without touching anything else

COMMANDS AND PERMISSIONS

• /cf preview <crate> · /cf shop · /cf set <crate> · /cf givekey <player> <crate> · /cf reload
• crateforge.use defaults to everyone; crateforge.admin and crateforge.shop.bypass are yours to hand out
• Every node is declared in plugin.yml, so your permissions plugin lists them all

Commands

Full command and permission reference in the docs ↗