BeeHiveAnnouncer

# BeeHiveAnnouncer

Announces beehive breaks.

## Features
– Lightweight and configurable.
– Server-side only.
– Works on Paper/Spigot/Purpur.

## Config (snippet)
“`yml
tracked-blocks:
– BEE_NEST
– BEEHIVE
message: “&b{player} found {block}!”
“`

## Compatibility
– Server: Paper, Spigot, Purpur
– Minecraft: 1.16.5 – 1.21.4

## Credits
– Modrinth profile: https://modrinth.com/user/yuutaxd

BadlandsHaste

# BadlandsHaste

Haste in badlands.

## Features
– Lightweight and configurable.
– Server-side only.
– Works on Paper/Spigot/Purpur.

## Config (snippet)
“`yml
amplifier: 0
duration-seconds: 5
biomes:
– BADLANDS
“`

## Compatibility
– Server: Paper, Spigot, Purpur
– Minecraft: 1.16.5 – 1.21.4

## Credits
– Modrinth profile: https://modrinth.com/user/yuutaxd

AutoPickupDrops

# AutoPickupDrops

Auto-pickup block drops into inventory.

## Features
– Lightweight and configurable.
– Server-side only.
– Works on Paper/Spigot/Purpur.

## Config (snippet)
“`yml
enabled: true
“`

## Compatibility
– Server: Paper, Spigot, Purpur
– Minecraft: 1.16.5 – 1.21.4

## Credits
– Modrinth profile: https://modrinth.com/user/yuutaxd

AncientDebrisAnnouncer

# AncientDebrisAnnouncer

Announces ancient debris finds.

## Features
– Lightweight and configurable.
– Server-side only.
– Works on Paper/Spigot/Purpur.

## Config (snippet)
“`yml
tracked-blocks:
– ANCIENT_DEBRIS
message: “&b{player} found {block}!”
“`

## Compatibility
– Server: Paper, Spigot, Purpur
– Minecraft: 1.16.5 – 1.21.4

## Credits
– Modrinth profile: https://modrinth.com/user/yuutaxd

YuRTP

# YuRandomTeleport | Cross-Version · High Performance · Universal Compatibility

**Supported Versions: 1.8.x – 1.26.x**
**Compatible Server Types: Spigot / Paper / All Hybrid Forks (Mohist, Magma, Arclight, etc.)**

—

## 🎉 Promotional Text

### ✦ Escape the Crowd. Explore the Unknown. — YuRandomTeleport

Tired of overcrowded spawn points? Struggling to find untouched, pristine land?
**YuRandomTeleport** is an intelligent random teleportation plugin built for Minecraft servers, delivering a safe, smooth, and highly customizable teleport experience.

#### ✨ Why Choose YuRandomTeleport?

– **Ultimate Cross-Version Compatibility**
From 1.8 to the latest 1.26.x, it runs seamlessly on Spigot, Paper, and all hybrid server forks—one plugin for every version.

– **Smart & Safe Location Algorithm**
Automatically avoids lava, cacti, the void, fire, and other hazardous blocks. Players always land on solid ground with open sky above—safe upon arrival.

– **Granular Per‑World Configuration**
Each world can have independent radius, height limits, safety rules, and blocked material lists. Perfectly tailored for Overworld, Nether, and End dimensions.

– **Seamless Economy & Cooldown Integration**
Supports Vault economy deductions and customizable cooldowns. Granular permission nodes keep everything under control and prevent abuse.

– **Programmable Command Hooks**
Execute custom commands (including JSON titles and particle effects) before and after teleportation, taking your server’s interactivity to the next level.

– **Zero‑Fuss, Out‑of‑the‑Box**
Default configurations work immediately. No complex setup required—even novice server admins can deploy it effortlessly.

– **Active Maintenance & Community**
The plugin is under continuous development. Join our official community **1080918424** to report issues, request features, or just chat with fellow admins.

#### 🚀 Join Us
**Official Community Group: 1080918424**
Bug Reports · Update Announcements · Tech Support · Customization Inquiries

—

## 📖 User Manual

### 1. Installation Guide

1. Place `YuRandomTeleport-.jar` into your server’s `plugins` folder.
2. Restart the server or load the plugin using a plugin manager.
3. The plugin will automatically generate `config.yml` and `messages.yml` inside `plugins/YuRandomTeleport/`.
4. (Optional) Edit the configuration files as desired and apply changes with `/yurtp reload`.

### 2. Commands & Permissions

#### Player Commands

#### Admin Commands

#### Permission Nodes

### 3. Configuration Quick Reference

#### Core Options in `config.yml`

“`yaml
# Economy settings (requires Vault)
economy:
enabled: false
cost: 0.0

# Cooldown in seconds
cooldown:
seconds: 3

# Worlds where teleportation is forbidden
world-blacklist:
– lobby

# Default parameters (inherited by all worlds unless overridden)
default:
radius:
min: 500
max: 2000
height:
min: -64 # Leave blank to auto-detect from world
max: 320
safety:
check: true
allow-void: false
allow-water: false
allow-lava: false
max-attempts: 32
min-air-above: 8
blocked-materials:
– “MAGMA*”
– “CACTUS”
– “SWEET_BERRY_BUSH”
– “COBWEB”
– “*FIRE*”

# Per‑world overrides
worlds:
world_nether:
radius:
min: 200
max: 800
safety:
allow-lava: true

# Custom commands to execute (supports placeholders: {player}, {x}, {z}, etc.)
commands:
on-teleport:
– “title {player} title {“text”:”Searching for a safe location…”,”color”:”yellow”}”
on-success:
– “title {player} title {“text”:”Teleport Successful!”,”color”:”green”}”
on-fail:
– “title {player} title {“text”:”Teleport Failed”,”color”:”red”}”
“`

#### Notes on `messages.yml`
All frontend messages support color codes (`&` in place of `§`) and can be fully translated or customized. After editing, run `/yurtp reload` to apply changes.

### 4. Frequently Asked Questions

**Q: Why can’t a player teleport?**
A: Verify that the world is not listed in `world-blacklist`, the player has the `yurtp.use` permission, and cooldown/balance requirements are met.

**Q: The teleport locations aren’t ideal. How can I improve them?**
A: Adjust the `radius` range, `height` limits, or relax the `blocked-materials` rules for the specific world. Enable `debug: true` in the config to view detailed location‑search logs in the console.

**Q: Does the plugin support sounds on 1.8?**
A: Yes. A built‑in cross‑version sound compatibility layer ensures sounds work across all supported versions without errors or silence.

**Q: Is Moonrise asynchronous server supported?**
A: Moonrise is not currently supported due to conflicts between its asynchronous architecture and some core plugin logic. We will evaluate potential compatibility in future updates.

### 5. Community & Support

– **QQ Group: 1080918424**
Bug reports · Feature suggestions · Update notifications · Technical discussions

– **Documentation & Updates**
The latest version and detailed documentation are always available within the community group.

—

**YuRandomTeleport — Every journey begins with anticipation.**

YUpdateChecker

[![Discord](https://img.shields.io/discord/1236019317208776786?style=flat&logo=discord&label=Discord&color=%235d6af2
)](https://discord.gg/kZJhKZ48j8)
# YUpdateChecker
Plugin and datapack update checker that works out of the box. No need to configure anything. Too good to be true? Well, yes. The catch is that it works only with projects downloaded from Modrinth, thanks to their awesome [API](https://docs.modrinth.com/api/).

## How it works?
It’s really simple. Plugin hashes a file (.jar or .zip), checks the hash using Modrinth API and logs the results. Yep, that’s it. Modrinth is doing the heavy lifting by hashing every single file that is uploaded and then making it available via their API. Only caveat is – you can’t change the contents of a downloaded jar or datapack. So no editing `plugin.yml` or MC functions. That’s how hashing works, different file – different hash. I mean, you can change it of course, it just won’t be picked by the plugin ¯\_(ツ)_/¯

### Additional info
– Messages are fully customizable with a lang file, supporting [PlaceholderAPI](https://github.com/PlaceholderAPI/PlaceholderAPI) and [MiniMessage](https://docs.advntr.dev/minimessage/index.html)
– Commands have tab completions
– Modrinth API is currently [rate limited](https://docs.modrinth.com/api#ratelimits) at 300 requests per minute per IP. Which means that an update check may take a little bit longer, if you have wayyy too many plugins/datapacks ~~or if you spam the check command~~. (Plugin makes 1 request per every Modrinth project that you use)

# Media
Checking updates
![Gif presents an usage of the in-game commands. “/updates check” command is entered. Plugin proceeds to check updates while showing an action bar with current progress status. Upon completion a message is sent with a suggestion of running “/updates show” next. After running it, general data about the check is shown: how many plugins and datapacks were found on Modrinth, how many is up to date, and how long it took to complete the check.](https://i.imgur.com/rea1vRx.gif)

Looking through results
![Presented are results of “/updates show plugins” and “show datapacks”. Those are split into pages of 10 items, each listed under one another, with a name of a plugin/datapack and an information whether it’s up to date or whether it’s X versions behind. Names of the projects can be hovered for additional info like description and current/new version numbers. When clicked it will open an url with the latest plugin/datapack version that meets the config and Minecraft version requirements.](https://i.imgur.com/llPpHuL.gif)

# Integrity with other plugins
I make these plugins for me, according to my needs, meaning, I don’t search for every possible plugin that I don’t care about, that could be somehow better integrated with mine. But, if you care about better integration between this plugin and some other, then just let me know through [Discord](https://discord.gg/kZJhKZ48j8) or [GitHub](https://github.com/Ynfuien/YUpdateChecker) and I will see what I can do.

Same goes for any features that you think may be missing. If something isn’t outside the scope of the plugin, then I’ll probably do it.

# License
This project uses [GNU GPLv3](https://github.com/Ynfuien/YUpdateChecker/main/blob/LICENSE) license.

YuPay

# 🎮 YuPay —— Make Sponsorship Management a Pleasure

> **Minecraft server sponsorship has never been been this elegant.**
>
> Direct integration with WeChat Pay & Alipay, redeem code system, refund review, multi-language, full lifecycle event listening — everything you need, YuPay delivers it all at once. Free, no middlemen, no tricks. 100% of the revenue goes straight to your account. The only fees are those charged by Alipay and WeChat.

—

## 📦 What Is It

**YuPay** is a free, modern payment plugin tailored for Minecraft servers. It breaks down the hassle of “sponsorship management” into four steps: **Initiate → Pay → Receive → Record**. Every step is automated, every step traceable.

Server operators use it to collect sponsorships, players use it to scan and pay. Both sides enjoy a worry-free experience. Supports direct API integration with WeChat Pay and Alipay — no third-party relay, your funds stay secure in your own hands.

> ⚠️ This plugin is designed for scenarios where “players voluntarily sponsor server operations”. Please ensure usage complies with local laws and payment platform regulations.

—

## ✨ Highlights at a Glance

—

## 🔄 What a Complete Sponsorship Looks Like

1. Player executes a command, e.g. `/donate 50 wechat`
2. System creates order asynchronously, writes to database
3. Calls WeChat/Alipay API to generate payment QR code
4. Depending on your config, sends **clickable link**, **text-art QR** in chat, or **map QR** in inventory
5. Player scans and completes payment
6. Payment platform calls back to your server
7. Plugin verifies signature, confirms receipt, grants rewards (economy + commands)
8. Leaderboard and placeholders update in real time
9. All logs written, traceable anytime

Fully automated. You just configure the rewards, YuPay handles the rest.

—

## 🎁 Four Reward Layers, Mix and Match

YuPay’s reward system is like a Lego box — four trigger modes you can combine freely.

| Layer | Trigger | Example |
|——-|———|———|
| **Base Reward** | Every successful payment | `give {player} diamond 1` |
| **Single Milestone** | Single payment reaches threshold | 50 yuan → 5 gold blocks |
| **Total Achievement** | Lifetime total reaches new height | 500 yuan → SVIP permission group |
| **Limited Sprint** | Cumulative within specified time period | 200 yuan in 24h → enchanted golden apple |

Each layer’s commands are fully customizable, support variables like `{player}`, `{amount}`, `{points}`, and can integrate with permission/economy plugins like LuckPerms, CMI, etc.

> 💡 Adding `-n` (e.g. `/donate 10 -n`) makes it a **no-reward sponsorship** — pure server support, no rewards triggered.

—

## 🔑 Redeem Code System: More Than Just a Voucher

YuPay’s redeem code module goes far beyond typical “gift codes”:

– **Free codes**: Players enter to claim — great for event giveaways
– **Paid activation codes**: Players must scan and pay a specified amount before redeeming — suitable for selling item entitlements, redeeming codes from other platforms, etc.
– **Economy rewards**: Automatically grant Vault currency or PlayerPoints upon redemption
– **Custom commands**: Each code can bind a set of commands executed on redemption
– **Usage limits & expiry**: Independent control per code
– **Code PAPI**: Placeholders directly read any code’s status, amount, remaining uses

Create a paid activation code with a single command:
“`
/yp code create –code VIP2026 –amount 50 –economy vault –eco-amount 5000 –commands “lp user {player} parent set vip” –max-uses 100 –expire 30d
“`

—

## 💵 Refund System: Bad Debt Terminator

Refunds are no longer a nightmare. YuPay’s refund process is complete and reassuring:

– **Players request refund**: Submit application with reason
– **Admin reviews**: Approve/deny in an orderly manner
– **Forced refund**: Direct operation for urgent cases, no waiting for review
– **Partial refund**: Flexible handling, precise to the cent
– **Code refund**: Refund money and rollback usage count, status automatically restored
– **Refund callback**: Interfaces with WeChat/Alipay official refund API, money returns to original payment method
– **Complete logs**: Who refunded, how much, when, why — all clear

—

## 🌐 Thousand Players, Thousand Languages — No Language Fights

A lifesaver for international server operators.

– Comes with **Simplified Chinese** and **English** complete translations
– Server owners can add any language file in `language.mappings`
– Players switch preference with `/yp lang `, stored in database, persists across sessions
– New players automatically **detect client language** and match the best translation
– Different players on the same server see different language prompts — truly per-player localization

—

## 🔌 Complete PAPI Placeholder List

YuPay provides **40+ built-in PlaceholderAPI placeholders**, covering personal, server, leaderboard, and redeem code dimensions. All monetary values keep two decimal places. Full list below:

—

### 1. Personal Dimension (requires player context)

> 💡 **Dynamic parameters**: `` is in **milliseconds** (e.g. `86400000` = 24h), `` is monetary threshold (yuan). All monetary placeholders retain two decimals.

—

### 2. Server Dimension (no player needed)

—

### 3. Leaderboard Dimension (no player needed)

Two formats supported (first recommended):

> `` ranges `1` ~ `10`. If rank doesn’t exist, name returns fallback text from language file (default “None”), amount returns `0.00`.

—

### 4. Redeem Code Dimension

Includes global statistics (no player needed) and specific code attributes (where `redeemed` and `can_redeem` require player context).

#### Global Statistics

| Placeholder | Description | Example Return |
|————-|————-|—————-|
| `%yupay_code_total%` | Total number of codes | `25` |
| `%yupay_code_active%` | Number of active codes (status ACTIVE) | `18` |

#### Specific Code Attributes — replace `` with actual code string (auto-uppercase)


| Placeholder | Description | Example (code = `VIP2026`) |

|-------------|-------------|----------------------------|

| `%yupay_code__status%` | Current status of the code | `ACTIVE` |

| `%yupay_code__amount%` | Required payment amount (yuan) | `50.00` |

| `%yupay_code__economy_type%` | Economy reward type | `vault` |

| `%yupay_code__economy_amount%` | Economy reward amount | `5000.00` |

| `%yupay_code__used%` | Number of times redeemed | `23` |

| `%yupay_code__max_uses%` | Max redeem count (-1 = unlimited) | `100` |

| `%yupay_code__expire%` | Expiry timestamp (ms), -1 = never | `1798675199999` |

| `%yupay_code__expire_formatted%` | Formatted expiry time | `2026-12-31 23:59` |

| `%yupay_code__remark%` | Code remark | `"VIP activation code"` |

| `%yupay_code__locked%` | Whether locked by a payment (someone is paying) | `true` / `false` |

| `%yupay_code__redeemed%` | Whether **current player** has redeemed this code | `true` / `false` |

| `%yupay_code__can_redeem%` | Whether **current player** can redeem now (comprehensive check) | `true` / `false` |

> 💡 `_can_redeem` checks: code status normal, not expired, uses left, not locked by others, and current player hasn't redeemed it.
---
### Usage Notes
- **All monetary placeholders** are in `yuan`, with two decimal places, e.g. `99.50`. Integer amounts also show `.00`.

- Dynamic time parameter `` always uses **milliseconds** — 24h = `86400000`, 7d = `604800000`.

- Code strings in placeholders are auto-uppercased; lowercase input works too.

- Server and leaderboard placeholders **do not require a player context**; personal and some code placeholders **require a player** or return empty/default.

- Placeholders work in any plugin that supports PlaceholderAPI (scoreboard, BossBar, DeluxeTags, chat prefix, item lore, etc.).
---
## 🧩 Gift for Developers
If you can write plugins, these events will make your secondary development experience fly:
| Event | Trigger | Modifiable Parameters |

|-------|---------|----------------------|

| `PrePaymentEvent` | Before payment | amount, payment method, order ID, cancel flag |

| `PaymentOrderCreatedEvent` | Order created successfully | read-only (has QR URL) |

| `PaymentCompletedEvent` | Payment success + rewards granted | read-only (full data) |

| `PaymentFailedEvent` | Payment failed / canceled | read-only |

| `RefundCompletedEvent` | Refund completed | read-only |

| `RedeemCodeRedeemedEvent` | Code redeemed | read-only |

| `RedeemCodeLifetimeEvent` | Code status changed | read-only (old → new state) |

| `PlayerPointsChangedEvent` | Economy changed | read-only |
All events support sync. You can intercept before order creation, trigger联动 other systems after payment, sync data on refund — every detail of the sponsorship lifecycle is observable.
---
## 🛡️ Security Is Not Just Talk
- **Signature verification**: WeChat/Alipay callbacks are fully signature-verified against forgery

- **Anti-duplicate delivery**: Order status check + idempotent handling

- **IP whitelist**: Callback interface can restrict access to official payment platform IPs only

- **TLS/HTTPS**: Supports certificate-encrypted communication

- **Event monitoring**: `/yp audit` one-click audit, 24h monitoring of which plugins are listening to YuPay's fund events

- **Map virtual lock**: When a payment QR is placed in the inventory, the player is locked in place, cannot drop/switch items, payment unlocks
---
## ⚡ Blazing Fast Startup
The rewritten dependency loading system means YuPay no longer requires cumbersome JVM startup parameters. All dependencies are automatically managed, verification speed increased by 600%, out-of-the-box. Drop it into the `plugins` folder, start the server, it's ready.
---
## 📊 Data at Your Fingertips
`/yp history` is one of your most-used commands. Order history supports **page browsing**, click an order ID to **copy it with one click** — reconciliation efficiency doubled.
`/yp top` lets you know at any time who is contributing to the server — leaderboard data syncs with placeholders in real time.
`/yp total` for personal stats, `/yp total all` for server-wide stats — all available at your fingertips.
---
## 🚀 Two-Minute Quick Start Guide
1. Drop `YuPay.jar` into the `plugins/` folder

2. Start the server, wait for `config.yml` and `messages.yml` to generate

3. Open `config.yml`, fill in your WeChat/Alipay parameters

4. Ensure the callback port (default `8080`) is open in your server firewall and security group

5. In-game, type `/donate 0.01` to test a small payment

6. Confirm callback works and rewards arrive — start business 🎉
---
## 🏆 Why Server Owners Are Using YuPay
- ✅ **Stable**: Production-tested, compatible with Spigot/Paper 1.8 to latest versions

- ✅ **Reliable**: Direct official API connection, no middlemen, money goes to your account directly

- ✅ **Worry-free**: From payment to rewards fully automated, you just configure

- ✅ **Flexible**: Reward logic fully programmable, command aliases freely definable

- ✅ **Secure**: Signature verification + anti-duplicate + IP whitelist + event monitoring

- ✅ **Transparent**: Every order, every refund, every code redemption has logs

- ✅ **Evolving**: Actively maintained, continuously iterated, community-driven
---
> 💬 **Plugin Discussion Group: 1080918424**

>

> For issues, feature requests, or just to chat — welcome. Every improvement of YuPay comes from feedback from server owners.
> 💛 **Support the Author on AiFaDian**: https://ifdian.net/item/012b6c1c4a0911f18d1b52540025c377

>

> If YuPay has helped your server, consider buying the author a milk tea ~ Your support is the biggest motivation for the plugin's continued evolution.
**Stop struggling with sponsorship management. Leave the professional stuff to YuPay, and focus on running your server well.**
***
# 📖 YuPay Operation Manual
## 1. Environment Requirements
| Item | Requirement |

|------|-------------|

| Server | Spigot / Paper / compatible forks / compatible hybrid servers, 1.8 – 1.26+ |

| Java | JDK 8 or higher |

| Optional dependencies | Vault (economy), PlayerPoints (points), PlaceholderAPI (placeholders), ProtocolLib (map lock) |
> 🎉 **Good news**: You no longer need to manually add JVM startup parameters for Java 9+. YuPay's latest version has built-in smart dependency management — out-of-the-box.
## 2. Installation & Startup
1. Download `YuPay.jar`, place it in the server's `plugins/` directory

2. Start the server, the plugin will automatically generate `config.yml`, `messages.yml`, and SQLite database files

3. Edit `plugins/YuPay/config.yml`, fill in payment channel configuration parameters

4. Depending on your payment method, configure callback URLs in the payment platform backend:

   - WeChat: `http(s)://your-domain-or-ip:port/pay/wechat/notify`

   - Alipay: `http(s)://your-domain-or-ip:port/pay/alipay/notify`

5. Ensure the callback port (default `8080`) is open in firewall and security group

6. Execute `/yupay reload` or type `reload` in console to apply configuration

7. In-game, type `/donate 0.01` to test a small payment
## 3. Configuration Quick Reference
### 3.1 Core Payment Parameters
| Path | Description | Example |

|------|-------------|---------|

| `pay.default-method` | Default payment method | `wechat` / `alipay` |

| `pay.min-amount` | Minimum amount per order (yuan) | `0.01` |

| `pay.max-amount` | Maximum amount per order (-1 = unlimited) | `500` |

| `pay.max-daily-amount` | Daily cumulative limit (-1 = unlimited) | `1000` |

| `pay.order-subject` | Order subject template | `Sponsorship-{player}-{amount}yuan` |
### 3.2 WeChat Pay Parameters
| Path | Description |

|------|-------------|

| `wechat.enabled` | Enable (true/false) |

| `wechat.mchid` | Merchant ID |

| `wechat.appid` | Official account / Mini Program AppID |

| `wechat.serial-no` | API certificate serial number |

| `wechat.private-key-path` | Merchant private key (relative to `pems/` directory) |

| `wechat.public-key-path` | Platform public key (relative to `pems/` directory) |

| `wechat.public-key-id` | Platform public key ID |

| `wechat.api-v3-key` | API v3 key (32 characters) |

| `wechat.notify-url` | Complete callback notification URL |
### 3.3 Alipay Parameters
| Path | Description |

|------|-------------|

| `alipay.enabled` | Enable |

| `alipay.mode` | `public_key` or `cert` |

| `alipay.app-id` | App ID |

| `alipay.merchant-private-key` | Merchant private key (PKCS8, without headers/footers) |

| `alipay.alipay-public-key` | Alipay public key (required for public_key mode) |

| `alipay.app-cert-path` | App public key certificate (cert mode) |

| `alipay.alipay-cert-path` | Alipay public key certificate (cert mode) |

| `alipay.alipay-root-cert-path` | Alipay root certificate (cert mode) |

| `alipay.notify-url` | Async notification URL |

| `alipay.return-url` | Sync return URL |
### 3.4 Economy System
| Path | Description |

|------|-------------|

| `economy.enabled` | Enable economy rewards |

| `economy.type` | `vault` or `playerpoints` |

| `economy.rate` | 1 yuan = how many in-game currency/points |
### 3.5 QR Code Display
| Path | Description |

|------|-------------|

| `qrcode.default-output-mode` | `link` / `text` / `map` |

| `qrcode.text-qr-size` | Text mode QR side length (characters, default 12) |

| `qrcode.text-black-char` | Black pixel character (default `██`) |

| `qrcode.api-url` | Image generation API for link mode |
### 3.6 Callback Server
| Path | Description |

|------|-------------|

| `callback.port` | Listening port |

| `callback.host` | Bind address (`0.0.0.0` = all interfaces) |

| `callback.io-threads` | IO thread count |

| `callback.worker-threads` | Worker thread count |

| `callback.allowed-ips` | IP whitelist (CIDR format, empty = allow all) |

| `callback.access-log` | Enable access logging |
### 3.7 Database
| Path | Description |

|------|-------------|

| `database.type` | `sqlite` (standalone) or `mysql` (multi-server sync) |

| `database.mysql.*` | MySQL connection parameters |

| `database.connection-pool.*` | HikariCP connection pool parameters |

| `database.table-names.prefix` | Table prefix to avoid conflicts |

| `database.table-names.*` | Individual business table names (can be customized) |
## 4. Complete Reward Configuration Guide
### 4.1 Base Reward (on-success)
Executed on every successful payment — suitable for "base reward every sponsorship".
```yaml

commands:

  on-success:

    - "give {player} diamond 1"

    - "effect give {player} minecraft:speed 30 1"

```
Available variables: `{player}` (player name), `{amount}` (amount), `{points}` (economy points earned)
### 4.2 Single Milestone (on-single-achieved)
Triggered when a single payment reaches a set amount. **Sort amounts from low to high**, multiple tiers allowed.
```yaml

commands:

  on-single-achieved:

    - amount: 50

      commands:

        - "say {player} reached 50 yuan in a single sponsorship!"

        - "give {player} minecraft:gold_block 5"

    - amount: 100

      commands:

        - "give {player} minecraft:diamond_block 3"

        - "lp user {player} parent set vip"

```
### 4.3 Total Achievement (on-total-achieved)
Triggered when lifetime total reaches a new height. **Each tier triggers only once** — anti-duplicate mechanism built-in.
```yaml

commands:

  on-total-achieved:

    - total: 100

      commands:

        - "lp user {player} parent set vip"

    - total: 1000

      commands:

        - "lp user {player} parent set ultimate"

        - "give {player} minecraft:beacon 1"

```
### 4.4 Limited Sprint Reward (on-recent-achieved)
Triggered when cumulative amount within a specified time period (milliseconds) reaches the target. Great for holiday events, weekend leaderboard pushes, etc.
```yaml

commands:

  on-recent-achieved:

    - time: 86400000    # 24 hours

      total: 200

      commands:

        - "give {player} minecraft:enchanted_golden_apple 5"

    - time: 604800000   # 7 days

      total: 500

      commands:

        - "give {player} minecraft:elytra 1"

```
### 4.5 Refund Trigger Commands (on-refund)
Executed after a successful refund — can be used to notify admins, log events.
```yaml

commands:

  on-refund:

    - "say {player}'s order {order} has been refunded {amount} yuan"

```
## 5. Command System
### 5.1 Player Commands
| Command | Function | Default Aliases |

|---------|----------|----------------|

| `/donate  [payment] [output] [-n]` | Initiate sponsorship | `/pay`, `/zanzhu` |

| `/ytop` | Sponsorship leaderboard Top10 | `/paytop`, `/yt` |

| `/ytotal [player|all]` | Query total sponsorship | `/paytotal`, `/ytt` |

| `/yp history [page]` | My sponsorship history | `/yupay history` |

| `/yp lang [language]` | Switch personal language preference | |

| `/yp code redeem ` | Redeem a code | |

| `/yp cancel` | Cancel current map payment | |

> 💡 The `-n` flag means "no-reward sponsorship" — pure server support, no reward commands or economy items triggered.
### 5.2 Admin Commands
| Command | Function |

|---------|----------|

| `/yp reload` | Hot reload configuration |

| `/yp set

### 5.3 Key Permission Nodes
| Permission Node | Operations |

|----------------|------------|

| `yupay.command.pay` | Initiate sponsorship |

| `yupay.command.top` | View leaderboard |

| `yupay.command.total` | Query total sponsorship |

| `yupay.command.history` | View order history |

| `yupay.reload` | Reload config |

| `yupay.ban` | Manage blacklist |

| `yupay.convert` | Currency conversion |

| `yupay.audit` | Event listener audit |

| `yupay.admin` | Includes all above admin permissions |
## 6. Redeem Code System In-Depth
### 6.1 Code Creation Command Details
Code creation uses named parameters in `--param value` format, freely combinable:
```bash

# Free welfare code (unlimited uses, never expires)

/yp code create --code FREEGIFT --max-uses -1 --economy vault --eco-amount 100 --remark "New player gift"
# Paid activation code (pay 50 yuan to redeem, 100 uses, expires after 30 days)

/yp code create --code PREMIUM --amount 50 --economy vault --eco-amount 5000 --max-uses 100 --expire 30d --commands "lp user {player} parent set vip"
# Command-only code (no economy, no payment)

/yp code create --code WELCOME --commands "give {player} diamond 5; say {player} Welcome back!"

```
**Parameter quick reference:**
| Parameter | Description | Example |

|-----------|-------------|---------|

| `--code` | Code string (auto-uppercase) | `VIP2026` |

| `--amount` | Required payment amount (0 = free) | `50` |

| `--economy` | Economy type (vault / playerpoints / none) | `vault` |

| `--eco-amount` | Economy reward amount | `5000` |

| `--max-uses` | Max redeem count (-1 = unlimited) | `100` |

| `--expire` | Expiry time (`30d` / `24h` / `2026-12-31` / `never`) | `30d` |

| `--commands` | Commands to execute on redemption (semicolon-separated) | `"cmd1; cmd2"` |

| `--remark` | Remark description | `"VIP activation code"` |
### 6.2 Code Status Explanation
| Status | Meaning |

|--------|---------|

| `ACTIVE` | Usable |

| `DEPLETED` | Uses exhausted (automatic) |

| `EXPIRED` | Expired (automatic) |

| `DISABLED` | Manually disabled by admin |
### 6.3 Code PAPI Placeholders
Using code `VIP2026` as example:
| Placeholder | Example Return |

|-------------|----------------|

| `%yupay_code_total%` | Total number of codes |

| `%yupay_code_active%` | Number of active codes |

| `%yupay_code_VIP2026_status%` | `ACTIVE` |

| `%yupay_code_VIP2026_amount%` | `50.00` |

| `%yupay_code_VIP2026_used%` | `23` |

| `%yupay_code_VIP2026_max_uses%` | `100` |

| `%yupay_code_VIP2026_expire_formatted%` | `2026-12-31 23:59` |

| `%yupay_code_VIP2026_can_redeem%` | `true` / `false` |

| `%yupay_code_VIP2026_locked%` | `true` / `false` |

| `%yupay_code_VIP2026_redeemed%` | Whether current player has redeemed |
## 7. Refund System In-Depth
### 7.1 Refund Method Comparison
| Method | Command Example | Use Case |

|--------|-----------------|----------|

| Direct refund | `/yp refund ORDER001 50` | Confirmed refund needed, quick processing |

| Forced refund | `/yp refund ORDER001 50 -f` | Skip amount check, refund directly |

| Partial refund | `/yp refund ORDER001 30` | Refund part of the amount |

| Approval workflow | `/yp refund request ORDER001` → wait for approve | Scenarios requiring approval |

| Code refund | `/yp refund -r ` | Refund code payment + restore usage count |
### 7.2 Refund Approval Workflow
1. Player or admin submits refund request: `/yp refund request  [amount]`

2. Admin views pending list: `/yp refund pending`

3. Approve or reject: `/yp refund approve ` / `reject`

4. Upon approval, actual refund automatically executes; upon rejection, requester is notified
### 7.3 What Happens After Refund
- Payment platform (WeChat/Alipay) receives refund request, money returns to original payment method

- Plugin updates order refund status (`FULL_REFUND` / `PARTIAL_REFUND`)

- If code refund: code usage count -1, status restored to `ACTIVE`

- Executes commands configured in `commands.on-refund`

- Triggers `RefundCompletedEvent` for other plugins to react

- Complete refund logs written to database
## 8. Multi-Language System
### 8.1 Adding a Language
Add under `language.mappings` node in `config.yml`:
```yaml

language:

  mappings:

    zh_cn:

      file: "messages.yml"

      aliases: [zh, cn, chinese]

      client-locales: ["zh_cn", "zh_*"]

    en:

      file: "messages_en.yml"

      aliases: [english, eng]

      client-locales: ["en_*"]

    ja:

      file: "messages_ja.yml"

      aliases: [japanese, jp]

      client-locales: ["ja_*"]

```
Then create `plugins/YuPay/messages_ja.yml`, translating based on `messages.yml`. Plugin will automatically fill in missing keys.
### 8.2 Switching Language
- Players switch manually: `/yp lang en` (supports aliases, e.g. `english`)

- First join auto-detects client language and matches best translation

- Language preference stored in database, remembered across sessions
## 9. Database Selection Guide
| Server Scale | Recommended Type | Reason |

|--------------|------------------|--------|

| Single small server | SQLite | Zero configuration, out-of-the-box |

| Multi-server network | MySQL | Unified data, cross-server sync |

| Large network | MySQL + connection pool | High concurrency support, connection reuse |
## 10. Troubleshooting Common Issues
### Callback server fails to start

- Check if port is occupied

- Confirm firewall/security group has opened the port

- Check console error logs
### Payment successful but rewards not received

- Check order `status` in database — should be `SUCCESS`

- Confirm `economy.enabled` and `commands.enabled` are both `true`

- Check console for economy plugin load errors
### Map QR code not showing

- Confirm ProtocolLib matching server version is installed

- Check if `qrcode.default-output-mode` is set to `map`

- If ProtocolLib missing, mode auto-falls back to `link`
### WeChat Pay says public key file not found

- Check existence of `plugins/YuPay/pems/` directory

- Confirm `wechat.public-key-path` is correct

- Go to WeChat Merchant Platform → API Security → API Certificates → download platform certificate
### Configuration lost after plugin upgrade

- YuPay has built-in smart config upgrader — automatically backs up old file (`.bak` suffix) and merges new keys

- Manual backup before upgrade for extra peace of mind
## 11. Database Tables
| Table Name | Stored Content |

|------------|----------------|

| `yu_payments` | All payment orders, including refund status |

| `yu_total_levels` | Cumulative reward tier records |

| `yu_banned_players` | Sponsorship blacklist |

| `yu_player_lang` | Player language preferences |

| `yu_redeem_codes` | Redeem code master table |

| `yu_redeem_logs` | Redemption records |

| `yu_refund_logs` | Refund operation logs |

| `yu_refund_requests` | Refund review requests |
## 12. Uninstallation Steps
1. Execute `/yp reload` (ensure in-memory config is flushed)

2. Stop the server

3. Delete `plugins/YuPay.jar`

4. For complete removal, delete `plugins/YuPay` folder (including database)
---
> 💬 Plugin Discussion Group: **1080918424**

> Don't struggle alone — bring your logs and config screenshots to the group, the author and helpful server owners are there.
> 💛 **Support the Author on AiFaDian**: https://ifdian.net/item/012b6c1c4a0911f18d1b52540025c377

>

> If YuPay has helped your server, consider buying the author a milk tea ~ Your support is the biggest motivation for the plugin's continued evolution.

```


                    
                YouTube Chat
                ## 📺 YouTube Live Chat Integration
A Minecraft plugin for Spigot/Paper servers that seamlessly integrates YouTube Live Chat into your server. Messages sent during a live stream are displayed in real-time directly in the in-game chat, allowing players to interact with live audiences effortlessly.
### ✨ Features

– Real-time YouTube Live Chat integration

– Displays live stream messages in Minecraft chat

– Easy configuration and setup
### 🎮 Use Cases

Perfect for streamers who want to connect their in-game players with their YouTube audience, creating a more interactive and engaging experience.
### ⚙️ Compatibility

– Bukkit / Purpur / Paper / Spigot servers

– Modern Minecraft versions
![YouTube Live Chat in game](https://cdn.modrinth.com/data/cached_images/d3b685d95e03db1605402952e98412a536f14811.png)
            
                    
                YoTPA
                ![Logo](https://raw.githubusercontent.com/PhyschicWinter9/YoTPA/refs/heads/main/screenshot/yotpa.png)
# YoTPA
YoTPA is a lightweight and powerful teleport request plugin with adaptive performance optimization. Simple to use, easy to configure, and built for modern Minecraft servers.
## Features
### Adaptive Performance System

The plugin automatically detects your server’s available RAM and optimizes itself accordingly – zero configuration needed!
**4 Performance Modes:**

– **ULTRA_LIGHT** – For 512 MB – 1 GB RAM (Free/Cheap VPS)

  – Best for: 5-10 players, minimal plugins

– **LIGHT** – For 1-2 GB RAM (Low-end servers)

  – Best for: 10-15 players, light plugins

– **BALANCED** – For 2-4 GB RAM (Mid-range servers)

  – Best for: 15-25 players, moderate plugins

– **HIGH_PERFORMANCE** – For 4+ GB RAM (High-end servers)

  – Best for: 25+ players, any plugins
**Performance Benefits:**

– 30-70% less memory usage

– 25-60% less CPU usage

– Up to 83% faster maintenance tasks

– Dynamic optimization based on your server specs
### Core Features
– **Simple TPA System** – Request to teleport to other players or invite them to you

– **Countdown Timer** – Configurable delay before teleporting with visual feedback

– **Title Display** – Clear visual indication of teleport countdown

– **Movement Detection** – Teleport cancels if player moves during countdown

– **Custom Sound Effects** – Fully customizable audio feedback using Minecraft’s sound registry

– **Config Validation** – Prevents server crashes from broken configs with detailed error messages

– **Permission System** – Fine-grained access control

– **Request Management** – Toggle receiving requests, cancel outgoing requests

– **Multi-Threading Support** – Thread-safe for more concurrent players

– **Customizable Messages** – Fully localizable and configurable messages
### Internationalization (NEW in 1.4.0)
Customize all plugin messages in any language with full MiniMessage support:
“`yaml

prefix: “[YoTPA] ”
commands:

  tpa:

    sent: “Teleport request sent to {target}”

    received: “{requester} wants to teleport to you.”

“`

**MiniMessage Features:**

– Rich text formatting (bold, italic, underlined)

– Color gradients: `text`

– Rainbow effect: `text`

– Hex colors: `<#FF5733>text`
### Custom Sound Effects
Customize all plugin sounds using Minecraft’s sound IDs:
“`yaml

sounds:

  countdown: “block.note_block.pling”

  success: “entity.enderman.teleport”

  cancel: “entity.villager.no”

  request: “entity.experience_orb.pickup”

“`
Test sounds in-game: `/playsound minecraft:block.note_block.pling master @s`
## Configuration
YoTPA’s `config.yml` file allows you to customize various aspects of the plugin:
– Request timeout duration

– Cooldown between requests

– Teleport delay countdown

– Performance mode settings

– Sound effects for different actions

– Feature toggles (statistics, bStats, titles, sounds)
### Configuration File
“`yaml

# YoTPA Configuration v1.3.0-Adaptive

# Smart Auto-Optimization for All Server Sizes
# Request timeout in seconds (how long before a request expires)

# Recommended: 30-120 seconds

request-timeout: 60
# Request cooldown in seconds (how long before sending another request)

# Recommended: 15-60 seconds

request-cooldown: 30
# Teleport delay in seconds (countdown before actual teleport)

# Recommended: 3-10 seconds

teleport-delay: 5
# Performance mode settings

performance:

  # Options: AUTO, ULTRA_LIGHT, LIGHT, BALANCED, HIGH_PERFORMANCE

  mode: AUTO
# Sound effects (use Minecraft sound names)

sounds:

  countdown: “block.note_block.pling”

  success: “entity.enderman.teleport”

  cancel: “entity.villager.no”

  request: “entity.experience_orb.pickup”
# Feature toggles

features:

  statistics: true

  bstats: true

  titles: true

  sounds: true

“`
### Messages Configuration (messages.yml)

“`yaml

# Customize your prefix

prefix: “[YoTPA] ”
# All messages are customizable

commands:

  tpa:

    usage: “Usage: /tpa ”

    sent: “Teleport request sent to {target}”

    received: “{requester} wants to teleport to you.”
teleport:

  countdown:

    title: “Teleporting…”

    subtitle: “Don’t move!”

    message: “Teleporting in {seconds} seconds”

“`

## Customization Examples
### Change Language to Spanish
Edit `messages.yml`:

“`yaml

prefix: “[YoTPA] ”
commands:

  tpa:

    usage: “Uso: /tpa ”

    sent: “Solicitud enviada a {target}”

    received: “{requester} quiere teletransportarse a ti.”

“`
Then use `/tpareload` to apply changes!
### Add Beautiful Gradients
“`yaml

prefix: “✦ YoTPA ✦ ”
teleport:

  countdown:

    title: “Teleporting…”

    message: “Teleporting in {seconds} seconds”

“`
### Customize Colors
“`yaml

prefix: “[TPA] ”
commands:

  tpa:

    sent: “Request sent to {target}”

“`
### Use Hex Colors
“`yaml

prefix: “[YoTPA] ”
teleport:

  success: “Teleported to {target} successfully!”

“`
**Placeholders:**

– `{player}` – Player name

– `{target}` – Target player name

– `{requester}` – Requester player name

– `{seconds}` – Number of seconds

– `{cooldown}` – Cooldown duration
### Configuration Sections Explained
**General Settings:**

– `request-timeout` – How long (in seconds) teleport requests remain valid (recommended: 30-120)

– `request-cooldown` – Time (in seconds) before a player can send another request (recommended: 15-60)

– `teleport-delay` – Countdown time (in seconds) before teleportation happens (minimum: 1)
**Performance Settings:**

– `performance.mode` – AUTO (recommended), ULTRA_LIGHT, LIGHT, BALANCED, or HIGH_PERFORMANCE

  – AUTO automatically detects your server’s RAM and selects the best mode
**Sound Settings:**

– All sounds use Minecraft’s sound registry format (lowercase with dots)

– The plugin validates sounds on config reload

– Full sound list: https://minecraft.wiki/w/Sounds.json
**Feature Toggles:**

– `statistics` – Enable or disable statistics tracking

– `bstats` – Enable or disable bStats metrics

– `titles` – Enable or disable title animations during countdown

– `sounds` – Enable or disable all sound effects
### Config Validation
When reloading with `/tpareload`, the plugin validates:

– YAML syntax

– All values are in valid ranges

– Sounds exist in Minecraft’s registry

– Shows detailed error messages if invalid
Example validation output:

“`

Configuration validation failed!

✗ teleport-delay must be at least 1 second

✗ Sound ‘countdown’ (invalid.sound) not found in registry
Warnings:

• request-timeout (5) is very low, recommended: 30-120
Config not applied. Fix errors and try again.

Using previous configuration.

“`
## How to Edit and Reload
1. Edit the `plugins/YoTPA/config.yml` file

2. Save your changes

3. Use `/tpareload` in-game to apply changes with validation
## Commands Overview
| Command | Description | Permission |

| :—— | :———- | :——— |

| `/tpa ` | Request to teleport to another player | `yotpa.tpa` |

| `/tpaccept` | Accept a pending teleport request | `yotpa.tpaccept` |

| `/tpadeny` | Deny a pending teleport request | `yotpa.tpadeny` |

| `/tpahere ` | Request a player to teleport to you | `yotpa.tpahere` |

| `/tpacancel` | Cancel your outgoing teleport request | `yotpa.tpacancel` |

| `/tpatoggle` | Toggle receiving teleport requests | `yotpa.tpatoggle` |

| `/tpareload` | Reload the plugin configuration | `yotpa.reload` |

| `/tpainfo` | View plugin information and statistics | `yotpa.info` |

| `/tpastats` | View teleport statistics | `yotpa.stats` |
**Default:** All permissions are granted to all players by default.
## Detailed Commands
### TPA Command
Send a request to teleport to another player.
“`

/tpa 
“`
| Parameter | Type | Description |

| :——– | :— | :———- |

| `player` | `string` | **Required**. The player name you want to teleport to |
**Examples:**

“`

/tpa Steve      # Request to teleport to player named Steve

/tpa Alex123    # Request to teleport to player named Alex123

“`
![TPA Command](https://github.com/PhyschicWinter9/YoTPA/blob/main/screenshot/tpav2.gif?raw=true)
**Notes:**

– You cannot send a request to yourself

– There is a configurable cooldown between sending requests (default: 30 seconds)

– Request will expire after a configurable time (default: 60 seconds)

– Target player will receive a notification with clickable accept/deny buttons
—
### TPAccept Command
Accept a pending teleport request from another player.
“`

/tpaccept

“`
No parameters required – accepts the most recent teleport request.
**Examples:**

“`

/tpaccept    # Accept the pending teleport request

“`
![TPAccept Command](https://github.com/PhyschicWinter9/YoTPA/blob/main/screenshot/tpaacceptv2.gif?raw=true)
**Notes:**

– Only works if you have a pending teleport request

– After accepting, the teleportation will begin with a countdown

– The player must stay still during the countdown or it will be cancelled

– If accepting a `/tpa` request, the requester will teleport to you

– If accepting a `/tpahere` request, you will teleport to the requester
—
### TPADeny Command
Deny a pending teleport request from another player.
“`

/tpadeny

“`
No parameters required – denies the most recent teleport request.
**Examples:**

“`

/tpadeny    # Deny the pending teleport request

“`
![TPADeny Command](https://github.com/PhyschicWinter9/YoTPA/blob/main/screenshot/tpadenyv2.gif?raw=true)
**Notes:**

– Only works if you have a pending teleport request

– The requester will be notified that their request was denied

– Request is immediately removed from the system
—
### TPAHere Command
Request another player to teleport to your location.
“`

/tpahere 
“`
| Parameter | Type | Description |

| :——– | :— | :———- |

| `player` | `string` | **Required**. The player name you want to request to teleport to you |
**Examples:**

“`

/tpahere Steve      # Request Steve to teleport to you

/tpahere Alex123    # Request Alex123 to teleport to you

“`
![TPAHere Command](https://github.com/PhyschicWinter9/YoTPA/blob/main/screenshot/tpaherev2.gif?raw=true)
**Notes:**

– You cannot send a request to yourself

– There is a configurable cooldown between sending requests (default: 30 seconds)

– Request will expire after a configurable time (default: 60 seconds)

– The target player must accept with `/tpaccept`
—
### TPACancel Command
Cancel your outgoing teleport request.
“`

/tpacancel

“`
No parameters required – cancels your most recent outgoing request.
**Examples:**

“`

/tpacancel    # Cancel your pending request

“`
**Notes:**

– Only works if you have an active outgoing request

– The target player will be notified that the request was cancelled

– Useful if you sent a request by mistake
—
### TPAToggle Command
Toggle whether you want to receive teleport requests.
“`

/tpatoggle

“`
No parameters required – toggles your request reception status.
**Examples:**

“`

/tpatoggle    # Toggle receiving teleport requests on/off

“`
**Notes:**

– When toggled off, other players cannot send you teleport requests

– You will receive a message showing your current status

– Your setting persists across server restarts
—
### TPAReload Command
Reload the plugin configuration with validation.
“`

/tpareload

“`
No parameters required – reloads and validates the configuration file.
**Examples:**

“`

/tpareload    # Reload the plugin configuration

“`
![TPAReload Command](https://github.com/PhyschicWinter9/YoTPA/blob/main/screenshot/tpareloadv2.gif?raw=true)
**Notes:**

– Requires the `yotpa.reload` permission (default: op only)

– Validates YAML syntax and all configuration values

– Checks that all sounds exist in Minecraft’s registry

– Shows detailed errors if config is invalid

– Only applies config if all validation passes

– Useful after making changes to the config.yml file
—
### TPAInfo Command
View plugin information and real-time statistics.
“`

/tpainfo

“`
No parameters required – displays plugin information.
**Examples:**

“`

/tpainfo    # View plugin info and stats

“`
**Shows:**

– Current performance mode (auto-detected based on RAM)

– Optimization level and settings

– Active teleport requests

– Ongoing teleports

– Memory usage statistics

– Plugin version
**Notes:**

– Useful for monitoring plugin performance

– Helps diagnose issues

– Shows how the plugin has optimized itself for your server
—
### TPAStats Command
View teleport statistics and usage data.
“`

/tpastats

“`
No parameters required – displays teleport statistics.
**Examples:**

“`

/tpastats    # View teleport statistics

“`
**Shows:**

– Total teleport requests sent

– Total teleport requests received

– Success rate

– Most active players

– Other usage metrics
**Notes:**

– Requires `features.statistics: true` in config

– Statistics are tracked per player

– Data persists across server restarts
## Optimization Tips
### For FREE/LOW-SPEC servers (512 MB – 1 GB):

– Keep mode as AUTO or ULTRA_LIGHT

– Limit total plugins to 5-8

– Set view-distance to 4 in server.properties

– Use Paper instead of Spigot

– Limit players to 5-10 concurrent
### For MID-RANGE servers (2-4 GB):

– Use AUTO or BALANCED mode

– Can run 10-15 plugins

– view-distance 6-8

– 15-25 players should be fine
### For HIGH-END servers (4+ GB):

– Use AUTO or HIGH_PERFORMANCE mode

– No significant plugin limitations

– view-distance 10-12

– 25+ players supported
## Performance
YoTPA is built with performance in mind:
– **Lightweight** – Minimal impact on server TPS

– **Thread-Safe** – No lag from concurrent operations

– **Memory Efficient** – Adapts to your server’s resources automatically

– **Async Operations** – Non-blocking task execution

– **Lock-Free** – No race conditions or deadlocks
## Installation
1. Download the latest JAR from the releases

2. Place the JAR in your server’s `plugins` folder

3. Restart your server

4. That’s it! The plugin will auto-configure based on your server’s specs
—

![YoTPA bstats](https://bstats.org/signatures/bukkit/yotpa.svg)
**Note:** This is my first plugin project!.
            
                    
                Yoo RAM
                **Description:**

Yoo RAM shows real-time memory usage, including used, free, and total RAM. It helps administrators and users monitor system performance easily, making memory management simple and transparent. The tool is lightweight, reliable, and designed for quick insights into how resources are being used.
**Commands:**
“`

 /ram – Displays current RAM usage.

 /yoo-ram – An alternative command for the same functionality.
 /rambar – toggles the RAM BossBar.

 /yoo-ram bar – alternative access to the BossBar

“`
**Permissions:**
“`

 yoonai.ram.command.ram – Allows access to the `/ram(/rambar)` and `/yoo-ram(/yoo-ram bar)` commands.

“`