docs: add asciidoc docs for use with refinedsites

docs/pages/autocrafting/autocrafting-with-filled-buckets.adoc

@@ -0,0 +1,15 @@
+= Autocrafting with filled buckets
+
+Some crafting recipes may require a filled fluid bucket.
+To use fluids from your fluid storage to fill buckets, you can set up a xref:pattern.adoc#_processing[processing pattern] that has following inputs:
+
+- 1 empty bucket
+- 1000 mB of the fluid of your choice
+
+For the output:
+
+- 1 filled bucket
+
+Put that in a xref:crafter.adoc[] that faces a bucket filling machine (link:https://teamcofh.com/docs/thermal-expansion/fluid-transposer/[that for example Thermal Expansion has]).
+Refined Storage will output the fluid from your fluid storage, and, an empty bucket.
+It is up to the external machine to fill it.

docs/pages/autocrafting/crafter-manager.adoc

@@ -0,0 +1,32 @@
+= Crafter Manager
+:icon: crafter-manager.png
+:from: v1.5.33
+
+The Crafter Manager is a block that allows you to see all your xref:pattern.adoc[patterns] in one GUI.
+
+== Naming
+
+All the xref:pattern.adoc[patterns] are listed and categorized per xref:crafter.adoc[].
+The categorization is based on the name of the xref:crafter.adoc[].
+
+To decide which name a xref:crafter.adoc[] gets, the following rules (in order) are used:
+
+1. If the xref:crafter.adoc[] is renamed with a Minecraft link:https://minecraft.gamepedia.com/Anvil[Anvil], use that name
+2. If the xref:crafter.adoc[] is connected to a machine in the world, use the name of that machine
+3. Use "Crafter" as name
+
+== Sizes
+
+One can configure the Crafter Manager size:
+
+- Stretched (default)
+- Small
+- Medium
+- Large
+
+When choosing the stretched size, the Crafter Manager will take up all the vertical screen space.
+This can be limited through the `maxRowsStretch` config option.
+
+include::../../partials/search-box.adoc[]
+
+include::../../partials/recoloring.adoc[]

docs/pages/autocrafting/crafter.adoc

@@ -0,0 +1,37 @@
+= Crafter
+:icon: crafter.png
+:from: v0.6.0-alpha
+
+The {doctitle} is a block that crafts items with xref:pattern.adoc[patterns].
+It can take xref:../upgrades/speed-upgrade.adoc[speed upgrades] to increase the crafting speed.
+
+With processing xref:pattern.adoc[patterns], the {doctitle} has to face the correct input side of the machine.
+
+[#_chaining]
+== Chaining
+
+A {doctitle} can be chained by letting them face each other.
+
+This is useful when connecting a {doctitle} to a single machine.
+When you run out of slots in your first {doctitle}, the one facing the machine, you can put another {doctitle} behind the first {doctitle} to get additional xref:pattern.adoc[] slots.
+
+== {doctitle} modes
+
+The {doctitle} has 4 modes:
+
+- Ignore redstone signal (default)
+- Redstone signal unlocks autocrafting
+- Redstone signal locks autocrafting
+- Redstone pulse inserts next set
+
+The (un)locking mechanism is used to block the {doctitle}, so it can't insert items or fluids into the connected inventory.
+
+"Blocking mode" can be achieved with the "Redstone pulse inserts next set" mode.
+
+See xref:locking-and-unlocking.adoc[] for more details.
+
+include::../../partials/recoloring.adoc[]
+
+== Applicable upgrades
+
+- xref:../upgrades/speed-upgrade.adoc[]

docs/pages/autocrafting/crafting-monitor.adoc

@@ -0,0 +1,31 @@
+= Crafting Monitor
+:icon: crafting-monitor.png
+:from: v0.6.0-alpha
+
+The {doctitle} is a block that shows all the current running crafting tasks and how long they have been running.
+
+Each crafting task can be cancelled manually.
+It is also possible to cancel all crafting tasks at once.
+
+Per task, it shows a grid of cells, each containing information about how an item or fluid is used in the crafting task.
+This is what the terminology in those cells mean:
+
+- Stored: the item or fluid is stored in the internal inventory of the crafting task, and will be used later on
+- Missing: the crafting task cannot continue without this item or fluid as it's missing
+- Processing: the item or fluid displayed is currently inserted into an external machine and is processing
+- Scheduled: the item or fluid is scheduled to be made by inserting it's ingredients in an external machine later
+- Crafting: this item is being crafted (regular crafting, not processing)
+
+== Sizes
+
+The size of any {doctitle} can be configured as well:
+
+- Stretched (default)
+- Small
+- Medium
+- Large
+
+When choosing the stretched size, the {doctitle} will take up all the vertical screen space.
+This can be limited through the `maxRowsStretch` config option.
+
+include::../../partials/recoloring.adoc[]

docs/pages/autocrafting/fluid-autocrafting.adoc

@@ -0,0 +1,27 @@
+= Fluid autocrafting
+
+So far you've set up autocrafting for items.
+Since Refined Storage has support for xref:../storage/storing-fluids.adoc[storing fluids] as well, it speaks for itself that Refined Storage can also autocraft with fluids.
+
+Every autocrafting pattern that uses fluids is a processing pattern.
+If you forgot, a processing pattern is a xref:pattern.adoc[] that outputs items to an external inventory and expects an output back, as declared in the xref:pattern.adoc[].
+
+With fluid autocrafting, you get the ability to make the xref:crafter.adoc[] output fluids (or items), and when the "result" fluid (or item) is back in the storage network, Refined Storage will detect the task and mark it as finished.
+
+This means that you can also declare fluids as an output in the processing pattern.
+It also means that you can request fluids from the xref:../viewing-resources/fluid-grid.adoc[].
+
+You can mix fluid and item inputs/outputs freely.
+
+== Creation of the mixed pattern
+
+To make a mixed (fluid or item) processing pattern, toggle the xref:pattern-grid.adoc[] in fluid or item mode.
+
+You can then use link:https://minecraft.curseforge.com/projects/jei[JEI (Just Enough Items)] transfer to transfer item and fluid ingredients.
+You can also use a filled fluid container (like a bucket) to specify the fluid.
+
+Use left or right click on the fluid slot to modify the millibuckets (mB).
+
+== Other resources
+
+- link:https://www.youtube.com/watch?v=6v-e_NdLEnI[Demo video]

docs/pages/autocrafting/getting-started-with-autocrafting.adoc

@@ -0,0 +1,87 @@
+= Getting started with autocrafting
+
+== What is autocrafting?
+
+Autocrafting is automated crafting through Refined Storage.
+
+You can already craft items manually using items from your storage network with the xref:../viewing-resources/crafting-grid.adoc[], but autocrafting makes it a tad bit easier and automated.
+
+Instead of manually moving items in the crafting matrix, you can make Refined Storage do all the work.
+
+== Patterns
+
+To teach Refined Storage a recipe to craft we use a xref:pattern-grid.adoc[].
+This xref:pattern-grid.adoc[] creates xref:pattern.adoc[patterns].
+
+A xref:pattern.adoc[] contains the recipe of the item you want to craft.
+
+== Pattern dependencies
+
+You need to create a xref:pattern.adoc[] for each sub-item you want automatically crafted.
+
+Refined Storage will first try to extract the sub-item from your storage, but if it isn't available, it will fall back to the xref:pattern.adoc[] of the sub-item to know how to create it.
+If there is no xref:pattern.adoc[] for the sub-item, the sub-item will be displayed as "missing" and the autocrafting task can't run.
+
+== Example
+
+You want to autocraft link:https://minecraft.gamepedia.com/Chest[chests].
+
+- Create a xref:pattern.adoc[] for the chest
+- Create a xref:pattern.adoc[] for the wooden planks that are used to craft the chest
+- If you don't create the pattern, and you have wooden planks, than Refined Storage will be able to use those
+- If you run out of planks, Refined Storage will not know what to do
+- If you don't create the pattern, and you don't have wooden planks, than Refined Storage will not know how to craft this item and the crafting task can't
+
+== Exact mode
+
+Exact mode is turned on by default which means every xref:pattern.adoc[] is an "exact pattern".
+This means Refined Storage takes items exactly as defined in the xref:pattern.adoc[]
+
+When Exact mode is turned off it will also match for other acceptable inputs for that crafting recipe (other types of wood, etc).
+
+== Crafters
+
+Once you created your xref:pattern.adoc[patterns], craft a xref:crafter.adoc[] and connect it to your storage network.
+
+In those xref:crafter.adoc[crafters] you'll store all your xref:pattern.adoc[patterns].
+
+== Requesting an item
+
+As soon as the relevant xref:pattern.adoc[patterns] to craft an item are stored in a xref:crafter.adoc[], you will be able to request the item through any xref:../viewing-resources/grid.adoc[].
+
+You can do this by clicking on the item you want to autocraft.
+If the item is already available and you want to request more of that item, you can use the CTRL + SHIFT key combination to open the crafting window.
+
+When requesting an item, Refined Storage will first ask how many of that item you want to craft.
+Then, it will show you what items it will take or craft.
+
+You can't start an autocrafting task if you have insufficient resources, unless you have the ability to autocraft those resources.
+
+== How autocrafting works internally
+
+Initially, when the autocrafting task is started, all the "initial" needed items and fluids are extracted from the storage network and inserted into the internal storage of the autocrafting task (crafting storage).
+
+All further actions to those items are performed in the internal storage, so the network doesn't "see" any changes while the task is running.
+
+Because all the subcrafts are done in the internal storage, the storage network can not "steal" items from autocrafting tasks.
+
+When an item is inserted through an xref:../input-and-output/importer.adoc[] or xref:../input-and-output/interface.adoc[], it will first go through the internal storage of autocrafting.
+That is prioritized.
+If the autocrafting task deems the item or fluid as necessary, it will be intercepted and the storage network will receive nothing.
+
+== Monitoring your crafting tasks
+
+Craft a xref:crafting-monitor.adoc[] and connect it to your storage network to see how the crafting task is progressing.
+
+You can also cancel autocrafting tasks from there.
+
+You can also use a xref:../wireless-networking/wireless-crafting-monitor.adoc[] to see the running crafting tasks remotely from your inventory.
+
+== Managing your patterns in a convenient way
+
+Want a convenient way to access all your xref:pattern.adoc[patterns] in the xref:crafter.adoc[crafters] of your storage network?
+Use the xref:crafter-manager.adoc[].
+
+== Speeding up your crafting tasks
+
+Insert xref:../upgrades/speed-upgrade.adoc[speed upgrades] in the xref:crafter.adoc[crafters].

docs/pages/autocrafting/index.adoc

@@ -0,0 +1,15 @@
+= Autocrafting
+
+- xref:getting-started-with-autocrafting.adoc[]
+- xref:processing-recipes.adoc[]
+- xref:keeping-items-in-stock.adoc[]
+- xref:fluid-autocrafting.adoc[]
+- xref:keeping-fluids-in-stock.adoc[]
+- xref:autocrafting-with-filled-buckets.adoc[]
+- xref:locking-and-unlocking.adoc[]
+- xref:pattern-grid.adoc[]
+- xref:pattern.adoc[]
+- xref:crafter.adoc[]
+- xref:crafting-monitor.adoc[]
+- xref:crafter-manager.adoc[]
+- xref:processing-pattern-encoder.adoc[]

docs/pages/autocrafting/keeping-fluids-in-stock.adoc

@@ -0,0 +1,14 @@
+= Keeping fluids in stock
+
+Keeping fluids in stock work the same way as xref:keeping-items-in-stock.adoc[keeping items in stock].
+
+Create a xref:../input-and-output/fluid-interface.adoc[] with a xref:../upgrades/crafting-upgrade.adoc[] in it.
+Then, specify the fluid that you want to keep in stock by clicking a fluid container (like a bucket) in the "out" slot.
+You can change the amount by left or right clicking on the fluid.
+The fluids will now be autocrafted if needed.
+
+To make the stocked fluids available to your storage network, create an xref:../storage/external-storage.adoc[] and put it on the xref:../input-and-output/fluid-interface.adoc[].
+Put the xref:../storage/external-storage.adoc[] in fluid mode.
+
+Make sure the xref:../storage/external-storage.adoc[] is in "extract-only" mode.
+That way, Refined Storage won't attempt to insert fluids in the xref:../input-and-output/fluid-interface.adoc[] that is meant for keeping in stock.

docs/pages/autocrafting/keeping-items-in-stock.adoc

@@ -0,0 +1,10 @@
+= Keeping items in stock
+
+Create an xref:../input-and-output/interface.adoc[] with a xref:../upgrades/crafting-upgrade.adoc[] in it.
+Then, specify the items that you want to keep in stock.
+The items will now be autocrafted if needed.
+
+To make the stocked items available to your storage network, create an xref:../storage/external-storage.adoc[] and put it on the xref:../input-and-output/interface.adoc[].
+
+Make sure the xref:../storage/external-storage.adoc[] is in "extract-only" mode.
+That way, Refined Storage won't attempt to insert items in the xref:../input-and-output/interface.adoc[] that is meant for keeping in stock.

docs/pages/autocrafting/locking-and-unlocking.adoc

@@ -0,0 +1,68 @@
+= Locking and unlocking
+:from: v1.6.6
+
+The xref:crafter.adoc[] in Refined Storage supports locking mechanisms.
+
+Locking and unlocking a xref:crafter.adoc[] only applies to processing recipes.
+
+The locking and unlocking functionality also has to be enabled by configuring the xref:crafter.adoc[] mode.
+
+== Crafter modes
+
+=== Ignore redstone signal (default)
+
+Ignores redstone signals.
+This is the default.
+
+=== Redstone signal locks autocrafting
+
+- If a xref:crafter.adoc[] is locked, it can't insert items or fluids to the connected inventory.
+- If a xref:crafter.adoc[] is unlocked, it can insert items or fluids to the connected inventory.
+
+=== Redstone signal unlocks autocrafting
+
+This is the opposite of the "Redstone signal locks autocrafting" mode.
+
+=== Redstone pulse inserts next set
+
+This mode was primarily introduced to support a concept called "blocking mode".
+
+Blocking mode is primarily utilised for processing recipes, where the machine that does the processing can only handle 1 recipe at a time.
+
+If the xref:crafter.adoc[] is in "Redstone pulse inserts next set" mode, this is the flow:
+
+- The xref:crafter.adoc[] will automatically go in an unlocked state
+- As soon as you request a recipe in this xref:crafter.adoc[], it will send out 1 set of items and fluids defined in the xref:pattern.adoc[]
+- The xref:crafter.adoc[] now goes in a locked state, and it won't push out any more items and fluids
+- The xref:crafter.adoc[] will stay locked until it receives a redstone pulse
+
+When you apply a redstone pulse:
+
+- The xref:crafter.adoc[] will unlock itself
+- The xref:crafter.adoc[] pushes the next set of items and fluids, if any
+- If there were any items and fluids to push, the xref:crafter.adoc[] will lock itself again
+
+Generally, you'd apply a redstone signal if the recipe you're processing has completed.
+It is up to the player to handle that.
+
+== Common mistakes with "Redstone pulse inserts next set"
+
+- Wrong redstone flow causes the xref:crafter.adoc[] to lock when it is supposed to unlock
+- When testing your contraption, accidentally locking the xref:crafter.adoc[] and then wondering why your xref:crafter.adoc[] doesn't process anything next time you request something
+
+=== Crafter deadlock
+
+If you use an xref:../input-and-output/importer.adoc[] on a chest to import the final processed item, and also using a comparator to send the redstone signal to the xref:crafter.adoc[] to unlock again:
+
+- If the xref:../input-and-output/importer.adoc[] imports too fast AND
+- the comparator doesn't pick up the item being in the chest AND
+- by not picking up the item, thus, not sending out a redstone signal
+
+You'd cause a deadlock because the xref:crafter.adoc[] doesn't receive a redstone pulse, and the xref:crafter.adoc[] would keep waiting forever.
+
+The solution for this is to only enable the xref:../input-and-output/importer.adoc[] AFTER the redstone pulse is sent to the xref:crafter.adoc[].
+Use the xref:../input-and-output/importer.adoc[] redstone settings to achieve this.
+
+== Other resources
+
+- link:https://www.youtube.com/watch?v=c9s-IfDPKxw[Demo video]

docs/pages/autocrafting/pattern-grid.adoc

@@ -0,0 +1,51 @@
+= Pattern Grid
+:icon: pattern-grid.png
+:from: v0.6.0-alpha
+
+The {doctitle} is the same as a regular xref:../viewing-resources/grid.adoc[], but also allows for the creation of xref:pattern.adoc[patterns].
+
+== Mode
+
+By default, the {doctitle} creates regular crafting xref:pattern.adoc[patterns].
+
+To create processing xref:pattern.adoc[patterns], toggle the "processing" checkbox.
+
+== Allowed tags
+
+The allowed tags system in Refined Storage allows the player to decide which items or fluids can be used as alternatives when the specified item or fluid isn't found in the storage network.
+
+These tags are retrieved from link:https://minecraft.gamepedia.com/Tag[Minecraft's tag system].
+You can specify the allowed tags in the {doctitle}.
+
+To define valid alternatives for an item or fluid, use CTRL + click on the input slot and specify the allowed tags that can be used during autocrafting.
+Items or fluids from that tag are then marked as valid alternatives if the original item or fluid can't be found in the storage network.
+
+You can also define valid alternatives by clicking on the item or fluid and then clicking on "Alternatives".
+
+== Ore dictionary (Refined Storage v1.6.x or lower only)
+
+To create ore dictionary sensitive xref:pattern.adoc[patterns], toggle the "oredict" checkbox.
+
+== Modifying a pattern
+
+You can re-insert a xref:pattern.adoc[] in the output slot to modify and (possibly) override it.
+
+== Recipe transferring
+
+The {doctitle} integrates with link:https://minecraft.curseforge.com/projects/jei[JEI (Just Enough Items)] so the player can use recipe transferring.
+
+You don't necessarily need the actual items in your storage network to create a xref:pattern.adoc[] for it.
+
+Refined Storage will notify you when you have a xref:pattern.adoc[] for an item configured when transferring a recipe.
+
+== Manual input/output configuration
+
+Click an item or fluid in the slots to configure the xref:pattern.adoc[].
+
+Click on the item or fluid to change the quantity.
+
+Use CTRL + click to modify the allowed tags for the input slot (Minecraft 1.14.4 and above).
+
+Use shift to clear the slot.
+
+include::../../partials/recoloring.adoc[]

docs/pages/autocrafting/pattern.adoc

@@ -0,0 +1,44 @@
+= Pattern
+:icon: pattern.png
+:from: v0.6.0-alpha
+
+A {doctitle} is an item that is used in autocrafting.
+It stores the recipe that should be autocrafted.
+
+A recipe can be assigned with the xref:pattern-grid.adoc[] and the {doctitle} is stored in a xref:crafter.adoc[].
+
+[#_processing]
+== Processing
+
+If the {doctitle} is in processing mode, it will push the inputs to the connected inventory of the xref:crafter.adoc[].
+
+== Exact mode (patterns in crafting mode)
+
+Exact mode is turned on by default which means every {doctitle} is an "exact pattern".
+This means Refined Storage takes items exactly as defined in the {doctitle}.
+
+When Exact mode is turned off it will also match for other acceptable inputs for that crafting recipe.
+
+Exact mode can't be set for patterns in processing mode.
+For processing mode, see the section about allowed tags.
+
+== Allowed tags (patterns in processing mode)
+
+The allowed tags system in Refined Storage allows the player to decide which items or fluids can be used as alternatives when the original specified item or fluid isn't found in the storage network.
+
+These tags are retrieved from link:https://minecraft.gamepedia.com/Tag[Minecraft's tag system].
+You can specify the allowed tags in the xref:pattern-grid.adoc[].
+
+== Ore dictionary mode (Refined Storage v1.6.x or lower only)
+
+The {doctitle} can be configured to be an ore dictionary pattern.
+Instead of extracting the exact item, it'll try to extract equivalent items according to the ore dictionary as well.
+
+== Clearing
+
+Use SHIFT + right click in your inventory while holding the {doctitle} to clear it.
+You can also override the {doctitle} in the xref:pattern-grid.adoc[].
+
+== Modifying
+
+You can re-insert a {doctitle} in the output slot of the xref:pattern-grid.adoc[] to modify and (possibly) override it.

docs/pages/autocrafting/processing-pattern-encoder.adoc

@@ -0,0 +1,21 @@
+= Processing Pattern Encoder
+:icon: processing-pattern-encoder.png
+:from: v0.6.0-alpha
+:to: v1.5.6
+
+[.alert.alert-warning]
+****
+The {doctitle} has been removed in v1.5.6 and its functionality has been moved to the xref:pattern-grid.adoc[].
+****
+
+A {doctitle} is used to create xref:pattern.adoc[patterns] meant for machine automation.
+
+It takes up to 9 inputs and 9 outputs, so the storage network knows what to take and what to expect.
+
+This block can't be connected to a storage network.
+
+== Recipe transferring
+
+The {doctitle} integrates with link:https://minecraft.curseforge.com/projects/jei[JEI (Just Enough Items)] so the player can use recipe transferring.
+
+When using this, Refined Storage will use the inputs and outputs that the link:https://minecraft.curseforge.com/projects/jei[JEI] recipe has.

docs/pages/autocrafting/processing-recipes.adoc

@@ -0,0 +1,47 @@
+= Processing recipes
+
+== What are processing recipes?
+
+So far, in xref:getting-started-with-autocrafting.adoc[] you learnt how to automate regular crafting recipes.
+
+What if you want to automate the creation of items that don't involve a crafting recipe, like ores to ingots in a furnace?
+
+For this you use processing xref:pattern.adoc[patterns].
+
+== Processing patterns
+
+You can create processing xref:pattern.adoc[patterns] in the xref:pattern-grid.adoc[] by toggling the "processing" checkbox.
+
+The GUI will change and it'll allow you to define up to 9 inputs and outputs.
+
+- Inputs is what Refined Storage will extract from your storage network.
+- Outputs are what Refined Storage expects back in the network when the item has processed.
+
+== Example
+
+Let's say you want to automate link:https://minecraft.gamepedia.com/Iron_Ore[Iron Ore] to link:https://minecraft.gamepedia.com/Iron_Ingot[Iron Ingot].
+
+- In the input section you put 1 link:https://minecraft.gamepedia.com/Iron_Ore[Iron Ore].
+- In the output section you put 1 link:https://minecraft.gamepedia.com/Iron_Ingot[Iron Ingot].
+
+== Inserting the pattern
+
+Make a xref:crafter.adoc[] and let it face the machine in a way it can input it in the correct slot.
+
+Insert the processing xref:pattern.adoc[] you just created in the xref:crafter.adoc[] facing the machine.
+
+When you now request the item, Refined Storage will insert the inputs in the machine.
+
+You do need to get the item manually back in the storage network so Refined Storage knows that the item has been processed.
+You can use any device to get the item back in the storage network, like an xref:../input-and-output/interface.adoc[] or xref:../input-and-output/importer.adoc[].
+
+== Allowed tags
+
+The allowed tags system in Refined Storage allows the player to decide which items or fluids can be used as alternatives when the original specified item or fluid isn't found in the storage network.
+
+These tags are retrieved from Minecraft's tag system.
+You can specify the allowed tags in the xref:pattern-grid.adoc[].
+
+== Chaining crafters
+
+You can xref:crafter.adoc#_chaining[chain crafters] to connect multiple xref:crafter.adoc[crafters] to the same machine.