## You Died
This mod adds a Dark Souls inspired death screen.
#### Bugs/Ideas/Requests?
Post bugs/ideas/requests on my Github issue tracker.
#### Modpacks?
You are free to use this mod in modpacks.
Whenever you die you lose a heart, if you lose all of them you will be forced to go into spectator mode. This is similar to normal hardcore in Minecraft but somewhat forgiving.
Limit the maximum amount of hearts with /gamerule maxHearts (by default set to 20 hearts) and whether players can even get hearts with /gamerule canRestoreHearts true/false (by default set to true)
You can replenish hearts by eating enchanted golden apples. This gives enchanted golden apples actual use outside of pvp.
This is originally for modpack [AnimateCraft: Lankeren](https://modrinth.com/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!](https://modrinth.com/mod/you-thief-remastered-edition)***. 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主页](https://space.bilibili.com/190900020)，也欢迎在简介艾特我，我很想看你们的视频！**
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.
Now you will always be greeted in the morning by the beautiful face of LeBron James.
replaces the sun texture with the “you are my sunshine” meme.
# 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](https://modrinth.com/mod/yosbr) by *shedaniel*
1. Changes the scale of hunger and hearts (does not work on hardcore)
2. Changes the golden apple and carrot
3. Changes the trident
4. Items with the name:
– flint and steel – lighter
– shears – pruner
– totem of undying – yortev
– netherite and diamond sword – divider
– netherite and diamond axe – chopper
– netherite and diamond pickaxe – crusher
– netherite and diamond shovel – breaker
– netherite and diamond hoe – braid
OptiFine required!
( Rename Any sword to “Yoriichi katana” to use it. )
For support, download this resource pack from my website:
[yoriichi_katana.zip](https://mineanimecreations.com/resource-pack/yoriichi_katana.zip)
Discord server: discord.gg/z86yJcAZKc.
Also check out my other packs: https://modrinth.com/user/MineAnimeCreations
Resource pack makes it possible to replace any sword with a Yoriichi katana from the anime Demon Slayer by renaming
# 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](https://github.com/yoonaipro/Yoo-Announce/issues).
* Provide as much detail as possible (Minecraft version, plugin version, error messages).
# YonKaGor of Undying
This resourcepack adds YonKaGor Totems (SeaDrive and Tetra).
Simply rename any Totem of Undying to **”SeaDrive”** or **”Tetra”**.
**Requires CIT Resewn (on 1.21.4 and earlier). Also works(should) on OptFine.**
## Credits
Resources for this resourcepack is taken from [YonKaGor YouTube](https://www.youtube.com/@YonKaGor).
[](https://modrinth.com/mod/cit-resewn)
[](https://modrinth.com/project/yonkagor-of-undying/gallery)
# Yolo – A hardcore plugin
—
[](https://discord.gg/zMqkeRseME)
[](https://github.com/eingruenesbeb/Yolo/releases/)
[](https://jitpack.io/#eingruenesbeb/Yolo/v0.5.0)
[](https://github.com/eingruenesbeb/Yolo/blob/master/COPYING)
—
## Content
1. [What does this plugin do?](#1-what-does-this-plugin-do)
2. [Configuration](#2-configuration)
1. [`config.yml`](#21-configyml)
2. [`chat_messages.properties`](#22-chatmessagesproperties)
3. [`discord/[…].json`](#23-discordjson)
4. [`ban_message.txt`](#24-banmessagetxt)
5. [Text replacements](#25-text-replacements)
3. [Permissions](#3-permissions)
4. [Commands](#4-commands)
5. [Further considerations](#5-further-considerations)
6. [Planned features](#6-planned-features)
7. [For developers](#7-for-developers)
—
## 1. What does this plugin do?
You only live once… the name says it all.
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:
“`yaml
spicord:
send: false
message_channel_id: “”
“`
– `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:
“`yaml
announce:
death:
discord: false
chat: true
totem:
discord: false
chat: true
revive:
discord: false
chat: true
“`
This should be pretty self-explanatory.
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:
“`json
{
“embed”: {
“title”: “%player_name% has died!”,
“description”: “Press “F” to pay respect.”,
“color”: 16521991,
“author”: {
“name”: “author name”,
“url”: “https://discordapp.com”,
“icon_url”: “https://cdn.modrinth.com/data/ExWUwvY3/a8ab710896279f5c3ed9c377d408a10587f5509d.png”
},
“image”: {
“url”: “https://media.tenor.com/bMbIAroA0PkAAAAi/rip-rest.gif”
}
}
}
“`
### 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]
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*