Deployed d01721e to 1.20.1 with MkDocs 1.6.1 and mike 2.1.3

Author: github-actions[bot]

1.20.1/Gameplay/Logistics/Machines/index.html

@@ -919,6 +919,23 @@
     </span>
   </a>
 
+    <nav class="md-nav" aria-label="Multiblock Machines">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#distinct-painted-and-filtered-inputs-and-outputs" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Distinct, Painted, and Filtered Inputs and Outputs
+      
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
 
         <li class="md-nav__item">
@@ -4339,6 +4356,23 @@
     </span>
   </a>
 
+    <nav class="md-nav" aria-label="Multiblock Machines">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#distinct-painted-and-filtered-inputs-and-outputs" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Distinct, Painted, and Filtered Inputs and Outputs
+      
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
 
         <li class="md-nav__item">
@@ -4420,6 +4454,36 @@ <h2 id="multiblock-machines">Multiblock Machines</h2>
 <strong>auto-export</strong> to any inventories, tanks, or pipes. This behavior can be toggled by Disabling the hatch, either through
 the power button in its UI or by right-clicking it with a Soft Mallet.</p>
 <p>Buses and Hatches can accept automated import or export from other sides, so long as something else is causing it.</p>
+<h3 id="distinct-painted-and-filtered-inputs-and-outputs">Distinct, Painted, and Filtered Inputs and Outputs</h3>
+<p>Under normal circumstances, <strong>all</strong> input Buses and Hatches and on a multiblock machine will be checked for recipe
+inputs, and all output buses and hatches will be used to place recipe outputs. However, this can lead to unwanted behavior
+where a user wants a single machine to do multiple recipes, but the ingredients to those recipes can conflict and be used
+to run an unwanted third recipe. Additionally, when a machine is being used like this, the output bus/hatch to which
+produced items/fluids are delivered is chosen somewhat arbitrarily, making it difficult or unwieldy to plan pipes to carry
+specific output products away.</p>
+<p>GTM offers three tools for this problem: Fluid Hatch Filter Locking, Distinct Buses and Painted Buses/Hatches.  </p>
+<ul>
+<li>Fluid Hatch Filter Locking is a simple system for resolving the problem of deciding what output hatches receive what
+produced fluids. Using the same interface as a Super Tank, a Fluid Output Hatch can have its current contained fluid
+Locked, meaning that only that fluid will ever be placed in it; or the Hatch can be pre-emptively locked to a fluid by
+dragging that fluid from JEI/EMI into the Hatch's output slot.</li>
+<li>Filter Locking only works with standard <em>single</em> fluid hatches, and cannot be done to the higher-tier Quadruple or 
+Nonuple Fluid Hatches. (However, those Hatches also cannot contain a single fluid in more than one slot, so they do
+still allow for some degree of output separation when used with Quadruple or Nonuple Fluid Pipes.)</li>
+<li>Distinct Buses is a toggle used on Input Buses (not Hatches), which causes the machine to look at this bus as being
+separate from all other Distinct Buses. (One distinct bus has no meaning, but two distinct buses on one machine will
+cause the machine to search each distinct bus separately).</li>
+<li>Painted Buses/Hatches are hatches which have been Painted using a can of spray paint. Input Buses/Hatches which have been
+Painted in the same color are looked at together by the machine searching for recipe inputs, but any items/fluids stored
+in buses/hatches with a different color are not used for the search. The isolation works the same as for Distinct Buses,
+but it allows for multiple buses/hatches to be searched together as a group.</li>
+<li>Prior to version 7.5.0, painting <strong>Output</strong> Buses/Hatches had no effect. Version 7.5.0 introduced machines pairing their 
+Painted Outputs to their Painted Inputs, such that if a recipe pulls items from a Painted Input, it can only output the 
+products of that recipe to a Painted Output of the same color (or an unpainted output).</li>
+<li>Buses and Hatches that are not painted, or not set to Distinct, are always fair game for the machine - Distinct and 
+Painted Inputs can always pull from other non-distinct and non-painted inputs; and recipes that used ingredients from 
+Painted Inputs can always send their products to non-painted outputs.</li>
+</ul>
 <h2 id="passthrough-hatches-and-the-cleanroom">Passthrough Hatches and the Cleanroom</h2>
 <p>The Cleanroom is a unique multiblock with unique restrictions. Because the Cleanroom must have solid walls, pipes, cables,
 and inventories outside cannot directly connect to machines inside. For this purpose, Passthrough Hatches exist.

1.20.1/Modpacks/Changes/v7.5.0/index.html

@@ -3409,6 +3409,28 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#painted-output-buseshatches" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Painted Output Buses/Hatches
+      
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#change-to-gtrecipe-constructor" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Change to GTRecipe constructor
+      
+    </span>
+  </a>
+  
 </li>
 
     </ul>
@@ -4425,6 +4447,28 @@
     </span>
   </a>
 
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#painted-output-buseshatches" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Painted Output Buses/Hatches
+      
+    </span>
+  </a>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#change-to-gtrecipe-constructor" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        Change to GTRecipe constructor
+      
+    </span>
+  </a>
+  
 </li>
 
     </ul>
@@ -4515,6 +4559,20 @@ <h2 id="lamp-predicates">Lamp Predicates</h2>
 <p>Previously, lamps were not useable with the terminal in multiblocks. There are new lamp predicates that will help solve this problem.
 The predicate to use all lamps is: <code>Predicates.anyLamp()</code>
 The predicate to use a specific color is: <code>Predicates.lampsByColor(DyeColor.DYE_COLOR)</code>. Where DYE_COLOR is the name of the color you want.</p>
+<h2 id="painted-output-buseshatches">Painted Output Buses/Hatches</h2>
+<p>For some time, Spray Paint cans could be used to paint Input and Output Buses/Hatches on multiblock machines.
+Version 7.0.0  added the feature that Painted Input Buses/Hatches of different colors would not share their ingredients with
+each other when the machine ran recipes. This system is more fully explained at <a href="../../../Gameplay/Logistics/Machines/#distinct-painted-and-filtered-inputs-and-outputs">Painted Inputs and Outputs</a>.</p>
+<p>7.5.0 also applies this logic to Output Buses/Hatches as well. Input Buses/Hatches which have been painted are now only
+allowed to send their outputs to Output Buses/Hatches that are of the same paint color, or unpainted. This may cause
+existing setups to stop running, if they had painted Output Buses/hatches on them.</p>
+<h2 id="change-to-gtrecipe-constructor">Change to GTRecipe constructor</h2>
+<p>GTRecipe has had one new field added to it and its constructors: <code>int groupColor</code>. For new recipes, this parameter
+is set to <code>-1</code>; however for recipes that are being prepared and run, this field holds the Paint color of the 
+Painted Input Group that the recipe drew its inputs from.</p>
+<p>Addon mods which explicitly attempt to construct, copy, or apply their own ModifierFunctions to a GTRecipe 
+(not using the standard builder or kjs functions) will need to either add the additional <code>int</code> parameter to the end of 
+their constructor calls, or the additional <code>recipe.groupColor</code> to their copy calls.</p>