Re-confirmed in https://mojira.dev/MC-306715
Could you please link the issue that duplicates this?
The current report.bug.mojang is quite shoddy compared to the old one.
Additional investigation showed
"amount": does alter the total number of trades per profession level. This doesn’t require addition of "replace" :true,
Only trades, from the same profession can be swapped between levels. This requires the addition of "replace" :true, to the start of the #data/minecraft/villager_trade/<profession>/<#>/ level_#.jsonExample: Chain Mail armor trades of the Armorer are able to be taken from later profession levels, and placed/offered as a Novice level.
No trade with a different file name, than those provided by default, are viewed as valid. Despite the file names and folders being correct, the error given will always be:Couldn't load tag minecraft:<profession>/level_# as it is missing following references: minecraft:<profession>/<#>/<trade.json> (from file/<datapack_folder_name>).
Can confirm issues present in 1.21
Can confirm in 1.21
Can confirm, this issue is present in 1.21. As well as the additional rendering issues detailed in MC-271100
Confirmed, in 1.21-pre release 2.
While this post misses out on the remainder of saddle/ride-able mobs, it is still present in 1.20.5 shown here in more detail: MC-271100 Specifically, this alternate bug includes the inconsistency shared by Llamas.
While this post misses out on the remainder of saddle/ride-able mobs, it is still present in 1.20.5 shown here in more detail: MC-271100 Specifically, this alternate bug includes the inconsistency shared by Llamas.
@jingly I don't believe the linked bugs reflect this issue accurately. Specifically the other do not include the mobs Strider, Trader Llams and their carpets.
Please un-mark this as 'duplicate' as this bug specifically identifies the carpets worn by Llama (both normal and Trader) as in consistent. If there are additional bug reports already in place including Llama's and their carpets, I'd be glad to link this report to there as well.
Thank you.
Could Mojang elaborate how this is 'works as intended'?
If the saved structure has a single water logged block (Say, a water logged stair inside of a pyramid) Why is it 'intended that loading said structure will alter every other stair/slab/fence/chest/ etc. to be water logged?
I believe most users would intend for the 'saved' structure to be loaded exactly the same as it was saved.
Still present in 26.1 snapshot 11. As shared here: MC-306714