philmasterplus
Active member
Update: I've officially released the item search script here.
So I've been working on my inventory killer cleanup script and the IOTM catalog script, and decided that I needed a universal item search script. So after a full week of tinkering, here is my first attempt at ASH scripting.
Now that I've got most of the basics working fine, could you please look at my script for helpful criticism? In particular, could anyone help me with parsing text queries? I can't figure out how to parse and process A-OR-B queries, such as brimstone accessory, stainless accessory, plexiglass accessory
Edit: To clarify, my script tries to do what most item-related CLI commands do--match a query to a specific item. However, instead of trying to find a single exact match, it tries to find multiple matches of an item, so you can specify a class of items--IOTMs, untradeable equipment, etc. This would help scripts like OCD Inventory Control that require a large list of item management rules (right now you have to manually enter each item). Also, it would help accept arbitrary input from the user to evaluate multiple items at once. Of course, to prevent accidental mismatches, the user should be allowed to test the query before actually using it.
At the moment, I want to use this script in my inventory clean-up script and the IOTM catalogue script. Seeing as many scripts handle one or more list of items , I thought it would be neat to allow searching items based on categories and/or flags.
So I've been working on my inventory killer cleanup script and the IOTM catalog script, and decided that I needed a universal item search script. So after a full week of tinkering, here is my first attempt at ASH scripting.
Now that I've got most of the basics working fine, could you please look at my script for helpful criticism? In particular, could anyone help me with parsing text queries? I can't figure out how to parse and process A-OR-B queries, such as brimstone accessory, stainless accessory, plexiglass accessory
Edit: To clarify, my script tries to do what most item-related CLI commands do--match a query to a specific item. However, instead of trying to find a single exact match, it tries to find multiple matches of an item, so you can specify a class of items--IOTMs, untradeable equipment, etc. This would help scripts like OCD Inventory Control that require a large list of item management rules (right now you have to manually enter each item). Also, it would help accept arbitrary input from the user to evaluate multiple items at once. Of course, to prevent accidental mismatches, the user should be allowed to test the query before actually using it.
At the moment, I want to use this script in my inventory clean-up script and the IOTM catalogue script. Seeing as many scripts handle one or more list of items , I thought it would be neat to allow searching items based on categories and/or flags.
Attachments
Last edited: