TitleAnnouncer

# TitleAnnouncer

[](https://github.com/4drian3d/TitleAnnouncer/actions)
[](https://discord.gg/5NMMzK5mAn)

A lightweight plugin to send Titles, Actionbars, Bossbars and Chat Announces to Paper servers and Velocity networks.

## Features
– Ability to send announcements by using titles, actionbars, bossbars, and chat messages.
– Send announcements to users in the same world or server you are in.
– Send announcements to a specific user.
– Use of the [MiniMessage format](https://docs.adventure.kyori.net/minimessage.html#format) throughout the plugin, allowing the maximum possible customization.
– [MiniPlaceholders](https://modrinth.com/plugin/miniplaceholders) support

[](https://www.bisecthosting.com/4drian3d?r=ModTitleAnnouncer)

## Commands

To use the commands in Velocity, just add a “v” at the beginning of the command, for example: “/vannounce” or “/vtitleannouncer”.

### Announce Command

| Command | Arguments | Permission |
|————————-|————————————————————————————————|————————|
| /announce or /vannounce | [(Format type)](#format-argument) [(Target Argument)](#target-argument) (Format Arguments) | titleannouncer.command |

## Arguments

### Target Argument

When sending an announcement, you can define who to send it to using the target argument.
This argument allows you to select either an online player or the executor themselves, a server, or a world to send the announcement to.
The available targets are:

#### Self Target

This target allows you to send the respective announcement to the same executor of the command.
Keep in mind that if the server console uses this target, it will not be able to receive bossbars, actionbars, titles, or sounds;
it will only be able to receive chat announcements

**Example Usage**

`/(v)announce chat self Some announcement`

#### Player Target

This target allows you to send an announcement to a specific player.

Use the format `“player:PlayerName”`.

As it is an argument that uses a colon character and due to limitations of the Minecraft Vanilla command system,
it must be enclosed in quotation marks.

If executed in-game, online player names will be suggested.

**Example Usage**

`/(v)announce title “player:4drian3d” “TitleAnnouncer” “by 4drian3d”`

#### All Target

This target allows you to send an announcement to all players on the server or proxy.

If you run the command from TitleAnnouncer in Velocity, the announcement will be sent to all players on your network.
If you run it from TitleAnnouncer installed in Paper, the announcement will be sent to players connected to the server where it is run.

**Example Usage**

`/(v)announce actionbar all TitleAnnouncer | `

#### Server Target

> This target is exclusive to Velocity

This target allows you to send an announcement to the specific server where the player executing it is connected, or to a specific server.

For the executor to send the announcement to the server where it is connected, you only need to place `server` as an argument.

But if the executor wants it to be executed on another server, it must be specified with the format `“server:ServerName”`.
Like the player argument, when requiring `:`, it must be enclosed in quotation marks.

**Example Usage**

`/vannounce bossbar server 30 blue notched_12 A big announcement!!!`

`/vannounce bossbar “server:lobby” 30 blue notched_12 A big announcement!!!`

#### World Target

> This target is exclusive to Paper

This target allows you to send an announcement to the world where the player executing the command is located or to a specified world.

If you want to send the announcement to the world where the player is located, you must use the `world` argument.

But if you want to specify another world, you must use the `“world:WorldName”` argument.
Like the player argument, when requiring `:`, it must be enclosed in quotation marks.

**Example Usage**

`/announce bossbar world 30 blue notched_12 A big announcement!!!`

`/announce bossbar “world:lobby” 30 blue notched_12 A big announcement!!!`

### Format Argument

#### Chat Format

| Arguments | Permission |
|————-|—————————–|
| [Message] | titleannouncer.command.chat |


#### Actionbar Format

| Arguments | Permission |
|————-|———————————-|
| [Message] | titleannouncer.command.actionbar |


#### Title Format

| Arguments | Permission |
|—————————————————————–|——————————|
| [Title] [SubTitle] (FadeIn Time) (Stay Time) (FadeOut Time) | titleannouncer.command.title |


#### BossBar Format

| Arguments | Permission |
|—————————————————|——————————–|
| [Display Time] [Color] [Overlay] [Content] | titleannouncer.command.bossbar |


#### Sound Format

> If running on Velocity, this format will only be able to send sounds to players with versions higher than 1.19.3.

| Arguments | Permission |
|———————————————-|——————————|
| [Sound Key] (Source Type) (Volume) (Pitch) | titleannouncer.command.sound |

Tip4serv Donation Webstore

[Tip4serv.com](https://tip4serv.com/?ads=modrinth) provides gaming communities with a platform to effortlessly set up their virtual store and facilitate the sale of digital goods, including donations.

Managing a community and creating content can be demanding tasks. We aim to streamline the process, enabling managers to efficiently handle donations and automatically reward players.

Our mission is to deliver a user-friendly platform that simplifies the experience for both creators and buyers.

Here are examples of stores that you can customize: [https://murga.tip4serv.com](https://murga.tip4serv.com), [https://neon.tip4serv.com](https://neon.tip4serv.com) and [https://steelcraft.tip4serv.com](https://steelcraft.tip4serv.com)

## Features for starter plan (only 5% fee)
– Unlimited game servers & commands
– Create subscriptions plan
– Commands status tracking
– Stock management
– Deliver roles & messages on Discord
– Create discount coupon
– Add managers for your store
– Purchase email and invoice
– Sales statistics
– Private flow for subscribers
– Custom sub-domain
– Resend commands
– No ads

## Features for PRO members (subscription required)
– Dynamic Dark/Light theme
– Account linking with avatars
– Product page with gallery & video
– GUI colors editor & additional CSS
– Top customers & related products

## Store available in 15 languages

English, Danish, Dutch, English, French, German, Hungarian, Italian, Norwegian, Polish, Portuguese, Romanian, Russian, Spanish, Swedish and Turkish.

## Payment method

Here are the payment methods you can offer your players: Visa, Paypal, Cash App, Google Pay, Apple Pay, Ideal, GiroPay, BanContact, Sofort, Sepa, EPS, BACS, Amazon Pay, Revolut Pay, Mobile Pay, MultiBanco, BECS, Przelewy24, Boleto, Oxxo, Afterpay, Link.

## How does this work?

Tip4Serv checks if a player has made a donation on your Tip4Serv store and delivers the order in a minute (e.g., group, money, etc.) by executing commands in the server console.

Create your store and connect your Minecraft server in **5 minutes** on [Tip4Serv](https://tip4serv.com) in 4 simple steps:

1. **Store Settings:**
Enter your store name and set the desired URL.

2. **Payment Methods:**
Select your preferred payment options.

3. **Connect Server:**
Link your Minecraft server to Tip4Serv using your API key.

4. **Add Products:**
Create and configure products with executable commands on your server.

## Commands

**tip4serv connect** – Link your server to Tip4Serv (Ensure the API key is correctly set in tip4serv/tip4serv.key).

**tip4serv reload** – Deliver pending orders if there are any.

**/storelink** – Show a link to the store in the server chat.

## Proxy commands (Velocity & Bungeecord)

**tip4proxy connect** – Link your server to Tip4Serv.

**tip4proxy reload** – Deliver pending orders if there are any.

## Need help?
– [Documentation](https://docs.tip4serv.com/games/minecraft)
– [Contact us](https://tip4serv.com/contact)

tiAuth

# tiAuth
Authorization plugin for BungeeCord

—

### Features:
– Dialog window support `(1.21.6+)`
– Interactive window with a password input field
– Premium mode
– Allows licensed players to skip password entry by activating local `online-mode true`
– Session support
– Allows players to skip password entry for a certain period after successful authentication
– Multiple database types support
– Supports `SQLite`, `H2`, `MySQL`, `PostgreSQL`
– Virtual server
– Virtual server for auth server powered by [NanoLimbo](https://github.com/1050TIt0p/NanoLimbo)

—

### Commands:
#### For players:
– `/register ` – Register an account
– `/login ` – Log in
– `/logout` – Destory session
– `/changepassword ` – Change password
– `/premium` – Enable premium mode
– `/unregister` – Delete account

#### For administrators:
– `/tiauth reload` – Reload config
– Permission: `tiauth.admin.commands.reload`
– `/tiauth unregister ` – Delete player account
– Permission: `tiauth.admin.commands.unregister`
– `/tiauth changepassword ` – Change player password
– Permission: `tiauth.admin.commands.changepassword`
– `/tiauth forcelogin ` – Force login player
– Permission: `tiauth.admin.commands.forcelogin`
– `/tiauth migrate[file] [user] [password] [host] [port] [name]` – Migrate database from other plugins/database type
– Permission: `tiauth.admin.commands.migrate`

—

### Migration
#### Supported Plugins
– **tiAuth** (for changing the database type)
– **MCAuth**
– **LimboAuth**
– **AuthMe**

#### Migration Commands

Below are the commands for the default database types used by these plugins.

If you are using a **file-based database** (SQLite or H2):

– Place the database file into the plugin folder.
– For **H2**, **do not include** the `.mv.db` extension in the filename.
– If there is no username or password, set both `user` and `password` to `empty`.

#### MCAuth SQLite
“`
/tiauth migrate mcauth sqlite auth.db
“`

#### LimboAuth H2
“`
/tiauth migrate limboauth h2 limboauth-v2 empty empty
“`

#### AuthMe SQLite
“`
/tiauth migrate authme sqlite authme.db
“`

#### Important — LimboAuth H2 Migration

Before migrating from **LimboAuth H2** (which uses H2 as its default database):

1. Open your `config.yml`.
2. Change the `version` value under `libraries.h-2` to **2.1.214**.
3. Delete the **tiAuth** database file (if you are using H2 — it’s the default).
4. Restart your server.

This is required because **LimboAuth** uses an **outdated version of H2** that is incompatible with the newer version used by **tiAuth** by default.
If you skip these steps, the plugin will throw an error during migration.

—

### Virtual server configuration

After setting `servers.use-virtual-server` to `true` and restarting the server,
you need to configure **NanoLimbo** — its configuration is located in:

“`
/plugins/tiAuth/limbo
“`

#### Configure `infoForwarding`

– Set `type` to **MODERN** if you are using **VELOCITY_MODERN**,
then specify your **key** under `secret`.
– If you are using **BungeeGuard**, set `type` to **BUNGEE_GUARD**,
then specify your **tokens** under `tokens`.
– **LEGACY** mode is **not recommended** as it is insecure.

#### Optional Settings
You may optionally:
– Change the **port**
– Disable **BossBar**, **Join Message**, etc.

After editing `/plugins/tiAuth/limbo/settings.yml`,
**restart your proxy** to apply the changes.

—

### Support
[Discord Server](https://discord.matvey.tatar/)
[Telegram](https://t.me/x1050ti_top)

ThemisToProxy

# ThemisToProxy

Get Themis’ notifications from anywhere in your network

Available for **Bukkit/Spigot/Paper** and **Velocity** (**BungeeCord** support soon)


# Installation
– Install the plugin in your proxy and backends that use [**Themis Anti Cheat**](https://www.spigotmc.org/resources/themis-anti-cheat-1-17-1-21-bedrock-support-paper-compatibility-free-optimized.90766/)
– Restart your proxy and backends
– You’re done! Every player that has permission to see Themis’ notifications will receive a notification
if a player gets flagged in any server.

# Config
Only available in the proxy. Default config:
“`yaml
message-format: “§6%server% §8| §r%message%”
“`

TheAPI


## Our purpose
Are you tired of looking for different APIs on the internet to create in your projects? Neither do we! And this is why TheAPI is here.
We bring the most useful and most wanted features directly for developers. From custom configurations with comments feature to Object parsers to String and back. Also, TheAPI offers an extensive Sockets API that will make working with sockets a million times easier! And we have much more, check out the sample code in the Examples section.

## Looking for source-code?
Our project is located on github:
https://github.com/TheDevTec/TheAPI

# How to include the API with Maven:

“`


jitpack.io
https://jitpack.io




com.github.TheDevTec
TheAPI
13.8
provided


“`

# How to include the API with Gradle:
“`
repositories {
maven { url ‘https://jitpack.io’ }
}
dependencies {
compileOnly “com.github.TheDevTec:TheAPI:13.8”
}
“`

## Our community
Join our Discord community for help and advice!
https://discord.gg/APwYKQRxby

TG-MOTD

# If you want to help us please [Donate](https://kamaucha.me/prabin9) us.
### ✨ Key Features

**🎨 Advanced Text Formatting**
– Full MiniMessage support with gradients and advanced formatting
– Legacy color codes with hex color support (&#RRGGBB)
– Create stunning MOTDs with unlimited color combinations
– Support for bold, italic, underline, strikethrough, and more

**🔧 Highly Customizable**
– Multi-line MOTD with dynamic placeholders
– Custom hover information for player list
– Custom server icons (favicons)
– Fake player count manipulation (add fixed or percentage)
– Protocol-specific MOTDs for different Minecraft versions
– Configurable update intervals

**🛠️ Professional Maintenance Mode**
– Toggle maintenance with a simple command
– Custom maintenance MOTD and kick messages
– Whitelist system for admins and staff
– Override player counts during maintenance
– Separate maintenance hover information

**👥 Powerful Whitelist System**
– Dedicated `players.yml` for whitelisted players
– Whitelisted players automatically get admin permissions
– Easy management with intuitive commands
– Bypass maintenance mode restrictions

**⚡ Performance Optimized**
– Lightweight and efficient
– Cached favicon loading
– Configurable update intervals
– Minimal resource usage

—

**🎥 Tutorials**
– Techinpoint Gamerz

—

### 📋 Requirements

– **Velocity:** 3.3.0 or higher
– **Java:** 21 or higher

—

### 🚀 Quick Start

1. Download the plugin
2. Place in your Velocity `plugins` folder
3. Restart your proxy
4. Edit `config.yml` in `plugins/tgmotd/`
5. Run `/tgmotd reload`

—

### 📝 Commands

| Command | Description |
|———|————-|
| `/tgmotd reload` | Reload configuration |
| `/whitelist add ` | Add player to whitelist |
| `/whitelist remove ` | Remove player from whitelist |
| `/whitelist list` | List whitelisted players |
| `/maintenance ` | Toggle maintenance mode |

**Permission:** `tgmotd.admin` or be whitelisted

—

### 🎨 Example MOTDs

**Gradient MOTD:**
“`yaml
motd:
lines:
– “MY SERVER | [1.21+]”
– “⚡ Join Today!”
“`

**Legacy with Hex Colors:**
“`yaml
formatter: LEGACY
motd:
lines:
– “&#FF0000&lM&#FF3333&lY &#FF6666&lS&#FF9999&lE&#FFCCCC&lR&#FFFFFF&lV&#CCCCFF&lE&#9999FF&lR”
– “&7Welcome to our network!”
“`

—

### 🎯 Perfect For

– ✅ Network servers wanting professional appearance
– ✅ Servers needing maintenance mode
– ✅ Communities wanting custom branding
– ✅ Admins who value easy configuration
– ✅ Servers requiring whitelist functionality

—

### 🔑 Placeholders

– `{online}` – Current online players
– `{max}` – Maximum players
– Use in MOTD lines, hover text, and kick messages

—

### 🛡️ Support

Need help? We’ve got you covered:
– 💬 [Discord Support](https://discord.com/invite/y5UKjK3Zxp)

—

### 📊 Statistics

– ⚡ Lightweight: < 1MB - 🚀 Fast: Optimized performance - 🔧 Configurable: 20+ options - 📝 Commands: 5 useful commands --- ### 👨‍💻 Developer Created by **TG ([Techinpoint Gamerz](https://www.youtube.com/@TechinpointGamerz))** --- ### 📄 License MIT License - Free to use --- **Download now and give your server the professional look it deserves!** ⭐

TeleHop

# 🌐 TeleHop
**Cross-server teleportation for Paper and Velocity networks**

TeleHop is a full-featured teleportation suite built for **multi-server Minecraft networks**.
Every feature works across servers, players stay connected across your entire network.

All data is stored in **MySQL**, so homes, warps, teleport requests, and player state stay synced at all times.

—

## 🔗 Links
– [GitHub Repository](https://github.com/gitEpildev/TeleHop)
– [Full Documentation](https://github.com/gitEpildev/TeleHop/blob/main/README.md)
– [Configuration Guide](https://github.com/gitEpildev/TeleHop/blob/main/WIKI.md)
– [Installation Guide](https://github.com/gitEpildev/TeleHop#installation)
– [Permissions Reference](https://github.com/gitEpildev/TeleHop#permissions)
– [Database Structure](https://github.com/gitEpildev/TeleHop#database-tables)
– [Issue Tracker and Support](https://github.com/gitEpildev/TeleHop/issues)
– [Releases](https://github.com/gitEpildev/TeleHop/releases)

—

## 📦 Version 1.0.2
Focus on **stability, cross-server consistency, and feature completeness.**

### ➕ Added
– Random respawn system with safe async location search
– Respawn config with full control over behaviour
– Generated `WIKI.md` config reference on first run
– Improved feature toggles for per-server control

### 🔧 Improved
– Cross-server sync for homes, warps, and TPA
– Teleport safety checks for RTP and respawn
– Async handling for teleport and location search
– Config migration system with non-destructive updates

### 🐛 Fixed
– Cross-server teleport failures in edge cases
– TPA desync between servers
– Back command inconsistencies after death
– Permission inconsistencies across modules

—

## ✨ Features

### 🚀 Teleportation
– `/spawn` send players to the hub server from anywhere
– `/tpa` request teleport to another player across servers
– `/tpahere` pull another player to your location
– `/tpaaccept`, `/tpadeny`, `/tpacancel`
– `/tpatoggle` block incoming requests for the session
– `/back` return to last teleport or death location across servers
– `/rtp` random teleport with GUI region and dimension selection, configurable radius, safe landing

—

### 💀 Random Respawn
– Teleport players to a safe random location on death
– Async safe location search
– Respects beds and anchors
– Skips hub server
– Controlled via `respawn.yml`
– Enabled by default via `features.yml`

—

### 🌍 Warps
– Admin warps: `/warp`, `/setwarp`, `/delwarp`, `/warps`
– Shared across all servers via MySQL
– Player warps: `/pwarp` with per-rank limits and public or private toggle

—

### 🏠 Homes
– `/home`, `/sethome`
– Permission-based slots from 1 to 5
– GUI with slot indicators
– Cross-server teleport support
– Blocked server support

—

### 🛠 Admin Tools
– `/tp`, `/tphere` cross-server admin teleportation
– `/telehop reload` reload config
– `/telehop version` show version
– `/telehop perms` list permissions
– `/telehop help` show help
– `/listwarps` list all warps
– `/forcedelwarp` remove warp
– `/forcedelhome` remove player home

—

## ⚡ Highlights

– Fully cross-server, all features sync across Velocity
– MySQL backed, no per-server duplication, MariaDB supported
– Random respawn system with full config control
– Modular config, enable or disable features per server
– Teleport effects, configurable particles and sounds
– Multi-language, 6 built-in languages with fallback support
– LuckPerms support for limits and permissions
– Tab completion across the entire network
– Auto config migration with safe updates
– `WIKI.md` generated automatically for full config reference

—

## 🧩 Multi-Server Support

TeleHop is built for **Velocity networks**, not single-server setups.

– Velocity handles routing and player tracking
– Paper handles teleport execution
– MySQL stores shared data

This enables:
– Cross-server TPA and teleportation
– Shared homes and warps across all servers
– `/back` working across server boundaries
– Session-based TPA toggle synced across servers

Both Velocity and Paper plugins are required.

—

## 📥 Installation

### Requirements
– Paper 1.21+
– Velocity 3.3+
– Java 21+
– MySQL 8.0+ or MariaDB 10.5+
– LuckPerms 5.4+ optional

—

### Setup
1. Create a MySQL database and user
2. Place `telehop-velocity-1.0.2.jar` in the Velocity plugins folder
3. Place `telehop-paper-1.0.2.jar` in each Paper server plugins folder
4. Start Velocity once to generate config, then stop
5. Configure `database.yml` with your credentials
6. Set `server-name` in `general.yml` to match Velocity config
7. Start Velocity, then start all backend servers

Database tables are created automatically on first startup.
Random respawn is enabled by default. Disable in `features.yml` if needed.

—

## 🔄 Updating

– Replace old `.jar` files
– New config files are added automatically
– Existing configs are not overwritten
– Legacy `config.yml` is migrated and renamed to `.old`

—

## 📁 Configuration Layout

“`
plugins/TeleHop/
config/
general.yml
database.yml
features.yml
teleport.yml
tpa.yml
rtp.yml
home.yml
respawn.yml
WIKI.md
storage.yml
languages/
“`

—

## 🗄 Database Tables

– `players` tracks player server
– `warps` stores admin warps
– `player_warps` stores player warps
– `tpa_requests` stores active requests
– `homes` stores player homes

—

## 🔐 Permissions

Use `/telehop perms` in-game for the full list.

### Default Permissions
– `telehop.spawn`
– `telehop.rtp`
– `telehop.warp`
– `telehop.pwarp`
– `telehop.tpa`
– `telehop.tpahere`
– `telehop.tpa.accept`
– `telehop.tpa.deny`
– `telehop.tpa.cancel`
– `telehop.tpa.toggle`
– `telehop.homes`
– `telehop.homes.1`

—

### 🏠 Home Slots
– `telehop.homes.1` to `telehop.homes.5`

—

### 🌍 Player Warp Limits
– `telehop.warps.1`
– `telehop.warps.3`
– `telehop.warps.10`
– `telehop.warps.100`
– `telehop.warps.unlimited`

—

### 🔓 Per Warp Access
– `telehop.warp.`

—

### 🛠 Admin Permissions
– `telehop.admin`
– `telehop.back`
– `telehop.back.death`
– `telehop.tp`
– `telehop.tphere`
– `telehop.rtp.bypasscooldown`
– `telehop.rtp.bypassdelay`
– `telehop.tpa.bypasscooldown`
– `telehop.warps.unlimited`

—

## ⚠ Compatibility

– Paper only
– Velocity only
– BungeeCord not supported
– Hybrid servers not supported

—

## 👤 Credits

Developed by Epildev & GitEpildev from Epildevconnect ltd
Licensed under MIT Licence

TelegramWhitelist

# TelegramWhitelist
This is plugin for add player in whitelist via Telegram bot on proxy server

## Setup
1. Setup plugin on your proxy server
2. Restart server and go to plugin config
3. Enter your telegram bot token, allowed user id and whitelist command
4. Restart server and all done

## How it work
When you write bot nickname of player, bot execute your whitelist command on proxy server

## FAQ
What if someone who is not a allowed user type writes to the bot?
> Bot just send to user “❌ You are not allowed” and type warning in console

## Support
If you have idea for new feauture to plugin, or you found a bug, [open issue](https://github.com/pixiemays/TelegramWhitelist/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen) in plugin repository or go to [my discord](https://discord.gg/gU7XPHeqnW) for support

## Basic config
“`
# Telegram bot token (get in @BotFather)
bot-token: “YOUR_BOT_TOKEN_HERE”

# Telegram user ID list, of allowed user
allowed-users:
– 123456789
– 987654321

# Execution command (paste nick)
# {nick} — player nick placeholder
commands:
add: “swl add {nick}”
remove: “swl remove {nick}”
“`

TelegramLogger

# Telegram Logger
This plugin allows you to receive notifications in a telegram group/chat when a player connects to the Velocity server

## Installation
– Download the latest version from the [versions page](https://modrinth.com/plugin/telegramlogger/versions).
– Move the installed file to the `plugins` folder.
– Start server.

## Usage
After fully setting up the plugin, you will receive notifications about players joining from your Velocity server

## Configuration
– After starting server, `config.yml` will be generated in the `plugins/telegram-logger` folder
– In field `telegramBotToken` you must write your [Telegram Bot Token](t.me/BotFather)
– In field ‘chatId’ you must write your [Telegram Chat Id](https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id/32572159#32572159)
– You can configure messages in fields `playerLoginMessage` `proxyStartMessage` `proxyShutdownMessage`

## Find bug or need help?
– You can join my [discord](https://discord.gg/nyyyDStTRF) and ask for help =)

Tebex

## What Is Tebex?
Tebex is a game monetization engine featuring over 120 payment methods, chargeback protection, fraud protection, and 3-day payouts. Tebex allows you to sell items, subscriptions, and more from an in-game customized shop.

Players browse your store, select and purchase their items, and Tebex automatically delivers the items when the player is next online. View more at https://tebex.io

See an interactive Tebex store using one of our free templates at https://example.tebex.io/

## Features
– **Simple and Powerful.** Create fully customizable themed web stores and start selling in minutes.
– **No Hidden Fees.** Enjoy flat-rate pricing with no surprises.
– **Worldwide Payments Support.** Accept over 120+ payment types with Tebex acting as your merchant of record, including PayPal, Paysafecard, Google Pay, and more.
– **Chargeback and Fraud Protection.** Tebex handles fraud reports and disputes/chargebacks on your behalf while providing 100% insurance.
– **Made for Everyone.** Whether you’re starting or an established network, Tebex offers a comprehensive set of shop management tools to handle every facet of your game’s economy.

## Installation and Setup
1. Create a free webstore at https://tebex.io/
2. Download the latest version of the plugin from Modrinth or any official Tebex listing.
3. Place the downloaded Tebex `.jar` in the `plugins` folder of your relevant platform.
4. Restart your server.
5. Run `/tebex secret your-key-here` as a server admin to connect the server to Tebex.

Your secret key can always be found at: https://creator.tebex.io/game-servers. Click Connect Game Server, and then choose Plugin to view your secret key.

## Usage and Commands
Tebex will automatically fulfill any orders from your webstore every two minutes. These are run as server commands, such as giving items or adding groups, which you can define in your store.

Note: Not all commands are available on all platforms. Proxy servers may have a reduced set of commands. Use `/tebex help` to get the relevant list of commands on any platform.

Below are a list of commands used to manage the plugin:

### Permissions
All commands have a permission node which matches with the exact command name. For example a player must have `tebex.help` as a permission in order to view available
commands.

### User Commands
“`
/tebex help Shows available commands
/tebex secret Sets your store’s secret key
/tebex info Shows store information
/tebex checkout Creates payment link for a package
“`

### Administrator Commands
“`
/tebex sendlink Sends payment link to player
/tebex report Reports a problem to Tebex
/tebex ban Bans a user from the webstore
/tebex lookup Looks up user transaction info
“`

### Debug Commands
“`
/tebex debug Enables debug logging
/tebex forcecheck Force runs all time-based events
/tebex refresh Reloads store and package info
“`

## Resources
Here are some additional resources to help you build your Tebex store.

– ❔ [Frequently Asked Questions](https://docs.tebex.io/creators/faq) – Get answers to common questions fast
– 🧠 [Tebex Academy](https://www.youtube.com/@tebex/videos) – Learn to build a successful Tebex store with video tutorials
– ⚙️ [Technical Support](mailto:[email protected]) – Get assistance as a buyer or seller, email us at [email protected]
– 🖥️ [Developer Documentation](https://docs.tebex.io/developers/) – Develop custom integrations to suit your needs
– 💬 [Feedback Form](https://wkf.ms/45PQwfE) – Help us build a better product by sharing your feedback

## Our Mission
Founded in 2011, our mission has always been the same: helping creators in the gaming industry create new revenue streams without having to invest the time and effort involved in processing and managing global payments.

Since then, we helped generate over half a billion dollars for our clients, providing them with a full suite of monetization features, handling all taxes, billing, and providing full insurance. Making sure they can focus on what they do best – creating great gaming experiences.