**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](https://github.com/yoonaipro/Yoo-Announce/issues).
* 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](https://drive.google.com/file/d/1UWoiOGFlt2QIyQPVKAv5flLTNeNiI439/view?usp=share_link).*)
## 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](https://emn178.github.io/online-tools/sha1_checksum.html) 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](https://support.discord.com/hc/en-us/articles/206346498-Where-can-I-find-my-User-Server-Message-ID-)
(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](https://docs.advntr.dev/minimessage/format.html).
### 2.3 `discord/[…].json`
In these files, you can customize the embeds, sent by the plugin.
You can use [this tool](https://leovoel.github.io/embed-visualizer/) 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](https://bukkit.fandom.com/wiki/Permissions.yml). *(I’d recommend using a permission manager like
[LuckPerms](https://luckperms.net/) 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](https://github.com/eingruenesbeb/Yolo/issues/new/choose), 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](https://github.com/eingruenesbeb/Yolo/issues/new/choose)!
## 7. For developers
To add this project as a dependency for yours, follow [this link](https://jitpack.io/#eingruenesbeb/Yolo) 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](https://eingruenesbeb.github.io/Yolo/).
—
*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.
# YGenerators
Custom generators with custom durability, recipe, item and more.
# Features
### Generators with customizable:
– durability (can be infinite)
– items with lore and display name
– chances for generated blocks
– cooldown of block generation
– recipe of generator item
– interactions for picking up and information checking
### Double drop:
– a timed event that multiplies chances for better blocks
– slows down the wear of generator’s durability
– with custom multiplayer
– can be enabled / disabled per generator
– time set / add / remove with a command
### Other:
– option to change blocks that are generated by vanilla generators
– option to enable 1.16 ores drop instead of 1.17 raw ores
– fully customizable messages with a 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/YGenerators/wiki/4.-Developer-API) for developers
# Documentation
You can read about plugin’s [permissions](https://github.com/Ynfuien/YGenerators/wiki/2.-Permissions), [placeholders](https://github.com/Ynfuien/YGenerators/wiki/3.-Placeholders) etc. on the [wiki](https://github.com/Ynfuien/YGenerators/wiki) page.
# Media – Example generators
#### Items
#### Crafting
#### Checking durability
#### Picking up generator
#### Example infinite generator with 0 tick cooldown
# 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/YGenerators) 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/YGenerators/blob/main/LICENSE) license.
Yeth’s TPA
**Yeth’s TPA is a Teletransportation Accept mod for Minecraft designed to be compatible, stable, and sufficient.**
## Commands
– **/tpa ** Sends a TPA request to a user
– **/tpa accept ** Accepts a TPA request from a user
– **/tpa here** Sends a TPA Here request to a user
– **/tpa cancel** Cancels an outgoing TPA request
– **/tpa ignore ** Ignores a player from making TPA requests
– **/tpa help** Sends a list of all commands
– **/tpa disable** Disables TPA requests from being sent to you
– **/tpa enable** Enables TPA requests to be sent to you
– **/tpa setting ** Configures settings in TPA
## Features
– Automatic expiry of TPA requests
– TP delay w/ countdown
– Multiple request handling
– Permissions for server owners
– Anti-TPA-traps
## Support
Yeth’s TPA supports the following mod loaders:
– Fabric
– Neoforge
– Forge
– Quilt
– Legacy Fabric
– Babric
– Ornithe
– BTA
– LiteLoader
For Minecraft versions 1.7.2 – 26.1.2
Yet Another RTP
Yes, it’s yet *another* RTP plugin. However this time, it’s focused on performance! (And customizability)
This plugin will, on command, teleport a player to a completely random location in a set area, world, and at least x blocks away. While this plugin may not be the best at showmanship, it’s purpose is to excel at pure performance.
If you have a problem or suggestion for the plugin, make sure to check out the GitHub!
### Commands:
/rtp
– Permission: rtp.runcmd **Only needed if `require-perm:` is set to true in the config**
– The main RTP command. Teleports whoever ran the command to a random location
/addused
– Permission: rtp.add
– Makes the plugin act as if said player has already ran the command (Useful if `one-use` is set to true in the config)
/removeused
– Permission: rtp.remove
– Makes the plugin act as if said player hasn’t ran the command (Useful if `one-use` is set to true in the config)
### Misc Permissions:
rtp.exempt
– People with this permission can use the command without a time limit between uses
### Default Config:
“`version: 2
settings:
one-use: false
# Makes the command one use only
require-perm: false
# Makes the command require a permission
max-dist: 5000
# Max distance away from specified location. 5000 = -5000 to 5000 in x and z
min-dist: 100
# Min distance away from the center of the RTP teleport range
pointx: 0
pointz: 0
# The center of the RTP teleport range. X and Z coords
world-dest: world
# The specified world to teleport to
cooldown: 60
# Amount of seconds to wait before player can use the command again
bstats: true
messages:
# All messages use MiniMessage format. See here: https://docs.advntr.dev/minimessage/
run-rtp: Beginning RTP.
# Message to send when RTP command is ran
after-rtp:
# Message to send after RTP command is ran
no-perm: You don’t have permission to run this command.
# Message to send when lacking permission to run RTP command
used-once: You’ve already used this command once
# Message to send when command has already been used
invalid-player: Invalid player specified
# Message to send when an invalid player is specified for a command
YeeeesMOTD
Customized server motd and random icon, it can use player’s head as server icon,like this:
# 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.
### 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.