Block and entity NBT information support

[ghost]

e.g. crop maturity, biological health, horse speed and jumping height, etc

[Minenash]

something like {nbt:<path>} I assume? That sounds cool

Edit: or {target_block_nbt:<path>} and {item:<slot>:nbt:<path>}

[ghost]

I think it can be like {target_block:nbt:<path>}, other attributes can also be changed to this. Just like {target_block:id} and {target_block:x}.

[Minenash]

It's {target_block_id}not {target_block:id} rn, but yeah. : is usually used for dynamic stuff, like slots, settings, time.

Unless you meant the _ should be replaced with the :. In that case, I've thought about, but that would require extra parsing, especially when the old version would be kept for compatibility, and the short versions are useful

[ghost]

I just think this object-oriented representation is better. If implementation is difficult, {target_block_nbt:<path>} and {item:<slot>:nbt:<path>} are also good choices.

[Minenash]

It's definitely better organizationly, and probably should've been the way I designed it in the beginning, but having two sets of things do the same thing is kinda meh, especially since the short versions would still be used. It also makes the documentation harder as it would have to convey both

[ghost]

These can be completed slowly. I think more features are needed now.

Perhaps you can refactor in v4.0. lol

[pyrocosm]

Would really love to see this. Block and entity NBT tags are a big part of the F3 menu for me (for checking if observers are powered, for seeing which stage of growth crops are in, etc.)