I always know that you will back to this plugin !
Very great no more words, easy setup (if you read the notes )
Full customizable - how many hearts , which command after ban (can use custom command from litebans example)
Lot of placeholders
MySQL database for saving data
full control for admins
easy command usage
#created with passion
#olios back to coding
#olios developer nigdy nie umrze
#pozdrawiam leos franek kacper i inni

p.s meaby update notifier with the translatable text? ;D
and meaby /hm about for send info about plugin for example
database: sqlite/mysql
version of plugin
ban mode:
hearts amount:
etc.
more priv xd

This plugin works exactly as intended. After a player dies, they get banned for the configured amount of time. It’s perfect for hardcore servers where death should have real consequences.
The configuration is simple and flexible.
I really hope the developer decides to resume the project and add more features in the future — for example, custom ban reasons, per-world settings, or integration with other plugins.
It also needs an update to stay compatible with the latest versions.
Highly recommended, but it has great potential for even more improvements!

Messed up my death message after removal. Don't even know what to do at this point.

Cool plugin but half the options in the config file don't work for me.
For example i cannot seem to turn off lives, cannot turn on admin bans etc...

Good plugin but fix the images in the page. Dont understand people who leave 1 star
Coś muszę dopisać elo wampir

i dont think u understannd what i meant to say ban are good but why there is a zero also it should be one lives after then ban it should not go to zero cause player think he have 4 lives like 4 3 2 1 but there are actually 5 lives 4 3 2 1 0 this is what i meant to say!

it is so much good but only problem i think it has liuke lives are 5 4 3 2 1 then there is also a 0 if it is like 1 then ban it would be so good to have upgraded by the way thanks creator of this plugin u did an awesome job but like i said 0 problem

I installed this plugin, decided I didn't want to use it, and uninstalled it. The players who joined while the plugin was installed now have a permanent prefix in front of their names.

Very nice plugin :) .

Nice plugin! thanks for the fast support on discord now the plugin works perfectly.

For there to be extra difficulty, more reason for survival and more fun is perfect.

Please add an unban or revive command. as for now one of the players testing the plugin could not get back in even after I gave him lives.

Very Good Plugin and Worked like it should. :D

And ofcurse an very friendly and fast Developer. :)

Plugin works as described, but there is no way to configure the ban command. Running a Waterfall server, this customization would be ideal, as then players could still rejoin other servers on the network after being banned on the server with this plugin installed.

the plugin is amazing i love how smooth it is and how it works so well with other plugins without issue and it fits in perfectly into my server gameplay style

Great Plugin, Nice work "german translation" would be nice in the future. :::: THX ::::

Really wonderful plugin for different implementations. The developer responds and updates the plugin almost daily, if not for him, I had to pay money for it!

Thank you very much ;)

This is a dream plugin for me and I was very happy to discover it this week. I like increasing the difficulty of survival worlds and this an important plugin to get players into a true survival mindset.

The author appears to have put in a lot of care into the plugin. They've gone as far to give us the ability to configure messaging around the deaths and bans.

This worked as-is with no configuration on my 1.19.2 multiplayer server. Navigating the config.yml was very easy as the author left us quite a lot of documentation.

An easy 5 stars from me.

Hi man, I really like the plugin. Would it be possible to add the death message e.g. "You hit the ground too hard" / "You were killed by a Zombie" to the Ban / Kick reason. The way it is right now a player dies and is banned before being able to read the death message in chat. So maybe adding a new variable for the cause of death (in the ban-reason config block) would be really cool.

Sincerely I won't be using this plugin, but I think it's a cool idea and rating 1 star just because someone don't know where to ask for support isn't fair. There you go Olios, good work on your plugin

I can activate de plugin, this is the plugman log:

[13:45:40 WARN]: org.bukkit.plugin.InvalidPluginException: Unsupported API version 1.18
[13:45:40 WARN]: at org.bukkit.craftbukkit.v1_16_R3.util.CraftMagicNumbers.checkSupported(CraftMagicNumbers.java:361)
[13:45:40 WARN]: at org.bukkit.plugin.java.JavaPluginLoader.loadPlugin(JavaPluginLoader.java:149)
[13:45:40 WARN]: at org.bukkit.plugin.SimplePluginManager.loadPlugin(SimplePluginManager.java:414)
[13:45:40 WARN]: at com.rylinaux.plugman.util.PluginUtil.load(PluginUtil.java:299)
[13:45:40 WARN]: at com.rylinaux.plugman.command.LoadCommand.execute(LoadCommand.java:120)
[13:45:40 WARN]: at com.rylinaux.plugman.PlugManCommandHandler.onCommand(PlugManCommandHandler.java:95)
[13:45:40 WARN]: at org.bukkit.command.PluginCommand.execute(PluginCommand.java:45)
[13:45:40 WARN]: at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:159)
[13:45:40 WARN]: at org.bukkit.craftbukkit.v1_16_R3.CraftServer.dispatchCommand(CraftServer.java:826)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.PlayerConnection.handleCommand(PlayerConnection.java:2185)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.PlayerConnection.c(PlayerConnection.java:2000)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.PlayerConnection.a(PlayerConnection.java:1953)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.PacketPlayInChat.a(PacketPlayInChat.java:49)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.PacketPlayInChat.a(PacketPlayInChat.java:7)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.PlayerConnectionUtils.lambda$ensureMainThread$1(PlayerConnectionUtils.java:35)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.TickTask.run(SourceFile:18)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.executeTask(IAsyncTaskHandler.java:136)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.IAsyncTaskHandlerReentrant.executeTask(SourceFile:23)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.executeNext(IAsyncTaskHandler.java:109)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.MinecraftServer.bb(MinecraftServer.java:1271)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.MinecraftServer.executeNext(MinecraftServer.java:1264)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.IAsyncTaskHandler.awaitTasks(IAsyncTaskHandler.java:119)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.MinecraftServer.sleepForTick(MinecraftServer.java:1225)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.MinecraftServer.w(MinecraftServer.java:1139)
[13:45:40 WARN]: at net.minecraft.server.v1_16_R3.MinecraftServer.lambda$a$0(MinecraftServer.java:291)
[13:45:40 WARN]: at java.lang.Thread.run(Thread.java:748)