mojira.dev

CreeperMagnet_

Assigned

No issues.

Reported

View all
MC-311222 NBT to SNBT data generators crash when attempting to convert old NBT files Fixed MC-296519 Using /data remove to remove the Offers.Recipes data on wandering traders does not save properly Community Consensus MC-277552 Wandering traders look smaller than in previous versions Fixed MC-270665 Previously damageable items with the damage component removed do not support higher max_stack_size component Invalid MC-270136 Thrown projectiles with custom_model_data do not maintain proper particles when breaking Fixed MC-270134 Loot table set_count function does not function properly when combined with max_stack_size component on items that have lower stack limits Invalid MC-269847 Shaped custom recipes for unstackable items with a max_stack_size result greater than 1 cause improper recipe book behavior Duplicate MC-269824 Disabling the enchantments component also prevents renaming items in anvil Community Consensus MC-268326 Mending can be applied to items with Unbreakable:1b Works As Intended MC-265278 Inconsistency between outlines in plains and taiga village map icons Works As Intended

Comments

This is no longer an issue as of 26.3-snapshot-3, when the suspicious gravel was removed entirely.

Can confirm.

[media]

Affects 1.21.2-pre3.

Affects 24w40a.

Seems to be resolved in 1.21. Not sure when this happened, but sitting/standing now runs the trigger properly. I don't think whoever marked 1.21 as an affected version checked properly.

This is still an issue in 1.20.6 and 1.21-pre2.

Ah. That's a little unintuitive. Should've read changelog closer. Please close this as invalid, replacing !damage with !max_damage works. 

Please mark this issue as invalid. Proper behavior can be observed if the set_count function is placed after the set_components function instead of before.

MC-268716 is definitely at least related, but I can't be sure if they have the same root cause or not.

I believe this is caused by the command expecting an integer immediately after (i.e. entity_effect1), rather than one space after. 

See screenshots comparing this and dust;

[media]
[media]

Can confirm.

I can reproduce this issue still in 24w06a. Please note that this affects only signed written books—I'll update the report to be more clear.

Confirmed for 1.20.4.

Can confirm in 1.20.4.

Can also confirm. @Dhranios, this is occurring in 1.20.5 snapshots, not 1.20.4. This is likely due to some of the changes surrounding interactions in that snapshot (see MC-267456)

This is working as intended—the requirements require the player to brush a suspicious block *and* pick up a sherd, hence "Brush a Suspicious Block to obtain a Pottery Sherd".

Affects 23w31a and 1.20.1.

This is also the case with any form of return run function, even when run from the chat command line.

Can confirm in 1.20-pre1.

This issue was fixed in 23w12a. Can no longer reproduce.

Load more comments