YearCalendar

### ⚠️ This plugin is no longer being updated.

# YearCalendar

**Original Calendar plugin.**
*Let your players check the date!*

—

## Features
– GUI: Keep it simple with only `/calendar` command
– Edit: Edit months, days, colors in config.yml

—

## Commands & Permissions

| Command | Alias | Description | Permission |
|—————|——-|———————|——————–|
| `/calendar` | – | Opens main gui | `calendar365.use` |

—

## Images / Screenshots

Section “**Gallery**”

—

## Files

[Documents](https://github.com/Primly-Project/Documentation)

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.

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*

YamatoPlugin

# YamatoPlugin

YamatoPlugin adds a custom Yamato sword to your Minecraft server

The sword is made for fast combat and gives players several active abilities, ultimate charge from kills, and a configurable item description. It fits well for PvP servers, RPG servers, private servers, and any setup where you want one clean custom weapon without extra plugin dependencies

## Features

* Custom Yamato sword
* Active combat abilities
* Ultimate charge from kills
* Charge progress shown in the item lore
* Configurable damage and cooldowns
* Editable item name and description
* Editable plugin messages
* Works without required dependencies

## Commands

`/yamato give`
Gives Yamato to yourself.

`/yamato give `
Gives Yamato to another player.

`/yamato reload`
Reloads the plugin config.

## Permission

`yamato.admin`

This permission is required for the Yamato command. Server operators have it by default

## Compatibility

* Minecraft 1.20.5 to 1.21.1
* Java 21 or newer
* Spigot, Paper and Purpur

## Installation

1. Download the jar file
2. Put it into your server plugins folder
3. Start or restart the server
4. Edit `plugins/YamatoPlugin/config.yml` if needed
5. Use `/yamato give`

## Configuration

Most important parts can be changed in `config.yml`, including the sword name, material, item description, ability damage, cooldowns, ultimate charge and messages

YAdminCore

[![Discord](https://img.shields.io/discord/1236019317208776786?style=flat&logo=discord&label=Discord&color=%235d6af2
)](https://discord.gg/kZJhKZ48j8)

# YAdminCore
Plugin with, in my opinion, essential commands for server admins. Using permissions for different command functionalities you should be able to precisely specify what admins can do what.

# Commands
– heal and feed
– item
– memory
– god
– gamemode
– fly
– tp – In vanilla style, with @ selectors
– tphere
– tpoffline
– back – Teleports back, based on the last teleport event
– entityinfo / playerinfo
– enchant
– workbench, enderchest, anvil, grindstone, stonecutter, smithingtable, cartographytable, loom

### Other features
– SQLite or MySQL database for saving player data
– 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 for developers

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

# Media – Example commands
`/entityinfo`

`/item` and `/enchant`

`/tp`

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

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.

xWhitelist

# xWhitelist 📋

**xWhitelist** is a high-performance, hybrid whitelist plugin for Minecraft servers. Designed for flexibility and security, it allows server administrators to manage player access through a local whitelist file, a MySQL database, or a staff-only maintenance whitelist.

### Key Features 💫

– **Hybrid Whitelist Support** – Operates in offline/local mode or online MySQL mode.
– **Maintenance Whitelist** – Restrict server access to staff members during maintenance periods.
– **Customizable Messaging** – Multi-line kick messages, configurable prefixes, and command feedback.
– **Permissions Integration** – Fine-grained control over plugin and whitelist commands.
– **Placeholder Support** – Compatible with PlaceholderAPI for dynamic in-game information.
– **User-Friendly** – Simple configuration and intuitive commands for efficient management.
– **Free and Open Source** – Fully available for download and modification under a permissive license.

### Useful Links 🔗

– [GitHub Repository](https://github.com/xDrygo/xWhitelist) – Access the source code, fast releases, and submit **Issues** for bug reports, feature requests, or questions.
– [Wiki Documentation](https://wiki.drygo.dev/xwhitelist) – Detailed guides, configuration examples, and instructions for using xWhitelist.

### Support ❓

For technical issues, unexpected behavior, or enhancement suggestions, please submit an **Issue** on the [GitHub repository](https://github.com/xDrygo/xWhitelist/issues). This ensures your feedback is tracked and addressed efficiently.

—

xWhitelist is engineered to provide a **robust, reliable, and professional whitelist solution**, ensuring secure and efficient player management for your Minecraft server.

xVoidSpawn


# ⭐ xVoidSpawn – Advanced Anti-Void & Spawn Management

—

## 🚀 Key Features

### 🛡 Intelligent Anti-Void System
Automatically teleports players to a safe spawn when they fall below a configurable Y-level.

### ✈ Spawn on Join
Optionally teleport players to the main spawn every time they join the server. Ideal for lobbies and network environments.

### 💥 Fall Damage Protection
Resets the player’s fall distance after teleportation to ensure they never die from fall damage after being saved.

### 🎨 100% Configurable
Fully editable:
– Prefix
– Console messages
– Help menu
– All player messages
– Join behavior
– Void level trigger

Everything is managed inside `config.yml`.

### 🌈 Modern Color Support
Supports:
– Legacy color codes (`&a`, `&l`, etc.)
– HEX color codes (`&#RRGGBB`) for Minecraft 1.16.5+

### ⚡ Lightweight & Performance Friendly
Built to have minimal impact on server performance. No unnecessary tasks or heavy processes.

—

## 🛠 Commands & Permissions

Main Permission: `xvoidspawn.admin`

| Command | Description |
|———-|————-|
| `/xvs setspawn` | Sets the exact teleport spawn location |
| `/xvs reload` | Reloads the configuration without restarting |
| `/xvs help` | Displays the help menu |

All messages and help lines are fully customizable.

—

> ## ⚙ Configuration Overview (config.yml)

“`yaml
# ___ __ _
# / _____ _ __ / _(_) __ _ ⋆✴︎˚｡⋆
# / / / _ | ‘_ | |_| |/ _` | Plugin by ˖⁺‧₊˚♡˚₊‧⁺˖
# / /__| (_) | | | | _| | (_| | xPlugins
# ____/___/|_| |_|_| |_|__, |
# |___/ .yml

# Language setting. Options: ‘en’, ‘es’.
# If you change this to ‘es’ and reload, the config messages will update to Spanish.
locale: en

teleport-on-join: true
void-level: 0

console-messages:
plugin-enabled: “&#55FF55[xVoidSpawn] &#AAAAAAPlugin enabled successfully.”
plugin-disabled: “&#FF5555[xVoidSpawn] &#AAAAAAPlugin disabled successfully.”

prefix: “&#4498DBxVoidSpawn &8» ”

messages:
no-permission: “&#FF0000 ✘ ¡Error! &fYou do not have permission.”
player-only: “&#FF0000 ✘ ¡Error! &fOnly players can use this.”
spawn-set: “&#00FF49 ✔ ¡Success! &fVoid spawn set.”
spawn-not-set: “&#FAEDCB ℹ ¡Attention! &fSpawn not set.”
void-teleport: “&#FCD05C ☀ ¡Careful! &fSaved from the void.”
reload: “&#55FF55 ✔ ¡Success! &fConfiguration reloaded.”
help-message:
– “”
– “&#FF5555&l xVoidSpawn – Help”
– “”
– “&8 • &#4498DB/xvs setspawn &8▸ &fSet spawn.”
– “&8 • &#4498DB/xvs reload &8▸ &fReload config.”
– “&8 • &#4498DB/xvs help &8▸ &fShow help.”
– “”
“`
—

> ## 📥 Installation

1. Download the latest .jar file.
2. Place it inside your server’s plugins folder.
3. Restart your server.

– In-game, run “/xvs setspawn“ at a safe location.
-# Your server is now protected from void deaths.

> ## 🎯 Ideal For

1. Lobby Servers
2. SkyBlock Hubs
3. Minigame Worlds
4. Void Maps
5. Network Setups

## 🔧 Compatibility

1. ✔ Spigot
2. ✔ Paper
3. ✔ 1.16.5+

xTranslate

# xTranslate
—————————————————————————————————-
### What is xTranslate ?
_xTranslate is a Minecraft Translation Plugin that translates In-game Chat messages in real time_

### How do i change my language ?
_You can change your language simply by typing /lauguage _

### How many languages are supported ?
_I dont even know the exact count but over 100+ languages are supported_
###

### How does it work and is it free ?
_xTranslate is 100% and uses the offical `GOOGLE TRANSLATOR API`_