YeeeesMOTD

Customized server motd and random icon, it can use player’s head as server icon,like this:

)

also use player’s name as motd description, and random icon

everything is up to you

for more information please go to github: https://github.com/RTAkland/YeeeesMOTD

YChatManager

# YChatManager
Plugin for chat management, formatting, anti-spam etc. Requires at least **[Paper](https://github.com/PaperMC/Paper)**, won’t work on Spigot or Bukkit.

# Features
### Chat formatting
– Custom chat format with [MiniMessage](https://docs.advntr.dev/minimessage/index.html), [PlaceholderAPI](https://github.com/PlaceholderAPI/PlaceholderAPI) and [Vault](https://github.com/milkbowl/Vault).
– Custom displayname format also with [MM](https://docs.advntr.dev/minimessage/index.html), [PAPI](https://github.com/PlaceholderAPI/PlaceholderAPI) and [Vault](https://github.com/milkbowl/Vault).
– Per permission colors, formats and [MiniMessage](https://docs.advntr.dev/minimessage/index.html) tags to use in messages.

### Chat culture
– Anti swear, flood, caps
– Allowed message RegEx pattern
– Message cooldown
– Command cooldown

### Private messages
– With receive sound
– And socialspy for admins

### Other
– Custom nicknames using simple command, where every [MiniMessage](https://docs.advntr.dev/minimessage/index.html) tag and legacy format is available per permission.
– Clear chat command.
– Join, quit and death messages, also with an option to disable them
– Fully customizable messages with lang file, supporting [PlaceholderAPI](https://github.com/PlaceholderAPI/PlaceholderAPI) and [MiniMessage](https://docs.advntr.dev/minimessage/index.html)
– Commands with tab completions
– [API](https://github.com/Ynfuien/YChatManager/wiki/4.-Developer-API) for developers

# Documentation
You can read about plugin’s [permissions](https://github.com/Ynfuien/YChatManager/wiki/2.-Permissions), [placeholders](https://github.com/Ynfuien/YChatManager/wiki/3.-Placeholders) etc. on the [wiki](https://github.com/Ynfuien/YChatManager/wiki) page.

# Media

# 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/YChatManager) 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/YChatManager/main/blob/LICENSE) license.

YARMM

Another menu plugin, yaaay

# Examples

## Fully Customizable & Dynamic Items
Whether you want dynamic item names, lore, slots, damage, player head, shield color, banner pattern, potion effect, firework effect, light level, crossbow projectile… bundle inventory? You can have it all! And all are refreshed basically instantly thanks to TAB’s handling of placeholders (can be configured in its config).

You can also use TAB’s animations with the change-interval that you want to display custom data.

Menu: https://paste.helpch.at/yayeretiwa.less
TAB’s animations.yml: https://paste.helpch.at/gikidelemo.makefile

## Prompts

# Plugin Convertion

At this time, YARMM only supports converting menus from DeluxeMenus.
Almost everything is converted except for the meta action & requirement (will be added to ConditionalActions at some point)

To convert menus, simply run /yarmm convert DeluxeMenus (plugin not required on the server, only the folder) and everything in the `/plugins/DeluxeMenus/gui_menus` folder will be converted (regardless of whether they’re registered in DM’s config.yml or not)

# Dependencies
**This plugin depends on both TAB and ConditionalActions** (and by extension PAPI, yes I know that makes 3 dependencies, sorry XD)
TAB allows for instant refreshing of item properties (including material) as well as mennu title; ConditionalActions lets you execute actions on click depending on conditions.
You have access to both TAB & PlaceholderAPI placeholders.

YardWatch

# YardWatch (for server owners)
Implementation of [YardWatchAPI](https://github.com/YouHaveTrouble/YardWatchAPI) for common protection plugins. If any of supported plugins implements the API itself, then this plugin will stop providing its implementation to allow the
plugin to take over.

If you’re a developer looking for information how to implement YardWatchAPI in your plugin, see
[YardWatchAPI](https://github.com/YouHaveTrouble/YardWatchAPI)

## Requirements
– Java 17
– Minecraft 1.16+

## Implementations for:
– GriefPrevention (v16+)
– WorldGuard (7.0.0+)
– LWCX
– FactionsUUID
– SuperiorSkyBlock
– Towny
– PlotSquared (6.0.0+)

## Plugin you’re using is not implementing YardWatchAPI?
Contact the plugin developer and send them [here](https://github.com/YouHaveTrouble/YardWatchAPI/blob/master/readme.md)!

You can also request a temporary implementation within this plugin [here](https://github.com/YouHaveTrouble/YardWatch/issues/new?assignees=&labels=enhancement&projects=&template=implementation-request.yml&title=%5BNEW+IMPLEMENTATION%5D%3A+).

# YardWatchAPI (for developers)

API to unify protection plugins for minecraft bukkit servers to allow easy protection queries without having to import
10 different plugin apis with separate implementations.

Current version: [](https://jitpack.io/#YouHaveTrouble/YardWatchAPI)

If you’re looking for a plugin implementing YardWatchAPI for common protection plugins, see [YardWatch plugin](https://github.com/YouHaveTrouble/YardWatch).

# Usage

### Import the api using dependency manager

In any case of usage you will need to import the API. Replace `VERSION` with current version tag. You should also adjust your `` to `provided` if you’re not implementing the api and just querying it.

#### Maven
“`xml

jitpack.io
https://jitpack.io


com.github.YouHaveTrouble
YardWatchAPI
VERSION
compile

“`
#### Gradle
“`gradle
dependencyResolutionManagement {
repositoriesMode.set(RepositoriesMode.FAIL_ON_PROJECT_REPOS)
repositories {
mavenCentral()
maven { url ‘https://jitpack.io’ }
}
}
dependencies {
compileOnly ‘com.github.YouHaveTrouble:YardWatchAPI:VERSION’
}
“`

## For plugins wanting to see if something is protected

### Check if player can break a block

Example handling of block breaking check. There’s no need to depend on any plugins for this.

“`java
public boolean canBreakBlock(Player player, Block block) {
ServicesManager servicesManager = getServer().getServicesManager();
Collection> protections = servicesManager.getRegistrations(Protection.class);
for (RegisteredServiceProvider protection : protections) {
if (protection.getProvider().canBreakBlock(player, block.getState(true))) continue;
return false; // if any protection plugin disallowed breaking the block, return false
}
// If all protection plugins allowed breaking the block, return true
return true;
}
“`

## For protection plugins

### Depend on YardWatch plugin

You can optionally softdepend and check if YardWatch is present to add an optional integration.

“`yml
depend:
– “YardWatch”
“`

### Implement Protection interface

Implement all the methods required by the interface

“`java
public class YourPluginProtection implements Protection {}
“`

### Register your implementation as a service

“`java
@Override
public void onEnable() {
getServer().getServicesManager().register(
Protection.class,
new YourPluginProtection(),
this,
ServicePriority.Normal
);
}
“`

YAML API

# YAML API

YAML API is a specialized library that simplifies working with YAML configuration files in Bukkit/Spigot/Paper plugins. It provides a robust and consistent interface for loading, saving, updating, and managing YAML-based configurations, along with advanced mapping capabilities for configuration sections and configurable units.

—

## Overview

The **YAML API** package offers a set of tools designed to handle YAML configuration files efficiently. It abstracts the complexity of file I/O and reflection-based configuration parsing, allowing you to focus on using configuration data in your plugin.

Key components include:

– **YAMLFile**: A class to load, save, and update YAML configuration files.
– **ResourceUtils**: Utility methods for handling resources and file operations.
– **Configurable & ConfigurableFile**: Interfaces and classes that provide easy access to the underlying `FileConfiguration`.
– **ConfigurableUnit**: An interface representing a configuration unit, useful for handling permissions or groups in the configuration.
– **Mappable, SectionMappable, UnitMappable & HashMappable**: A set of interfaces and classes for mapping configuration sections and units into Java collections.
– **YAMLUpdater**: A class that updates YAML files by merging default values and preserving comments.

—

## Key Features

– **Unified Configuration Management**:
Provides a consistent API for reading, writing, and updating YAML configuration files.

– **Dynamic Mapping and Conversion**:
Supports mapping configuration sections to custom units and collections, making it easier to work with complex configuration structures.

– **Resource and File Utilities**:
Includes helper classes to simplify file loading, resource saving, and directory management.

– **Comment Preservation and Updates**:
YAMLUpdater handles merging of default configuration values while preserving existing comments.

– **Reflection-Based Parsing**:
Uses reflection to dynamically access configuration sections and values, ensuring compatibility across server versions.

—

## Usage Example

Below is an example demonstrating how to use the YAML API to load, update, and work with configuration files.

### Example: Using ConfigurableFile and YAMLFile

“`java
package com.example.myplugin;

import me.croabeast.file.ConfigurableFile;
import me.croabeast.file.YAMLFile;
import org.bukkit.configuration.file.FileConfiguration;
import org.bukkit.plugin.java.JavaPlugin;

import java.io.IOException;

public class MyPlugin extends JavaPlugin {

private ConfigurableFile config;

@Override
public void onEnable() {
try {
// Create a new configuration file located in the “config” folder
config = new ConfigurableFile(this, “config”, “settings”)
// Optionally, override methods to control updatability or other behaviors
{
@Override
public boolean isUpdatable() {
// Retrieve the “update” key from the configuration to decide if updates are allowed
return get(“update”, false);
}
};
// Save the default configuration if not present
config.saveDefaults();
// Update the configuration file (merges defaults and preserves comments)
config.update();
} catch (IOException e) {
e.printStackTrace();
}

// Access configuration values
String prefix = config.get(“lang-prefix”, “&e MyPlugin »&7”);
getLogger().info(“Language prefix: ” + prefix);
}
}
“`

### Example: Working with Mappable and SectionMappable

“`java
package com.example.myplugin;

import me.croabeast.file.SectionMappable;
import me.croabeast.file.ConfigurableFile;
import org.bukkit.configuration.ConfigurationSection;
import org.bukkit.plugin.java.JavaPlugin;

public class MyPlugin extends JavaPlugin {

private ConfigurableFile config;

@Override
public void onEnable() {
try {
config = new ConfigurableFile(this, “config”, “settings”);
config.saveDefaults();
config.update();
} catch (Exception e) {
e.printStackTrace();
}

// Assume we have a configuration section “advancements”
ConfigurationSection section = config.getConfiguration().getConfigurationSection(“advancements”);
if (section != null) {
// Create a SectionMappable from the configuration section
SectionMappable.Set sectionMap = SectionMappable.asSet(section.getValues(false));
// Process the mapped configuration as needed
getLogger().info(“Loaded advancements: ” + sectionMap);
}
}
}
“`

—

## Maven / Gradle Installation

To include YAML API to the project, add the following repository and dependency to your build configuration. Replace `${version}` with the desired version tag.

### Maven

Add the repository and dependency to your `pom.xml`:

“`xml


croabeast-repo
https://croabeast.github.io/repo/

me.croabeast
YAML-API
${version}
compile


“`

### Gradle

Add the repository and dependency to your `build.gradle`:

“`groovy
repositories {
maven {
url “https://croabeast.github.io/repo/”
}
}

dependencies {
implementation “me.croabeast:YAML-API:${version}”
}
“`

Replace `${version}` with the appropriate module version.

—

## Conclusion

**YAML API** is a powerful library for managing YAML configurations in your Bukkit/Spigot/Paper plugins. It streamlines file operations, mapping, and updates while preserving comments and ensuring compatibility across server versions. Whether you are building simple configuration systems or working with complex, nested settings, YAML API provides the tools you need to efficiently manage your plugin’s configuration.

Happy coding!

— *CroaBeast*

yaay

YAAY (Yes, Another Addon for Yamipa) is a feature-rich addon for the Yamipa plugin that expands the image-claiming experience with a dedicated /imgui menu flow. Built for Paper and Folia servers, it provides a paginated inventory-based interface that makes browsing and claiming images easier and more intuitive for players.

### Key features

– **Paginated /imgui GUI** for browsing and claiming images
– **Visibility filtering** based on public and private path patterns
– **Claim cooldowns** to control how often players can claim images
– **Hourly limits** to help balance usage on busy servers
– **Anti-exploit protections** for safer image claim handling
– **Language support** with persistent per-player preferences
– **Public language sync API** for integration with other plugins
– **Per-file display overrides** through `display.yml`
– **Item overrides** for more flexible presentation
– **Multiple configuration files** for easy customization

### Configuration files

YAAY includes separate files for customizing:

– GUI behavior
– Claim limits
– Messages and translations
– Display settings
– Player locale options

### Compatibility

– **Java 8+**
– **Paper/Folia compatible**
– **Requires YamipaPlugin**

YAAY is designed to extend Yamipa with a cleaner, more configurable, and more user-friendly image management experience.

XTransfer

# XTransfer

## Features
– Developer API
– Whitelist of Player UUID’s
– Token Whitelist via Paper’s Cookie System.
– Customizable and developer-friendly

## Commands
– `/xtransfer` (or your custom Option) – Permission: `transferpacket.command.`

## Permissions
– `xtransfer.command..transfer`
– `xtransfer.command..whitelist`
– `xtransfer.command..whitelist.list`
– `xtransfer.command..whitelist.player`
– `xtransfer.command..whitelist.player.add`
– `xtransfer.command..whitelist.player.remove`
– `xtransfer.command..whitelist.token`
– `xtransfer.command..whitelist.token.add`
– `xtransfer.command..whitelist.token.remove`

## Developer API

**Use our repo to Download the API**
– [https://repo.jespersen.zip/#/releases/dev/xyzjesper/xtransfer](https://repo.jespersen.zip/#/releases/dev/xyzjesper/xtransfer)

### Project Setup

To access the API use the `XTransferAPI` Menthods and interact with the plugin.
__Note: Please add the Plugin TransferPacket as depend! And check the enabled status.__

“`kts
repositories {
mavenCentral()
maven(“https://repo.jespersen.zip/releases”)
}

dependencies {
compileOnly(“zip.jespersen:xtransfer:“)
}

“`

xTPA

## 🚀 xTPA: The Definitive Teleportation Suite

The **xTPA** (Extended Teleport Ask) plugin is a next-generation teleportation management system built specifically for high-performance Minecraft servers running **Paper/Folia 1.21+**.

It moves beyond standard TPA functionality by offering an exceptionally feature-rich, optimized, and customizable experience for server administrators and players alike.

### ✨ Core Features & Technical Excellence

* **Asynchronous & Folia-Ready Performance:** Designed from the ground up to utilize modern multi-threading, ensuring zero lag even under heavy load by performing non-critical operations (I/O, cooldown checks) off the main server thread.
* **Deep Customization:** Every element—from messages (supporting MiniMessage gradients and clickables) to GUI layouts, particle effects, and sound cues—is fully configurable via modular YAML files.
* **Advanced Warmup System:** Features highly visual countdowns using Boss Bars and Action Bars, with fully configurable cancellation conditions (movement, damage, interaction), ensuring strategic and fair teleports.
* **Comprehensive Command Set:** Includes standard TPA/TPAHere, but extends to include safe, configurable Random Teleport (`/tpr`), multi-location History (`/back`), and admin utilities like `/tpsummon`.
* **Integrated Economy:** Seamlessly hooks into **Vault** and **PlaceholderAPI** to allow per-command costs, request fees, and acceptance rewards, transforming teleportation into an engaging economic feature.
* **Modern GUIs:** Provides inventory-based interfaces (`/tpagui`, `/tpalist`) for effortless request management and player selection, replacing cumbersome chat commands.

**xTPA is engineered to be the most reliable, flexible, and high-performance TPA solution available for the modern Minecraft ecosystem.**

XTransfer


# 0 What the heck is this?

A new plugin designed to **transfer players’ data between names or UUIDs**. I didn’t find any other plugin can handle this problem before, so I made my own one and uploaded it to here to help anyone who needs this feature for his/her server.

# 1 Features

## 1.1 Smart UUID Detection

Automatically detects UUIDs from:
– Online players
– usercache.json (for premium players)
– Offline-mode UUID generation

## 1.2 Complete Data Transfer

Transfers all vanilla player data:
– Player inventory and Ender Chest (`playerdata/`)
– Statistics (`stats/`)
– Advancements (`advancements/`) for 1.13+

## 1.3 Safe & Reliable

– Creates automatic backups before overwriting
– Kicks online players to prevent data overwrite (configurable)
– Asynchronous file operations – no server lag!

# 2 Commands and Permission Nodes

## 2.1 Commands

“`markdown
– /xtransfer – Show version info
– /xtransfer transfer – Transfer by player names
– /xtransfer transferuuid – Transfer by UUIDs
– /xtransfer list – List all player data files
– /xtransfer list – Show files for specific player
– /xtransfer reload – Reload configuration
– /xtransfer help – Show the help message

/xtf = /transfer = /xtransfer
“`

## 2.2 Permission Nodes

“`markdown
– xtransfer.manage – Allows using all XTransfer commands (default: op)
“`

# 3 Config

“`yaml
# Show logo when plugin enabled
show_logo: true

# World settings
world:
# Manual world name (only used if auto-detect is false)
name: “world”
# Automatically detect world name from server
auto-detect: true

# Transfer settings
transfer:
# Transfer statistics files
stats: true
# Transfer advancements files (1.13+)
advancements: true

# Backup settings
backup:
# Create backup of existing files before overwriting
create: true
# Suffix for backup files
suffix: “.old”

# Online player handling
# If true, kick online players before transfer
# If false, show warning but continue
kick-online-player: true

# Language settings
language: “en”

# Debug mode (enable only for troubleshooting)
debug: false

# Messages – You can customize all messages here
messages:
# English messages
en:
no-permission: “&cYou don’t have permission!”
usage-header: “&9&lX&f&lTransfer &f&lHelp”
usage-transfer: “&7/xtransfer transfer &f ”
usage-transferuuid: “&7/xtransfer transferuuid &f ”
usage-list: “&7/xtransfer list &f[player]”
usage-reload: “&7/xtransfer reload”
usage-help: “&7/xtransfer help”
reload-success: “&a✓ Configuration reloaded!”
transfer-start: “&eStarting async transfer…”

looking-up: “&eLooking up UUIDs for &f{old} &eand &f{new}&e…”
uuid-not-found: “&cCould not find UUID for: &f{name}”
try-uuid: “&7Try using /xtransfer transferuuid with direct UUIDs”
invalid-uuid: “&cInvalid UUID format! Use: /xtransfer transferuuid ”
uuid-example: “&7Example: 12345678-1234-1234-1234-123456789012”

source-data-missing: “&cSource player {name} ({uuid}) has no data file!”

transfer-from: “&7From: &f{name} &7({uuid})”
transfer-to: “&7To: &f{name} &7({uuid})”
transfer-file: “&7File: &f{file}”
backup-created: “&7Backed up existing file to: &f{file}”
transfer-success: “&a✓ Successfully transferred player data!”
transfer-stats: “&7✓ Transferred stats file”
transfer-advancements: “&7✓ Transferred advancements file”
transfer-error: “&cError during transfer: {error}”

folder-not-found: “&cPlayer data folder not found: {path}”
source-not-found: “&cSource file not found: {file}”
source-location: “&7Looked in: {path}”

player-online-warning: “&e⚠ Warning: Player {player} is online! Data may be overwritten when they log out.”
player-kicked: “&e✓ Player {player} has been kicked for data transfer.”
kick-message: “&cYour data is being transferred. Please rejoin in a few seconds.”

no-files: “&eNo player data files found”
list-header: “&6=== Player Data Files ({count}) ===”
list-more: “&7… and {count} more”
list-entry: “&7{name} &8- {uuid}”
list-unknown: “&8{uuid} &7(unknown)”

files-header: “&6=== Files for {player} ===”
file-playerdata: “&7Player Data: {status}{size}”
file-stats: “&7Stats: {status}”
file-advancements: “&7Advancements: {status}”

# Other language…
“`

X-Socials

—

### 🌟 Comprehensive Social Management

X-Socials is a professional and highly optimized solution for managing your server’s social networks. From 1.8 to 1.26.1, provide your players with a **Premium GUI Editor**, **Interactive Links**, **Automatic Rewards**, **Custom Cooldowns**, **Statistics**, and **Rich Text Formatting**. Runs natively on **Folia**, **Paper**, **Purpur**, and **Spigot**.

—

### 🚀 Premium Features

– **🪄 Auto-Config Updater** — Configs stay up-to-date automatically with every new version.
– **🖥️ Professional GUI Editor** — Create, edit and delete social networks from an intuitive in-game interface.
– **💬 Interactive Links** — Clickable URLs with hover tooltips via Bungee Chat API.
– **🎁 Reward System** — Console commands executed on first visit (UUID-based, one-time).
– **⏱️ Custom Cooldowns** — Per-social network cooldown configuration.
– **🔊 Custom Sounds** — Play different sounds for each social network.
– **📺 Custom Titles** — Show titles when players use social commands.
– **📊 Statistics System** — Track total and per-social network usage with placeholders.
– **🎨 Rich Text** — RGB colors, gradients, MiniMessage support.
– **🌍 Universal Compatibility** — Native support for Folia, Paper, Purpur, Spigot, and Bukkit.
– **🌐 Multi-Language** — Bundled support for ES, EN, PT, JA, RU.
– **📡 Broadcast System** — Automatic multi-line announcements.
– **🧩 PlaceholderAPI** — Native expansion with multiple placeholders.

—

### 💻 Commands

| Command | Description | Permission |
| :— | :— | :— |
| `/xs -gui` | Open the premium GUI editor | `xsocials.gui` |
| `/xs reload` | Reload configurations | `xsocials.admin` |
| `/xs list` | List all social networks | `xsocials.use` |
| `/xs update` | Check for updates | `xsocials.admin` |
| `/xs version` | Show plugin version | `xsocials.use` |

**Dynamic Social Commands** — `/discord`, `/youtube`, `/[your-network]`…

—

### 🔐 Permissions

| Permission | Description | Default |
|———–|————-|———|
| `xsocials.*` | Full wildcard access | ❌ |
| `xsocials.admin` | Editor, reload, gui, update | ❌ (OP) |
| `xsocials.gui` | GUI editor access | ❌ (OP) |
| `xsocials.use` | Basic player access | ✅ All players |

—

### 🧩 Placeholders

| Placeholder | Description |
| :— | :— |
| `%xsocials_total_uses%` | Total uses |
| `%xsocials__uses%` | Uses for specific network |
| `%xsocials__enabled%` | Enabled status |
| `%xsocials__link%` | Network link |
| `%xsocials__command%` | Network command |

—