Uploaded image for project: 'Minecraft: Java Edition'
  1. Minecraft: Java Edition
  2. MC-268471

Jump Boost, Haste and Mining Fatigue status effects are not tied to their corresponding attributes

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • None
    • 24w06a
    • None
    • Confirmed
    • Commands

      Since the addition of some attributes in 24w06a, notably generic.block_break_speed, generic.safe_fall_distance and the refactor of generic.jump_strength, players are now able to achieve the effects of Jump Boost, Mining Fatigue and Haste via attributes.

      However, these effects and attributes are not directly tied to each other, unlike other effects and attributes such as Strength/Weakness with attack_damage, Speed/Slowness with movement_speed, Health Boost/Absorption with max_health/max_absorption or even Haste/Mining Fatigue with attack_speed.

      This causes an inconsistency with the previously mentioned effects and other issues:

      • block_break_speed and jump_strength attributes don't scale with Jump Boost, Haste or Mining Fatigue amplifiers.
      • Both of these attributes do not appear in potion tooltips, such as the Jump Boost potion.
      • Combined effects of high amplifiers + max value attributes allow you to exceed the upper cap (behavior-wise), which is not the case with other effects.

      Curiously, the recently added generic.safe_fall_distance is tied to Jump Boost as expected, so it shows the attribute in the tooltip and can't surpass the attribute cap.

      How to reproduce

      1. Execute the next command:
        /attribute @s generic.jump_strength get
        
      2. Notice the current attribute value.
      3. Grant the player the next effect:
        /effect give @s jump_boost infinite 1
        
      4. Execute the first command again.
      5. Notice how the value hasn't been changed.

            Unassigned Unassigned
            Chavamix700 syarumi
            Votes:
            7 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved:
              CHK: