mingwangdada

Then introduce a new constraint?

This should be marked as resolved since EntityIsTamedComponent.tamedToPlayer has been added

It’s quite an old request so it may not so complete. But since someone had confirmed this could they help to improve this?

As I said in the report, there are 2 different values appear in the error log which should be the same.

To correctly show the log, it will be posted in 4 seconds after player join.

I see EntityHurtBeforeEvent.cancel and EntityHurtBeforeEvent.damage doesn’t work in 26.20

If you don’t understand the post, here’s a demonstration.

If that so, this one should be closed as intended

it may work

How to use the pack

1. use “Debug”

   [media: image-20260328-153753.png]

2. click “Editor Mode”

   [media: image-20260328-153845.png]

3. click “Item”

   [media: image-20260328-153927.png]

4. choose “Inventory” in the dropdown list, input “0” in the textfield, then submit

   [media: image-20260328-154208.png]

5. the value of the slider named after “Write” refers to the number of page you want to check, then submit

   [media: image-20260328-154458.png]

6. the first textfield is the content detected in this page. Please note, when getRawContent() returns {}, it is shown as {“rawtext”:[{}]} in the textField

   [media: image-20260328-154737.png]

the key code in line 678:

.textField({translate: "portfolioScreen.page", with: [String(pageNum)]}, {translate: "type:JSON"}, {defaultValue: book.getPageContent(pageNum-1)??`{"rawtext":[${JSON.stringify(book.getRawPageContent(pageNum-1)??{})}]}`})

Got it. So, should this happen?

Can confirm on Windows. It also affects when some experimental features were enabled

You want an example, that’s it. But I must clarify that I’m not asking for help on addon, I seriously consider it as a bug.

Also, if you regard it as incorrect usage of coding, please prove it with your correct code that it’s not a bug, but not to simply close my request.

@tryashtar

It’s not on my addon, even I tried to move it outside “on_damage”, I still received damage

Just ingore the code

,
                  {
                    "test": "has_equipment",
                    "subject": "self",
                    "domain": "main_hand",
                    "value": "custom:knife"
                  }

I currently cannot edit my report. So I can’t remove it

Actually, they acts the same when only one trigger exists

If you want a pack, here it is.

Sadly, it’s still a bug. It won’t be fixed until you find a way to access to the information of tamed entities after “minecraft:tameable” is removed from them.