Fix: Shock module ignores biometric authorisation #115
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
UPDATE TO #113
Fixed bug where shock module damaged authorised players despite biometric
authorisation. Refactored force field damage system to prevent redundant
damage (instant death + shock simultaneously) and provide granular control.
Changes:
MFFSConfig.java: Split damage config into two separate options:
ForceFieldBlockImpl.java: Fixed boolean logic bug where authorised players incorrectly took instant death damage
ShockModule.java: Added biometric authorisation checks and config support. Shock damage now only applies when instant death is disabled (acts as alternative damage). Authorised players can disable shock damage via config. Unauthorised players/mobs always take shock damage when instant death disabled.
Behavior: Instant death and shock damage are now mutually exclusive. When
instant death is enabled, only instant death applies. When disabled, shock
module provides alternative damage that authorised players can optionally disable.