Yeahlows PVP Pack
THIS IS A TEXTURE PACK
Okay you probably already knew that…
This texture pack prioritizes making the most important changes for a pvp pack without making the game look completley different. Older versions of this texture pack include short swords for 1.8, low shields and smaller items.
This pack supports both 1.6.1-1.8.9 for short swords, and 1.21-1.21.10 (Might support older versions)
Ye Shunguang Totem
This resource pack replaces the default Totem of Undying with a custom texture inspired by **_Ye Shunguang from Zenless Zone Zero_**. The original Minecraft totem is swapped out for a stylized depiction of Yeshenguāng, designed to blend smoothly with the game’s visual style while standing out as a unique cosmetic change. The pack does not affect gameplay in any way, serving purely as a visual enhancement for players who enjoy personalizing their world and showcasing their appreciation for **Zenless Zone Zero.**
YDM’s Scorpions
YDM’s Scorpions for FORGE/FABRIC/NEOFORGE
This mod adds scorpions to the game!
Brown and Emperor Scorpion spawns in the desert, while the Nether Scorpion Spawns in the Soul Sand Valley.
They will burrow themself in to the ground on daylight.
They drop Scorpion stingers that can be brewed into Venom Coat Potion.
After consuming this potion you will get a venom “armor” that will poison attackers!
If you have a spider eye in your hand then they won’t attack you and are tempted by it.
So like that you can make them follow you.
Other mod biome compatibility!
Spawn config options:
– Biome name(s) where it should spawn
– Spawn rate (The higher, the more chance for spawning a group)
– Minimum and maximum number of a Group
– Poison Duration (20 means -> 20 seconds)
– Health Point
– Damage Value
If you want the scorpions to spawn in another mods biome.
You have to change the biome_name line:
For example to:
biome_name = “modid:name_of_the_biome”
To let it spawn in more biomes you have to put a comma (,) between the biome names like this:
biome_name = “modid:name_of_the_biome,minecraft:desert”
The 1.19 version doesn’t have a spawn config.
The biome world generation changed a bit and now the spawn settings will be editable in json files.
To select the desired biomes for the mob you have to edit the biome tags.
(/data/scorpions/tags/worldgen/biome/…)
To edit the spawn settings you have to edit the biome_modifier
(/data/scorpions/forge/biome_modifier/…)
Suggested by: gohkenytp
Thanks for downloading this mod!
YDM’s MobHealthBar
### Mob Health Bar Mod
#### Forge, Fabric and Neoforge
This mod adds a health bar above the mob.
There are 13 type of bars available that are positionable.
You can open the selector by pushing the “H” button.
Other changeable options for the bars are:
– Render distance
– scale size
– name display
– health points display (if the selected bar type supports hp display).
– make a bar only appear when the mob is aggressive, damaged or when you hover over it
– texture visibility
– show only damaged mobs
– blacklist mobs in config
– If you use forge then:
(type after blacklist = minecraft:cow,minecraft:pig and like this these mobs will be blacklisted)
– If you use fabric then:
(type after blacklist = cow,pig and like this these mobs will be blacklisted)
Hope you like it.
Please let me know if you find any bugs.
Thanks for downloading this mod!
YDM’s Iceologer
#### YDM’s Iceologer
**For forge, neoforge and fabric**
This mod adds the Iceologer from the 2020 mob vote and an Ice Chunk Block
that is summoned by the Iceologer and you need to mine it with a tool that is enchanted with Silk Touch.
Currently it spawns in:
– Snowy taiga
– Snowy slopes
– Frozen peaks
-Jagged peaks
– Snowy beach
– Snowy plains
– Ice spikes
– Frozen Ocean
– Frozen river
Other mod biome compatibility!
You can set the spawning biomes for the Iceologer.
You can find the config for it in your run folder.
If you want the iceologer to spawn in another mods biome.
You have to change the biome_name line:
For example to:
biome_name = “modid:name_of_the_biome”
To let it spawn in more biomes you have to put a comma (,) between the biome names like this:
biome_name = “modid:name_of_the_biome,minecraft:snowy_plains”
Other options in the config is:
– spawn rate
– minimum number
– maximum number
– Time between Ice Chunk Summon (40 means -> 40 tick, 40 tick = 2 second)
In 1.19 the config for spawn settings was replaced with biome tag and biome modifier json files.
These can be found under the data folder in the jar.
Thanks for downloading this mod!
YDM’s Custom Camera View
### YDM’S Custom Camera View
You can change the position and rotation of the camera when you play in third person.
Or you can just make it stop following you.
Default key binds are:
UP = KEY UP
DOWN = KEY DOWN
LEFT = KEY LEFT
RIGHT = KEY RIGHT
FORWARD = KEY G
BACKWARD = KEY H
STOP CAMERA = KEY B
RESET CAMERA = KEY V
ROTATE JAW PLUS = KEY I
ROTATE JAW MINUS = KEY U
ROTATE PITCH PLUS = KEY K
ROTATE PITCH MINUS = KEY J
You can change these in your key binds option.
YChatManager
# YChatManager
Plugin for chat management, formatting, anti-spam etc. Requires at least **Paper**, won’t work on Spigot or Bukkit.
# Features
### Chat formatting
– Custom chat format with MiniMessage, PlaceholderAPI and Vault.
– Custom displayname format also with MM, PAPI and Vault.
– Per permission colors, formats and MiniMessage 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 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 and MiniMessage
– Commands with tab completions
– API for developers
# Documentation
You can read about plugin’s permissions, placeholders etc. on the 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 or GitHub 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 license.
Yet Another World Protector
# Yet Another World Protector
Yet Another World Protector (YAWP) is _the_ admin tool to protect your minecraft server (dedicated or LAN as well as single-player!). It’s available for (Neo-) Forge and Fabric.
YAWP designed to be used on dedicated servers, but can also be used in single player worlds and worlds opened to LAN.
It allows admins (and players with assigned permission) to protect their creations against various events/actions of
players, mobs and
the environment.
Create regions for your builds and apply region flags to protect them.
Assign players or vanilla teams to regions, so they can manage their own regions.
YAWP was inspired by the forge mod WorldProtector and
the WorldGuard plugin.
Join our discord if you have any questions or suggestions: YAWP Discord
***
| Discord | Paypal | Patreon | Github | Wiki | Issues | Curseforge | Modrinth |
|:—————————————-:|:———————————————————————–:|:—————————————–:|:—————————————————————:|:——————————————————————:|:———————————————————————-:|:—————————————————————:|:—————————————–:|
***
***The mod is currently in its beta state, with many features not yet implemented but to come. These features will
include most of the things you know from WorldProtector and WorldGuard.***
This mod will be released for Minecraft versions 1.16.5+. If you are living in the past and are looking for a version for Minecraft 1.12.2, I suggest looking into using WorldDefender.
Starting with Minecraft **1.20.4**, YAWP will no longer be available for Forge and adapt **NeoForge** instead.
***
In YAWP there are three different kinds of regions to protect your server:
## *The* Global Region
The Global Region is… well global. Flags set in the Global Region, apply to all dimensions of the server and thus all
Local Regions.
## Dimensional Regions
Dimensional Regions are special regions which are tied to one dimension – like gamerule-flags for different dimensions.
Dimensional Regions have no spatial restrictions in the corresponding dimension. Dimensional Regions work like normal
regions, but are tied to a dimension.
They can’t be created manually. They are in fact automatically generated with each new dimension. The first Dimensional
Region for the overworld is created when the server is created.
The following Dimensional Regions are created whenever a player travels to a new dimension, thus creating the new
dimension with their respective Dimensional Region. Modded dimensions are supported as well.
## Local Regions
Local Regions are the regions you most likely now from WorldGuard or WorldProtector. They have a defined area in which
they work in and which they are limited to.
With Local Regions you are able to create areas in your world, which you want to protect from certain actions/events
which are caused by players, other entities or the environment.
To create a Local Regions you will need to have the permission of the parent region or permission from the config.
Local Regions can be created
by marking the area with a RegionMarker and executing the corresponding command or by just using a command without the
RegionMarker.
For now the area of a region can be defined as in a cuboid or spherical shape, but I am planning to add more shapes for
region areas in future updates.
***
## Properties of regions
The properties of regions, flags, groups, etc. can all be managed through
an interactive CLI.
The colored text indicates interactive shortcuts commands or command suggestions. All colored text have a tooltip hint
which explains shortly what clicking on the corresponding link does.
Clicking on them gives the player a suggestion for executing a command or sometimes straight execute the command which
is hinted by the hover text.
Regions can only be managed by their owners, or by players which have the required OP level or have an entry in the
configuration. For more information, visit the wiki.
***
Whenever a new Local Region is created without supplying a parent region, the parent is set to the Dimensional Region
which the new Local Region is created in.
Local Regions can also have child regions. The children of a Local Regions need to be contained in the area of the
parent region. The region hierarchy also defines the region priorities. Child regions always must have a higher priority
than their parent.
Dimensional Regions always have the Global Region as a parent, and thus the Global Region all Dimensional Regions as
child regions.
***
Regions have owners and normal members. Owners are allowed to manage the region and bypass the flags, members are
only allowed to bypass the flags set in the region.
Owners and Members can be individual players or a team.
Groups allow you assign specific region permissions to different players and teams. Currently, there are only two
default groups: **owners** and **members**.
***
– **Owners** can manage their region themselves and add other players/teams to the region. They can also create their
own sub-regions within their region, manage flags, ect. and of course owners bypass flags.
– **Members** are only allowed to bypass flags only.
I am planning on adding a LuckPerms integration with a future
update, so you can define your own groups and permissions.
If you have trouble with setting up regions, visit the discord for help.
***
Flags are the core of the region protection system. They define which actions are allowed or denied in a region. Flags
can be set to
– **Allowed**, to allow the corresponding action,
– **Denied**, to deny the corresponding action,
– **Disabled**, to disable the specific flag for flag checks.
Child regions inherit the flags from their parent regions. It is further possible to override the flag state for child
regions by setting the **override** property of the flag of the parent region accordingly.
See the Flags page for more details about the
different flags.
I am planning to add more flag in the future. A list of suggested flags which I’ll slowly add to the mod can be found
here: Flag suggestions
There will also be more complex flags in the future. Like *ListFlag* which will allow you to define a list of allowed
blocks/entities/.. which are forbidden in the context of a flag.
***
***
The commands of mod are also designed to be used by the server console and can be executed by command blocks.
This allows you to automate region setups, add/remove players, enable or disable regions, etc.
***
YAWP provides a growing mod integration API for easier mod and modpack integration. Currently, the API allows other mods
to listen for events for region creation, changes and deletion and cancel these events to prevent them from happening.
Additionally, there are events for flag checks and their results, which can be used to manipulate the outcome of the
flag check.
***
The client side installation of the mod provides language support (I18n) in form of a resource pack. Currently, english,
german and russian language is supported.
Starting with mod version 0.0.2.9-beta2 and Minecraft Version 1.19.4, YAWP provides a default english translation.
If your language is not yet supported, feel free to reach out to me via discord or issue a pull request via github! 🙂
***
The configuration of the mod allows you to control which is allowed to use the mod, sets default flags for Local and
Dimension Regions, command line interface options, etc.
The configuration is split in different files, covering different topics.
– `yawp-common.toml` – config for command permissions
– `yawp-flags.toml` – config for flags, custom flag messages, etc
– `yawp-region-defaults.toml` – config for default region properties
Since YAWP is a server-side mod, the config for it is found in the directory `/serverconfig` in your minecraft world
directory.
***
The documentation of the mod is small but growing. I am trying to keep up with the content. You can find the
documentation << here >>.
The documentation covers
* descriptions of different regions
* getting started & FAQ
* available commands & flags
* configuration
* and more …
If something is not covered feel free to hop on our discord server and ask your question there. 🙂
___
## Roadmap
There are many more features to come. The mod is in active development!
The following list is not comprehensive.
* Different flag types (List, Effect, …) for more granular control
* Data pack driven flag configuration
* Region boundary visualization
* Define your own region groups for more granular management of regions (LuckPerms)
* More granular permission system (combined with the more granular group features)
* Region templates for easier managing same regions with different spatial properties
* Region triggers for entering/leaving a region (for displaying messages, executing commands, etc)*
* Regions with different shapes (Cylinder, Prism, 3DPolygon)*
*
YetAnotherWhitelistPlugin (YAWL)
# YAWL (Yet Another Whitelist Plugin)
**YAWL** is an incredibly simple, lightweight, and efficient whitelist plugin designed exclusively for the **Velocity** proxy. If you need a no-fuss, easy-to-manage whitelist solution that just works, this is the plugin for you.
## 🚀 Overview
The core philosophy of YAWL is **simplicity**. In a world of complex plugins, YAWL stands out by doing one thing and doing it well. It manages a server whitelist through a plain text file (`whitelist.txt`), making it easy to view, edit, and manage without needing databases or complicated commands. It’s built to be as performant and unobtrusive as possible, ensuring zero impact on your server’s performance.
## ✨ Why Choose YAWL?
* **⚡ Lightweight:** The plugin has a minimal footprint. It’s written to be extremely efficient and won’t add any bloat or lag to your proxy.
* **✏️ Simple Text-Based Management:** All whitelisted players are stored in a simple `whitelist.txt` file. You can edit this file directly and reload the plugin in-game.
* **⚙️ Straightforward Configuration:** A clean `config.toml` file allows you to toggle the whitelist, change message languages, and set case sensitivity with ease.
* **🌍 Multi-Language Support:** YAWL comes with multiple pre-packaged languages (`en`, `ar`, `de`, `es`, `fr`, `ja`, `ru`, `uk`, `zh-cn`, `pt-br`, `tr`). It can even **automatically display messages in a player’s client language**!
* **🔄 Live Reload:** No need to restart your entire proxy. A simple command reloads the configuration and the whitelist instantly.
* **🔒 Permissions-Ready:** Fine-grained permission nodes give you complete control over who can manage the whitelist.
## 📦 Installation
1. Download the latest version of the plugin.
2. Place the downloaded `.jar` file into the `plugins` folder of your Velocity proxy.
3. Start or restart your proxy.
4. The default configuration (`config.toml`), locales, and an empty `whitelist.txt` file will be generated in `plugins/yawl`. Edit them to your liking!
## ⚙️ Configuration
The configuration is handled in the `plugins/yawl/config.toml` file.
“`toml
[settings]
# Enable or disable the whitelist. If false, the plugin will not kick anyone.
enabled = true
# Sets the language for plugin messages.
# Corresponds to a file name in the ‘locales’ folder (e.g., “en”, “ru”).
locale = “en”
# If true and the client has a language set that exists in the plugin’s locales folder, it will be displayed.
# If false, it will display default locale defined by upper setting.
use-client-locale = false
# If true, player names in the whitelist will be case-sensitive (e.g., “Player” is different from “player”).
# If false, case will be ignored (“Player” and “player” are the same).
# It’s recommended to keep this ‘false’ for user-friendliness.
case-sensitive = false
# Kick active player immediately after whitelist removal or expiry.
# If false, the player will remain connected until they reconnect or reload occurs.
kick-active-on-revoke = true
# Placeholder reload interval in minutes
placeholder-reload-interval = 2
“`
## 🆔 Placeholders
Starting with version 1.2, you can use the `%yawl_duration%` placeholder, which contains the amount of time remaining for the player. To use placeholders, you need to install YetAnotherWhitelistCompanion and PlaceholderAPI on your backend server(s).
## 💬 Commands
All commands start with `/yawl`.
| Command | Description |
| ——————————— | ————————————————— |
| `/yawl` | Displays the plugin help message. |
| `/yawl add ` | Adds a player to the whitelist. |
| `/yawl add []` | Adds a player to the whitelist for a specific time. |
| `/yawl extend [] [add|replace]` | Adds time for a specific player. If the white list timer has expired, it will suggest replacing the time based on the actual time or adding to the old time limit. |
| `/yawl remove ` | Removes a player from the whitelist. |
| `/yawl list` | Shows a list of all whitelisted players. |
| `/yawl reload` | Reloads the config and `whitelist.txt`. |
## 🔑 Permissions
Grant these permissions to your staff groups to control who can manage the whitelist.
| Permission | Description |
| ———————- | ————————————————————- |
| `yawl.bypass` | Allows a player to join the server even if not on the whitelist. |
| `yawl.command.add` | Allows using the `/yawl add` command. |
| `yawl.command.extend` | Allows using the `/yawl extend` command. |
| `yawl.command.remove` | Allows using the `/yawl remove` command. |
| `yawl.command.list` | Allows using the `/yawl list` command. |
| `yawl.command.reload` | Allows using the `/yawl reload` command. |
YATPAS
YATPAS is a simple but robust Player-to-Player Teleport (TPA) system for Bukkit/Spigot/Paper servers. It features clickable requests, configurable cooldowns, timeouts, and automatic cancellation upon movement or damage, ensuring a balanced gameplay experience.
***
## 🇮🇹 IMPORTANT NOTE ON LANGUAGE
The default language for the messages inside the plugin’s `config.yml` is **Italian**. You can easily translate all messages to English or any other language by editing the `messages:` section of the configuration file.
***
## ✨ Key Features
* **Clickable Requests:** Players can accept or deny TPA requests with a single click.
* **Correct TPA/TPAHERE Logic:** Supports both teleporting to another player (`/tpa`) and calling a player to your location (`/tpahere`).
* **Warmup:** Configurable time before the actual teleport, which is cancelled if the player moves or takes damage.
* **Cooldown & Timeout:** Limits request spam and ensures requests expire automatically.
* **Customizable Messages:** All messages are fully configurable via `config.yml`.
## 📦 Commands
| Command | Alias | Description | Permission |
| :— | :— | :— | :— |
| `/tpa ` | | Requests to teleport to the specified player. | `yatpas.use.tpa` |
| `/tpahere ` | | Requests the specified player to teleport to you. | `yatpas.use.tpahere` |
| `/tpaccept` | | Accepts the pending TPA request. | `yatpas.use.tpaccept` |
| `/tpdeny` | | Denies the pending TPA request. | `yatpas.use.tpdeny` |
| `/tpacancel` | | Cancels your outgoing TPA request. | `yatpas.use.tpacancel` |
## ⚙️ Configuration
The `config.yml` file allows you to customize every aspect of the TPA system.
| Config Key | Description | Default Value |
| :— | :— | :— |
| `teleport-warmup-seconds` | Time in seconds before the teleport occurs. | `5` |
| `tpa-cooldown-seconds` | Cooldown between sending two TPA requests. | `2` |
| `request-timeout-seconds` | Time before a TPA request expires. | `60` |
| `cancel-on-move` | `true` to cancel warmup if the player moves. | `true` |
| `cancel-on-damage` | `true` to cancel warmup if the player takes damage. | `true` |
| `messages.prefix` | Prefix displayed in all messages. | `&3YATPAS&8» &f` |
—