JWForever5504

Although since this bug was already inconsistent, I hope that someone else can confirm that it isn’t happening anymore.

It seems to be resolved.

I only have an online character, and I have experienced both in singleplayer and multiplayer. Switching melee weapons from the sculker claws to something else (specifically the Emerald Hammer) fixed the issue. I had a Death Cap Mushroom in slot 1, a Powershaker in slot 2, and a Turtle Master’s Mandolin in slot 3. Only the first 2 were affected, despite all 3 being spammed during melee fighting.

Why hasn’t this been reopened. Isn’t it supposed to be reopened automatically when someone sends a message like what I did?

MCD2-135 is the earliest report I found on this

I know I’m not the original reporter, but here’s what I have found.

Steps to Reproduce:

1. Equip Skulker Claws

2. Start fighting mobs and using artifacts.

Observed Results:

• Sometimes it takes a bit, but eventually, some artifacts will become unusable and flash red even if the cooldown is done and you have enough souls

Expected Results:

• Artifacts remain usable when cooldowns are complete and you have enough souls.

This is related to or a duplicate of MCD2-135.

This is related to or a duplicate of MCD2-135. I’ve also only ever seen videos of it when the player has sculker claws equipped. Is that the case for you?

This is related to or a duplicate of MCD2-135.

The second issue is related to or a duplicate of MCD2-135. I’ve also only ever seen videos of it when the player has sculker claws equipped. Is that the case for you?

Every video I’ve seen of this issue involves a player with sculker claws equipped. I feel like that is notable.

Related to or a duplicate of MCD2-135

I just did another one, and it spawned properly, so this isn’t consistently the case.

This may be related to or a duplicate of MCD2-135

Due to OP’s inactivity, I created an example behavior pack. It works in 1.21.100 with no experiments enabled. I would also be willing to take over control of this report if that is deemed reasonable.

When I interact with this tamed wolf, I receive an error saying that the property “tamedToPlayer” is undefined. I have it set up to send a chat message when I have interacted, and the result of tamedToPlayer, tamedToPlayerId, and isTamed The script file is below, in addition to the behavior pack.

world.afterEvents.playerInteractWithEntity.subscribe((event) => {
    world.sendMessage('interact')
    const tamedToPlayer = event.target.getComponent("tameable").tamedToPlayer
    const isTamed = event.target.getComponent("tameable").isTamed
    const tamedToPlayerId = event.target.getComponent("tameable").tamedToPlayerId

    world.sendMessage(`tamedToPlayerId: ${tamedToPlayerId}`)
    world.sendMessage(`tamedToPlayer name: ${tamedToPlayer.name}`)
    world.sendMessage(`isTamed?: ${isTamed}`)
})

I believe marking this as Working as Intended is not a great decision. Using text formatting codes allows us to make things unique. As an add-on creator, I use it in the description of an add-on to emphasize certain information. Without this, I lose a vital piece of communication with add-on users.

Affects 1.21.92

This affects Preview 1.21.100.20

This is not an issue in the latest Preview version, 1.21.90.27. I’m not sure which version it was originally fixed in.