Tebex Minecraft setup, from account to a tested purchase

Tebex Minecraft setup is four steps: a store on tebex.io with a game server added to it, the Tebex plugin on your server linked with one command, packages whose commands run in game, and a test purchase in Test Mode before you tell anyone. Most owners get through it in an hour, and most "commands don't run" problems come from one of the seven causes in the table at the end.

This guide is the setup only. Which platform to use, what to sell and what it costs are in the store guide, and what Mojang lets you sell is in the EULA guide. Everything here was checked against Tebex's own documentation in September 2026; the panel gets renamed now and then, so if a menu doesn't match, the pages linked below are the current ones.

Step 1: the account, the store and the game server

1. Create an account at tebex.io and a webstore. The Starter plan is free; new stores also get a 90-day trial of Plus.
2. Pick the game type carefully. Minecraft: Java Edition verifies usernames against Mojang. If your server runs in offline mode, or Bedrock players join through Geyser and Floodgate, Tebex's Java setup page says to choose Minecraft: Offline, so usernames are not verified and Bedrock names (which arrive with Floodgate's prefix, a dot by default) can buy.
3. Add a game server and copy its secret key. In the creator panel open Game Servers, choose Connect Game Server, then Plugin, and the secret key is shown (older panels: Integrations, Game Servers, Edit). One key per server; a network with several backends gets several game servers and several keys.

Step 2: install the plugin and link it

1. Download the plugin for your platform from the panel (Tebex, then Plugins) or from Modrinth; the source is on GitHub. There are builds for Bukkit, Spigot and Paper, Fabric, Sponge, BungeeCord and Velocity.
2. Put the jar in plugins/ (mods/ on Fabric) and restart. The plugin creates plugins/Tebex/config.yml.
3. Link it: in the server console run tebex secret YOUR_SECRET_KEY (in game as an operator it is /tebex secret YOUR_SECRET_KEY).
4. Verify with /tebex info. It prints the store's details. If it doesn't, the key is wrong or belongs to a different game server.

Proxy builds have a smaller set; /tebex help lists what exists on the platform you are on.

Step 3: packages and the commands they run

A package is a product; its deliverable is one or more commands the plugin runs on your server. In the panel open Packages, then Add New, then Package, and work through the form: name and description, a category, an image (PNG, up to 165 pixels tall) or a YouTube video, and the price as a one-time payment, a subscription, or both. Two options in the pricing step matter more than they look. Charge Every sets the subscription interval. Remove After revokes the package after a number of days and runs its expiry commands, which is how a 30-day rank actually ends. Subscriptions can also offer a free trial of 1 to 30 days. Purchase limits (global or per customer) and restrictions (a required package, visibility) are optional.

Under deliverables choose Game Server Commands. The rules, from Tebex's command guide and troubleshooting page:

• No leading slash. Write lp user {username} parent add vip, not /lp ....
• Variables. {username}, and on Java {uuid}, plus {id}, {transaction}, {price}, {packageName}, {packageExpiry}, {purchaserName} and {server} among others.
• Initial versus expiry commands. Initial commands run once payment is confirmed. Expiry commands run when Remove After ends the package. A temporary rank needs both.
• Require the customer to be online. On by default; it is what makes a give command wait until the player logs in. Turn it off per command for things that work offline, such as a LuckPerms rank change.
• Console-safe commands only. Some commands that work in chat fail from the console. Run each one in the console yourself first.

A monthly rank, in full:

Initial:  lp user {username} parent add vip
Expiry:   lp user {username} parent remove vip
Pricing:  subscription, Charge Every 1 month, Remove After 30 days

The plugin polls Tebex for new purchases about every minute, so a purchase turns into commands within a couple of minutes; run /tebex forcecheck to skip the wait while testing.

Velocity, BungeeCord and several backends

For a network, Tebex has separate proxy builds. Its docs say to place the jar in the proxy's plugins/ folder, restart, and set proxy: true under server: in plugins/Tebex/config.yml. The same setting is used for Geyser stores, because it turns off username verification so Bedrock names go through. Commands then run on the proxy, which is fine for anything the proxy can do itself (a LuckPerms rank on Velocity or BungeeCord with a shared database, for example) but not for a give or a crate key on one backend.

For per-backend commands, add each backend as its own game server in the panel with its own key, install the normal plugin on each, and in the package's Game Server Command settings enable "Allow customers to select the game server they want to receive this package on" so the buyer picks Survival or Skyblock at checkout. Global commands run on every server. The Velocity setup guide covers the proxy itself.

Templates, pages and fees

Your store's look is under Webstore, then Appearance. Starter gives you the built-in themes; custom templates (Twig, with HTML and CSS editing), a custom domain and customer lookup need Plus, which is £12.49 a month at the time of writing. Pages, also under Webstore, lets you add unlimited custom pages (rules, a join guide, staff) on any plan, which is how a store doubles as a website; the website guide covers that route. Fees, from Tebex's plans page: a 5% platform fee on every sale on both plans, plus payment processing at negotiated rates, with Tebex as merchant of record handling tax and chargebacks. The store guide works the math on a $10 rank.

Test a purchase before you announce

1. Turn on Test Mode: Settings, then Checkout, scroll to Test Mode, toggle it on.
2. Buy the package on your own store with your Minecraft username. Test purchases complete instantly with no payment details.
3. Watch the server console (and run /tebex forcecheck). You should see the command execute and, for a rank, LuckPerms confirm the change. Log in if the command requires the customer to be online.
4. Check the panel. Test transactions appear in sales statistics and trigger webhooks, but never touch earnings. Delete them with the button at the bottom of Checkout Settings.
5. Turn Test Mode off. Tebex's testing page repeats this for a reason: a store left in Test Mode gives everything away.

For a single delivery without the checkout, Payments, then Create Payment (a manual payment) issues a package to a username. Manual payments don't trigger webhooks or appear in statistics, which also makes them the right way to give a package to a player for free.

Common errors and what they mean

When a test purchase lands in game, put the store link on your listing (claim it from its server page and use the website field), add a /store command that prints it, and write one line in your description saying what the store sells. Then list the server if you haven't, so the players the store is for can find you.

Quick questions