ViaVersionStatus

# Description

ViaVersionStatus will report which Minecraft versions your players are using when they join your server. Reports are sent to your server log file and online players with the permission viaversionstatus.notify. Optionally, if a player joins with a client version different than your server version, the plugin can send the player a warning that he’s not using the matching client version. The plugin can also issue console commands based on the client’s version.

Reasonable default values are provided in the configuration file, so you can simply put the plugin in your plugins folder and restart your server. The plugin requires [ViaVersion](https://modrinth.com/plugin/viaversion) and Java 17+.



Note that ViaVersion provides a command to show the versions of all currently online players: /viaversion list

# Permissions

ViaVersionStatus has a number of permissions to allow fine-tuning of its behavior. However, all you really need to do is give the permission **viaversionstatus.notify** to admins you want to receive in-game version notifications when other players join. If you give yourself the ‘*’ permission, you might also want to set **viaversionstatus.notify.ignoresame** to false.

Following are details of all ViaVersionStatus permissions:

## Permission Details

The following permissions normally given only to admins, as they control the in-game notification given when players join the server.

**viaversionstatus.notify** – A player with this permission will get a message with the player’s client version (as shown above) when they join the server. Defaults to op.

**viaversionstatus.notify.ignoresame** – A player with this permission will not get a message with the player’s client version if the client’s version matches the server’s version. Defaults to false.

The following permissions apply to the players joining your server and can be used to control exactly which features of ViaVersionStatus will be invoked when they join. All of the following permissions default to false, so simply give a player(s) a permission to exempt them from the corresponding processing. Most of these features can also be disabled in the config file if you want to do so for all players.

**viaversionstatus.exempt** – Exempts this player from all processing at join.

**viaversionstatus.exempt.log** – Exempts this player from client version being logged at join.

**viaversionstatus.exempt.notify** – Exempts this player from notifying other players at join while also preventing them from triggering the configured join notification command.

**viaversionstatus.exempt.notify.message** – Exempts this player from notifying other players at join.

**viaversionstatus.exempt.notify.command** – Exempts this player from triggering the configured join notification command.

**viaversionstatus.exempt.warn** – Exempts this player from receiving an older version warning while also preventing them from triggering the configured older version warning command.

**viaversionstatus.exempt.warn.message** – Exempts this player from receiving an older version warning.

**viaversionstatus.exempt.warn.command** – Exempts this player from triggering the configured older version warning command.

**viaversionstatus.exempt.warn.newer** – Exempts this player from receiving an newer version warning while also preventing them from triggering the configured newer version warning command.

**viaversionstatus.exempt.warn.newer.message** – Exempts this player from receiving a newer version warning.

**viaversionstatus.exempt.warn.newer.command** – Exempts this player from triggering the configured newer version warning command.

# Configuration (optional)

Strings in the configuration file can use four variables: **%player%** is replaced with the player’s name, **%displayname%** is replaced with the player’s “display name”, **%version%** is replaced with the version of the player’s client, and **%server%** is replaced with the detected server version. You can also use the standard Minecraft color codes. Strings should be enclosed in double quotes (“…”).

**notify-ops** – If true, ops will be notified of the client’s version when any player joins the server.

**notify-string** – This message is sent to players with the viaversionstatus.notify permission when any player joins the server.

**notify-command** – This command is issued by the console when a player joins the server (defaults to none).

**warn-players** – If true, players joining with a client that is older than the server version will be warned with the warn-string message.

**warn-string** – This message is set to players joining with a client that is older than the server version, if enabled. Note that warn-players must be true to use this.

**warn-command** – This command is issued by the console when a player joins with a client that is older than the server version (defaults to none). Note that warn-players must be true to use this.

**warn-players-newer** – If true, players joining with a client that is newer than the server version will be warned with the warn-string message.

**warn-string-newer** – This message is set to players joining with a client that is newer than the server version, if enabled. Note that warn-players-newer must be true to use this.

**warn-command-newer** – This command is issued by the console when a player joins with a client that is newer than the server version (defaults to none). Note that warn-players-newer must be true to use this.

**high-priority** – When set to true, ViaVersionStatus will run later in the login process. This can be useful if %displayname% in notify-string is not working as expected.

**list-supported-protocols** – If true, the protocols (Minecraft versions) supported by ViaVersion will be written to the log file at startup.

**enable-metrics** – If true, bStats metrics will be enabled by this plugin, subject to the bStats global config entry.

**prism-integration** – If true, ViaVersionStatus will send an event to the Prism logging plugin, with the player’s name and client version. See the section below for more details.

**prism-action-string** – This string is used by Prism when displaying a player’s client version.

A note about %displayname%: The displayname is set by other plugins, so this is dependent on the other plugin’s timing. In particular, EssentialsX has a built-in time delay which will prevent the displayname from appearing in the notification sent to ops. However, the displayname can be used in the version warning sent to the players.

The default configuration results in the messages shown above.

# Prism Integration

If you use the [Prism V4](https://modrinth.com/plugin/prism) logging plugin, you can have ViaVersionStatus log each player’s name and client version when they join the server. Prism V4 is a complete rewrite of Prism. The event is logged with the action vvs-connect. You can specify this during a lookup with the parameter a:connect. You must be using **Prism V4.3-dev31 or later**.

In order to enable the Prism integration you need to set **prism-integration** in the ViaVersionStatus config file to true. ViaVersionStatus will write to the log file if it has successfully hooked into Prism.

Here’s an example of the Prism lookup results:


# Commands

None.

# Miscellaneous

This plugin is compatible with ViaVersion, ViaBackwards, and ViaRewind.

This plugin uses the bStats metrics system to provide _anonymous_ usage data. You may opt-out by changing **enable-metrics** in the ViaVersionStatus config file. The metrics are available at [https://bstats.org/plugin/bukkit/ViaVersionStatus](https://bstats.org/plugin/bukkit/ViaVersionStatus)


ViaVersion

# ViaVersion
Allows you to connect to servers that are older than your Java Edition client version. See our [GitHub page](https://github.com/ViaVersion) for more information.

**On Fabric, use either [ViaFabric](https://modrinth.com/mod/viafabric) or [ViaFabricPlus](https://modrinth.com/mod/viafabricplus). To override the included version**
– in **ViaFabric**, put ViaVersion into the `mods` folder
– in **ViaFabricPlus**, put ViaVersion into the `config/viafabricplus/jars` folder

[Bungee](https://hangar.papermc.io/ViaVersion/ViaBungee) and [Sponge](https://modrinth.com/project/viasponge) also have their own platform implementations.

Requires Java 17. See [here](https://docs.papermc.io/misc/java-install) how to update your installed Java version. As a last resort, you can download Java 8 downgraded builds from [our ci](https://ci.viaversion.com/job/ViaVersion-Java8/).

## Get access to Via* with new MC version support early
**Starting with 1.20.5, ViaVersion and ViaBackwards will only be released a day or so *after* a Minecraft update** unless the protocol changes of the update were trivial. **If you want early-access, usually days or even weeks before the final release, you can subscribe to either**:
– [GitHub Sponsors](https://github.com/sponsors/kennytv/sponsorships?sponsor=kennytv&tier_id=385613&preview=false) (*preferred option*. Use the `/verify` command on this Discord after), or alternatively
– [Patreon](https://www.patreon.com/kennytv/membership) (see the highest tier and make sure to link Patreon to your Discord account under Discord Settings->Connections)

## Note on release channels
It is recommended to always use the latest beta release. Alpha builds are used for work on snapshot version compatibility or other cutting-edge changes.

**Always use the same build channel across the ViaVersion, ViaBackwards, and ViaRewind projects.**

Releases/Dev Builds
——–
You can find official releases in the following places:

– **Hangar (for our plugins)**: https://hangar.papermc.io/ViaVersion/ViaVersion
– **Modrinth (for our mods)**: https://modrinth.com/mod/viaversion
– **GitHub**: https://github.com/ViaVersion/ViaVersion/releases

Dev builds for **all** of our projects are on our Jenkins server:

– **Jenkins**: https://ci.viaversion.com

ViaVersion as a Dependency
———-

**JavaDocs:** https://jd.viaversion.com

**Maven:**

“`xml

viaversion-repo
https://repo.viaversion.com

“`

“`xml

com.viaversion
viaversion-api
[4.0.0,5.0.0)
provided

“`

**Gradle:**

“`kotlin
repositories {
maven(“https://repo.viaversion.com”)
}

dependencies {
compileOnly(“com.viaversion:viaversion-api:VERSION”) // Replace the version
}
“`

Resources
——–

– **[Via Mappings Generator](https://github.com/ViaVersion/Mappings)**
– **[Mojang mappings](https://minecraft.wiki/w/Obfuscation_map)** (Thank you, Mojang, very cool)
– **[wiki.vg](https://wiki.vg)** (Used for historic information regarding packet structure, we also contribute back)
– **[Burger](https://github.com/Pokechu22/Burger)** (See [PAaaS](https://github.com/Matsv/Paaas))

Special thanks to all our [Contributors](https://github.com/ViaVersion/ViaVersion/graphs/contributors).

ViaRewind

# ViaRewind
**ViaVersion addon to allow 1.8.x and 1.7.x clients on newer server versions.**
Runs on 1.9-latest servers or 1.8 clients and lower.

**You can override the included version in [ViaFabric](https://modrinth.com/mod/viafabric) or [ViaProxy](https://github.com/ViaVersion/ViaProxy):**
– in **ViaFabric**, put ViaRewind into the `mods` folder
– in **ViaProxy**, put ViaRewind into the `jars` folder

Requires Java 17. See [here](https://docs.papermc.io/misc/java-install) how to update your installed Java version. As a last resort, you can download Java 8 downgraded builds from [our ci](https://ci.viaversion.com/view/ViaRewind/job/ViaRewind-Java8/).

**Requires [ViaVersion](https://hangar.papermc.io/ViaVersion/ViaVersion) and [ViaBackwards](https://hangar.papermc.io/ViaVersion/ViaBackwards) to be installed..**

Releases/Dev Builds
–
You can find releases in the following places:

– **Hangar (for our plugins)**: https://hangar.papermc.io/ViaVersion/ViaRewind
– **Modrinth (for our mods)**: https://modrinth.com/mod/viarewind
– **GitHub**: https://github.com/ViaVersion/ViaRewind/releases

Dev builds for **all** of our projects are on our Jenkins server:

– **Jenkins**: https://ci.viaversion.com/view/ViaRewind/

Other Links
–
**Maven:** https://repo.viaversion.com/

**Issue tracker:** https://github.com/ViaVersion/ViaRewind/issues

**List of contributors:** https://github.com/ViaVersion/ViaRewind/graphs/contributors

ViaAprilFools

# ViaAprilFools
ViaVersion addon to add support for some notable Minecraft snapshots.

**You can override the included version in [ViaFabric](https://modrinth.com/mod/viafabric) or [ViaProxy](https://github.com/ViaVersion/ViaProxy):**
– in **ViaFabric**, put ViaAprilFools into the `mods` folder
– in **ViaProxy**, put ViaAprilFools into the `jars` folder

Requires Java 17. See [here](https://docs.papermc.io/misc/java-install) how to update your installed Java version.

**Requires [ViaVersion](https://hangar.papermc.io/ViaVersion/ViaVersion) and [ViaBackwards](https://hangar.papermc.io/ViaVersion/ViaBackwards) to be installed..**

### Added Server protocols
– 3D Shareware
– 20w14infinite
– Combat Test 8c

### Added Client protocols
– 3D Shareware
– Combat Test 8c

## Contact
If you encounter any issues, please report them on the
[issue tracker](https://github.com/ViaVersion/ViaAprilFools/issues).
If you just want to talk or need help implementing ViaAprilFools feel free to join the ViaVersion
[Discord](https://discord.gg/viaversion).

vHubs

# vHubs

    

vHubs is a lightweight, configurable Velocity plugin for managing hub servers and hub behaviour across your proxy network. It focuses on easy setup, flexible hub definitions, and useful convenience commands to streamline player flow on large networks.

## Features

– Hub server management: define one or more hub servers. Allows for randomized server selection.
– Simple commands for staff and users to teleport to hubs.
– Permission-based control for fine-grained access.

## Quick start

1. Drop `vHubs-VERSION.jar` into your Velocity `plugins` folder.
2. Start or restart your Velocity proxy to generate the default config.
3. Edit `plugins/vhubs/config.yml` to add your hubs and preferences.

## Installing

1. Place `vHubs-VERSION.jar` into your Velocity `plugins` folder.
2. Start or restart your Velocity proxy.
3. Edit the generated configuration file (`plugins/vhubs/config.yml`) to suit your preferences.

Once installed and configured, vHubs will automatically handle hub commands behavior according to your config.

Permission nodes are configurable in your permission manager of choice.

## Why vHubs?

– Purpose-built for Velocity: simple, stable, and focused on proxy-side hub logic.
– Quick setup: install, edit a small YAML, and you’re ready.
– Community-friendly: open to feedback and contributions.

## Contributing

Contributions are welcome. Good first steps:
– Open issues to report bugs or propose features.
– Submit pull requests with clear descriptions and tests where possible.
– Follow repository code style and include a changelog entry for larger changes.

## Building from Source

Prerequisites: Java 17+, Maven.

“`bash
git clone https://github.com/szymon-off/vHubs.git
cd vHubs
mvn clean package
“`

The built jar will be in the `target` directory.

## Support

For help or to report issues, please use the [GitHub Issues page](https://github.com/szymon-off/vHubs/issues)
or join our [Discord server](https://discord.gg/your-invite-link).

## License

vHubs is licensed under the GPLv3 License. See the [LICENSE](LICENSE.md) file for details.

VHS Shader

**English version:**

VHS Shader — Play Minecraft Like It’s on an Old VHS Tape 📼

Transforms your Minecraft into a retro VHS camera recording. RGB color split, tape wobble, scanlines, random tracking glitches, color bleed, warm yellow tint, heavy grain and head switching artifact at the bottom — everything you’d expect from a dusty old VHS tape found in the attic.

**Features:**
– RGB color split like deteriorating tape
– Horizontal tape wobble distortion
– CRT scanlines
– Random tracking glitch lines
– Horizontal color bleed
– Warm yellow-green VHS tint
– Heavy 24fps film grain
– Head switching artifact at the bottom of the screen
– Brightness flicker like power fluctuation
– Camera lens vignette

Compatible with Minecraft 1.0–1.21.x via OptiFine or Iris.

Subscribe so you don’t miss any updates! If you have questions or need support, join our Discord.

—

**Русская версия:**

VHS Shader — Играй в Майнкрафт как на старой VHS кассете 📼

Превращает твой Майнкрафт в запись на ретро VHS камеру. Расползание RGB каналов, дрожание ленты, сканлайны, случайные глитчи трекинга, размытие цветов, тёплый жёлтый тинт, тяжёлое зерно и артефакт переключения головки внизу экрана — всё как на пыльной кассете найденной на чердаке.

**Возможности:**
– Расползание RGB каналов как на изношенной ленте
– Горизонтальное дрожание ленты
– CRT сканлайны
– Случайные полосы трекинга
– Горизонтальное размытие цветов
– Тёплый жёлто-зелёный VHS тинт
– Тяжёлое зерно на 24 fps
– Артефакт переключения головки внизу экрана
– Мигание яркости как перепады питания
– Виньетка объектива камеры

Совместимо с Minecraft 1.0–1.21.x через OptiFine или Iris.

Подписывайтесь, чтобы не пропустить обновления! Если есть вопросы — заходите в Discord за поддержкой.

Vexal Infinite Buckets

—

# 🪣 Vexal Infinite Bucket

An advanced Minecraft plugin that enhances the vanilla bucket experience by introducing **infinite** and **multi-capacity** fluid storage.
Perfect for **builders**, **redstone engineers**, and **survival players** who want to handle water and lava efficiently — without sacrificing performance or stability.

—
## Showcase Video

—

## ✨ Features

* ♾️ **Infinite Mode** – Use **water** or **lava** endlessly without refilling.
* 🧺 **Storage Mode** – Store **multiple buckets** of the same fluid in one item.
* 🔁 **Mode Switching** – Toggle between **Infinite** and **Storage** modes by sneaking and right-clicking.
* 🔥 **Supports All Fluids** – Works with both **water** and **lava**.
* ⚙️ **Fully Configurable** – Customize capacity limits, messages, and behavior via `config.yml`.
* 🧩 **Paper / Spigot Compatible** – Works seamlessly with modern server software.
* 💾 **Lightweight** – Designed for production servers; zero lag and minimal overhead.

—

## 🧱 Requirements

* **Minecraft:** 1.20+
* **Server Software:** Paper, Purpur, or Spigot
* **Java:** 17 or newer

—

## ⚙️ Installation

1. Download the latest version of `VexalInfiniteBucket.jar`.
2. Drop it into your server’s `/plugins/` directory.
3. Start or restart the server.
4. Edit `/plugins/VexalInfiniteBucket/config.yml` to customize settings.
5. Run `/bucket reload` to apply configuration changes.

—

## 💬 Commands & Permissions

| Command | Description | Permission | Default | |
| ———————– | —————————————— | —————————————- | ————————- | —- |
| `/bucket give ` | Gives a Vexal Infinite Bucket to a player. | `vexalinfinitebucket.give` | OP | |
| `/bucket mode ` | Toggles or sets the current bucket mode. | `vexalinfinitebucket.use` | TRUE |
| `/bucket reload` | Reloads the plugin configuration. | `vexalinfinitebucket.reload` | OP | |

—

## 🧾 Configuration Example

“`yaml
# Vexal Infinite Bucket Configuration
settings:
default-mode: storage
max-storage: 16 # Number of fluid units stored in storage mode
allow-infinite: true
messages:
switched-mode: “&aYou switched your bucket to &e%mode% &amode!”
not-allowed: “&cYou don’t have permission to use this bucket.”
“`

—

## 🪄 Usage

1. Obtain a bucket with `/bucket give`.
2. **Sneak + Right-click** to toggle between **Infinite** and **Storage** modes.
3. In **Storage Mode**, collect and place fluids — the bucket tracks how much it holds.
4. In **Infinite Mode**, it never runs out.

—

## 💬 Support

Need help or found a bug?
Join our [Discord community](https://discord.vexalstudios.com) for fast support and updates.

—

## 🧩 Compatibility

✅ Paper / Spigot / Purpur
✅ Works with protection plugins like WorldGuard & GriefPrevention
✅ Compatible with Minecraft 1.20–latest

—

## 🏷️ Tags

`bukkit` · `paper` · `utility` · `survival` · `fluids` · `infinite` · `minecraft-plugin`

—

VersionTinmoli

# VersionTinmoli

> **Version**: 1.0.2
> **Supported Platforms**: Velocity 3.0+ | BungeeCord 1.16+ | Bukkit/Spigot/Paper 1.20.1+

A lightweight Minecraft proxy/server plugin for customizing the version name displayed in the server list, with rich color and formatting support.

[中文文档](README_CN.md) | [English Documentation](README.md)

—

## Table of Contents

– [Features](#features)
– [Supported Platforms](#supported-platforms)
– [Quick Start](#quick-start)
– [Color Support](#color-support)
– [Commands](#commands)
– [Configuration](#configuration)
– [FAQ](#faq)
– [Changelog](#changelog)

—

## Features

– **Colored Version Names** – Velocity supports MiniMessage format (RGB, gradients, rainbow), BungeeCord/Bukkit support legacy color codes
– **Rich Formatting** – Bold, italic, underline, strikethrough support
– **Hot Reload** – Reload configuration with `/vt reload` command
– **Dynamic Modification** – Instantly modify version name with `/vt md ` command
– **Simple Configuration** – YAML configuration file
– **Lightweight** – No performance impact
– **Auto Fallback** – Compatible with older client versions
– **Multi-language** – Supports English and Chinese

—

## Supported Platforms

| Platform | Version | Java Version | Status |
|———-|———|————–|——–|
| Velocity | 3.0+ | Java 21+ | Fully Supported |
| BungeeCord | 1.16+ | Java 17+ | Fully Supported |
| Bukkit/Spigot | 1.20.1-1.21.11 | Java 17+ | Requires newer version |
| Paper | 1.20.1-1.21.11 | Java 17+ | Fully Supported |

—

## Quick Start

### Installation

1. Download the JAR file for your platform from [Releases](https://github.com/Tinmoli/VersionTinmoli/releases)
2. Place the JAR file in your server’s `plugins/` directory
3. Restart the server
4. Edit the configuration file (auto-generated)
5. Use `/vt reload` to reload the configuration

### Configuration File Location

– **Velocity**: `plugins/versiontinmoli/config.yml`
– **BungeeCord**: `plugins/VersionTinmoli/config.yml`
– **Bukkit**: `plugins/VersionTinmoli/config.yml`

—

## Color Support

### Velocity – MiniMessage Format

“`yaml
# Named colors
version_name: “Velocity 1.8-1.21”

# RGB colors (1.16+)
version_name: “<#FF5555>Red <#55FF55>Green”

# Gradient effects
version_name: “Rainbow Server”

# Rainbow effects
version_name: “Rainbow Server”

# Style combinations
version_name: “VIP | Online”
“`

**Available Colors**: ``, ``, ``, ``, ``, ``, ``, ``, ``, ``, ``

**Available Styles**: ``, ``, ``, ``

—

### BungeeCord/Bukkit – Legacy Color Codes

“`yaml
# Basic colors
version_name: “&6BungeeCord &71.8-1.21”

# With formatting
version_name: “&l&6VIP Server&r &7| &a1.8-1.21”

# Multi-color combinations
version_name: “&cRed &6Gold &eYellow &aGreen”
“`

**Color Codes**: `&0`-`&9`, `&a`-`&f` (black, dark blue, dark green, dark aqua, dark red, purple, gold, gray, dark gray, blue, green, aqua, red, pink, yellow, white)

**Format Codes**: `&l` (bold), `&m` (strikethrough), `&n` (underline), `&o` (italic), `&r` (reset)

—

### Client Compatibility

| Client Version | Supported Colors |
|—————-|——————|
| 1.16+ | Full RGB colors |
| 1.7-1.15 | 16 named colors |
| < 1.7 | Basic colors | --- ## Commands | Command | Permission | Description | |---------|------------|-------------| | `/vt` | `versiontinmoli.admin` | Show plugin information | | `/vt reload` | `versiontinmoli.admin` | Reload configuration file | | `/vt md ` | `versiontinmoli.admin` | Modify version name |

**Permission Notes**: Velocity/BungeeCord require `versiontinmoli.admin` permission, Bukkit defaults to OP

—

## Configuration

### Basic Configuration

“`yaml
# VersionTinmoli Configuration File
# Customize the version name displayed in the server list

# Language setting (en_US or zh_CN)
language: “en_US”

# Version name configuration
version_name: “Velocity 1.8.x-1.21.11”
“`

### Language Settings

The plugin supports multiple languages. You can set the language in the configuration file:

– `en_US` – English
– `zh_CN` – Simplified Chinese

After modifying the `language` field, use `/vt reload` to reload the configuration and switch languages. All command messages and prompts will be displayed in the corresponding language.

### Language File Customization

Language files are automatically copied to the external directory on first run:
– **Velocity**: `plugins/versiontinmoli/lang/`
– **BungeeCord**: `plugins/VersionTinmoli/lang/`
– **Bukkit**: `plugins/VersionTinmoli/lang/`

You can edit these files to customize messages. The plugin will load from the external directory first, then fall back to the built-in files.

### Configuration Examples

**Regular Server**
“`yaml
# Velocity
version_name: “Minecraft 1.8-1.21”

# BungeeCord/Bukkit
version_name: “&6Minecraft &71.8-1.21”
“`

**VIP Server**
“`yaml
# Velocity
version_name: “VIP Server”

# BungeeCord/Bukkit
version_name: “&l&6VIP Server”
“`

**Minigames Server**
“`yaml
# Velocity
version_name: “MiniGames | Online”

# BungeeCord/Bukkit
version_name: “&cM&6i&en&ai&9G&ba&dm&5e&cs &f| &aOnline”
“`

**PVP Server**
“`yaml
# Velocity
version_name: “PVP | Fighting”

# BungeeCord/Bukkit
version_name: “&l&cPVP &r&7| &eFighting”
“`

—

## FAQ

### Migrating from TOML to YAML

If you’re upgrading from an older version (before v1.0.2), you need to migrate your configuration from TOML format to YAML format.

**Automatic Migration (Recommended):**
1. Backup your `config.toml` file
2. Delete the `config.toml` file
3. Restart the server or run `/vt reload`
4. The plugin will automatically create a new `config.yml` file
5. Edit `config.yml` and set your custom version name

**Manual Migration:**

TOML format (old):
“`toml
version_name = “My Server 1.20”
“`

YAML format (new):
“`yaml
version_name: “My Server 1.20”
“`

Main difference: Use colon `:` instead of equals sign `=`

### Configuration Not Working

1. Ensure the configuration file is in the correct location
2. Check YAML syntax is correct
3. Use `/vt reload` to reload configuration
4. If still not working, restart the server

### Colors Not Displaying or Showing as Text

**Problem**: RGB color codes display as text like `Red Green`

**Cause**: Using incorrect closing tags ``

**Solution**:
“`yaml
# Wrong
version_name: “<#FF5555>Red <#55FF55>Green”

# Correct
version_name: “<#FF5555>Red <#55FF55>Green”
version_name: “Red Green”
“`

**Other Color Issues**:
1. **Velocity**: Use MiniMessage format `text`
2. **BungeeCord/Bukkit**: Use `&` or `§` color codes
3. RGB colors require Minecraft 1.16+ client
4. Check server logs for errors

### Platform-Specific Requirements

1. **Velocity**: Requires Velocity 3.0+ and Java 21+
2. **BungeeCord**: Requires BungeeCord 1.16+ and Java 17+
3. **Bukkit**: Requires Minecraft 1.20.1+ and Java 17+

—

## License

This project is licensed under the MIT License.

## Support

For issues or suggestions, please submit them on [GitHub Issues](https://github.com/Tinmoli/VersionTinmoli/issues).

—

**Documentation Version**: 1.0.2
**Maintainer**: Tinmoli

Version Manager

# Version Manager – Advanced Version Control

Version Manager is your ultimate solution for managing Minecraft versions on your server. With real-time version control and powerful features, you can easily manage which Minecraft versions can connect to your server.

## Key Features
### Version Control
– Enable/disable specific versions (1.8.9, 1.16.5, etc.)
– Control entire version groups (all 1.8.x versions)
– Real-time changes – no server restart needed
– Support for all versions from 1.8 to 1.21

## Commands

| Command | Description |
|———|————-|
| /vg enable | Allow players to join with specified version |
| /vg disable | Block players using specified version |
| /vg list | Show all version statuses |
| /vg reload | Reload the plugin |

Examples:

“`
/vg disable 1.8 – Blocks all 1.8.x versions
/vg enable 1.16.5 – Allows version 1.16.5
/vg disable 1.20 – Blocks all 1.20.x versions
“`

## Permissions
| Permission | Description |
|————|————-|
| versiongate.admin | Access to all commands |
| versiongate.bypass | Bypass version restrictions |

## Requirements
– Server: Spigot/Paper 1.8.8 or newer
– Java: Java 8 or higher
– Memory: Minimal impact
– Optional: ViaVersion, ProtocolSupport

Support
For support, please visit our [Discord Server](https://discord.com/invite/krcaTEK5VD) on issue for any bugs or feature requests.

VerseChests

# Verse Chests Plugin Description

The **Verse Chests Plugin** is a performance-optimized and feature-packed solution for adding customizable loot chests to your Minecraft PvP server. It enhances gameplay by introducing dynamic chests scattered across the map, offering unique loot and fostering competitive exploration.

## Features:
– **Dynamic Loot Chests**: Automatically spawn loot-filled chests across the map to encourage exploration and PvP engagement.
– **Custom Chest Creation**: Easily create chests by placing specific blocks on the ground, making setup quick and intuitive.
– **Advanced Loot Configuration**:
– Customize loot tables directly from configuration files or through in-game commands.
– Set item rarities and precise drop chances for balanced and rewarding gameplay.
– **Rarity & Drop Control**: Configure item rarity levels (e.g., Rare, Epic, Mythic, Legendary) and adjust probabilities for fine-tuned loot distribution.
– **Command Support**: Manage chest contents, rarity levels, and drop chances conveniently with commands.
– **Optimized Performance**: Verified for minimal server load, as proven by **Spark Profiler** testing (see screenshot below), ensuring smooth performance even on high-traffic servers.

## Benefits:
– Encourage exploration and competitiveness by offering randomized loot rewards across the map.
– Simplify chest creation and loot management with user-friendly tools and commands.
– Maintain server performance without compromising features or functionality, as verified by Spark Profiler results showing negligible impact on server threads.

—

## Spark Profiler Screenshot

The **Verse Chests Plugin** is ideal for servers aiming to create an exciting, loot-driven PvP environment with seamless customization and performance efficiency.