The Inventory Sorter and You!

A guide on how to use the Clientside Inventory Sorter mod

Introduction

Ever found yourself in a fight and realized you forgot to load ammo and repair parts into your grid? Tired of clicking 387 times to offload loot and ore? Is your sorter looping? You might just need to sort your inventory!

The Inventory Sorter is a mod that runs independently of any server or programmable block, and is used to sort the inventory of a grid on-demand rather than on timers like Programmable Block inventory sorter scripts. It reduces server load by doing all the sorting on the client, and simply sends a series of commands to the server after sorting is complete, as if you were dragging the items around yourself in the inventory screen.

This guide will cover basic and advanced configuration of the inventory sorter mod to help you get the most out of it that you can.

Getting Started

This section covers the most basic possible way to set up your base and mobile grids for inventory sorting.

1. Name each container you want to put things in at your base one or more of the 6 types. For example, if you have 10 containers, name 4 of them "Base Components [P50]", 4 of them "Base Ingots, Ores [P50]", 1 of them "Base Ammo [P50]" and 1 of them "Base Tools, Bottles [P50]". You can also add numbers, e.g. Base Components 1, Base Components 2, etc. The word "Base" doesn't matter, but "Components" is a keyword meaning all components such as Steel Plate, and "[P50]" is the priority of the container.
   
2. On your mobile grid, name each container something like "Mobile Container Any Item [P70]", optionally adding numbers or letters to indicate where the container is on the vehicle - for example, "Mobile Container L1 Any Item [P70]". "Any Item" is a shorthand way to say "Ores, Ingots, Components, Ammo, Tools, Bottles". Setting a lower priority (70) as compared to the base's 50 means when you sort items, it will take items out of your mobile grid to put them in the base.
   
3. Open the Control Panel menu, select your cockpit, and click "Sort Inventory".
   
4. Take a look at the window that pops up, then dismiss it and check your inventory. You should see that all items have been removed from your mobile grid and placed in your base.
   
5. If you want to retain certain items in your mobile grid (e.g. a bottle and a set of tools), add the word "Special" to an otherwise unused block that has an inventory, for example your cockpit. After the cockpit is named something like "Mobile Cockpit Special", put a bottle and tools in it. Open up the Custom Data and make sure it's totally blank, then click Sort Inventory again. If you check the Custom Data now, you should see something like this, and the cockpit will now keep those items in stock every time you sort your inventory.
   

   [Inventory]
   Tool/AngleGrinder4Item=1
   Tool/Welder4Item=1
   Tool/HandDrill4Item=1
   Bottle/HydrogenBottle=1

It should look something like this when you're done:

Now that you have a grasp on the basics and your grids are set up to sort, you should be good to go, but read on to find out about all of the other features of the sorter mod!

Basic Operation

Before we talk about configuring the sorting mod, we need to know how to run it!

There are three ways to trigger the sorter:

• The "/sort" chat command - just enter "/sort" in the chat and the sorter will run if you are currently seated.
  
  
• The hotbar of any cockpit or remote control - just drag the control block itself to your hotbar and select the Sort Inventory option.
  
  
• The Control Panel menu of any seat or cockpit on the grid - even from bed!
  

The sorter cannot be run from Timer Blocks, Event Controllers or any other automated means, as it depends on your game client to do the bulk of the work, so you must trigger it yourself.

The sorter can also sort only your current construct (the grid you are seated in, plus any subgrids attached with rotors, pistons, hinges, or suspensions, but not connectors) with the "/csort" command. There are also corresponding buttons and cockpit actions for construct-only sorting.

Result Display

When you run the sorter from the chat command or hotbar, the results will be displayed in the chat to avoid obscuring your view, but if the sorter is run from the Control Panel, the results will be displayed in a popup window.

Chat Results

Control Panel Results

The results will show the number of transfers requested, as well as any necessary items that may be required to fill requests from blocks on the grid or errors found when trying to determine what items were needed.

Basic Configuration

The Inventory Sorter was partially inspired Isy's Inventory Manager and thus uses very similar configuration language.

There are two kinds of container configuration directives: Type and Specific. There is also a priority for the container, and blocks like O2/H2 Generators and Guns will attempt to fill themselves with whatever they need even if you do not tag them.

Directives can be used on any block that has an inventory and a conveyor connection. This means that not just cargo containers can have directives - a block such as an Assembler or a gun can have directives. The requirement of having a conveyor connection does mean things that can't possibly give or receive items, such as Beds, are not possible to include in the sorting system.

Type Containers

Type containers use a part of the container's name to determine what to put in that container.

Type container category names are:

• Ores
  
• Ingots
  
• Ammo
  
• Components
  
• Bottles
  
• Tools
  
• Consumables
  
• Ingredients

Simply naming a container something like "Ores Cargo Container" is enough to cause the inventory sorter to start putting Iron Ore, Stone, Cobalt Ore, etc. into that container when you run sorting.

If you want a container to accept any item, use "Any Item" in the name. This is equivalent to a type set of "Ores, Ingots, Components, Ammo, Tools, Bottles". For example, "Hauler Cargo Any Item" will allow the cargo to accept all possible items.

Priority

A priority system can be created by by adding "[P##]" in the container's name - for example, "[P10]". Lower numbers are higher priority - [P1] will be filled before [P20]. The possible priority range is between 1 and 250.

Containers will be filled in priority order if space is available and will never take from containers of the same or higher priority.

Untagged Block Filling

Certain untagged functional blocks will automatically fill themselves. For example, O2/H2 generators will attempt to maintain an amount of ice in themselves, guns will attempt to fill themselves with ammo, and Reactors will attempt to fuel themselves.

Ignoring Blocks

To disable the inventory sorter entirely for a specific block add, "Hidden" "Locked" or "!manual" to the name. The Inventory Sorter will then completely ignore the block.

Specific Containers

Specific container tags use the container's Custom Data to select items. These tags are placed in the names like a Type container, but cause additional, different behavior. The tags are:

• Special
  
• Limited

Special is an exclusive tag - combining Special with another tag such as Tools will not work and the container will be treated as Special only. Special containers use unique priority handling:

• Special containers are considered highest priority above all other blocks except other Special containers.
  
• If the mod config option AllowSpecialSteal is true (the default), Special containers will pull items from other special containers if necessary, depending on their relative priority.
  
• If the mod config option AllowSpecialSteal is false, Special containers will only remove excess items and pull in needed items from other non-Special containers.

Limited is an inclusive tag: Type container categories and Limited tagging can be combined. "Cargo Container Limited, Bottles and Tools [P70]" is valid and will try to contain all bottles, all tools, and any items specified in the container's Custom Data. Priority affects limited containers normally and both limited and type containers participate in the same priority system.

Advanced Configuration

Special and Limited containers are the best way to make the inventory sorter work for you, because the Custom Data can be used to specify very intricate sorting directives.

The simplest way to create the custom data value needed is:

1. Make sure the custom data is blank.
   
2. Put the items you want in the container.
   
3. Run the sorter.

When you open the custom data again, the contents of the container will have been copied into the custom data.

For example, if you put 6 steel plate in a container named Cargo Container Special and ran the sorter, you would be greeted with this in the custom data:

[Inventory]
Component/SteelPlate=6

This is an inventory sorting directive to keep exactly 6 steel plate in the container.

If you took 3 out and put them in another container, then ran the sorter again, they will be returned to this container. If you put 3 more in and another container on the grid could accept them, the excess would be transferred out.

Special and Limited containers can have four different modes on a per-item-basis:

• Normal: pulls in and stores the specified amount, removes any excess. Usage:

  item=100

• Minimum: pulls in and stores the specified amount, ignores excess. Usage:

  item=100M

• Limit: Only removes items in excess of the specified value. Any value below the limit is kept, but more is not pulled in. Usage:

  item=100L

• Percent: Tries to fill the container to the specified volume percentage of its maximum capacity. Usage:

  item=50%

• All: Pulls in as many of the specified item as it can until the inventory is full. Usage:

  item=All

• Max: Fills all remaining (after other, more specific amounts) space in the container with the specified item. Can accept multiple, ordering does matter. Usage:

  item=Max

All is particularly useful to create a container that has just a few types of items, but tries to take as many as possible. For example, you could have "Base Cargo Container Construction [P70] Limited" that has the following custom data:

[Inventory]
Component/Construction=All
Component/Girder=All
Component/BulletproofGlass=All
Component/InteriorPlate=All

This container would contain only Construction Components, Girders, Bulletproof Glass and Interior plate, but would take as many as possible of each.

Combining "Limited" and Types

Type directives can be thought of as a broad spectrum "All" directive (in a way, something like "Ore/Any=All" is what the "Ores" type directive is in spirit, even though "Ore/Any" is not actually valid), but what if you want to be a bit more specific?

The "Limited" specific container tag can be combined with other types, such as Tools and Bottles. When using this tag, if you specify an item in the Custom Data that is covered by the Type directive, the Custom Data applies. For example, a "Tools, Limited" container would pull in any hand tools such as grinders, but if you wanted to explicitly disallow Basic tools, you could create a directive like this in the custom data:

[Inventory]
Tool/AngleGrinderItem=0
Tool/WelderItem=0
Tool/HandDrillItem=0

This means that any tools would be put in this container, with the exclusion of Basic tools.

This also means if you used the following directive on a "Tools, Limited" container that only 2 Elite Grinders would be kept in the container, but as many of all other tools would be put their as possible.

[Inventory]
Tool/AngleGrinder4Item=2

Untagged Blocks

Functional blocks such as guns or O2/H2 generators are considered non-special, high priority blocks and will attempt to fill themselves with whatever they need or get rid of things they don't want from other non-special containers.

To override these behaviors, add a Special/Limited tag or use one of the Lock keywords in the name.

• Ice is added to or removed from O2/H2 generators to maintain around 70-80% fullness, but bottles will always be moved from generators to a Bottles container if one exists.
  
• Bottles will always be moved from any tanks to a Bottles container if one exists.
  
• Refinery inputs are left alone, but outputs are fully emptied.
  
• If an assembler is in disassemble mode, its input (the ingots side) will be emptied, but if it's in assemble mode its output (the components side) will be emptied. The opposite inventory will be emptied if the assembler is off or not producing items. If the assembler is producing items, if it has too many of an input, that excess input will be removed to keep the assembler from clogging.
  
• Reactor fuel will be filled or removed to make the reactor contain around 100 for Large Grid and 25 for Small Grid, unless there's not enough - then it will be equally distributed to all reactors.
  
• Weapons will be fully filled with whatever ammo they want if they can only take a single type of ammo. If they can take more than one ammo type, make sure you specify which ammo to fill them with in the CustomData and tag them as Special.
  
• Parachutes will be filled with canvas.

Priority System

The priority tiers in highest (will be filled first) to lowest:

Special [P0]
...
Special [P255] (Default priority if unspecified in name)
Untagged functional blocks like Guns or reactors (Default P0), and [P0] tagged cargo containers (don't tag stuff P0 yourself, let it stay reserved for functional blocks)
Type (Ores, Ingots, Components, Ammo, Tools, Bottles) and Limited containers [P1]
...
Type and Limited containers [P255] (Default priority if unspecified in name)

Excluding Grids

Whole grids can be excluded from sorting to allow you to trade with allies or preserve the state of an inventory within a ship when docked.

Add "[nosort]" to the name of a grid to exclude it and any connected grids. Add "[nosort]" to the name of a connector to exclude any connected grids from sorting.

Exclusions by both grid name and connector name are transitive.

For example, given this grid/connector topology, both Ship A and Ship B are excluded from sorting, if sorting is started from the Trade Station grid.

[Trade Station (Trade Connector [nosort]) <-> (Docking Connector) Ship A (Hangar Connector 1) <-> (Docking Connector) Ship B

The same behavior would apply if the tag was in the ship name as well:

Trade Station (Trade Connector) <-> (Docking Connector) Ship A [nosort] (Hangar Connector 1) <-> (Docking Connector) Ship B

Warning: Multiple Connections

If there are two or more connectors linking grids A and B, all connected connectors on one of the grids must be tagged with "[nosort]" especially if the connectors form a loop via other grids (e.g. Pistons or Hinges), or routes may form where sorting is allowed.

A topology like this provides a route to the ship and will cause unexpected item movement:

Station (Connector A [nosort]) <-> (Docking Connector A) Ship grid
        (Connector B)          <-> (Docking Connector B)

Custom Data Creation

While it's possible to create custom data by simply throwing items in a container and running the sorter, what if you want to create a list containing all the prerequisites for many components, or a list of components that you don't have yet?

Get All Sortable Items Chat Command

The most raw view is to run a chat command:

/getallsortableitems

This will generate a list of all items that can be sorted and put the list in your clipboard. Paste it into Notepad or some other text editor to view the data.

The first section is a map of the the sortable ID to the display name so you can figure out what ID to use.

The second section is all items but in inventory custom data format. You can edit this section directly to remove item IDs and change numbers, then paste it right back into the game as long as you remember to keep the "[Inventory]" header.

Assembler Custom Data

All Assemblers (including survival kits and basic assemblers, as well as any modded assemblers) will have new buttons to help with this.


The resulting data can be pasted directly into the Custom Data of a Special or Limited tagged container to fill it with the prerequisites or results from the assembler.

Make Prerequisite Data

The "Make Prerequisite Data" button will open a window that will allow you to copy the prerequisites for the selected assembler's queue to the clipboard.

Given the following production queue:

Clicking the "Make Prerequisite Data" button will produce the following on a 3x efficiency world with no mods:

[Inventory]
Ingot/Iron=767
Ingot/Gold=7
Ingot/Silicon=4
Ingot/Nickel=7

The numbers are rounded up, as the Custom Data directives do not allow partial items.

Make Result Data

The "Make Result Data" button will open a window that will allow you to copy the results for the selected assembler's queue to the clipboard. This is just the queue itself but is useful for getting it into text for or converting the display name of an item (Elite Grinder) to the inventory directive name (Tool/AngleGrinder4Item).

Given the following production queue:

Clicking the "Make Result Data" button will produce the following:

[Inventory]
Component/SteelPlate=100
Component/Superconductor=10
Component/PowerCell=10

This is especially useful when using the Build Planner or something like a projector-to-assembler script to figure out what parts you would need to construct something, then putting those in a container to haul some place else.

Comments

If you want to leave yourself a comment in the Custom Data to explain to your future self or another person why you did something, put it on its own line with a leading semicolon:

[Inventory]
;Limit reactor Uranium because this is a cheap drone
Ingot/Uranium=5

Additional Custom Data Commands

Additional commands exist to assist with managing custom data.

"Pattern" in the following commands means a full or partial piece of text that selects one or more blocks. The pattern "G:Group Name" can be used to reference an in-game block group instead.

These commands do not change any sort of priority or container names - they simply operate on the custom data.

If the block described by Source is not also described by Destination, the custom data of the source block is left unchanged.

Copying Custom Data

Copy custom data from a single block selected by "Source" to one or more blocks selected by "Destination". This simply copies all the custom data from source to destination, and destination may include the source block.

Examples:

/copycd "Source" "Destination"

Splitting Custom Data

Split custom data from a single block selected by "Source" to one or more blocks selected by "Destination". This will split the amounts relatively based on the volume the containers can hold. The command also respects profiles so you can make a profile based on a blueprint or something similar.

Examples:

/splitcd "Source" "Destination"

/splitcd "Source" "Destination" "profile"

Building with Custom Data

It's nice to be able to create custom data from existing cargo, an assembler, or text, but what about if you want to make components for a blueprint? The sorter can do that too!

Make Data from Projection

Projectors (including modded projectors) now have a button called "Make Data from Projection".


This is compatible with the Multigrid Projector[github.com] plugin, and if that plugin is in use, will take into account any subgrids such as Wheels or Rotors in the blueprint. If the plugin is not in use, subgrids are not included in the results - it takes what the projector can give it.

This will open a window with the parts required to build the entire projection. This does not take into account any currently or partially built blocks - this is simply a raw accounting of the components required to produce the blocks in the blueprint. Any modded components are included, but any production chains (e.g. component 1 is used to produce component 2) are not.

Make Queue from Data

Instead of putting items in the inventory of the assembler, clicking the "Make Queue from Data" button will queue up items listed in the assembler's custom data, if possible.



This button is only enabled when the assembler has inventory Custom Data set and is not tagged Special or Limited.

Let's try it using the data we got from the projector!



Clicking the button and going to the Production tab shows the following queue - exactly what we need to produce the blueprint!



Queuing items this way does not clear the assembler's existing queue or alter it in any way, and the custom data is preserved, so if you have a set of items that you'd always like to be able to produce (for example, a missile's components) or, as demonstrated above, you want to queue required items for a blueprint, this is the way to do it.

Clicking the button again simply adds another copy of the data to the queue at the end.

Clearing Queues

If you want to clear the queues of one or more assemblers, all assemblers now include a Clear Queue button in the Control Panel, and if multiple assemblers are selected, the control panel button will clear all selected queues at once.

Production Quotas

For more complex production goals, the sorter supports quota production. It is strongly recommended to run the sorter before doing a quota check to redistribute items.

The quota system is simplistic but prioritizes preservation of existing jobs over replacement. It includes custom logic to split queues over assemblers in tagged groups, but can work with Cooperative Mode instead if desired. Quotas can only be started by action (hotbar item) or button (in the Control Panel). There is no slash command to start quota production.

Quota Configuration

Configuring an assembler is done via the Assembler's Custom Data.

Defaults are shown in QuotaOptions, but the QuotaOptions section does not have to be present nor do all options in it have to be present. The defaults are shown below:

[QuotaOptions]
AllowAssembly=true
AllowDisassembly=false
ClearQueue=false

• AllowAssembly means that the assembler is allowed to create items when quota production is run. Defaults to true.
  
• AllowDisassembly means that the assembler is allowed to disassemble items. By default, disassembly is disabled and must be enabled on each assembler that you want to disassemble items on.
  
• ClearQueue clears the assembler's existing queue when the quota production is run. By default, the queue is not cleared, it is only merged with requested production.

Primary (see Quota Groups below) or single assemblers that are used as a "lead" assembler for cooperative mode must also have a Quota section. It looks like this:

[Quota]
Component/SteelPlate=200000M
Component/MetalGrid=100000
Component/Girder=5000L
Component/Reactor=100-200
Tool/AngleGrinderItem=0

Ordering of the [Quota] section does matter - jobs are created in priority order, so the first item in the list is going to be the first item in the queue. If you have queued up something manually, the quota jobs are placed in front of of the current manual job.

• No suffix means it will attempt to maintain an exact value, assembling if below the number and disassembling if above the number. M and no suffix behave the same if there are no assemblers that allow disassembly (the default).
  
• M (minimum) means it will build to the amount and ignore any excess.
  
• L (limit) means it will disassemble any excess but not assemble any.
  
• x-y (range) means that will assemble to the lower amount and disassemble if above the upper amount, but not do anything if the amount is in the middle.

Running Quota Production

Important: Only certain containers are considered when counting existing items. The same [nosort] and container ignore tag rules as the cargo sorter apply but all containers with the word "Cargo" in the name are considered to be quota containers. This can be changed in the global settings for the mod. This means that welders, connectors, etc. that have components in them will not be considered when checking to see how many items currently exist.

Run Sort first if you want to move everything to the correct place, then run Quota to top up or clean up. The "Clear Queue" button/action is also very helpful here if you're not sure what state your assemblers are in.



Quotas can also be started from the Control Panel:

Quota Groups

Quota groups are optional but are used to split jobs across multiple assemblers, much like cooperative mode. The difference is that assemblers in a quota group get the split job up front, whereas cooperative mode requires each cooperative assembler to pull from a primary assembler a little bit at a time.

Primary assemblers read quota data from that assembler's custom data. Secondary participates in load sharing and only reads assembler configuration (not items) from its custom data.

Assemblers in a "quota group" must have [Primary:QuotaGroupName] and [Secondary:QuotaGroupName] tags. The expected topology is that you have a single Primary and many Secondary assemblers. If you have multiple primary assemblers with the same tag, they act as a single primary and don't distribute to other primaries.

The Action hotbar item and button do not require a tag on the assembler for normal use. To use quota groups, you must use tags on the assemblers - the tag is how it can determine which assemblers should be used as secondaries. Game groups are not used for this purpose.

Co-op mode may cause issues but is not automatically disabled. If you want to keep using co-op mode, it is strongly recommended that you have a single primary assembler and leave all the secondary assemblers untagged to let co-op mode manage splitting of jobs.

Sort Profiles

Ever wanted to load up your grid for a specific purpose? Try Sort Profiles!

Here's a scenario where that might be useful: Let's say you normally go out mostly empty so that you are able to pick up as much loot as possible, but sometimes you need to take off with a full complement of repair parts and additional ammo to fend off an attack.

Let's make a sort profile called "Combat".

1. Pick one of your containers and set it up with some custom sorting data.
   
2. Change the [Inventory] line in the custom data to "[Inventory:Combat]".
   
3. When you do "/sort combat", containers with the "[Inventory:Combat]" custom data will be treated as Special containers with all that entails.

Overriding Priority for a Profile

If you need a container to be a different priority when using a sort profile, add a line that reads "Priority=5" or whatever the container's new priority should be to the "[Inventory:keyword]" section:

Ship Cargo C3 Any Item, Combat [P90]

[Inventory:combat]
Priority=1
Ammo/LargeCalibreAmmo=150

This means that the container is Priority 90 when doing a normal "/sort" and Priority 1 when doing a "/sort combat"

Profiles for Existing Special and Limited Containers

The inventory sections for special and limited containers are merged together with the profile sections. This means that they retain their normal items, and the items don't need to be re-specified, but it does mean that you do need to mark items you don't want as 0 quantity to not accept them during a profile sort.

Consider the following:

Ship Cabin Cargo Special [P5]

[Inventory]
Tool/AngleGrinder4Item=1
Tool/Welder4Item=1
Tool/HandDrill4Item=1
Bottle/HydrogenBottle=2

[Inventory:combat]
Tool/UltimateAutomaticRifleItem=1
Ammo/UltimateAutomaticRifleGun_Mag_30rd=2
Bottle/HydrogenBottle=1

What this means is that during a normal sort, the cargo will be loaded with 1 of each Elite tool, plus 2 hydrogen bottles. When doing a "/sort combat" to use the combat profile, it will be loaded with 1 of each Elite tool, plus an Elite Rifle and 2 magazines, but only one Hydrogen bottle, not 2 as in normal operation.

Quality of Life Features

Bottle Refilling

Normally, bottles will be sorted into any container that wants them, but if they are less than 100% full, the can be automatically refilled.

To do this, the following conditions must be met:

• You must have an O2/H2 generator or gas tank of the relevant gas available and working.
  
• The tank must have gas in it or the generator must have ice in it.
  
• The "Auto Refill" checkbox must be enabled.

If the above is all true, non-full bottles will be sorted into the first available generator or tank, and a second sort will put the now-full bottles back in the appropriate container.

Non-Conveyable Container Sorting

Certain blocks with inventories like the Bed, Armory, etc. cannot be connected to the conveyor
network in any way. This massively reduces how useful they can be. Normally, there's no way to easily keep a bed stocked with elite tools and a hydrogen bottle, or a kitchen stocked with food.

The sorter handles sorting into and out of containers that otherwise can't be normally conveyed to. This explicitly excludes any container with a conveyor port. You can't get around normal conveyor rules with the mod, but for containers that have no port whatsoever, the sorter can put items in them or remove items from them as if they did.

Generally, the block must be marked Special or Limited and have an appropriate priority and inventory custom data. Weapons are explicitly excluded from non-conveyable container sorting - as useful as it would be to have Interior Turrets get automatically filled with ammo, some weapons are balanced around having to be manually reloaded.

Character Inventory Swapping

Inventories that can fit fully in your character's inventory can be instantly swapped from the Control Panel of any block that has cargo. This includes lockers, armories, cockpits, cargo containers, etc.

To do this, open the cargo block's control panel (right click on it or look at it and press K) and click the Swap Inventories button.

If the button isn't visible, it means that the block either has too much cargo in it for your character's inventory to take, or that you are carrying too much for the block to contain.

This is generally meant for rearming quickly from an armor or locker (in conjunction with non-conveyable block sorting) to let you quickly dump your basic tools and get a fresh set of gear after respawning.

Remember to restock your lockers regularly!

Mod Configuration

Since the inventory sorter is 100% clientside, you can adjust certain aspects of it yourself to suit your playstyle.

Run "/configuresorter help" to see the list of configuration parameters and "/configuresorter option value" to change them.

[NeonPinHead]

When sorting items to the Food Processor I get the error "[ITEM] is not allowed in inventory 1 in the block" I could not locate info on a possible command to differentiate the input/output inventories of a block to correct this error.

[Boobies]

Hahaha such a simple thing! Thanks mate. Can't believe I missed that.

[Merii]

Yeah, it still works, nothing has changed recently that would cause it to break that I know of.

I see one issue immediately in your naming: The tag is "Ores" with an S, not "Ore". Make sure your tags are set up correctly and if it still doesn't work, please provide more details.

[Boobies]

Hi guys. Does this still work? I had it move a few things on a pterodactyl server (I have about 10 other mods - not Isys - working fine through this egg) but now it refuses to do anything. I have spent about 4 hours troubleshooting and resetting things to no avail. BLUF: I hit Sort Inventory and it just keeps saying 'nothing to sort' or whatever the default message is. There is absolutely stuff to sort. I have one container as the destination and ingots and ore in other connected containers and i have name the dest container Cargo, Large: Ore. It seems simple enough but this is doing my head in. It did work (kind of - it initially moved most stuff but not all) and now it does nothing and there's no indication why/where it's stuck. I am admin on my public server.

[Merii]

There's a reason the download page doesn't recommend using Isy's with it. Sorry.

[Bobisback]

Ya sadly something is still broken but I think it is on the isy side now, too bad.

[Bobisback]

this worked great, thanks

[Bobisback]

Oh I did not try that. I only tried some different forms of commenting haha. I will test this out.

Trying to use it with isys in a server so when PB are dieing I can just fall back to this sorter

[Merii]

What are you trying to use it with? I'd rather try to solve it or at least document what you can do to work around it, because unfortunately the Keen config parser is what errors out, so I can't extract any useful data - all I get back myself is "invalid data", or I would just ignore stuff and keep going.

I've not had too many incompatibilities, but I've had luck doing this (put a triple dash and then the rest of the non-INI config):

[Inventory]
SomeCrap=999

---

Other thing that isn't compatible

[Bobisback]

Or just make it when it finds a non matching pair it just gracefully ends and does the sort on what it did find up to that point. This could work to.