NoDamageTicks does not work for arrows, multishot can deal 3 times of damage #4110

Unknownreported this bug

Jun 23, 2023 at 7:53 AM

Summary MythicMobs-5.3.2-SNAPSHOT#4557 vanilla arrow nodamageticks does not work for mythicmobs, multishot arrow, or custom plugin launch multiple arrow, hit the same mythicmob at the same time, all arrows can deal damage to the mob. But in vanilla, if an arrow is hit, other arrows cannot deal damage and will bounce off

Steps to reproduce

Given a bow with multishot

[Legacy attachment omitted] it will shot 3 arrows

[Legacy attachment omitted] if all 3 arrows shot to same mob (like melee attack), all 3 arrow will deal damage to same mob [Legacy attachment omitted]

Mojang/vanilla mobs will all bounch off arrows if is understand nodamageticks, so only 1 damage is deal to the mob, but for mythicmobs mobs, even tho the arrow bounce off, damage is still deal onto the mob.

Current behavior

more damage is deal

Intended correct behavior

Noodamage tick works again for all the mobs by default.

Server log file https://paste.denizenscript.com/View/111522

Debug log snippet no error

Proposed fixes add nodamage ticks to mobs

Unknowncommented

3 years ago

mob:
  Type: zombie
  Display: ''
  Health: 4000
  Damage: 1
  Options:
    MovementSpeed: 0.4
    AlwaysShowName: false
    PreventOtherDrops: true
    Despawn: false
    PreventRandomEquipment: true
    PreventJockeyMounts: true
    PreventItemPickup: true
    PreventRenaming: true
    PreventSunburn: true
    KnockbackResistance: 1
    FollowRange: 50
    silent: true
    NoDamageTicks: 20
  AIGoalSelectors:
  - 0 clear
  - 1 lookatplayers
  - 2 randomlookaround
  AITargetSelectors:
  - 0 clear
  Skills:
  - velocity{m=set;x=0;y=0;z=0;delay=1} @self ~onDamaged
  - message{m="&edamaged %math_ROUND(<skill.var.damage-amount>,4)%"} @PlayersInRadius{r=10} ~ondamaged
  - skill{s=damage_dummy_cancelevent;sync=true} ~ondamaged

Unknowncommented

1 year ago

Closing this due to inactivity and major version releases since. If this issue is still relevant, please re-open the issue with a modern-version server log, example configurations being used to test, and step-by-step info to reproduce the issue.

Core Plugins