Config

The hardcore feature in the plugin is one of the biggest features in the whole plugin. On this page, I will explain every config line you need to know about. To go to the plugin’s config, simply go to your server -> file manager -> open the plugins folder -> EasySMP folder -> config.yml

Enabling Hardcore To enable hardcore, open the config.yml file in the "EasySMP" data folder. Open it and at the top, there is an option called "hardcore":

general:
  hardcore: true

If you set it to true, you have enabled hardcore. When enabling this, it requires a restart so that the plugin can apply all the changes and apply hardcore in-game, so that you have the nice hardcore hearts.

Grace period

You can start a grace period in-game by doing /hardcore grace start. This will start the grace period you have set up in the config. To stop the grace period, you can do /hardcore grace stop. This will do the exact same as when it ends automatically. You can set the grace period time in the config under "hardcore". You can use s, m, h, d: s = seconds m = minutes h = hours d = days

hardcore:
  grace-period: 1h

During the grace period, you will not take any damage — even from mobs!

Lives

Each player has a set amount of lives. If you have 1 life left and you die, you lose. You can set the default lives under "hardcore" and then lives. Use the %easysmp_lives% placeholder if you want to get the player's lives.

hardcore:
  grace-period: 1h
  lives: 1

If you want to give or take players' lives, you can do /playerdata set lives (player) (number). Check the PlayerData page to get more info on the command/file.

Respawn world

Make sure you set the respawn-world in the config!!

hardcore:
  ...
  respawn-world: world

Lives PVP

If you want to enable gaining a life when you kill someone, you can toggle that. The player you killed loses a life, and you get a new one.

hardcore:
  grace-period: 1h
  lives: 1
  respawn-world: world
  lives-pvp: false

When a player dies, they will be put in spectator mode if the time is not -1 or 0. If you don’t want the player to be able to spectate, you can set the time to -1, and they will be punished instantly. If you want the player to spectate infinitely, set it to 0.

Spectate time

hardcore:
  grace-period: 1h
  lives: 1
  respawn-world: world
  lives-pvp: false
  spectate: 60

Death Message

You can only change the final death message. If the player has more than 1 life, the death message would be: ClearedSpore has died and lost 1 life. They are now at 1 When you die and had 1 life left, it will send a death message and send the player that died a title.

hardcore:
  grace-period: 1h
  lives: 1
  respawn-world: world
  lives-pvp: false
  spectate: 60

  death-message: '&f%player% &chas died and can now spectate'
  death-titles:
    - '&cGG'
    - '&cWomp womp'
    - '&cCya'
    - '&cYou tried'
    - '&cBetter luck next time :)'

You can use %player% as a placeholder for the player that died. For the titles, you can add multiple entries. They will not all be sent — one will be chosen randomly. If you only want to show one title, you can just add one line.

Example:

death-message: '&f%player% &cgot smoked!!'
death-titles:
  - '&cWe hope you had fun!'

Punishment and Revive

When the spectate time ends, the player will be punished using commands. These are console commands, and you can use %player% as a placeholder for the player who died.

hardcore:
  grace-period: 1h
  lives: 1
  respawn-world: world
  lives-pvp: false
  spectate: 60

  death-message: '&f%player% &chas died and can now spectate'
  death-titles:
    - '&cGG'
    - '&cWomp womp'
    - '&cCya'
    - '&cYou tried'
    - '&cBetter luck next time :)'
  punishment:
    commands:
      - /ban %player% You had 0 lives and died!
      - /broadcast %player% is now banned forever!
  revive:
    commands:
      - /pardon %player%
      - /broadcast %player% has been revived

When you do /hardcore revive (player), it will run the console commands. Same as with punishment, you can use %player% as a placeholder for the player who got revived.

It is highly recommended not to use a /tempban in the punishment, since that could result in the player joining with 0 lives. If a player joins and has 0 lives, the system will break for that player.

When the player joins and has not been revived, the system will kick them and send a webhook.

Kick message:

if the discord webhook is enabled:

If the player joined and has 0 lives

if the discord webhook is enabled:

End

In the config, you need to set a few values. The world value will be the world where the end event is played. You can use a separate world if you want to have a clean landscape instead of your normal survival world.

Under border, you have to set 3 options:

• start: The starting border size. It sets the border to this value when the event begins.

• end-border: The smallest the border can become. For example, if it’s set to 10, the border will stop shrinking at 10 blocks.

• close: The number of blocks the border shrinks when a player dies. If the border is 500 and someone dies, it shrinks to 450.

The death-message is the message sent when a player dies. You can use the %player%, %killer%, and %players_alive% placeholders. If there is no killer (like fall damage), the plugin will use a default message. Color codes work!

The time is how long until sudden death activates. Check more about this feature elsewhere. When the sudden death timer starts, it sends an action bar to everyone showing the remaining time. You can disable this by setting actionbar to false.

⚠️ DO NOT CHANGE eventactive OR freezed!! The plugin uses these when you start the event. If freezed is set to true when the server starts, it will freeze everyone. If eventactive is set to true, it will apply death events and more.

end:
  world: world
  border:
    start: 500
    end-border: 10
    close: 50
  death-message: '&f%player% &fhas been killed by &f%killer% &cthere are &f%players_alive% &cleft'
  time: 1h
  actionbar: true
  scoreboard: true
  eventactive: false
  freezed: false

Extensions There are 2 extensions: PlaceholderAPI and Discord Webhook.

PlaceholderAPI For the hardcore value, you can change how it looks. If hardcore is enabled, you can set it to '&aYes', and if it is disabled, '&cNo'.

extensions:
  placeholderapi:
    hardcore-value:
      enabled: '&aYes'
      disabled: '&cNo'

Discord For Discord, you have to provide a webhook — otherwise, it will not send any messages. It should not give errors, except from its own logger. More info here:

discord:
  webhook: webhook_url