Hard Core Worlds
Hard Core Worlds
Description
This plugin brings something like Hardcore mode to select worlds on your server. Single player Hardcore mode is simulated by these things: Hunger will eventually kill you. Mob Damage is adjusted (by default) to hard difficulty damage, but this is customizable. You/others are banned from chosen worlds after dying in them.
Features
- Optional Server Lives you must have the appropriate permissions if you wish to be banned from the server
- Optional Lives
- Hunger can now bring you down to 0 health (via virtual hunger)
- Mob damage is changed for selected worlds. By default set to the hard difficulty, (Skeletons do 3 hearts, Zombies 3.5 etc.)
- Custom difficulties
- Hardcore worlds ban players upon death
- Can use permissions to ignore bans
- Permissions regulated commands to control banning
Usage
Ban.yml explanation
Mob Difficulty.yml explanation
config.yml explanation
Command List explanation
Permissions explanation
Todo:
Any suggestions?
Known bugs:
none
Unknown bugs:
- Let me know
If you feel compelled for some reason, to give me money, here is the link :)
Can you update for 1.3.2 please ? :)
@Dexter15
I reproduced the crushing bug. I have my server lives set to -1 (as the config comment tries to reference). When I die, my "Lives Remaining" is recorded as 0 in the ban file. I am then spawned in the safe world and immediately crushed to death. I then respawn in the safe world just fine. When I removed my ban from the hardcore world, rejoined (with my lives at zero or below in the ban file) and then died, I was placed in the safe world just fine.
Also, I tested the "Next World:" option and it still doesn't work. I am still taken straight to the safe world when I die in the first hardcore world.
-Dex
@Cayviel
I've been absent most all of this month due to work. As a result I didn't notice that you marked my feature request as fixed. I hope to test it next week when work lets up some.
I did want to add my observations to Xanwryn's problem now, though my information could be outdated. I haven't played in a while, as stated above, but when I did I had the same problem. After being banned from a world and spawning in the "safe" world, the screen would almost immediately go black (like I was inside a block) and I would start taking damage. I would die this way and then respawn nearby in the "safe" world again without problem. Through the use of some client mods that tracked my death locations, I learned that I was being spawned in the safe world and then moved 10 blocks down, causing me to be stuck in the stone or dirt there and die. The second spawn worked just fine. I run no position/spawn modification mods.
-Dex
I'm about to test this out; I expect it will go swimmingly. :) I'll report back my experiences.
@Xanwryn
Are they being crushed by blocks because they spawn inside of them? Do you use any plugins that modify the spawn location?
Not sure if this is intentional or not but when players on my server die they are expelled from the server with the standard ban message the plugin states and upon reconnecting they get squished by blocks to prevent them from spawning.
However, after dying a second time from being crushed they are able to respawn and interact with the world normally (though using teleport commands apparently "bans" them again).
All bugs and compatibilities have been fixed as of v1.5.0a according to my testing, so all the current tickets have been marked fixed. If any problems persist please make a new ticket
@MelonCraftServer I am really glad to hear this. Thanks @MelonCraftServer!
This is the ONLY plugin that i found that allowed me to integrate hardcore with the rest of my server (factions, creative, pvp, CTF hungergames, zombies, etc). Thanks! This was really a life saver.
@Cayviel
Cool. One other request (if you deem appropriate). Can you make hunger configurable (maybe a true/false if you want virtual hunger). At least for me, I mainly use your plugin because I want a "working" ban on death for a specific time. Which it works great for. I have mob difficulty set to normal as you show. Server difficulty is easy. For now I have recompiled your plugin and just removed the virtual hunger part. I understand my use of your plugin may not be the normal case though.
I tried a few things in the code for the Grief Protection plugin to try to see if I could get it to register the quit on pvp death with your plugin but the "easy" hacks didn't work. I tried besides setting health to 0, setting player damage to 1000 also.
So any testing or anything I can do to help, let me know.
@hillsoftware
This conflict sounds fixable after a bit of work. I'm still away from home, so no programming for me quite yet. But I am going home tonight so it won't be too long. I have no idea of what you could do to fix it, as a server owner, but I think a few tweaks (of an indeterminate difficulty and size) in the code could do the trick. So I made a ticket out of your problem. Track the progress of this bug by watching the ticket. I'm glad you like the plugin
Hi love your plugin. I was trying all kinds of plugins to do a ban on death and most didn't work well with the latest minecraft, or they conflicted with the Grief Protection plugin. I am just using your plugin for a ban from our server on death. Only using the one main world, but it is working very well.
The only issue I am having, and I hope you might have some ideas (or anyone), is that we use the plugin "Grief Prevention" which is a nice lightweight antigriefing plugin. It has a nice feature to kill someone and make them drop their stuff if they are fighting and then they quit to save themselves from dying.
Problem is that event is the only one that doesn't seem to register as a kill with your plugin.
The Grief Prevention basically looks for a Quit Message from the player when they are in combat. If they try quitting during combat, it sets their health to zero. Even though they exit the game their stuff drops, and it says they died on the server. On the quitting players side, once they log back in they get the "you have died" message but when they restart, they are back at spawn. For some reason hard core worlds is not seeing that one as a death.
Any thoughts on how to get around this?
Cool. Thanks. I didn't realize this wasn't a feature; I thought I was just doing something wrong. It makes sense now though. Thanks for turning it into a ticket for me. -Dex
@Dexter15
This is not currently supported, I could work it into a future update though. I'll make it into a ticket
Can I set up a failure chain for the worlds? For example, hardcore_world_1 might have "very hard" mobs. If a player dies there, I want them to go to hardcore_world_2 where the mobs are only "hard". If they die there, they go to hardcore_world_3 with normal mobs. Die there, then finally you go to the unbannable world. -Dex
@handicraftsman
All time is in hours.
@ Cayviel
Is the ban duration in sec, min or h ?
Need any help with coding things? I would like to help out.
@elcapitaine1
fixed as of v1.4.5
I can replicate it, I'm getting the same issue.
The hardcore world is simply named 'hardcore' I'm standing in a world named 'world'
/hcw unban playername hardcore
I get: Player playername is already not banned in world world
One other thing I wanted to ask as a feature request - a way to link lives between worlds. For example, I've got three worlds - hardcore, hardcore_nether, hardcore_the_end. What would be nice is a way to set it so you have only one life for all three worlds, so if you die on any of them you are banned from all of them for the ban duration. Basically, a way to group worlds for the purposes of hcw
Can anybody else replicate Alexr2311's problem?