DeathCraft 2
DeathCraft
DeathCraft is a plugin to make dying fun!
Not really. Dying always sucks - But DeathCraft will make it more fun for everyone else.
Features
- Unlimited, customized death messages for every type of death, or per item!
- Differentiates between PVE and PVP deaths!
- Option to use true account names, or display names (/nick, etc)
- Player optional ignoring of either type of death (PVE or PVP) messages
- Head drops! Fully configurable drops of player and mob heads!
- Permission based configurable 'Death Chests' that will store items upon an untimely demise - or be the prize of the PVP victor!
- /kill and /suicide, as well as the option to override these commands from other plugins to continue the DC Experience
- Permission based configurable 'Keep Xp on death
Installation
- 1) Download
- 2) Put deathcraft.jar in your /plugins folder
- 3) /reload your server, or restart.
- 4) ???
- 5) DEATH!
Known Conflicts
- CreeperHeal You must disable chests in one of the two plugins, or you will end with a looping chest creation.
Commands, Configuration & Permissions
Please see the new Commands, Configuration & Permissions Page!
Bug Reporting and Suggestions
If you find a bug, or have a suggestion, PLEASE open a ticket! I can't fix what I don't know is broken, and I can't add what I don't know is wanted. :)
ToDo
- Togglable allowance of locked chests for popular protection plugins (LWC, Locket)
- Allow Keep item on death permissions, completely bypassing Chests
Tutorials
Portuguese:
@rustyshakelford2
That's all part of the localization update that is pending review/approval (1.10.2). Once it is approved, you will be able to change many of the internal messages, including that one.
I just switched my server to this plugin to replace our horribly outdated deathtpplus. So far i'm really liking it, excellent work. Is it possible to disable or edit the message that says "You may use a compass and /dc2 find to point to this location!"?
Thanks for the quick update. I'll test it out and see how things go.
@Liger_XT5
Wow ... the file that I just uploaded was already approved ... See if DC v1.10.1 fixes your problem. I don't use Towny, but it works with GriefPrevention + WG (Granted, the last version did too ... so hey.)
@Liger_XT5
I'll take a look at this ASAP. Leave any additional info you have in the ticket that was created - Thanks
I'm sure I'm overlooking something.
I was recently notified that players have been able to break Skulls in WG and Towny. Though this was strange, I checked both plugin's configs and didn't see anything that showed sign relating to heads.
I decided to disable one plugin at a time, and nailed Deathcraft 1.10. As soon as it was unloaded, no one could bread heads inside of WG or Towny.
@Onewingseraphim
That's not fixing the problem, however, only avoiding it (as well as any new features added). When I get the debug info, I can help further. I can't do anything by just guessing.
@raum
Well I just went ahead and downgraded back to 1.9.6 works perfectly now.
@Onewingseraphim
Again, the only thing that changed with chests was verification that the player is able to build in the area based on a number of things. Turn on the debug mode and use checkchest. It will tell why they aren't dropping. Without knowing the reason it's being denied, there's little I can do.
Doing /dc2 checkchest always shows false for all players without OP. It didn't do this before so something else must've changed, It shows false anywhere in the world in any world.
@Onewingseraphim
No permissions changed at all for death chests - the only thing that was added regarding chests at all was verification that the person is able to build in that location.
Use the command "/dc2 checkchest" to see if a chest will drop in that location. You can verify what is causing a chest to not drop by turning the Debug setting to true ("/dc2 set debug true") and check the logs when a chest should spawn. Disclaimer: Debug mode will print a lot of information in your logs.
For some reason the permissions are messed up non-op players can't get death chests although it worked in ver. 1.9.6 just fine.
@raum
That sounds good doc. I really like your plugin, so i'm looking forward to that new release :-)
@ThisUsernameIsMine
Odd - the plugin writes the config on the first use - it doesn't actually use a default file like some plugins .. I'll have to see why it would have done that.
On a side note, the next version I completely rewrote how messages are handled, and they use the exact names of damages ... I dunno what I was thinking to not do it this way to start. All messages will convert over automatically.
I will also add some error checking to hopefully prevent re-writes of an invalid file. Sure, the messages will all derp out until it's fixed, but that's likely better than having the messages file rewrite on every mistake.
@raum
I see :-)
I noticed you forgot to enclose the FireballMob message within single quotes.
I tried to change the message (added color codes and such), saved the changes and after reloading the plugin it resetted the file back to its orignal state.
@DerekZil
There's no official rabbit or guardian heads at this time.
Can you block just PVE or PVP what?
@ThisUsernameIsMine
I've been coding for about two decades. All changing a language is about is learning the syntax, for the most part.
@raum
Add rabbit heads, and can we choose to block just PvE or PvP not both?
@raum
Well, you're right. I'll check the new build asap. Thnx! :-)
(btw, how long did it took to learn to code/develop in/for Java?)
@ThisUsernameIsMine
Make any feature requests as a ticket - that way it doesn't get lost in comment spam.
@lucasbuck2
I have not yet added any features regarding regions - although in another plugin I have, and it's much easier than I expected ... it could be added fairly easily to DC2.
@z65703071
The mob's name would be the killer, which is %2. A new version (that has not yet been uploaded - working on some more features) allows for custom names for modded servers and named mobs.
could you make a variable to show the display name of the mob.