If that so, this one should be closed as intended
it may work
How to use the pack
use “Debug”
click “Editor Mode”
click “Item”
choose “Inventory” in the dropdown list, input “0” in the textfield, then submit
the value of the slider named after “Write” refers to the number of page you want to check, then submit
the first textfield is the content detected in this page. Please note, when getRawContent() returns {}, it is shown as {“rawtext”:[{}]} in the textField
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.
I may offer a pack that I’m currently developing. Still, it’s a functional error. So I don’t know if you may get a hint from it, since the component is gone and you want to make out whether the property is available.
Also, the issue affects any entities that use “minecraft:npc” component
It’s for cauldrons in the witch hut, I guess. They use loot table to define which type of potion is spawned in the cauldron.
Sure it will store in the nbt. But you may not read it via SAPI. Since SAPI provides the properties, they were intend to provide a way to read the UID via SAPI. However, the properties won’t work as intended.
I tried my best.
If you don’t understand the post, here’s a demonstration.