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.
In reply to IvoryShots77998:
In reply to timsavage:
Can you prevent players from putting this compass to chests or remove this compass once logged out?
Is the new release 1.13 only? Or does it still work with older minecraft versions verisons?
In reply to TheDimSimKing:
@timsavage are you still active?
Works on 1.13.1 spigot
However it is using lots of ram, wtf?
Quote from IvoryShots77998 >>
In reply to timsavage:
Thanks, i will try. Do i need to remove the deathlocations.db?
Idk what happened but now it uses less memory, i havent changed anything yet.
But still i am going to set it to yaml
In reply to IvoryShots77998:
In reply to timsavage:
getting this error. I removed the old db file :(
https://hastebin.com/yajuweqake.cs
Oo! You updated plugin, going to try it now.
Compatible with 1.13 or needs to be updated?
Works great but I suggest adding an option in config where once a player reaches their death point the compass auto destroys itself, resetting all compass targets to default.
In reply to TheDimSimKing:
A new version (1.4.5) has been uploaded that was compiled with the Bukkit-1.11.2 API. It should work with servers running bukkit/spigot versions from current 1.11.2 back to 1.8, and likely older.
Doesn't work on 1.11
Seems to work as intended on my 1.11 test server. Perhaps a misconfiguration or plugin conflict? I released a new version compiled against the bukkit-1.11.2 API, you may want to give that a try.
A new version (1.4.4) has been uploaded, which corrects an issue with a missing library in the plugin jar file.
A new version (1.4.3) has been uploaded with the following new features:
Hopefully these new features will help overcome any compatibility issues with other plugins.