( Rename Any sword to “Yoriichi katana” to use it. )
For support, download this resource pack from my website:
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
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).
YonKaGor of Undying
# 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.
**Yeetoxic’s Optimized Minecraft** is a modpack created by Protoxon, then adapted by me (Yeetoxic).
This modpack is basically just my own personal version of the Optifine mod. It ain’t the best thing in the world, but I tried my best to make this pack a balanced experience between optimization & quality of life!
If you would like to recommend any features and/or issues with this modpack, feel free to contact me on my Discord server! (linked on this Modrinth page)
**Features** ——————————————————
This modpack includes a couple of new mods that improve small quality-of-life tidbits. This includes Essential, which adds a friend menu & local world multiplayer along with a few other things, and Worldedit, which improves building in-game tenfold, you’ll be able to easily paste, fill, and create structures limiting building to your imagination.
There are also a few other Mods such as SoundPhysics, a mod that changes how you listen to the game, NoChatReports, a mod to stop chat reporting and censorship in-game, & much more!
This modpack also comes with a few resourcepacks that’ll make the game look better while keeping the vanilla style.
**Special Thanks** ————————————————-
Protoxon – Originally created this modpack & continues to provide support for its backend!
Arkktik – Major Bug testing & helped me get this modpack out publicly!
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 ↓ ###
“`
It doesn’t alter the “appearance” of any block—at a glance, it’s the classic Minecraft you know. Instead, it changes the “soul” of the blocks, teaching them to interact with light and the environment.
– **PBR**:是PBR!我加入了PBR!阳光下的铁块会反射出刺眼的金属光泽,羊毛是柔和哑光的。冰块不再是单纯的蓝色方块,它现在能清晰地倒映出周围的景物,如同玻璃一般。
**PBR**:Metals are authentically shiny, wool is naturally matte, and ice feature mirror-like reflections.
**Normal & Parallax Mapping**:Surfaces gain real depth and a tangible 3D structure, moving beyond flat textures.
**Porosity**:Materials react intelligently to moisture—wood darkens as it absorbs water, while metal and stone form surface puddles.
– **次表面散射**:它让树脂、雪块在背光时,能像真实世界一样透出柔和的光线。
–
**Subsurface Scattering**:Light softly glows through translucent blocks like resin and snow, simulating realistic light penetration.
## 为什么我的效果没有上面的截图好?
## Why doesn’t my game look as good as the screenshots?
首先,检查你的光影是否支持**视差**和**labPBR**
First, check if your shader pack supports **Parallax** and **labPBR**.
其次,确保光影的视差和labPBR是开着的
Next, make sure these features are actually enabled in your shader settings.
然后,如果你的光影有以下功能,请按照下面设置:
Finally, if your shaders have the following options, please configure them accordingly:
– 将PBR格式改为**labPBR**
– Change the PBR format to **labPBR**.
– 关闭所有光影里关于**硬编码**的设置
– Disable all **Hardcoding** options within the shaders.
– 关闭**由视差生成法线**
– Disable **Normals by Parallax**.
– 打开**次表面散射**
– Enable **Subsurface Scattering**.
– 打开**平滑视差**
– Enable **Smooth Parallax**.
– 打开**孔隙率**
– Enable **Porosity**.
– 打开**屏幕空间追踪**或是**全局光线追踪**
– Enable **Screen Space Reflections** or **Global Illumination / Ray Tracing**.
– 打开**labPBR自发光**
– Enable **labPBR Emissive Textures**.
# Overview
Foxes will ocasionally go “YIPPEE” when it’s idle.
# Discord
Discord
You’re in Grave Danger
# You’re in Grave Danger
Get it?
## About
You’re in Grave Danger is a highly configurable grave mod.
This mod will add graves to your game, which will spawn at your death location with all your items. You can then go back and retrieve your lost items. The mod will remember your inventory layout and put everything back to where it was before you died. The mod is highly configurable. In fact, if you think a config is missing that has anything to do with what happens when you die, it’s not refered to as a missing feature, but a bug. (Not really but that’s how serious I am about everything being configurable).
If you play multiplayer you’ll have no trouble finding which grave is yours, as both your face and player name will render on it (if you’ve enabled it in the config of course)
## Features
The mod is available for 1.16.5, 1.17.1, and 1.18!
As 1.18 is the newest version of minecraft, 1.18 will be the version most updates are pushed to. This is why you will often find more features in this version than the other versions. However once in a while the 1.16.5 and 1.17.1 will be backported from the newest version. Any issues found with earlier versions will also be handled.
The mod aims to be compatible with most, if not all inventory mods. Currently You’re in Grave Danger provides compat for: inventorio [all versions], trinkets [all versions], curios [1.16], travelers backpack [1.16, 1.17]
Other inventory mods are also compatible with this mod, including backslot, extra inventory and BigInv. The mod will also work with infinitory, however that compatibility is not well tested. If any of the listed mods would not be compatible, or you know another mod affecting the inventory, please open an issue in the mod github repository, or report it in the discord server.
The mod is technically compatible with every soulbound enchantment, since you can configure which enchantments should not be dropped on death in your grave, and which you should as well keep in your inventory when you respawn.
Graves can be waterlogged, and renders can be adapted to the block the grave is standing on.
Graves can be completely customized with resource packs in all versions. They will affect block hitbox, render parts, the grave skull and grave text.
More features are also provided, however some of these are disabled by default as most people probably don’t want these issues as a part of the mod.
## Misc info
If you find any bug/missing config, or have a cool idea that would fit in the theme of the mod, please open an issue on the github issue tracker
The mod is under MIT license, so feel free to use this in your modpack!
This mod is required both on client and server, as it will add custom blocks and renderers.
Want more info about how to configure the mod for modpacks and servers or similar? Visit the github wiki