![[1.8-1.11] DeathManager - New Module: Actions](/data/resource_icons/0/220.jpg?1501937576){kind=icon}
He committed suicide, let's support him by using his plugin
Tested Minecraft Versions:
If images fail to load, you may use this link to preview them: Repository
This issue is down to SpigotMC's Proxy.
Have you ever wanted to control every aspect of a players' death, from the messages shown in-game to whether their items can be saved in a chest? DeathManager makes that possible! With its modular format, allowing you to only enable the features you want, and permissions-driven components; DeathManager is the perfect solution to player deaths, for absolutely any server.
DeathManager comes complete with various popular components that allow near unlimited control of player deaths. These components come with their own configuration file to reduce complexity when configuring various features.
DeathManagers' current modules are as follows;
DeathManagers' current in-development modules are as follows;
DeathManager has a few planned features, these are still in development or are still to be implemented. These modules are as follows;
The Messages module is simple in terms of what it does. It captures and filters the PlayerDeathEvent to identify the cause of death, and then replaces the built-in event message with one from the module configuration file.
A small selection of placeholders are available to enter into each message, as well as a prefix and suffix for messages.
This module is compatible with all other modules.
Permissions
The Compass module checks for various events related to Player Death, Interaction, Respawn and Join. When a player dies, the plugin stores the location and world that the player died in. A player may only have one death-point in each world, so existing records of player deaths will be replaced.
When the player respawns, the plugin distributes a Death-Compass that points to the death location of the players' current world. If none can be found, or the player has dropped the compass (based on configuration settings), the compass will point to the spawn location of the world and existing compasses will be destroyed.
This module is compatible with the following:
Permissions
The Chest module checks for events related to Player Death, Interaction, and Block Breaking. When a player dies, the surrounding area is scanned for suitable locations to deploy a death-chest of a selected size. When one is found, the plugin will then check whether the surrounding area is protected by a world-protection plugin before deploying a chest filled with the items found in the dead players' inventory.
Multiple death-chests can be deployed in each configured world. However, an expiration period can be configured so that existing chests will be deleted when their expiration time has been reached.
This module is compatible with the following:
Permissions
The Totem module introduces a 1.11 feature to older versions of Minecraft, it listens for the EntityDamageEvent and filters the Player instance. This features allows the resurrection of players when carrying a specific item in their inventory. This item can be crafted at a crafting table, and the recipe can be configured in the configuration component attached to the module.
The item can be stacked in the players' inventory. But it cannot be dropped, traded, or placed in any other inventory other than the players'. To make for a more accurate Roleplay experience, the crafting recipe for Totems can be disabled and instead replaced with a recharge timer.
This module is compatible with the following:
Permissions
The Action module introduces the ActionAPI to DeathManager. Allowing server owners to take a degree of control over three events inside DeathManager;
You may make use of any of the following actions;
This module is compatible with the following:
Permissions
Want your server listed here?
PM me the IP address, Port and Name and I'll add it!
DeathManager includes an API! Simply include the plugin in your project. Any method and class can be called in your plugin, including the custom events provided by DeathManager.
Note: The DeathManagerAPI is still in heavy development, so implementation of the API is not advised at this stage.
Code (Text):
/* ================================== */
import uk.co.projectrogue.dm.DeathManager; // Import DeathManager Class
import uk.co.projectrogue.dm.handlers.*; // Import all of the Handlers
public class MyPlugin extends JavaPlugin {
private DeathManagerAPI deathManagerAPI;
public void onEnable() {
/* code here ... */
// Initialise DeathManagerAPI Object
initDeathManagerAPI();
/* code here ... */
}
public void onDisable() {
/* code here ... */
}
/**
* DeathManager API Hook
*/
public void initDeathManagerAPI() {
// Get DeathManager Plugin
DeathManager deathManager = (DeathManager) getServer().getPluginManager().getPlugin( "DeathManager" );
// Get DeathManagerAPI Object
DeathManagerAPI deathManagerAPI = deathManager.getAPI();
// Define DeathManagerAPI variable for later access...
setDeathManagerAPI( deathManagerAPI );
}
/**
* Set the private DeathManagerAPI variable
* @param DeathManagerAPI
*/
private void setDeathManagerAPI( final DeathManagerAPI api ) {
this.deathManagerAPI = api;
}
/**
* Get the private DeathManagerAPI variable
* @return DeathManagerAPI
*/
public DeathManagerAPI getDeathManagerAPI() {
return this.deathManagerAPI;
}
}
/* ================================== */
DeathManager requires a few extra plugins for some features, these are listed below.
Please take special care when selecting the required plugins for your server.
Module Dependencies
Tested Minecraft Versions:
- 1.8
- 1.9
- 1.10
- 1.11
If images fail to load, you may use this link to preview them: Repository
This issue is down to SpigotMC's Proxy.
Have you ever wanted to control every aspect of a players' death, from the messages shown in-game to whether their items can be saved in a chest? DeathManager makes that possible! With its modular format, allowing you to only enable the features you want, and permissions-driven components; DeathManager is the perfect solution to player deaths, for absolutely any server.
DeathManager comes complete with various popular components that allow near unlimited control of player deaths. These components come with their own configuration file to reduce complexity when configuring various features.
DeathManagers' current modules are as follows;
- Chests - Create chests where the player dies to store their items.
- Totems - Craftable totems that revive the player on death.
- Compass - A compass that points to the players' last death point.
- Messages - Customise the messages shown in-game when a player dies.
- Actions - Perform actions when a player dies, respawns or when they get revived by a Totem.
DeathManagers' current in-development modules are as follows;
- Disguises - Collect mob and player disguises.
DeathManager has a few planned features, these are still in development or are still to be implemented. These modules are as follows;
- Bans - Ban the player for an amount of time on death.
- Limbo - Make your players earn the right to live again.
- Hunger - Force players' hunger level when they respawn.
- Rivals - Track players who kill each other the most, making them rivals.
- Holograms - Virtual grave-stone that can be looted for player items. Also features their skulls as a collectible, and a display of the murder weapon - if one was used.
- Economy - Punish players for dying by manipulating currency.
- Tombs - Alternative to Chests, allowing custom schematics.
- Graves - Create grave schematics in a pre-defined location.
- Recovery - Configurable tokens that restore a players inventory.
- Cadaver - Create lootable bodies where a player dies.
The Messages module is simple in terms of what it does. It captures and filters the PlayerDeathEvent to identify the cause of death, and then replaces the built-in event message with one from the module configuration file.
A small selection of placeholders are available to enter into each message, as well as a prefix and suffix for messages.
This module is compatible with all other modules.
Permissions
- deathmanager.death.messages - Allows messages to be altered for the player.
The Compass module checks for various events related to Player Death, Interaction, Respawn and Join. When a player dies, the plugin stores the location and world that the player died in. A player may only have one death-point in each world, so existing records of player deaths will be replaced.
When the player respawns, the plugin distributes a Death-Compass that points to the death location of the players' current world. If none can be found, or the player has dropped the compass (based on configuration settings), the compass will point to the spawn location of the world and existing compasses will be destroyed.
This module is compatible with the following:
- Bans
- Chests
- Messages
- Totems
- Actions
Permissions
- deathmanager.death.compass - Allows players to acquire a Death Compass.
The Chest module checks for events related to Player Death, Interaction, and Block Breaking. When a player dies, the surrounding area is scanned for suitable locations to deploy a death-chest of a selected size. When one is found, the plugin will then check whether the surrounding area is protected by a world-protection plugin before deploying a chest filled with the items found in the dead players' inventory.
Multiple death-chests can be deployed in each configured world. However, an expiration period can be configured so that existing chests will be deleted when their expiration time has been reached.
This module is compatible with the following:
- Bans
- Compass
- Messages
- Totems
- Actions
Permissions
- deathmanager.death.chest - Basic Chest Permissions, the ability to use a chest.
- deathmanager.death.chest.free - Gives the player a free chest.
- deathmanager.death.chest.double - Grants the placement of Double Chests.
- deathmanager.death.chest.item-place - Allows players to place items in Death Chests, regardless of Config.
- deathmanager.death.chest.access.other - Allows players to loot other Death Chests, regardless of Config.
- deathmanager.death.chest.access.creative - Allows players to access Death Chests, even in Creative.
The Totem module introduces a 1.11 feature to older versions of Minecraft, it listens for the EntityDamageEvent and filters the Player instance. This features allows the resurrection of players when carrying a specific item in their inventory. This item can be crafted at a crafting table, and the recipe can be configured in the configuration component attached to the module.
The item can be stacked in the players' inventory. But it cannot be dropped, traded, or placed in any other inventory other than the players'. To make for a more accurate Roleplay experience, the crafting recipe for Totems can be disabled and instead replaced with a recharge timer.
This module is compatible with the following:
- Bans
- Compass
- Messages
- Chests
- Actions
Permissions
- deathmanager.death.totem - Allows a player to be revived by a Totem.
- deathmanager.death.totem.give - Gives a player a totem when they join the server.
The Action module introduces the ActionAPI to DeathManager. Allowing server owners to take a degree of control over three events inside DeathManager;
- PlayerDeathEvent - Default
- PlayerRespawnEvent - Default
- PlayerRevivalEvent - Provided by the Totems module.
You may make use of any of the following actions;
- [Chance=<percentage>] [<action>] - Chance out of 100% that this action will be performed
- [Delay=<time>] [<action>] - Delays the action to be performed after the delay period in seconds
- [PlayerCommand] <command> - Executes the command as a player
- [ConsoleCommand] <command> - Executes the command as the console
- [OperatorCommand] <command> - Executes the command as an operator
- [Broadcast] <message> - Broadcasts the following message to the server
- [Message] <message> - Sends the following message to the player
- [Sound] <sound value> - Plays the sound for the player
- [VaultGive] <amount> - Adds the amount to the players Vault economy balance
- [VaultTake] <amount> - Takes the amount from the players Vault economy balance
- [Teleport] <world name>;<x>;<y>;<z> - Teleports the player to the specified coordinates
- [Teleport] <world name>;<x>;<y>;<z>;<yaw>;<pitch> - Teleports the player to the specified coordinates
- [GiveItem] <material>;<amount> - Gives the player the specified item
- [GiveItem] <material>;<amount>;<data> - Gives the player the specified item
- [GiveItem] <material>;<amount>;<data>;<name> - Gives the player the specified item
- [Title] <title> - Displays the title for the player
- [Title] <title>;<subtitle> - Displays the title & subtitle for the player
- [ActionBar] <message> - Displays the action bar message for the player
- [Bungee] <server> - Sends the player to the specified bungee server
- [JSONBroadcast] <message> - Sends the JSON message to the server
- [JSONMessage] <message> - Sends the JSON message to the player
This module is compatible with the following:
- Bans
- Compass
- Messages
- Chests
- Totems
Permissions
- deathmanager.action.death - Allows a player to be affected by the actions executed on Death.
- deathmanager.action.respawn - Allows a player to be affected by the actions executed on Respawn.
- deathmanager.action.revival - Allows a player to be affected by the actions executed on Revival.
Want your server listed here?
PM me the IP address, Port and Name and I'll add it!
DeathManager includes an API! Simply include the plugin in your project. Any method and class can be called in your plugin, including the custom events provided by DeathManager.
Note: The DeathManagerAPI is still in heavy development, so implementation of the API is not advised at this stage.
Code (Text):
/* ================================== */
import uk.co.projectrogue.dm.DeathManager; // Import DeathManager Class
import uk.co.projectrogue.dm.handlers.*; // Import all of the Handlers
public class MyPlugin extends JavaPlugin {
private DeathManagerAPI deathManagerAPI;
public void onEnable() {
/* code here ... */
// Initialise DeathManagerAPI Object
initDeathManagerAPI();
/* code here ... */
}
public void onDisable() {
/* code here ... */
}
/**
* DeathManager API Hook
*/
public void initDeathManagerAPI() {
// Get DeathManager Plugin
DeathManager deathManager = (DeathManager) getServer().getPluginManager().getPlugin( "DeathManager" );
// Get DeathManagerAPI Object
DeathManagerAPI deathManagerAPI = deathManager.getAPI();
// Define DeathManagerAPI variable for later access...
setDeathManagerAPI( deathManagerAPI );
}
/**
* Set the private DeathManagerAPI variable
* @param DeathManagerAPI
*/
private void setDeathManagerAPI( final DeathManagerAPI api ) {
this.deathManagerAPI = api;
}
/**
* Get the private DeathManagerAPI variable
* @return DeathManagerAPI
*/
public DeathManagerAPI getDeathManagerAPI() {
return this.deathManagerAPI;
}
}
/* ================================== */
DeathManager requires a few extra plugins for some features, these are listed below.
Please take special care when selecting the required plugins for your server.
Module Dependencies
- Vault - Required for Economy
- Lib's Disguises - Required for Disguises (Option #1)
- iDisguise - Required for Disguises (Option #2)
- PlaceholderAPI - Required for Placeholders
- RogueCoreLibrary - Required to send MCUpdate Stats and update the operational plugins.
- Please report any issues you encounter in the discussion section. Not in the reviews section. Leaving a bad review due to an issue reflects badly on the entire resource.
- This plugin has been compiled with Java 8, release 111. The operational standpoint of the plugin on servers running Java 7 is questionable. It is likely that the plugin will not work. Refer to #1.
- This plugin has been constructed to work on Spigot servers only. However, there is a chance that servers running a suitable version CraftBukkit may be able to run it with very few issues, if any. Refer to #1.
- Extensive testing has been performed against versions 1.10 and 1.11 of Spigot, but evidence points to the plugin working on older versions. Refer to #1.
- Do not, under any circumstances, redistribute this plugin on a website, forum, or any other media, without the express permission of the developer. Failure to meet this criteria will result in actions under the fullest extent of the law. See DMCA
- Do not decompile this plugin without the permission of the developer.
![[bd] Attachment Store for XenForo 2.0](/data/resource_icons/2/2384.jpg?1553353241){kind=icon}