Expected behavior:
Component selectors check if all list items are present.
What actually happens:
The selector checks for order as well, which may be arbitrary.
To reproduce:
Take 2 bundles and 2 of any 2 stackable items.
Place 1 of each item into both bundles, in different orders.
Run the following command. Only 1 of the bundles is matched.
/clear @s bundle[bundle_contents=[{id:"itemA"},{id:"itemB"}]] 0
Note:
I believe that testing for order can be useful as well (e.g. place items into a bundle in a specific order to enter a password), so perhaps a way to do both is needed.
Thank you for your report!
After consideration, the issue is being closed as Working as Intended.
Please note, that mechanics of the game may change between updates.
Things such as graphics, sounds, world creation, biomes, redstone, villagers, and animals may not work the same in current versions.
Full Version History – Snapshot Version History – The official Minecraft feedback site
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support (Technical Issues) – 📧 Microsoft Support (Account Issues)
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki