Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicMobs MythicMobs
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 134
    • Issues 134
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicMobsMythicMobs
  • Issues
  • #1899

Closed
Open
Created Apr 26, 2025 by DropExitJoin@DropExitJoin

~onDamaged triggers extra times and threat level way too high

Video

mythicmobsreport_compressed

Mob config file

https://pastebin.com/Jr0kw1Hr

Steps to reproduce

Use Purpur 1.21.4-2416, use MythicMobs 5.9.0-SNAPSHOT-824fd561 (this bug is very old, more than half a year), use default-generated MythicMobs folder, add my mob config file (see above), leave ImmunityTable: false (if you set ImmunityTable: true there is no issues), spam click this mob (see video)

Current behavior

When ImmunityTable: false, then ~onDamaged is triggered extra times when spam clicking (or just a lot of players hitting), so even if you set NoDamageTicks to 10, its possible to trigger ~onDamaged 3 or more times per second (should be impossible). And as a result, <target.threat> damage counter is showing bigger amount than expected (it turns out as ~130 if spam clicking a mob with 100 health)

Intended correct behavior

~onDamaged shouldnt trigger more than 2 times per second (since default NoDamageTicks is 10) and <target.threat> shouldnt show way too high number (±5% margin of error is fine, but not +34% in my test case)

Edited Apr 26, 2025 by DropExitJoin
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking