SavageDeathCompass
Description:
This plugin was created as an alternative to the /back on death command. With DeathCompass enabled, a player is given a compass when they respawn after death. This compass points to their last death location in that world, so they can find their dropped loot. It also works well alongside various death chest and graveyard plugins.
Features:
- Customizable item name, supports color codes
- Customizable item lore with color codes
- Customizable messages with variable substitution
- Option to disable messages individually
- Localization files for messages, item name and lore. default is English, with Spanish and German examples included. If you'd like to improve my translations, or submit a new language file for inclusion in subsequent versions, please PM me!
- Permissions for use and admin commands
- Configurable for which worlds the plugin is enabled
- stores last death locations for each world so they are persistent when changing worlds, logging out/in, and server restarts
- Uses SQLite for persistent storage
- Configurable option to destroy compass on drop, to keep them from cluttering your world. Also destroys compass on death drop if configured
- Configurable delay for setting compass target for better compatibility with other plugins that react to player respawn events
- Destroys compass on any interaction with SavageDeathChests owned by player
- Configurable option to prevent placing death compass in chests/containers
- Customizable sound effects
- A perfect compliment to SavageDeathChest and SavageGraveyards
Permissions:
Permission | Description | Default |
---|---|---|
deathcompass.use |
Give player a DeathCompass when respawning after death | false |
deathcompass.reload |
Allow reloading of configuration file |
op |
deathcompass.admin |
All admin commands |
op |
Commands:
/deathcompass help [command]
Displays short help and usage message.
/deathcompass reload
Reloads config file. Requires deathcompass.reload permission.
/deathcompass status
Displays version info and config settings. Requires deathcompass.status permission.
Installation:
- Place the jar file in your server plugins folder and restart the server.
- Open the
config.yml
file with your favorite text editor, and add any worlds in which you would like the plugin to be active to theenabled-worlds
section, and make any other configuration changes you desire. - Issue the
/deathcompass reload
command; restarting the server is not necessary for configuration changes to take effect - Remember to grant any players or groups that should receive death compasses the
deathcompass.use
permission node, and any administrators of the plugin thedeathcompass.admin
permission node.
Configuration:
Localization Files:
If you'd like to improve these translations, or submit a new language file for inclusion in future versions, please PM me.
@res83
I am unable to reproduce this issue with latest spigot 1.10 build (882). Do you have any other plugins that operate on player death or respawn events? Any other plugins that set players compass target? Any console errors?
Problem In Spigot 1.10 not show points to their last death location in that world
Version 1.3.4 with the config accessor bug fix for pre-1.9 servers running on Windows has been uploaded and will be available for download soon. Version 1.4.1 for 1.9 servers to follow shortly after.
@timsavage
Windows 10
@snablesnot
I am working on a fix and will upload a new version once it is confirmed to solve the problem. I believe this issue only occurs on Windows servers, can you confirm that is true in your case?
Getting a null pointer trying to pass a login event with 1.4 on spigot 1.9 for death compass.
@SmallSansSerif
Thanks for the feedback and praise. The intended default behavior is to have the compasses enabled in all worlds, by having the disabled-worlds section used, which should allow compasses in all worlds except those explicitly listed. If this isn't the case, then it is a bug that I will need to fix.
Originally, I only had the enabled-worlds section, but this required editing of the config to make the plugin work out of the box, and I decided it would be better to have it work in all worlds by default, so that changes to the config are only necessary for those that want to specify exactly which worlds to include or exclude.
For the curious, the logic for determining enabled worlds is this:
@SmallSansSerif
Um.. well I thought the config was defaulting to work in all worlds. Well just commented out the disabled world section and added my worlds in the enabled section and lo and behold I get the compass now :)
Sorry to bother you. Great plugins btw!
Posted this on Github but will post here as well for the benefit of all following below:
I am using the latest version of SavageDeathChest (v1.4.4) which is awesome by the way and I wanted to try this companion plugin (SDCompass v1.3.2) but I can't get the compass on death for some reason. I have given the proper permission (deathcompass.use) and am using the default config where it's enabled in all worlds.
No error appears in the log as well. Can you test this and fix please? Thanks in advance!
@Saphareas
Thanks for the report, and compliment on DeathChest. There is no real correlation between the version numbers of the two plugins, it's just due to the fact that I've developed them at roughly the same pace. I recommend using the latest version of each. I do plan a release version 1.3.1 of DeathChests any day now.
The plugin requires the worlds in which you would like death compasses to be issued to be listed in the enabled-worlds section of the config file; by default no compasses are given in a world unless it is explicitly listed in the configuration. I've had several requests to switch to a default allow mode, and have a disabled worlds section in the config instead. I think I will probably do this in a future release, to allow for the plugin to work for the most people without having to make any edits to the config.
It is also required to give players the deathcompass.use permission node for them to receive a compass in an enabled world on death. Perhaps I should consider making this permission node on by default as well in a future version.
If both of these requirements have been met, but you are still not getting a death compass when you die, let me know, and we'll track the issue down further.
For some reason I don't get a compass on respawn. And there are no Error messages in the server console. I'm running a 1.8 server and use version 1.3 of DeathCompass because I thought it would be more compatible with the 1.3 DeathChest, which works really nice btw.
Version 1.3.1 has been uploaded. The only change is better handling of the removal of death compasses from inventory on interaction with SavageDeathChests. The last version was failing to remove death compasses from inventory on the opening of a death chest. They are now removed on opening or punching a death chest or the attached sign.
A new version has been uploaded (v1.3) and is available for download. I have added the feature to remove compasses from player inventory on interaction with a SavageDeathChest. (Chest opening, chest damaging/breaking, and chest quick-looting.) I also added a feature where death compasses are no longer dropped on death if the destroy-on-drop configuration option is true. This will also prevent them from being placed in death chests, and therefore no death chest will be deployed if a player had only a death compass in their inventory at time of death, as their inventory will be empty on removal of the death compass, which occurs before death chest deployment.
@wiedzmin137
Absolutely. I had this feature at one point, but I took it out before publishing. It should be fairly easy to put it back in. It will probably be implemented in SavageDeathChest, and not this plugin.
Edit: I intend to implement this such that death compasses are removed from players inventory only upon opening (or quick-looting) death chests, as I think it's fair to allow players to stash death compasses in regular chests or other containers if they so desire. Thoughts?
Hello. Can you add support for your SavageDeathChest and destroy compass on getting items from chest?
@mr_T_creations
No, it should would on all versions 1.6.4 up, and I did some light testing on 1.7.10 a few months back. Are you getting any errors in the console? And does the chat message display when it should be giving a compass? Obviously you have added the enabled worlds in the config, or players wouldn't even get the first death compass. Are you using any other plugins that deal with inventory on death that may be causing a conflict? I'm sure it can be fixed if we can get to the root cause of the problem.
For some reason the compass is only given to the player the first time they die. If they drop the compass and it is destroyed, they won't get it back. Is this a problem with running a 1.8.1 plugin on a 1.7.10 server?
@timsavage
Hurray! :)
@Sinuce
I've got a new release ready, but I haven't been able to upload it to dev.bukkit.org due to an odd error with the website. I've opened a ticket, and will get it resolved, but I found myself busy with other things. I'll try to get it uploaded this week if I can. Thanks for your patience.
To recap, the new version no longer relies on setting a custom damage value on Death Compasses, as this causes recent versions of bukkit to display a pink/black cube in player inventories. The plugin will now rely solely on the custom metadata (name/lore) to distinguish them from normal compasses.
UPDATE: I finally managed to upload v1.2.1 with above fix. It should be available for download as soon as it is approved.
Hi timsavage,
Do you have an ETA on the next release? :)
Cheers~