mojira.dev

nottellingyou

More than one avatar was detected! There might be multiple accounts sharing this same name.

Assigned

No issues.

Reported

MC-208254 High-level potion effects return to level 1 upon reentering a world Duplicate MC-191880 Error with item tags in advancements Invalid MC-191169 Skeletons attempt to use melee attacks when wielding bows Awaiting Response MC-186130 Entering a world with a datapack that has already been loaded once requires /reload again Duplicate MC-185859 Items (The entities) become invisible when you pick them up Duplicate MC-180765 Attack Knockback attribute doesn't work on items. Duplicate MC-177264 Entities die when you modify their health using /execute store Cannot Reproduce MC-170624 Other than traditional helmets, items are not visible when placed in the head slot of giants Duplicate MC-166939 /execute store not working in 1.15+ (Snapshots, prereleases, etc.) Duplicate MC-103141 CRASH Invalid MC-103055 CRASH CRASH CRASHITY CRASH Incomplete

Comments

Sorry for the messy report, english is not my first language. Thank you for editing it.

I can confirm that this is still present in 20w51a.

This bug is present in 1.16.4.

The commands i used can now be found at the end of the report.

No, as it says in the report, i used /attribute to change my Attack Damage base from 1 to -1, therefore the calculation would be -1 + 3 = 2, and 2 would be the correct display value, while 4 is wrong.

Players have a base Attack Damage of 1, this is why you can punch mobs with a bare hand and deal 1 damage. With a Wooden Sword, players deal 4 damage. 4 - 1 = 3, so a Wooden Sword adds 3 Attack Damage.

MC-113552 relates to items with custom modifiers (Acquired via commands) displaying those modifiers instead of the player's actual stats. This issue relates to unmodified vanilla items (Acquired via Survival gameplay or Creative Inventory) displaying incorrect values, specifically the Attack Damage attribute.

I feel like an idiot. Never knew that '"tag":' was a thing, couldn't find a mention of it anywhere. I assumed it would be "item: "#whatever" because that's the way it works with entities. Don't know if that counts as an inconsistency, but consider this "bug" resolved i guess.

In advance, sorry for wasting your time.

Sorry, didn't see your second comment, internet is a bit slow. Some were spawned via command, others were spawned with eggs, but judging from the discovery above, i don't think it plays a role.

It would seem as though the issue is caused by the entity constantly getting the Health value altered via a datapack i'm making. I am fully aware that you can just disclose this post because of this, but i still don't see why this command would cause the skeleton to have incorrect behavior.

execute as <selector(Skeleton)> store result entity @s Health double 0.001 run scoreboard players get @s <score>

All instances were spawned in by myself. Also, i just noticed that they hold up their bows as they are supposed to do when they have immunity frames, although they still attempt to walk towards the player.