Describe the feature

PATTERN PROVIDER

• New button called Crafting CPU Selection with 3 modes

1. Prefer Smallest Crafting Processor
   Crafting Requests of patterns ordered by automation will always use Smallest CPU that the request requires.
   Manual Requests that do not go through the CPU selection screen on this recipe will use Smallest CPU that the request requires.
2. Prefer Fastest
   Crafting Requests of patterns ordered by automation will always use the CPU with the highest amount of Co-Processors
   Manual Requests that do not go through the CPU selection screen on this recipe will use the CPU with the highest amount of Co-Processors.
3. Only Use Specific
   Only uses selected CPUs for any patterns in the provider.
   Opens up a button that let's you select between CPUs in your network.

CRAFTING CPUs

• New Option called Recipe Fill Mode

1. Fill from Network
   Recipes done by this CPU will take from the network that the CPU is connected to. An item must be in a cell or in an inventory connected to the network via Storage Bus.

This is the standard mode and what the CPU normally does

2. Fill from adjacent Inventories
   Recipes done by this CPU will only take from any inventories that the CPU is connected to. (Can take from Item P2Ps too)

This is the main sauce of the suggestion. Since it takes from any inventory, it may take from INTERFACES as well, allowing for patterns that use items from a specific sub network and not the main network.
An example of a setup done with this is having a Subnet carry all Raw materials and a separate network with all crafted components. Any auto-crafting requests by a CPU will only take from the Raw Materials Subnet to ensure that any components that are already stocked in the separate network will not be used by it.

3. Both
   Recipes done by this CPU will take from any inventories that the CPU is connected to as well as the network.
   Prioritizes taking from adjacent Inventories

• Memory card and CPU parity
  Allows the memory card to Paste settings into CPUs

• New Boolean Option called CPU Visibility
  Yes: This CPU can be used by Providers that have Prefer Smallest and Prefer Fastest as well as appear when issuing manual requests.
  No: This CPU can only be used by Providers that have Only Use Specific and the this CPU selected.

• Co-Processing Units increase item export rate (for Processing patterns) and can be adjusted in the CPU itself. (or Provider if that's more useful)

This goes with the case of Mekanism machines getting items inserted too slowly and having to use patterns with larger amounts (i.e 64 Redstone --> 64 Enriched Redstone)

Reasons why it should be considered

Allows more versatility in the way Providers behave and where they take items from. It would also allow implementing more features to CPUs so that certain settings are applied to all Providers that the CPUs are used on instead of individually changing settings on each Provider.

Additional details

No response