Incremental Hardcore

Minecraft 版本： 1.21 1.21.1 1.21.2 1.21.3 1.21.4 1.21.5

平台： fabric forge neoforge quilt

标签： game-mechanics

This is a new gamemode, in which, every time you die, you lose a heart. Once you run out of max hearts you truly die just like in vanilla hardcore.

Disclaimer

DO NOT use Minecraft's hardcore game mode, as it interferes with the pack.

Useful Info

• You can access the settings menu using /function inh:settings
• You can uninstall the pack using /function inh:uninstall
• You can change the items used to revive and heal players by going to data\incrementalhardcore\tags\item\healing_item.json and data\incrementalhardcore\tags\item\revive_item.json respectivley. (This only applies to the datapack version)

Please note, if you're using the datapack version. In order to install the pack you need to put it in your worlds folder, this can be done by taking it from your profile/datapacks folder, to the saves/(your world here)/datapacks folder

Gameplay

• Every single time you die, no matter what. You lose a maximum heart. You start off with 10, just like in vanilla. All the way down to 0

• Once you hit 0 max hearts you get sent to spectator mode, in which you are stuck like that until you are revived (Disabled by default)

• In order to get back max hearts, you need to rename a netherite scrap to the player's name and throw it onto a lodestone.

• If enabled, you can revive friends by doing the same thing with totems of undying

Settings |Setting|Description|Default| |-|-|-| |AllowHealing|Whether or not you can regain max health using netherite ingots|`true`| |AllowRevives|Whether or not you can revive players using a totem of undying|`false`| |TotemEffect|Whether or not you get the totem of undying potion effects on revival|`false`| |ReviveHealth|The number of half-hearts a revived player will spawn with|`2`| How update packs when incompatible Version 2 to Version 3+ This is caused by the namespace changes of version 3. In order to fix this. You need to migrate the users data. To migrate your user's data you need to make sure they are on the server. Then run the command `/execute as @a run scoreboard players operation @s INH.MaxHealth = @s MaxHealth` If it is ran again, it will transfer the data of all players, including ones who have already had their data transferred, possibly rolling back their data. To transfer only one players data, instead run `/execute as (player) run scoreboard players operation @s INH.MaxHealth = @s MaxHealth`

For any feature requests, please let me know on the projects github!