First things first: THIS IS NOT A MOD, its a Script!
Scripts are loaded inside a Programmable Block that you place In-Game!!!
DO NOT, UNDER ANY CIRCUMSTANCES INSTALL IT SERVER SIDE, your game will throw errors!
now to the actual installation part:

1. Make sure that you enabled In-Game Scripts inside the world settings!
   
2. Place down a Programmable Block In-Game
   
3. Open the Control Panel of the PB and Click the Edit Button.
   if the Edit Button is greyed out, that means you dont have In-Game Scripts Enabled!
   
4. Click on Browse Scripts and search for GOAT Sorter
   
5. Double Click on the Script to install it
   
6. Click Ok and the script will boot up
   
   
7. the script will prompt you to build a LCD screen tagged with !StatusScreen, only normal LCD panels like the Text Panel, LCD Panel, Wide LCD Panel, Transparent etc work, perhaps in the future we will support mutli panel LCD screens for the Status Screen.

By Default, the Script Categorizes Items after the following Categories:
(sorted by personal preference)

• Ores
  
• Ingots
  
• Components
  
• Tools
  
• Ammo
  
• Consumables
  
• Foods
  
• Ingredients
  
• Seeds
  
• Misc

These are the default Categories which are used for all Vanilla Items and will only be needed if the script sees an item that belongs into that category. the [StatusScreen] will show you if a category is missing a container.
To sort these items into containers, add the Category to the name of your desired container.
Example Cargo Container Names:
as long as the Category name is inside the cargo container name, the script will try to sort the items into that container.

You can add or change Categories how ever you want, for that read part: The Custom Data

any undefined Item (modded items that dont have a clear category) will be added to the Misc category, which you can then later change in the custom data of course.

The Stock Container allows you to define a desired amount of items to be stored in that Inventory.
by adding [Stock] to the name of a Cargo Container, the script will populate the custom data of the container with a list of known items.
Changing the number after the = sign will store the amount inside the container.
There are also modifiers to alter the behaviour of the Item to be Stocked.
Examples:
This will keep 100 Steel Plates inside the Container, removing any excess that are above 100.

This will always Add 100 Steel Plates, but it will never take out excess amounts of Steel Plates.

This will never add Steel Plates automatically, but will only remove excess amounts of Steel Plates.

This puts all available Steel Plates inside untill the Container is Full, never removing any excess.

Pins the Item to the Top of the Stock Container List, that way its easier to find the Adjusted values.
Can be Combined with other Modifiers, you just need to add P after the other Modifers.

Note: the custom data will show the defined Item names and Categories that are written in the Custom Data of the Programmable block, so if you changed a item name, the old name in the Stock container will be updated to the new one while also keeping the set amount.

you can edit, or add tags for the [Stock] Container function inside the Script Settings.
Example:
make sure that you get the formatting right!

By adding [Locked] to the name of a Cargo Container, the Script wont touch Items that are stored within this Container.
Usefull if you want to keep Items stored without the Script touching those items.

Note: Assemblers and other machines that have "Automatic Push/Pull" enabled are still able to take out items of that Container, nothing we can really do there :/

To hide items amounts inside a container from the current item amount of the Autocrafting Panel, add [Hidden] to the Container name

you can edit, or add tags for the [Hidden] function inside the Script Settings.
Example:
just make sure that you get the formatting right!

The Script allows you to define Priorities for Type Containers and Stock Containers.
By adding [P:<number>] to the name of either a [Stock] or Type container, you can set its Priority.
Default Priority for non Priority defined containers is 0, and higher numbers have higher Priority.
Example:
this also works for [Stock] Containers, same rules apply.
higher Priority will be filled first (until quota is matched)

Since Reactors, O2/H2 Generators and Irrigation Systems are Important for life sustain, they have a Priority of 100.
so if you want to put Ice in a Cargo Container as backup for something else, make sure that you give it a Priority higher than 100.

Docking Priority is a important feature for the sittuation, where a Ship that runs GSIM Docks to a Station that also runs GSIM.
the script that has the higher priority set in the custom data of the Programmable Block that runs GSIM will take over and the one with the lower Priority will be paused untill it disconnects from the grid.
these are the default values which will be assigned at the first start of the script:
remember: higher number = higher priority!
If the priority is the same on both sides, none of the Scripts will be Paused!

Regarding [No GOAT], if 2 grids dock via a connector that has [No GOAT] in its name, none of the scripts will be paused!

By Default, the script sorts and manages connected grids, meaning if a ship connects to a station running the Script, non tagged containers will be emptied out, stock containers will be filled, O2/H2 generators and Reactors will be filled as well.
but if you dont want that you can add these tags to the name of either one of the connectors.

This will stop the Script from Sorting Containers but it will still fill [Stock] containers, O2/H2 Generators and Reactors.
If the Connected grid has GSIM Installed, Docking Priority will decide which Script will Pause

This will completely Stop the Script from Interacting with the Connected grid.
If the Connected grid has GSIM Installed, Both Scripts won't be Paused!

Remember, you can add these tags to both sides of the Connector!
You can also add or change these tags inside the Script Configuration part.

The Custom Data is a big part of this Script.
It stores all the Information about the Item Names, Item Categories, Crafting Blueprints, and some Internal things to be able to show them on LCD Screens like Oxygen, Hydrogen and Power levels.

The First section of the custom data shows you how the Items are written / stored inside the custom data.
all Items inside the Custom data are sorted after Categories first and then Alphabeticaly.

so, steel plates are defined like this:
You can edit the first 2 things, Name and Category.
Changing the Name will change the referenced item on the Autocrafting Screen, Inventory Screen, Stock Container and other places where you would reference or see the item.
meaning, if you change SteelPlate to Plate, it would show up as Plate on the Autocrafting Screen, Inventory Screen and even in the custom data of a [Stock] Container.
this works retroactively for Stock Containers and Autocrafting Panel so you wont have to re-adjust those values.
But for Inventory screens (not autocrafting) you would have to define the newly used name to display that item again.

Changing the Item Category to either one that already exists, or a new one,
will make it so that it gets sorted and listed under the new defined category.
for example: Changing the category of Algae from Ingredients to Ores, would store and list them under Ores

The Script stores Internally Tracked things like Hydrogen and Oxygen here.
you can add your own gasses if you want to display them on a Inventory LCD screen.
Example: DeuteriumGas, from the Life'Tech-Powers (Multilingual) Mod
once you added this to the Internals Section, you can show the amount of stored DeuteriumGas on Inventory Screens by just writing DeuteriumGas in the Inventory Screen.

Autocrafting allows you to automatically assemble or disassemble Items by a defined amount.
to get started, place down a LCD screen and add [AutoCrafting] (case sensitive!) to the name of the LCD screen.
only Single display LCD screens, that allow you to press F on them to open the Text section should be used. that way its easier to configure the LCD screen. (Text Panel, Wide LCD Panel, Corner LCD)
those LCD screens can be rotated using the rotating function. (very usefull for a horizontally placed wide LCD screen).

once the script cycled through a whole script cycle, the screen will show items that the script knows how to craft.
you can change the wanted numbers, by pressing F on the LCD panel to get to the EDIT Text screen.
here just change the number after the / to what you want the script to craft.
If in any case you want to access the text section outside of the screen F interaction trigger, you can do this by looking in the control panel of the AutoCrafting screen and change its content from app to text and images, then you can press the Edit Text button and adjust your values. the script will switch back to App once it cycles through.

Autocrafting modifier allow you to enable autodisassembling, define yield amounts per craft,
you can combine these modifiers in order to assemble and disassemble items.
for that just add AD after the wanted number (without a space)
Examples:

If you want items to be disassembled, you have to switch at least one Assembler to Disassemble in its Production tab

there are a few settings that you can adjust inside the Custom Data of the AutoCrafting Screen.

You can Extend the AutoCrafting main screen by adding [AutoCraftingExtension:#] to the name of secondary LCD screens where the # needs to be replaced with a number between 0 and 9.
That way you can display all craftable items but the secondary LCD screens cant be used to adjust the AutoCrafting values, you can ONLY do that on the main panel.

The Script looks at the Quotas that need to be fulfilled and will queue the wanted items by priority based on how far away the current amount is from the wanted amount.

we clear out Assembler queues and re-queue them to keep things organised.
so dont be surprised if you hear your assemblers do the "pling" sound every script cycle while items are needed.

The Script features a Learning Mode which will pause the normal Script execution so it can concentrate on fast and efficient Item Learning without you having to wait for a full script cycle.

In order to bring the Script into Learning mode,
you just need to write learning toggle into the script argument field and then press Run


the script will show you that its in script mode via the text screen of the programmable block (not the LCD screen)

assemblers will turn on "show on hud" and will have "is learning" in their name once they are ready to learn items.



once in learning mode, you just need to head to the production tab,
select a assembler that has "is Learning" in its name and then queue 1.000 of the item that you want to learn by holding ctrl + shift and left click on that item.
the script will empty the queue and the output once it successfully learned the item.
then you can start learning a new item.

The Learning process works by the Script looking at the Queue of the Assembler, and what lies in the Output of that Assembler.

In order to turn Off Item Learning, just run the same Script Argument again. learning toggle
Alternatively, the script resumes normal execution after 300 seconds as a safety measure.

Dont queue multiple item types at once, otherwise the learning wont work!
Only learn one Item at a time in 1 Assembler.
After the Script learned that item, it will empty out the queue and empty out the Output.
Another very important thing is, that the OUTPUT of the assembler NEEDS TO BE EMPTY AFTER EVERY LEARNED ITEM!!
or else you'll run into item blueprint mismatches, meaning the script will craft the wrong item for what you actually want.
If the Output wont get emtpied by the script, you might not have the needed type container and or space left in the needed type containers.


The Script features a Internal Item library where we added all Vanilla Items besides the Prototech Stuff. Meaning, if the Script sees a new Item, it will first go through that library and if it finds that Item inside the library, it will know how to craft it, so no need to teach the Script Vanilla Items!

Modded Items however need to be Learned manually!

The Script has 2 Refining Modes.

First one is Quota Refining,
this will refine the required Ingots to fullfill the wanted quota on the AutoCrafting Screen.
Quota Refining always comes before Automatic Refining as long as a quota of a Ingot is NOT fulfilled (and ore for that Ingot is available)

The Second one is Automatic Refining.
We Compare your Stored amount of Ingots with Each other and their corresponding yield factors and then decide what to refine.

we recommend leaving Ingot quotas at 0 to let the Script refine everything depending on your needs!

Changing a Ingot quota will make it so that the script prioritises this Ingot before the Automatic refining kicks in no matter how much of the other Ingots you have.

the calculation works like this:
in this case, since Iron Ingot has a lower coefficient compared to Cobalt and Platinum, Iron ore will be refined first, and once its on paar with Cobalt, both will be refined, first a bit of iron till it overtakes cobalt, then a bit of cobalt and so on till it meets platinum.

this also works with modded ores that yield more than one ingot, but important is that the script knows the yield rates of that ore. for that use the ore learning process.

we clear out refineries and re-fill them to keep things organised.
so dont be surprised if you hear your refineries powering down and back up again, this is normal.

The Script will prioritiese Scrap and Stone first so that your grids Inventory gets empty ASAP
We also Support Scrap from the AwwScrap mod, meaning that this Scrap will be refined first before the general refining mode starts.

The Refinery Handling works with Modded Ores!
So in order to tell the script what it can get from refining modded Ores,
you need to run it with learningOre toggle in the argument field.
The Script will then switch to the Ore Learning mode which will Automatically add 100 of unknown Ore to a Eligable Refinery to let that Refinery process the Ore.
Once the Refinery is done, the script will look at the output of the Refinery to see what came out of 100 Ore and that information will be added in the custom data of the PB running the Script.
so its basically Fully Automatic!

the refinery learning should stop itself once there is no ore left to learn.
alternatively you can run learningOre toggle again to stop the ore learning.
the learned values will only be added once the learning process has been stopped!
dont recompile the script, otherwise the learned data will be lost!

The Script fills Reactors and O2/H2 Generators with predefined amounts of Uranium and Ice.
The default values can be adjusted inside the Script Configuration near the top, under the Machine Managing section.
If you want to fill specific Reactors, O2/H2 Generators and or Irrigation Systems with Custom amounts,
just add the [Stock] tag to these Machines and set your amounts inside the Custom Data.

Note: The Script Deactivates "Automatic Push/Pull" for these Managed Machines.
That way they wont pull and or steal too many Items from your grid.
If you want to Exclude a Machine from Script Managing,
and perhaps want to enable "Automatic Push/Pull"
just add the [Manual] tag to the Machines name.

The Script Automatically Refills Hydrogen and Oxygen Bottles that are Stored in managed Containers (type and [Stock]) as long as a Hydrogen / Oxygen Tank is available filled with Gas.
The Refilling happens so fast, that we can only explain it as "Magic"
Just make sure that the conveyor path is available between the managed container and the gas tanks.
Bottle Refilling happens once every Script Cycle.

Since Reactors, O2/H2 Generators and Irrigation Systems are Important for life sustain, they have a Priority of 100.
so if you want to put Ice in a Cargo Container as backup for something else, make sure that you give it a Priority higher than 100.

If you want to Exclude certain Machines,
like Assemblers, Refineries, O2/H2 Generators, Reactors
so that you can use them manually
you just need to add [Manual] to the name of that block / Machine.
that way the script wont use this machine for things like Autocrafting, Ore Refining or balanced fuel filling etc.
It also allows you to enable "Automatic push / pull" again because usually the script turns it off so that these machines wont steal or overfill themselves with items.

By Tagging a (prefarably) Corner LCD Screen
that is placed next to a Inventory with [ContainerLevel]
You create a nice looking display that shows you your fill level of that Inventory.
this works for all Storage Containers and Gas Tanks.
you can change the settings of those screens by walking to them and pressing F on them.
there you can find things like which container it should show the level of and you can change the style for these screens.
there are 6 styles in total, just change the style= number to a number between 1 and 6

You can create custom Inventory Screens to display your desired items ona LCD Panel.
you can set these up in 2 ways,
The first way is to use a Interactable LCD screen where you can press F on when you stand in front of it, just add [Inventory] to the name of that LCD screen, then you can go into the edit text section by pressing of on the screen to set your things to show.

the second way is to add the universal [GOAT] tag to a multi panel LCD screen and then adjust the things inside the custom data of that screen.
for multi panel screens you have to start by defining your LCD screen and what exactly to show, this follows the same rule like Automatic LCDs 2
the 0 indicates which screen this should be shown to.

you configure both type of inventory screens the same way, meaning that if you write
into the text section of the interactable screen that is tagged with [Inventory] it will show the same things like the multi panel screen.

Available ways to Configure Inventory Screens:

you can use any of these images listed on this Sprite List[github.com]

The Following Command Arguments can be used for the script.
in order to use them, just write the argument in the argument field and press the run button.
or place down a button panel, cockpit or timer and add the PB running the script to the hotbar with the run option and define the argument there.

Q1: HELP, the Script keeps crafting X Item even though its quota is already fulfilled!
A1: this is a Item recipe error, meaning, the script needs A,
but thinks in order to get A it has to craft B.
take a loot at your [AutoCrafting] screen and check which Item has a Construction Icon next to its Icon and check if the amount number goes up or not.
if the number doesnt go up, you have to re-learn that item via the Learning method.
Guide section > Learning Items / Modded Items.

Q2: My Programmable Block Keeps Overheating / Damaged / uses too much Performance
aka PB Limiters or "how to slow down script"
A2: Turn on AutoThrottle and set the AutoThrottleTotalMs to the limit of the server,
or keep it at 0.5 which is the default value for most PB Limiters.
This will slow down the Script but will prevent it from getting Stopped by PB Limiters.

Q3: How to Refine X in X Refinery and Y in Y Refinery
A3: Either use Sorters and Prevent Ore from going to Refineries where you dont want your specific Resources to be refined in which will cause the [StatusScreen] to show a Warning but you can ignore it,
Or use [Manual] with [Stock] on your Refineries and set the Ores that you want to refine in those Refineries to =10000

If you have issues with the Script, you can place a LCD Screen and add [LogScreen] to the name of the LCD screen to display the Script logs.
Script actions and crashes will show up there.

If you have Issues, be sure to Join Our Discord Server[discord.gg]!