Native Minecraft Version:Legacy (< 1.13)Tested Minecraft Versions:
Custom death effects on player-death, 99% customizable, down to every single detail, be it the offset of a particle or the pitch of a sound.
Each player can buy and choose the death effects that they like most by using experience that they gain by playing on the server.
This plugin depends on my Core library! They must BOTH be installed for the plugin to work.
Player Data Storage
This plugin supports storing player data in multiple ways: MySQL database, SQLite database, MongoDB (beta, needs core 1.3.0) and, finally, per-player YAML files.
The plugin also blocks particles and entities from being sent to players whilst they're dead, preventing a known bug that would make the game lag or possibly even freeze.
Experience
Rewarding players for their playtime
Players gain experience by playing in the server, each world can be configured to give players a specific amount of experience every x amount of seconds (only configured and enabled worlds will give a player experience).
Spoiler: Example maps.yml
Experience Boost
The plugin supports "experience boosts", they're meant to reward your vips only at the moment but they will be expanded to purchasable boosts in the future.
You can create your own boost and, by giving the permission to a player or group, it'll be enabled for them.
Spoiler: Example boosts.yml
Spoiler: Screenshots
Configuration
This is the default config file
Spoiler: config.yml
Messages
Messages are stored in another configuration file called "english.yml" as, in the future, players will be able to change their language by using the /language command and the server administrator will be able to create new language files, such as "italian.yml"
The messages file also contains the effects names and lores, so they will be translatable in the future.
Spoiler: english.yml
Effects
Effects are extremely customizable
This is the effects.yml file from the video below (stripped from the example effects to show the multi-page functionality)
Spoiler: Example effects.yml
Commands
The only command is "/deatheffects" and it will open the effects inventory or the shop (aliases: /de, /cnde)
Permissions:
/deathinventory - deatheffects.death_inventory
/deathinventory shop - deatheffects.death_inventory.shop
Upcoming features:
+ ChestCommand like items, given on-join, to open the effect and effect shop inventories.
+ PlaceHolderAPI support.
+ Possibly adding chat messages to death effects (broadcast messages and messages only sent to the killer)
+ The possibility to add a new language just by creating the language file (which is why effects lores and display name are fetched from the English language file first).
* Maybe add a way to let players buy experience or effects with "Tebex" (buycraft)
* Possibly adding MongoDB support in the future Added with the update 1.3.0 to the Core plugin (using the latest version of it is recommended, though)
* Possibly a way for players to buy boosts, suggestions about what currency to use are welcome.
* Possibly adding custom events to make integration with this plugin easier
Videos
- 1.8
- 1.9
- 1.10
- 1.11
- 1.12
- 1.13
- 1.14
- 1.15
- 1.16
- 1.17
- 1.18
- 1.19
Custom death effects on player-death, 99% customizable, down to every single detail, be it the offset of a particle or the pitch of a sound.
Each player can buy and choose the death effects that they like most by using experience that they gain by playing on the server.
This plugin depends on my Core library! They must BOTH be installed for the plugin to work.
Player Data Storage
This plugin supports storing player data in multiple ways: MySQL database, SQLite database, MongoDB (beta, needs core 1.3.0) and, finally, per-player YAML files.
The plugin also blocks particles and entities from being sent to players whilst they're dead, preventing a known bug that would make the game lag or possibly even freeze.
Experience
Rewarding players for their playtime
Players gain experience by playing in the server, each world can be configured to give players a specific amount of experience every x amount of seconds (only configured and enabled worlds will give a player experience).
Spoiler: Example maps.yml
Experience Boost
The plugin supports "experience boosts", they're meant to reward your vips only at the moment but they will be expanded to purchasable boosts in the future.
You can create your own boost and, by giving the permission to a player or group, it'll be enabled for them.
Spoiler: Example boosts.yml
Spoiler: Screenshots
Configuration
This is the default config file
Spoiler: config.yml
Messages
Messages are stored in another configuration file called "english.yml" as, in the future, players will be able to change their language by using the /language command and the server administrator will be able to create new language files, such as "italian.yml"
The messages file also contains the effects names and lores, so they will be translatable in the future.
Spoiler: english.yml
Effects
Effects are extremely customizable
This is the effects.yml file from the video below (stripped from the example effects to show the multi-page functionality)
Spoiler: Example effects.yml
Commands
The only command is "/deatheffects" and it will open the effects inventory or the shop (aliases: /de, /cnde)
Permissions:
/deathinventory - deatheffects.death_inventory
/deathinventory shop - deatheffects.death_inventory.shop
Upcoming features:
+ ChestCommand like items, given on-join, to open the effect and effect shop inventories.
+ PlaceHolderAPI support.
+ Possibly adding chat messages to death effects (broadcast messages and messages only sent to the killer)
+ The possibility to add a new language just by creating the language file (which is why effects lores and display name are fetched from the English language file first).
* Maybe add a way to let players buy experience or effects with "Tebex" (buycraft)
* Possibly adding MongoDB support in the future Added with the update 1.3.0 to the Core plugin (using the latest version of it is recommended, though)
* Possibly a way for players to buy boosts, suggestions about what currency to use are welcome.
* Possibly adding custom events to make integration with this plugin easier
Videos
