DropHeads
DropHeads
Let the head hunt begin!
Using quality heads 99% supplied by Minecraft-Heads.com & Nano Team ❤️
Highlights
- Super configurable
- Heads as a loot drop, or with a command
- Huge variety (e.g., snow fox, lime sheep, zombified swamp farmer villager, …)
- Behead messages and translation support
- Regularly updated heads from the latest Minecraft snapshots
- Complete API for other developers to hook into
Configuration
Default values picked to fit well on most servers,
However, if you like getting into configuration, here's just a taste of what you can do:
- Adjust drop rates based on mob type
- Adjust drop rates based on ticks-lived
- Adjust drop rates based on what weapon is used
- Adjust drop rates based on spawn conditions (Breeding, Spawners, /summon, ...)
- Require using specific weapon(s) to get heads to drop
- Enabling charged creeper head drops
- Change any head textures, or add your own
- Optionally require killed by a player (configurable what counts as 'killed by a player')
- Opt-in automatic updates
- ...and more! Check out config files in the GitHub repository
Permissions
For an always update-to-date list, check here.
dropheads.canlosehead: Can drop a head upon death
dropheads.canbehead.<mob_type>: Can get heads from killing the given mob
dropheads.alwaysbehead.<mob_type>: Get heads for 100% of kills (unless canlosehead is false)
dropheads.silentbehead: Avoid triggering a global behead message in chat *
dropheads.canplacehead: Can place a head as a block
dropheads.clickinfo: Can see the name of a head by clicking it *
dropheads.spawn: Can get heads with a command *
dropheads.droprate: Can check head drop rates with a command
* = has sub-permissions
Troubleshooting / F.A.Q.
Q: Heads are not dropping!
A: There a many possible causes; here is a quick checklist of things you should try:
* Check if another plugin is causing the issue (compatibility)
* Check if you have the dropheads.canbehead permission
* Check head-drop-rates and spawn-cause-modifiers configs (e.g. spawn egg rates are nerfed!)
* Keep in mind the time-alive, weapon-used, and looting modifiers.
* If killing a player, check if they have the dropheads.canlosehead permission
* If you have modified your config files, check them carefully for other causes
Q: Does this plugin cause lag?
A: It shouldn't! I hear it is much faster than Xisumavoid's datapack :)
Q: Can I edit the head textures (i.e., to match a resource pack)?
A: Yes! Look in the head-textures.txt file
Q: Migrating from another heads plugin?
A: It should be an easy drag-n-drop replacement, but if you have any issues let me know!
Q: How do I install on Forge/Fabric/Singleplayer?
A: DropHeads currently only works on Bukkit and its forks (Spigot, etc); try the MMH-Nano datapack
Q: Where do I get help / report a bug?
A: You can post a comment below, create a bug report, or DM me :)
Q: Older versions of Minecraft?
A: Currently, DropHeads runs on 1.13+. You can find older DropHead jars for 1.12 in the Files tab, otherwise seek out a plugin with support for legacy versions, such as PlayerHeads.
Planned
- Fabric support
- Improve existing textures
- Tropical Fish heads (have the 22 common ones, still need the 3104 rare varieties ☹️)
- Horse variants (for the different patterns)
- Carpeted llamas
Please reach out if you find bugs or have a texture suggestions!
In reply to EvModder:
In reply to EvModder:
Thanks, just curious, is there any way to change the skulls that drop when using the plugin as i have another plugin installed that requires vanilla wither skulls to be able to craft x item, when i try it with the custom drop skull it dosent work as it has a different lore/id to the vanilla skulls.
In reply to TapToSearch:
Hmm, not sure, I'm surprised it doesn't work, I'll have to take a look at it in a week when I'm back home from travel, in the meantime LMK what the other plugin is and I'll see if I can figure it out. If you're able to get it to work on your own, just let me know what you did so that other people in the future can reference it if they get the same issue.
Hello!
I downloaded the plugin for my server, but for some reason heads drop 100% of the time once I set the canlosehead and canbehead permissions to true. When i do canalwaysbehead, i get the 100% drop rates and when I set it to false What permissions/config settings should I change and to what to get more normal droprates? I've already tried changing weapon and looting values, but to no avail. Thanks!
In reply to fintastica:
There are a few things to check:
1) if you use the JPerms permission plugin, it tends to screw up default settings for server ops (giving you dropheads.alwaysbehead even though it is false. Note it also has sub-perms such as dropheads.alwaysbehead.zombie)
2) be aware that the drop chances in head-drop-rates.txt are from 0.0 - 1.0, not 1 - 100, so avoid setting them higher than 1.
3) When in doubt, the usual best way to debug is to point the cursor at a mob, and before you kill it run /droprate, it will spit out a bunch of useful info that explains pretty much everything affecting the final drop %. It might be helpful to also test with op & non-op player accounts to see if there is a difference, to eliminate the possibility of a "give all ops *, *.*, *.*.*..."-type permission plugin
In reply to EvModder:
Thanks for the help- the droprates are back to normal (supposedly). Though while doublechecking everything was working I noticed that the old problem of nothing dropping at all is back. According to the message I get when runnign /droprate on anything, I get a "you need the canbehead perm" even though I have set it to every single group (I have alwaysbehead on false and canlosehead on true as well.) Our server uses essnetialsX and LuckPerms, do those affect anything?
In reply to fintastica:
Very odd that issue is popping up, I've never had issues reported for either of those plugins and they are pretty well tested, but if you figure it out please let me know (it might be helpful for others as well). I guess I'd recommend using LuckPerms command `/lp user <Name> permission check dropheads.canbehead` (and also for mob sub-perms to verify it is set up properly (I got the command format from the LuckPerms wiki so I assume that's how it's done)
Hey, can I somehow make different custom heads drop from the same mob?
In reply to muurkkk:
Unfortunately this is not currently a feature (except for different mob sub-types, like Red Sheep, Blue Sheep), but it is very easy to add and doesn't complicate anything else, so I might include it in v3.7.10 or as an extra addon :)
The way I plan to set it up, you will go to head-textures.txt and just have the same "key" repeated with multiple texture values, for example:
COW: 7df4f2e7846000b6e7548f86937d3f6af847b1607668ee05e7caf9f6f04c9423
will have a 50/50% chance of dropping either head when a cow is killed.
Hey man. Everything works just fine, but when I destroy a head that's been placed the name will be changed to "dropheads:COW's Head" which is not desired. What can I do?
All I want in the world right now is for the names to always be like when dropped at first ("Cow Head")
Also ditto on the reload config option being nice :)
In reply to MainBaze:
Huh, that is very strange, can you confirm what version of the plugin you are using and DM me your config? (or link it in a comment).
I've never heard anyone else report this issue so there is also a chance it's caused by a conflict of DropHeads with another plugin, in which case if you know of any plugins you use that affect heads DM me that as well so I can try to recreate the issue :)
In reply to MainBaze:
Actually, I should probably explain why I haven't gotten around to a reload config command yet, since it is fairly easy to do; the thing is I just can't decide what the command name should be; the obvious one is just `/dropheads reload`, but then what does just `/dropheads` do? are there other sub-commands? Alternatives like `/dhreload`, which I've seen other plugins do something similar, look kind of ugly or verbose. My favorite would be `/dropheads:reload`, a namespaced command, but then it might conflict with the vanilla `/reload` command. All of this is just minor implementation detail but I get wrapped up in perfection and end up not choosing any due to nitpick dissatisfaction.
The best current alternative to a reload command is if you have any plugin manager that lets you disable/enable plugins, e.g., with `/dp DropHeads` then `/ep DropHeads`, then that will work. I've even seem some that have `/reload <pluginName>` as a command... But I understand that not everyone wants to bother with installing a plugin that's only purpose is calling <otherPlugin>.enable() or .disable() in the server API.
Some permissions plugins or "Essentials" type plugins also offer similar commands, but in all honestly I think Bukkit/Spigot/Paper etc should just expose this API as a command themselves since IMO it is basic useful functionality, and then no plugin author would need to implement a reload command themselves.
(actually, now that I think I might go open it as a feature request on spigot Jira and see what they say lol. Once again, I could easily add the command myself, i'm just being lazy/nitpicky and trying to get to a solution that is more elegant imo)
In reply to EvModder:
Indeed the preferred one would be if /dropheads reload was possible. /dropheads could just show text that tells you what sub commands are available.
Also, I'll DM you :)
Is the drop rate the chances of a head dropping? and what number should that be if i want a mob 100% drop chance?
CHICKEN: 0.001 (thats the number its currently on)
If i install the plugin into my server, and i only changed ''must use axe true''. shouldnt it work immediatly?
I mostly want mob heads for my players on the server. As an OP i get the heads but not the players.
In reply to stefthepirate91:
You can set it to 1 for 100% (it is on a scale from 0.0 to 1.0).
If heads still aren't dropping 100% of the time I suggest clearing the contents of spawn-cause-modifiers.txt on your server, since that file can nerf drop rates e.g., for mobs spawned with commands or plugins. A good tool for debugging it can also be to do /droprate while looking at a mob, the plugin will spit out some information for anything/everything that might affect the drop rate.
There is a plugin that can rollback or restore any amount of damage.
https://www.spigotmc.org/resources/coreprotect.8631/
However, the plugin cannot restore the placed head that is damaged. The head will become Steve or Alex.
Is it possible that Dropheads can work well with Core Protect so the damaged head can be restored properly?
And there is a plugin called Mythicmobs.
https://www.spigotmc.org/resources/⚔-mythicmobs-free-version
It can create custom mobs.
Is it possible that Dropheads supports Mythicmobs so that the custom mobs can drop different kind of heads?
In reply to siulung201314:
Regarding CoreProtect, the owner has an issue here to eventually add support for custom heads, I'll contact them and see if they want some help doing it.
For Mythicmobs, I am not sure how easy it would be to do, since I think it will try and use the head of the underlying mob type which Mythicmobs is using, but perhaps if the Mythicmobs mob is wearing a custom head in the skin there would be a good way to do it as an addon, I'll look into it
i put this on true, i have a Paper server
# Only drop heads if the killer used an axe; overrides 'must-use'
must-use-axe: true
but still people can use swords to get the drophead.
,
Does EV Modder has an Discord for questions?
Thank you!
In reply to stefthepirate91:
Do the player have 'dropheads.alwaysbehead' permission? I think that permission overrides the 'must-use-axe: true' setting.
Otherwise, I would recommend restarting/reloading the server so the plugin can load the config changes in case you didn't try that already.
BTW my Discord account is EvModder#0001, you can message me if you like or PM me on this site, i don't have a user support server at the moment.
If there is a bug with this setting I can look into it some more, but it seemed to work for me when I tried it just now
Hello. I'm new, and trying to figure out some things.
I see that the latest version supports 1.19.1. My server is 1.19.2.
Will the plugin work properly on my server?
In reply to imjustbenben:
It works well in 1.19.2.