Skip to content

Fix: Normalized damage / count should have a double, not int threshold#6188

Merged
onebeastchris merged 1 commit intoGeyserMC:masterfrom
onebeastchris:fix/doubles-in-preds
Feb 14, 2026
Merged

Fix: Normalized damage / count should have a double, not int threshold#6188
onebeastchris merged 1 commit intoGeyserMC:masterfrom
onebeastchris:fix/doubles-in-preds

Conversation

@onebeastchris
Copy link
Member

Copilot AI review requested due to automatic review settings February 14, 2026 23:28
@onebeastchris onebeastchris merged commit 76dc374 into GeyserMC:master Feb 14, 2026
5 checks passed
@onebeastchris onebeastchris deleted the fix/doubles-in-preds branch February 14, 2026 23:28
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Fixes creation of normalized range-dispatch predicates so the threshold is treated as a double (matching the API contract) instead of being handled as an int, preventing type mismatch/runtime cast issues when using normalized damage/count predicates.

Changes:

  • Update RangeDispatchPredicate.Property.DAMAGE normalized predicate construction to pass a double threshold.
  • Update RangeDispatchPredicate.Property.COUNT normalized predicate construction to pass a double threshold.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

zxclimon pushed a commit to zxclimon/GeyserFork that referenced this pull request Feb 17, 2026
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.

1 participant