GOAT Sorter - Inventory Manager Guide

Space Engineers★ 4 · 110 ratings4.5k views264 favorites32 min readby KhodrinUpdated Jun 20View on Steam ↗

First time Setup

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:

Make sure that you enabled In-Game Scripts inside the world settings!
Place down a Programmable Block In-Game
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!
Click on Browse Scripts and search for GOAT Sorter
Double Click on the Script to install it
Click Ok and the script will boot up
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.

Basic Sorting and Item Categories

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:

Cargo Container Ores Ingots Container Components Storage Tools with Misc Foods, Ingredients and Seeds

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.

Balancing Single Type Containers

The Script now has a new Setting called RBTC which stands for ReBalanceTypeContainers.
line 144.
this will balance single type containers, meaning that if you have 2 Containers tagged with Ores, they will now try to balance themselves so that they have the same amount of items.
THIS ONLY WORKS WITH SINGLE TAGGED INVENTORIES!!!
meaning, if you have a container named Container Ores Ingots it wont work!
if we allowed that, it would make things much more complicated for us...
especially because of the fact that keens rounding function is broken...

[Stock] Container

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:

SteelPlate=100

This will keep 100 Steel Plates inside the Container, removing any excess that are above 100.

SteelPlate=100M

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

SteelPlate=100L

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

SteelPlate=all

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

SteelPlate=100P

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.

Editing the [Stock] tag

in line 68 you can edit, or add tags for the [Stock] Container function inside the Script Settings.
Example:

// Tags to mark Stock LCDs / Containers public static string[] SCT = { "!GSIM-Stock", "[Stock]", "MyCustomStockTag", "ShipStock", };

make sure that you get the formatting right!

!!!NEW!!! [Stock] Group via LCDs

With Version 1.2 of GSIM, the Script features a new way of [Stock] configuration that allows you to manage a whole group of Inventories as 1 Stock Container.

First thing you need to do is to add [Stock] to the name of a normal LCD Screen.
once the Display of the LCD updates, you can start editing the Text portion of the LCD screen.
(not the custom data)
In the Text section, you will see the new Stock Configuration, there you have to define which containers / inventories you want to be managed by this Stock LCD.
You can either write all Individual Container names,
or Group your containers before and write G:Container Group Name instead of all Individual names.

NOTE:
The LCD needs to be on the same Grid as the Cargo containers, otherwise it wont work properly

Example Configuration

@GOAT-Stock Definitions START ~~~~~~~~ Container List ~~~~~~~~ My Ship Cargo Container 1 Storage Box 2 Another Inventory 3 G:Grouped Cargo Containers ~~~~~~~~ Settings ~~~~~~~~ method=Priority rebalancePercentage=5 name=Awesome Stock Group ~~~~~~~~ Modifier Explanation ~~~~~~~~

once you defined the managed containers, the script will convert the given strings into the container ID, with a position relative to the LCD screen and the current name of that container.
Example after Conversion:

~~~~~~~~ Container List ~~~~~~~~ ID:88583844734476039|-4|5|0|My Ship Cargo Container 1 ID:98063861920052793|-1|5|0|Storage Box 2 ID:131838939560180954|-7|5|0|Another Inventory 3 ID:96811290583382215|-4|-5|0|Cargo Container Group 4 ID:98602179689815284|-1|-5|0|Cargo Container Group 5 ID:142324085250555866|-7|-5|0|Cargo Container Group 6 ~~~~~~~~ Settings ~~~~~~~~ method=Priority rebalancePercentage=5 name=Awesome Stock Group ~~~~~~~~ Modifier Explanation ~~~~~~~~

Once all this is done, you can start defining what you want to store in the Stock group, its the same like the normal Stock system just with the difference that all items will be sorted into all defined cargo containers.

Settings Explanation

method=Priority|Balance

Priority > Will fill the 1st Container in the Container list (in this case its My Ship Cargo Container 1), once its full the 2nd container (Storage Box 2) will be filled next and so on.
Balance > Will Balance all Items across all listed containers relative to their volumes.
this means, Large Cargo Containers will have more items than Small Cargo Containers.

rebalancePercentage=<number between 0 and 99>

this defines the amount of volume difference based on % need to trigger a re-balance for this Stock group. 0 will always try to rebalance.

name=Awesome Stock Group

This defines the name that references this Stock group so it can be used to display informations about this exact Stock group on Inventory screens.

Custom Data and LCD Configuration

The Custom Data of the LCD Screen allows you to change what you want to Display on the LCD Screen. the Screens come with a Default Configuration that can be changed.

List of Arguments for the Custom Data Margin=16 >>> Changes margin of text, the gap to the screen. NEEDS TO BE FIRST IN LINE Size=1.0 >>> Changes all text sizes after this line (can be used multiple times) StockStats >>> Shows Amount of Containers in this Group, and Last time it got updated. StockVolumeFull,Color=<Color> >>> Shows a bar that spans the full height of the screen depicting Inventory volume remaining capacity, Margin=0 is recommended StockVolume,Color=<Color> >>> Shows a bar depicting Inventory volume remaining capacity StockLevelFull,Color=<Color> >>> Shows a bar depicting how matched the stock list is: full bar = all items requested are there, Margin=0 is recommended StockLevel,Color=<Color> >>> Shows a bar that spans the full height of the screen depicting how matched the stock list is: full bar = all items requested are there StockList >>> Shows individual bars per item in the stocklist, depicting fulfillment of the demand

Color goes from 0-4:
0: Bar uses Screens Foreground Color
1: Green to Red
2: Red to Green
3: Foreground Color to Red
4: Foreground Color to Green
*If colorblind Colors are enabled, Red and Green will be replaced with the defined Colors

[Locked] Ignore Cargo Containers

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 :/

[Hidden] Hide Items from AutoCrafting Counter

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

Editing the [Hidden] tag

in line 76 you can edit, or add tags for the [Hidden] function inside the Script Settings.
Example:

// Tags to not count Items for the AutoCrafting Screen public static string[] HTS = { "!GSIM-Hidden", "[Hidden]", "Turret", "MyCustomHiddenTag", "Cannon", };

just make sure that you get the formatting right!

[P:<number>] Priority System

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:

Cargo Container Ores [P:5] >>> will be filled first Other Container Ores [P:2] >>> will be filled once Ores [P:5] is full Ores Storage >>> has no Priority, will be filled last

this also works for [Stock] Containers, same rules apply.
higher Priority will be filled first (until quota is matched)

Priority on Reactors, O2/H2 Generators and Irrigation Systems

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

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:

Large Grid Station=10 Large Grid Ship=5 Small Grid Ship=1

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!

[No GOAT] Ignoring Connected Grids

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.

[No Sorting]

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

[No GOAT]

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.

KNOWN ISSUE:

If you have a setup, that has a Rotor / Hinge / Piston AFTER a connector connection, the script wont see that grid. its a annoying issue that is currently too difficult to fix for us.
Example:

Main Grid > Hinge > Connector = Connector < Rotors / Hinge / Piston < 2nd Grid This doesnt work because it breaks at the Rotors / Hinge / Piston part that is after the connector. Main Grid > Hinge > Connector = Connector < 2nd Grid This does work with no issues. even if you add more Rotors / Hinge / Piston before the connector.

The Custom Data

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.

~Name~Category~TypeId~SubTypeId~Blueprint~

all Items inside the Custom data are sorted after Categories first and then Alphabeticaly. so, steel plates are defined like this:

~SteelPlate~Components~MyObjectBuilder_Component~SteelPlate~MyObjectBuilder_BlueprintDefinition/SteelPlate~

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

Internals Section

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 and another example for water, this works if you have some sort of water tank mod installed so you are actually able to store water

~DeuteriumGas~Gases~gas~deuterium~~ ~Water~Gases~gas~water~~

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 and Water to display Water.

[AutoCrafting] based on Priority!

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.

WARNING: you can only have 1 [AutoCrafting] screen per GSIM instance, or else AutoCrafting WILL BREAK!!!

Autocrafting Modifier

Autocrafting modifier allow you to enable autodisassembling, define yield amounts per craft,

A = Craft Items (this is default behaviour if no modifier is defined) D = Disassemble Items H = Hides item from the Autocrafting Display, but not from the Autocrafting settings. [Y:<number>] = defines yield per craft. (example: 10[Y:5] because 1 craft yields 5 items) [P:<number>] = defines a manual Crafting Priority. higher number = higher priority. (example: /10[P:5] this will craft this item before any other item. negative Priorities are possible. for example /10[P:-5] this will always craft this item after all others.)

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:

BulletproofGlass~~~~2000/2000 >>> This would only craft items BulletproofGlass~~~~2000/2000D >>> This would only disassemble, not crafting new items BulletproofGlass~~~~2000/2000AD >>> This would both craft new, and disassemble excess ModdedItemThatYieldsMoreThanOneItemPerCraft~~~~128/128AD[Y:8] >>> this item yields 8 items per craft, and we want to craft, disassemble it properly withouth the script getting confused that it yields more per craft. FruitSeeds~~~~10/0[P:1] >>> this will give seeds a priority of 1, that way they will always be crafted first!

Auto Disassembling

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

Adjustable Settings for the AutoCrafting Screen

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

More=14 >>> Don't touch this, the script handles this thing automatically. ScrollingEnabled=true >>> Allow the screen to Scroll through all Items FontSize=1 >>> Font Size, can be 0.5 for example to fit more Items on the Screen. Margin=16 >>> the amout of pixels between text and screen border. MinScrollWait=8 >>> amount of seconds to wait between scrolling ColoredIcons=false >>> apply the color changes to the icons as well (like it does with the text)

Extending 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.

How the AutoCrafting Priority Works:

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.
You can reverse this Priority System inside the Script Settings under "Adjustable Settings and Tags for Machines" category.

The Priority can be reversed inside the Script settings.
just set ReverseCraftingPriority to true

Note:

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.

Assembler Cleaning

we clear Assembler Inputs on 2 conditions so things wont get stuck.
first one is, if the inventory fills above 95%
second one is, if the assembler has items in its input but nothing queued.

Item Learning / Modded Items

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 learning 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.

IMPORTANT:

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.

Vanilla Items

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!

Alternatively, if you want to directly have every Item listed / Available on the AutoCrafting screen,
Run the PB with the addAllKnownItems argument.
This will also add all modded items if you have the GSIM Integration mod installed.

Modded Items however need to be Learned manually!

Refinery Management

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.
By that we mean that it ONLY refines the amount of Ore, that is needed for the wanted amount!
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.

Technical stuff starts here

the calculation works like this:

<Amount of Stored Ingot> / Yield factor = Ingot coefficient 1000 Iron Ingot / 70 = 14,28571429 1000 Cobal Ingot / 30 = 33,33333333 1000 Platinum Ingot / 0,5 = 2000 the Yield factor is the amount of Ingots you get from refining 100 of Ore that gives this Ingot

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.

Note:

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.
Another thing is the fact that the script only Refines Ores that are stored inside either a [Stock] or a type container (like Ores), we had to do it this way otherwise the script would want to refine Ores and or Scrap that arent reachable. for example inside a ejector system that is locked behind a outgoing sorter.

Scrap and Stone

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.

Refinery Learning and Modded Ores

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!

Reactor, O2/H2 Generator and Irrigation System Handling

By default, the script Groups and Balances Reactors, O2/H2 Generators and Irrigation Systems with their needed Items.
GSIM basically treats those Machines like a [Stock] LCD Group set to Balance with the only difference that it doesnt need a LCD for configuration and that the amount is relative to machine volume.
This saves a lot of Performance and Script space because we can re-use a already existing feature.
Since its easier for us to make a universal configuration, that fills all the machines relative to each other, you only get 1 number to configure your wanted amount.
The amount is relative of 1.000 Liter of volume.
Meaning, by default, normal 1 large block sized reactors, that have a volume of 1.000 Liter, they will get filled with 25 units of Uranium, and a Large grid Large Reactor gets filled with 200 units of Uranium because it has 8 times the volume of a normal Reactor (8.000 Liters).

TLDR:

Reactors, O2/H2 Generators and Irrigation Systems get filled and balanced based on their Inventory volume.
25 Uranium per 1.000 Liter of Volume.
2500 Ice per 1.000 Liter of Volume.

If you want to fill specific Reactors, O2/H2 Generators and or Irrigation Systems with Custom amounts,
Use the [Stock] System for them. Both the normal [Stock] and the LCD [Stock] group systems can work.

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.

Displaying Informations on [Inventory] screens

Inventory screens can display informations about the Reactors, O2/H2 Generators and Irrigation Systems Stock Group.
for Reactors the Stock reference name is Reactors and for the Gas generators its GasGenerators
Example [Inventory] Display

Margin=16 Size=1 Header=All Reactors Size=0.5 StockStats=Reactors Size=1 StockList=Reactors Header=All Gas Generators Size=0.5 StockStats=GasGenerators Size=1 StockList=GasGenerators

Bottle Refilling

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.

Priority on Reactors, O2/H2 Generators and Irrigation Systems

[Manual] Exclude Managed Machines

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 !GSIM-Manual or [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.

[ContainerLevel] Screens

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

[Inventory] Screens

You can create custom Inventory Screens to display your desired items on a 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 F 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

PUBLIC TEXT CONFIGURATION

using [Inventory], accessing the "Edit Text" part of the screen by looking at the LCD screen and pressing F to open the Public Text section. this is easier to access.

Header=Ingots Category=Ingots SteelPlate UraniumIngot Burrito Gravel

Write your Configuration in the Public Text section. NOT CUSTOM DATA, for that you need to use the custom data configuration (read below)

CUSTOM DATA CONFIGURATION

using [GOAT] as a tag, multi-panel screens allowed! (cockpits for example)

@0 GOAT-Inventory Header=Ingots Category=Ingots SteelPlate UraniumIngot Burrito Gravel

the 0 indicates which screen this should be shown to.
Configuration is the same between [Inventory] and [GOAT] Available ways to Configure Inventory Screens:

Margin=16 >>> Changes margin of text, the gap to the screen. NEEDS TO BE FIRST IN LINE <ItemName> >>> shows item with icon and number Size=1.0 >>> Changes all text sizes after this line HideEmpty >>> Hides empty items in Category List after this line ShowEmpty >>> Shows empty items in Category List after this line Header=<Text> >>> Displays a Header with <Text> and an underline Category=<category> >>> Shows all items of a given category Category=<category>,Offset=<number> >>> Shows all items of a given <category> but skips the first <number> entries ShortItem=<ItemName> >>> displays the just the Icon and amount of the given item Space=<number> >>> Adds <number> of empty lines IconBar=<item> >>> Shows the icon of the item together with a bar that shows current items compared to quota IconBar=<item>,Target=<amount> >>> Shows the icon of the item together with a bar that shows current items compared given <amount> Text=<text> >>> Just Displays one line of <text> CategoryLevel=<category> >>> shows a bar with the storage capacity of all storage containers that are tagged <category> DeltaItems >>> Shows all items that left, entered, got created, got consumed on the grid since the last script cycle Stonks >>> same as DeltaItems Icon=<item,iconPath> >>> shows the icon of a given icon or the direct icon from path Push=<distance> >>> pushes the output of the next line <distance> * font size pixels to the right BG >>> displays a grid background BG=<sprite>,Repeat=<repeat>,Opacity=<opacity> >>> displays sprite <sprite> as background, repeated <repeat> times with an opacity of <opacity>

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

Additional Arguments for the new Stock Group System

The Following Arguments can also be used on Inventory Screens, to Display Informations about the new Stock Groups:

StockVolume=<Stock Group Reference Name>,Color=<Color> >>> Shows a bar depicting Inventory volume remaining capacity of the Stock Group with the given GroupName StockStats=<Stock Group Reference Name>, >>> Shows Amount of Containers in this Group, and Last time it got updated. StockVolumeFull=<Stock Group Reference Name>,Color=<Color> >>> Shows a bar that spans the full height of the screen depicting Inventory volume remaining capacity, Margin=0 is recommended StockVolume=<Stock Group Reference Name>,Color=<Color> >>> Shows a bar depicting Inventory volume remaining capacity StockLevelFull=<Stock Group Reference Name>,Color=<Color> >>> Shows a bar depicting how matched the stock list is: full bar = all items requested are there, Margin=0 is recommended StockLevel=<Stock Group Reference Name>,Color=<Color> >>> Shows a bar that spans the full height of the screen depicting how matched the stock list is: full bar = all items requested are there StockList=<Stock Group Reference Name> >>> Shows individual bars per item in the stocklist, depicting fulfillment of the demand

Command Arguments

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.

Command Argument

Description

learning toggle

toggles the learning mode for assemblers

learningOre toggle

toggles the learning mode for refineries

resetIndex

resets all stored data of the PB (Custom Data) including ore Yields for modded Ores, Custom names and Custom / Changed Categories

removeNotCraftableBlueprints

Deletes all Stored Item Recipes that arent able to be crafted anymore.
This is very Usefull if you removed a Mod where the Script learned Items from.
That way you wont loose Items that can still be Crafted.
WARNING, will include all Items if you dont have assemblers on your grid that are able to craft that Item.
sub grid assemblers only count if you enabled the use of production blocks on sub grids.

addAllKnownItems

This Command adds all VANILLA Items from the Internal Item Library to the Script.
making every known Item Appear on the AutoCrafting screen without the script having to see that item first. If the GSIM Integration mod is installed, modded items will be added as well!

translateItemNames

This will translate all Item Names to their current translated displayname.
the translation depends on the set game language or server language if you use it on a server.
WARNING!!! This command only works if the GSIM Integration is Installed

Frequently Asked Questions

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

Q4: The Script cant Autocraft my Recipes that take too long because the queues get cleared constantly.
A4: we currently remove all assembler queues to then re-queue them with the correct priority of items needed.
sadly, this breaks recipes that take longer to craft.
the only way to currently somehow fix this is to increase "MinCycle" which you can find in the misc settings category of the script configuration but this doesnt help in every sittuation.
we do want to rework autocrafting in the future to better support items that have a longer crafting time. one option could be to be able to disable the queue clearing and priority autocrafting but we will have to see what we can do.
for now, either increase the MinCycle amount or use a !GSIM-Manual tagged assembler.

Q5: How can I store X (Ice for example) in a seperate container?
A5: you can achieve this in 2 ways:
either by using [Stock] and set Ice to =All
or the better way: change the Category of Ice in the Custom data to a new category, for example set its category to Ice and add Ice to the name of a Cargo Container.

[LogScreen] Crashes and Issues

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]!

!!!NEW!!! GSIM Integration Mod

With the help from Uzar we managed to create a mod, that allows GSIM to almost fully Automate all Item Recipe Learning by exposing certain Informations to Programmable blocks, that are usually not available for them.
This essentially means, that manual Item Learning is a thing of the past (with some minor exceptions)

The mod is called GSIM Integration and if you have that mod added to your game, GSIM will actually be able to see how to craft an Item without the need to Learn it and will directly add a newly seen Item, that is also craftable for you to the AutoCrafting screen!

If you want to directly have all Items on your AutoCrafting screen, just run the PB with the addAllKnownItems argument.

This Integration mod also allows automated Translating of item names depending on what language your client (or server, if you play on one) is set to.
by running the PB with the translateItemNames.

This Mod also gives you direct access to the Edit Text button while the content of a LCD screen is set to "Apps"

this mod is optional, and GSIM works without it.