A Minecraft (Spigot) plugin for collaborative hardcore. Rather than banning a player when they die (like the Vanilla implementation of hardcore does), create a new world and force everyone to start over. Inspired by this Reddit post.

Note: MultiplayerHardcore is intended to be used on a server of its own. Use BungeeCord networking if you want to offer multiple game modes.

• Create a new set of worlds (Overworld, Nether, End) every time a player dies, and move all players there (clearing out inventories and resetting expecience)
• Retain past attempts in case someone decided to build some crazy stuff you may want to revisit later
• Customise death messages
• Keep track of death causes for each player (although there is no convenient way of displaying this yet)
• Close the server on a schedule (i.e. only allow players onto the server at certain times) to ensure nobody grinds away every night and beats the game single-handedly
• Post death messages to Discord via a webhook.
• Display the current attempt number in the server MOTD

• Multiverse-Core (4.2.2) (compile, run)
• Multiverse-NetherPortals (run)

Built for: Spigot 1.16.5, Java 11

Schedule for when players should be allowed onto the server. Possible values for each day are open (all day), closed (all day), or a time span like 16:30-22:00. If the ending time is before the beginning, it is interpreted to be on the next day, e.g. writing FRIDAY: 16:30-02:00 would open the server starting fridays at 16:30hrs (4:30pm) until saturday at 02:00hrs (2am). All times are interpreted as server local time.

• enabled: true to attempt using a Discord webhook, false to disable this feature altogether (the default).
• webhookUrl: The URL to try and send messages to, if enabled above. See Discord's documentation if you don't know how to get create one.

• enabled: true if you want the plugin to handle the server's MOTD, false to use the MOTD from the server.properties file or another plugin (the default).
• line1: The first line of the MOTD.
• line2default: the format of the second line during normal play. The attempt number is substituted for %d. (Example: Attempt #%d)
• line2busy: the text of the second line while the server is busy generating a new world.
• line2broken: the text of the second line when generating a new world has failed, and the server is not allowing players in.
• line2closed: the text of the second line while the server is closed (see timeOfPlay). The beginning of the next playtime window is substituted for %s.

Custom messages to display when a player dies. %1$s is replaced with the dying player, %2$s is replaced with the attacker, if applicable (does not apply to the ending message).

For all message categories except ending, you can supply several messages. If you do, one will be chosen at random every time.

• ending: suffix that is always appended to the specific death message.
• general: list of messages that are used if no messages are set for the specific cause of death.
• ENTITY_ATTACK, etc.: for each damage cause, a list of messages to be used when a player dies of that cause.

For example, if the messages block in your config looks like this:

messages:
  ending: "Your journey begins anew..."
  general:
    - "%1$s died."
  PROJECTILE:
    - "%1$s was shot to death by %2$s."

and a player called "SomeGuy" is killed (shot) by a skeleton, the death message would read:

SomeGuy was shot to death by Skeleton. Your journey begins anew...

However, if they were killed by a Zombie, the message would use the more generic "SomeGuy died" wording, since we didn't set a specific message for ENTITY_ATTACK.

• attemptsToKeep: The number of old attempts to keep, in case you wish to revisit them. Set to a negative value to keep all old attempts. (Can cause significant memory and disk usage!) The default is 10, i.e. attempt1 will be deleted when attempt12 becomes active.
• worldPrefix: The base name to use for worlds created by the plugin. The default is attempt, which means the worlds will be called attempt1, attempt2, and so on. (Consequently, the Nether for the first attempt will be called attempt1_nether, and the corresponding End will be called attempt1_the_end.)

For each player (UUID), lists how often they have died of each cause. There is currently no way to output this nicely.

MultiplayerHardcore does not currently have any commands or permissions to worry about. Everything is handled by config file only.

If your server is running out of RAM or disk space to store old attempts, try reducing the number of attempts that are retained (using attempt.attemptsToKeep in the config file). If you can't launch the server to do this, delete the folders manually and remove the relevant blocks from plugins/Multiverse-Core/worlds.yml

MultiplayerHardcore is intended to be used on a server of its own. There is no way for players to "opt out of" MultiplayerHardcore, and the plugin will react to deaths in all worlds. Use BungeeCord networking if you want to offer several game modes.