Progressive Damage

Due to an issue in the newest versions of forge, several features have been temporarily removed
---------------------------------------------------------------------------------------------------------------------------------

~ Are you tired of getting knocked down constantly at the start of the game

~ Are you tired of the endgame being too easy, with nothing being able to threaten you

Progressive Damage will make it so towards the start of the game,

mobs will hardly be able to damage you.

However the more damage you take from a mob, the more and more

damage it will be able to do.  From 0 to 1 shotting you.

having high armor bars, blocking with a shield, and normal Protection are the only ways to protect yourself when the damage starts to progress.

There are game rules for you to adjust the values of your damage resistance, and shield resistance

[Removed Features]

To make the game easier, by default you can only take damage once every 20 ticks (1 second) .  That can be changed with the dmgcooldown gamerule.

Your damage resistance default value is 10.  lowering it will make you take more damage per hit, raising it will make you take less damage per hit.

Your shield resistance value, is defaulted to 5

[Damage Pool Types]

If the issue stopping my previous version from working is not resolved, this will come back in the next update.

(the alternative damage pool, makes it so all entity sources of damage come from the same attack pool for a much harder game)

[Ease of life]

clicking on a mob with a clock will show you its damage value.

There is no way to lower a mobs damage value without changing its scoreboard.

 [Shoutouts]

Huge Thankyou to Lillo97_TV for bringing a game breaking bug to my attention.
Progressive Damage is part of his modpack, check it out !

https://www.curseforge.com/minecraft/modpacks/simple-weavings

[Known Bugs]

Entities with single character ID's will not be able to damage the player (this should pretty much never happen)

This bug exists due to the way Entity IDs are extracted.  This bug is only in 1.16.5

1.16.5 and 1.17.1 will NOT be compatible.  This is due to how the ID's are extracted.
the same method provides different data between the versions.