Fix exact choice recipe book clicks

[Machine-Maker]

Fixes #7821

Anytime a recipe match is going to be computed by the server to try and place the recipe in the crafting area (grid, furnace, etc.), the recipe ingredients are looked at and any ingredients that are marked as "exact" are noted. When the inventory is accounted and unique int ids are created for each item type, any item that matches the exact ingredient tracked before is given an extra separate unique int id. Then that is used to calculate if the recipe is valid.

This also removes the need for the patch added here. This patch fixed shapeless recipes with exact recipe choices due to it uses the same StackedContents system. But now that that system has been integrated with the ExactChoices, we can just use the same thing there and it works.

Caveats

There are some client-side limitations that are unavoidable as far as I can figure. If you have an exact ingredient that has a custom display name, enchantments or a damage value, the client will show the recipe as red even if you can click on it and it will put the ingredients in the correct slots. This is because the client normally ignores items with names, damage, or enchants when calculating the ingredients for a recipe.

---

Download the paperclip jar for this pull request: paper-7822.zip

[Boy0000]

Tried building this locally to test myself but couldn't get it to work?
Atleast if its meant to have the autofill work with custom nbt items.

Recipe still only shows as "craftable" when non-nbt variant is in players inventory.
Clicking it with all the NBT items in the inventory does not autofill (manually placing them makes the recipe work ofc)
Unlike before though, the vanilla equivalent items are not autofilled when they are present

Clip below should show everything, triple checked the nbt of items in inv, the recipe ones and result items.
All were identical.

With patch:

nbt.mp4

Without:

2022-05-27.18-30-56.mp4

[Machine-Maker]

Items with damage values, enchantments, or custom display names do not work with auto filling. That isn't something this pr tries to fix. If you have custom nbt that isn't that, like custom lore, attributes, or something else it should work.

This now works with exact recipe choices, but note the caveats listed in the pr description.

[Boy0000]

Ah alright, kinda sad but seems to work atleast without displayname like intended.
Would this only be when the item registered in the recipe has a displayname?
So if i register the recipe with a clone of the itemstack but remove the displayname it would still work?

also when thinking about it yeah displayname and damage makes sense to not be taken into account 💀
forgot anvil renaming and enchanting was a thing apparently

[Machine-Maker]

So if i register the recipe with a clone of the itemstack but remove the displayname it would still work?

No. When the game tries to find stacks that match the recipe it just ignores itemstacks in your inventory that have a display name, enchants, or damage. It might be possible to address this in the future, but that's not what this PR does.

This now works, see Caveats listed in pr description.

[partydev]

I can confirm that this PR fixes #7821.

Previous behavior was that the correct recipe would not be sent to the player if it was marked as craftable. The material for the items in that recipe are sticks, so the recipe is seen as craftable by the client.

EDIT:

After 24 hours of testing, including running it on production, I have not seen any side effects from this PR's changes, and that the issue is fixed. I will continue posting updates.

EDIT:

After a a few days of production use, no issues stemming from this.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[Machine-Maker]

I wonder if there's some better way to track items like this, via some registering system for plugins to say, "This item should be treated separately in recipes". Right now, every unique nbt tag on an itemstack will create a separate id, and that could get rather big as there's really infinite nbt combinations.

[Machine-Maker]

Dramatically refactored this to an, imo, much better and more extensible system for predicate choice coming later. Details of how this works in PR description.