Skip to content

Conversation

@KabanFriends
Copy link
Contributor

@KabanFriends KabanFriends commented Feb 9, 2026

📌 Description

Forgive me for another PR!
This is a bit of a feature request that adds an optional feature. The default gameplay remains unchanged so it is not a breaking change.

Two new config values MobBaseDamage & MobBaseRangeDamage allow you to configure how much of Hytale's vanilla mob damage should be influenced in the "level 0" mob stats.
The damage that the player takes is calculated with the following formula:

finalDamage = incomingDamage * (baseDamage + damageMultiplier * mobLevel)

So, for example, when the baseDamage is 0.75 and damageMultiplier is 0.25, at the mob level 1, this results in the damage factor of 1.0 which is Hytale's vanilla mob strength.
You could say this is an "offset" value to the damage factor. These config values are 0 by default so that the damage formula remains the same unless specifically configured.

This is still a draft, so please let me know what you think about this feature!


🧪 Type of Change

Please check the types of changes your PR introduces:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Tests added / updated

✅ Checklist

Go over all the following items and check them before submitting your PR:

  • My code follows the project’s code style (simply run spotlessApply to apply formatting)
  • I have performed a self-review of my own code
  • I have commented my code where necessary
  • My changes generate no new warnings

@AzureDoom
Copy link
Owner

But the melee haha thanks!

@AzureDoom
Copy link
Owner

LGTM

@AzureDoom AzureDoom merged commit f91aa9e into AzureDoom:main Feb 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants