This is originally for modpack AnimateCraft: Lankeren. If you like this content, I’m sure you’ll like that modpack, too. Welcome to check it out!
—
You hate villagers? You think they are useless? You want to kick their asses? Alright, I don’t know why you think that way, but now I can let you do it in a cooler way.
Introducing ***You Bandit!***, a derive mod of ***You Thief!***. With this mod, you can choose to be a bandit, hang around with the illagers, and loot the villagers.
After killing two villagers, you will get an unluck debuff, and you become a bandit, really simple.
Being a bandit means you will be hated by villagers and iron golems, the former will rise their trading prices, the latter will not stop chasing you.
But bandits have advantages. You are now much stronger, and the illagers will not attack you anymore!–Not until you betray them.
When you kill one of the illagers (including witch and vex), you will be cursed with a Bad Omen V. Even worse, you cannot use milk bucket to get rid of it or the consequence it brings–continuously spawned vexs around you! Now this is the real bad omen!
Want to make up what you’ve done? Take the Bade Omen V to the village, and win the raid! Then you’ll gain a Hero of the Village V, which can decrease the trader price to the original level (only a bit higher :))
## 版权声明|License
– **作者保留该作品的所有权利。禁止在其他社交平台（包括群聊、网盘等）重新上传或商用，否则后果自负。** This content is All Rights Reserved, meaning that you cannot redistribute/modify & distribute this content, or use it in commercial ways.
– **欢迎您将其收录到整合包中或用其制作视频，请在简介处附上此发布页面的链接和我的bilibili主页，也欢迎在简介艾特我，我很想看你们的视频！**
If you make a video about this content or put this content in your modpack, please give credit and link to this page, and I would love to know! Thank you.
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:
# All messages are customizable
commands:
tpa:
usage: “Usage: /tpa ”
sent: “Teleport request sent to {target}”
received: “{requester} wants to teleport to you.”
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
“`
**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
“`
**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
“`
**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
“`
**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.
**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
“`
**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.
**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
A nice little vanilla+ pvp texture pack that just changes the gui. No blocks or item textures are modified. Thanks to Justinkras for making the original pack, which can be found here: https://www.curseforge.com/minecraft/texture-packs/old-blue-pvp.
Your Options Shall Be Saved (YOSBS)
# Your Options Shall Be Saved (YOSBS)
Your Options Shall Be Saved (YOSBS) is a lightweight utility mod that lets modpack creators define default configuration files without overwriting player preferences
Updating a modpack often resets custom settings like keybinds or mod configs, because most launchers replace the entire `config/` folder
YOSBS solves this by copying any file placed in `config/yosbs/` to its proper location only once on first launch — and never again
This gives full control to the pack author:
– Files inside `config/yosbs/` are treated as user-owned: copied once, then left untouched
– Files inside `config/` behave as usual: they will be replaced on each update
That way, you decide which configs should persist, and which should reset
## Features
– **Zero-config**: just drop the defaults under `/config/yosbs/…` (or legacy `/config/yosbr`)
– Works for **any** file – `options.txt`, mod configs, `optionsshaders.txt`, etc
– Runs in the **pre-launch phase**, before Fabric/Forge starts loading the rest of the mods
## Compatibility & Installation
1. Fabric Loader ≥ 0.4.0 *(No Fabric API required)*
2. Minecraft 1.14 – 1.21.x
3. Requires Java 8 or newer
4. Put the YOSBS jar in `mods/` and launch once – the folder `/config/yosbs` is created automatically (or create it manually)
## Usage examples
| Want to ship… | Do this before first launch |
|—————|—————————-|
| A default `options.txt` | Place your file at `/config/yosbs/options.txt` |
| A REI config | `/config/yosbs/config/roughlyenoughitems/config.json5` |
## Credits
Inspired by the original Your Options Shall Be Respected – YOSBR by *shedaniel*
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.
“`
Yoo Announce
# YooAnnounce
**YooAnnounce** – Minecraft plugin for automatic chat announcements.
## Commands
| Command | Alias | Description |
| — | — | — |
| `/yoo-announce help` | `/ya help` | Displays the help menu and plugin information. |
| `/yoo-announce reload` | `/ya reload` | Reloads the configuration and restarts the announcement task. |
## Permissions
| Permission | Description
| — | —
| `yoonai.announce.command.help` | Allows use of the `/ya help` command.
| `yoonai.announce.command.reload` | Allows use of the `/ya reload` command.
## Configuration
* All configuration files are located in the plugin folder.
* `config.yml` – main plugin settings (messages, intervals, etc.)
## Reporting Bugs
* If you encounter issues or have suggestions, please create an Issue.
* Provide as much detail as possible (Minecraft version, plugin version, error messages).
YönetimPaneli
YonetimPaneli is plugin to use to manage your server from desktop
Also this plugin provide to use some plugin from desktop
This plugin is meant for hardcore survival servers, that implements, but also expands on the vanilla hardcore
mechanics for a player’s death on a server.
Upon death players usually get banned off of a server, if (and only if) the setting for hardcore was enabled in
`server.properties` before world generation.
That is not the case if this setting was set to true retroactively.
And here is, where this plugin comes into play, by
implementing this behaviour regardless of when hardcore was enabled.
Additionally, you can exempt players from this rule
and send a customized message to a Discord-server upon the occurrence of a (non-exempt) player-death.
The plugin can also force a resource-pack of your choice, with the default one replacing the normal health-bar with
hardcore-hearts, on any non-exempt player.
(*You can check out the resource-pack
here.*)
## 2. Configuration
### 2.1 `config.yml`
There are currently four configuration sections.
The first one is for managing the resource-pack sent to non-exempt players:
“`yaml
# You can specify a custom resource pack and turn off forcing the pack onto non-exempt players.
resource-pack:
force: true
custom:
use: false
url: “”
sha1: “”
“`
– The `force` option lets you control, whether the player *has* to accept the pack. (Allowed values: `true`, `false`)
– `custom` lets you define a custom resource-pack, other than the default one.
– `use`: Set to `true` to use the custom pack, otherwise set it to `false`
– `url`: The download-link to the custom pack.
– `sha1`: The sha1-checksum of the file. You can use
this tool to obtain it.
The next section is for configuring the Spicord integration:
– `send`: Whether to enable the Spicord-Integration. (Allowed values: `true`, `false`)
– `message_channel_id`: The id of the channel to send the message to. You can obtain it using
this method
(you can also obtain the channel-id by itself, by right-clicking the channel on the channel-selection-sidebar).
In the `announce` section you can individually toggle messages:
The listed messages are announcements that would be sent on their respective occasions and targets.
The allowed values are `true` or `false`.
The option `enable-on-non-hc` lets you enable this plugin’s functionality even on a non-hardcore server, while the last
option `easy-disable` lets you disable the death-ban functionality, if it’s `true` (previously dead players can join, if
this is enabled).
It may take a while before banned players can join if this option is true.
Yet again acceptable values (for both) are `true` and `false`.
### 2.2 `chat_messages.properties`
The messages defined in this file are chat messages that can be customized.
There shouldn’t be a need to add more.
You can also use the MiniMessage format to make them *special*.
How you can use this format, you can read here.
### 2.3 `discord/[…].json`
In these files, you can customize the embeds, sent by the plugin.
You can use this tool to visualize them and generate the json file.
If, for example, you’d like to customize the discord message, that is getting sent upon a player’s death, you’d need to
modify `plugins/yolo/discord/death_message.json` to something like this:
### 2.4 `ban_message.txt`
This is where you can customize the ban message that players see when they’re dead.
### 2.5 Text replacements
Every message that gets sent by the Plugin can use the following replacements:
– `%player_name%` – The name of the affected player
– `%totem_uses%` – The number of totems the subject player of the message has used.
– `%death_message%` – The death message, if the player has died. (only available in messages, sent upon a
player’s death.)
– `%version%` – The current version of the plugin.
## 3. Permissions
One permission is `yolo.exempt`, which excludes any players having it from the plugin’s effects. There are also two
other permissions that relate to commands. These are described in the section about [commands](#4-commands).
For a general guide to permissions on Bukkit and its derivatives, please refer to
this page. *(I’d recommend using a permission manager like
LuckPerms though.)*
## 4. Commands
There are currently two commands available:
– `/yolo-reload`: This command is useful for reloading all configuration dependent features of this plugin, without
having to restart the whole server. It requires the `yolo.reload` permission.
– `/revive [revivable player] `: This command lets you revive a
player who has died, attempting to restore their inventory and teleporting them to their death location (if safe). It
requires the `yolo.revive` permission. You can also disable restoring their inventory and the teleportation, by setting
the arguments to `false`. (If you only want to disable the teleport, you need to explicitly set the inventory restoring
to `true`.)
– `/checkout_death_location` This command lets you teleport to a dead player’s death location. This is useful for
checking for traps and duplicate items. It requires the `yolo.revive` permission.
## 5. Further considerations
– If hardcore is enabled in `server.properties`, the resource pack is always forced upon players by default. (
configurable since: 0.4.0)
– In order to use Spicord, you have to configure it correctly. In order to register this plugin as an addon for a bot,
you have to add it like this:
“`toml
### ↑ Irrelevant stuff above ↑ ###
[[bots]]
name = “” # Name for the bot here.
enabled = true
token = “” # Your bot’s token here
command_support = true # Irrelevant for this plugin’s Spicord addon.
command_prefix = “-”
addons = [
# Potentially other addons.
“yolo”
]
### ↓ Other irrelevant stuff below ↓ ###
“`
– **This plugin was made for PaperMC-1.19.4.** Other versions and platforms haven’t been tested *yet*, but this is
planned
to be completed until the full release. Issues for incompatibility can
be submitted, but will not be resolved if
this means dropping support for other compatible versions.
– Reviving a player with inventory restoring enabled, can lead to item duplication, as players still drop their items.
You may want to check out the teleport location with `/checkout_death_location` first, in order to check for duplicates.
– This is a pre-release version, so bugs or glitches may be encountered more often.
## 6. Planned features
– Commands to undo a player’s revive
– GUI for the revive-system (planned for 2.0)
– Full support for PlaceholderAPI (planned for 2.0)
– Death location marker on Dynmap, Bluemap and co. (planned for in 2.0)
– Have a suggestion? Submit it here!
## 7. For developers
To add this project as a dependency for yours, follow this link and select
your desired version (go to *branches* → *master-SNAPSHOT* for the most recent version). Then follow the instructions
below.
To avoid inflating your jar-file, you can change the scope to `compileOnly`.
Additionally, you’ll need to declare the dependency in your `plugin.yml`-file like this:
“`yml
#### ↑ other stuff ↑ ###
depend: [ # Or `softdepend`
Yolo
]
#### ↓ other stuff ↓ ###
“`
You can find the documentation here.
—
*From Version: 0.7.0*
YoChat
**YoChat** is a Paper chat plugin for formatted chat, channel-based messaging and built-in moderation. It supports MiniMessage, legacy `&` colors, mentions, custom player prefixes/suffixes and Discord webhook logging for mute actions.
—
## Features
* MiniMessage chat with legacy colors and hex support
* Channels with radius, world restrictions and per-channel formatting
* Temporary and permanent mutes with optional webhook logging
* Blocked words, mention highlighting and mention sounds
* Prefix/suffix priority support for LuckPerms, Vault and YoChat
* Optional PlaceholderAPI support
* Developer API for channels, mutes, formatting and pipeline hooks
—
## Requirements
* Java 21
* Paper 1.21.x
* LuckPerms or Vault
* PlaceholderAPI optional
—
## Installation
1. Put `YoChat.jar` into the `plugins` folder.
2. Make sure Java 21 is in use.
3. Install LuckPerms or Vault.
4. Start the server at once.
5. Edit `config.yml` as needed.
6. Use `/yochat reload` after config changes.