Quantcast
Download
(184 Kb)
Download
Updated: 07/11/19 05:21 AM
Pictures
File Info
Compatibility:
Scalebreaker (5.1.0)
Elsweyr (5.0.5)
Wrathstone (4.3)
Updated:07/11/19 05:21 AM
Created:03/22/19 12:08 PM
Monthly downloads:134
Total downloads:720
Favorites:10
MD5:
Categories:Bags, Bank, Inventory, Utility Mods
5.0.5
ItemTrig
Version: 1.0.11
by: DavidJCobb [More]
ItemTrig is an inventory management add-on that allows you to define custom rules, to automatically perform actions on items in your inventory.

Custom rules come in the form of triggers. Each trigger has entry points, conditions, and actions. The entry point decides when ItemTrig should attempt to test the trigger's conditions; if all of the conditions are met, then the actions will be performed in sequence. This allows you to define flexible rules for handling items as they enter your inventory, or when you open certain services (e.g. crafting stations, merchants).

Here's a basic trigger, to serve as an example:

Name: Deconstruct intricate
Entry points: Crafting Menu Opened
Conditions:
1. The item [is] an [any equippable].
2. The item [is] intricate.
3. The current crafting station [is appropriate for] this item.
4. The player [has not] maxed out their [crafting skill for this item] skill.
Actions:
1. Deconstruct the item.

If you were to define that trigger and then open the crafting menu, then ItemTrig would attempt to automatically deconstruct any intricate equipment in your inventory -- but only if you haven't already maxed out the relevant item skill!

One word of warning, though: ItemTrig will do exactly what you tell it to, even if that's not what you meant.

How does this compare to Dustman?
Dustman is fast and much simpler to set up. It's an excellent mod, and if you're not looking to perform specialized tasks, then it's the mod for you.

ItemTrig is more useful for specialized tasks. You may wish, for example, to destroy low-rarity stolen treasures unless they're useful for the Covetous Countess quest, in which case you might want them laundered instead. You may wish to destroy stolen lockpicks if you already have a full or nearly-full stack of "clean" ones. You may wish to destroy incoming equipment unless it belongs to a specific item set. ItemTrig gives you the building blocks to do any of these (and much more), but you have to assemble those building blocks yourself. The ability to do so is ItemTrig's raison d'être.

Extra notes
This add-on requires LibAddonMenu-2.0 and LibStub to function.

You can open the trigger editor via the add-on's options menu, or by entering /itemtrig edit in the chatbox.

ItemTrig has a gallery of built-in triggers. You can import triggers from the gallery, or between characters, by clicking the "Import" button in the main window.

Most entry points only run triggers on the items in your backpack. Your equipped gear does not count as being "in your backpack." The entry points that run triggers on items in your bank are explicitly marked (e.g. "Crafting Menu Opened (runs on banked items)").

When writing your own triggers, consider enabling "Pretend Mode" in the options when you're testing. This feature prevents ItemTrig from taking any action on your inventory, instead announcing the actions it would take. It's a good way to make sure your "destroy these items that I don't care about" trigger doesn't match more than it's meant to!

Links
Github repo
1.0.11
ItemTrig should now be compatible with FCO ItemSaver: trigger actions will fail if FCO ItemSaver has been set to prevent them (e.g. trying to deconstruct something that you've locked in FCOIS). ItemTrig also offers a trigger condition to check whether FCOIS is installed, a condition to check the FCOIS marks on an item, and a trigger action to modify the marks on an item.

Added new conditions to check an armor's type (light/medium/heavy) and a weapon's type (sword/greatsword/staff/shield/etc.).

Added new conditions to check whether an item can be deconstructed, and to check whether an item can be refined. Gallery triggers involving deconstruction now use the former condition.

Added a new condition to check whether the Craft Bag is accessible.

Added a new action to queue the mass refinement of a single type of raw material, or of all raw materials across your inventory and Craft Bag. Due to how refinement works in-engine, it is impossible to limit what materials get refined or from where.

The "Log Message" trigger action now offers a "$(link)" token that can be used to produce an item link.

Users have reported that the "Withdraw from Bank" trigger action withdraws an entire item stack, even if it is directed to only withdraw a certain amount of the item. Unfortunately, this appears to be an issue with the underlying ZOS API: the same API is used for deposits and withdrawals, and when withdrawing, it seems to ignore its "count" parameter. As such, the "Withdraw from Bank" trigger action has had its own count option removed; it now only offers the option to withdraw a full stack, and its description makes this clear.

Fixed a Lua error that left the "Meets Usage Requirement" condition unusable.

1.0.10
Fixed issues that prevented ItemTrig from seeing the expanded bank space added by ESO Plus.

Fixed a few pieces of code that mixed up the Craft Bag with the expanded bank space added by ESO Plus. The fixed functions include those that power the Total Count condition.

Added a "Withdraw from Bank" trigger action, available for the "Bank Opened (run on banked items)" entry point.

Made minor fixes to savedata versioning (don't worry; the relevant bugs didn't affect anything).

1.0.9
Fixed defects in multiple gallery triggers: "sell" triggers will no longer attempt to sell stolen items; the "sell trash" trigger now correctly uses the "sell" action instead of the "launder" action; the "deconstruct worthless equipment" trigger will no longer try and fail to deconstruct provisioning ingredients when you are at a cooking station.

As of this version, ItemTrig will remember which triggers you imported from the Trigger Gallery. As long as you don't modify these triggers, they will auto-update if later versions of the mod fix their counterparts in the Trigger Gallery. You can disable this auto-updating in the mod settings.

1.0.8
Fixed a minor issue with the "Banked items: allow destroy" pref, which could cause LibAddonMenu errors to appear in the chat console.

1.0.7
Fixed a hang that could occur when trying to deconstruct multiple items, if your triggers directed ItemTrig to deconstruct items that for non-obvious reasons aren't considered deconstructable (e.g. the Forgotten Adventurer's Bow).

Deconstruction now properly "finishes" and logs a success after processing deconstruction of one single item; you should no longer incorrectly see warnings about "interrupting" the queue when leaving the crafting station.

1.0.6
Added two new entry points that will run triggers on items in your bank: "Bank Opened (run on banked items)" and "Crafting Menu Opened (run on banked items)." If you wish to run a trigger on both carried and banked items, then use it on both these entry points and the normal "Bank Opened" and "Crafting Menu Opened" entry points. The intended use case for this is being able to automatically deconstruct banked items.

The "Deposit in Bank" action will now cause a trigger failure and show an error message when attempting to deposit Character Bound items, instead of just failing silently.

Added a "Bound" condition to test whether an item is bound, or to test whether an item is Character Bound, specifically.

Zenimax forcibly disconnects players from the server if their add-ons attempt to deposit more than 99 item stacks in the bank during one bank session. ItemTrig is now aware of this and will attempt to stay 2 stacks below the limit. Note that ItemTrig cannot be aware of what other add-ons are doing, so ItemTrig and other add-ons can still exceed the limit together (this is also the case for laundering items).

Fixed a bug that could cause attempts to enable/disable a top-level trigger to fail.

Added an option to improve logging of trigger failures by "collapsing" certain kinds of trigger failures when they occur more than once. For example, if you have a trigger that tries to deposit ten items into your bank, and your bank is full, you do not need to see ten error messages all telling you that the bank is full. This option will instead display full details on the first such trigger failure, and then (after all triggers for the entry point have finished running) display the number of triggers that experienced the same error. This option is enabled by default.

Added an option to forcibly prevent triggers from destroying items in your bank, even if they run on bank-specific entry points. If the option is enabled, then Destroy actions on a banked item will cause a trigger failure. This does not apply to deconstructing items.

Made various fixes and improvements to ItemTrig's tooltips.

1.0.5
Added a new condition: "Item Type (Detailed)." This condition can be used to check for very specific item categories, such as "Museum Piece."

Added buttons to the trigger editor to duplicate a selected condition or action.

Fixed window sizing for the condition/action editor. Sizing errors could be seen when editing conditions/actions with long values (e.g. a Comment condition with copypasta stuffed into it).

Fixed theming for the condition/action option editor. Previously, explanatory text for some condition/action options didn't theme properly and was always in white print.

The description for the "Covetous Countess" condition should no longer produce an incorrect sentence.

Minor fixes to the "Deconstruct" trigger action: ItemTrig should no longer log both a "success" message and a "failure" message if a deconstruct is attempted and fails; if a deconstruct fails because your inventory is full, then all pending deconstructs will be aborted.

1.0.4
Critical fixes to the "Deconstruct" trigger action; it will no longer fail silently after deconstructing a single item, and it now works on enchanting glyphs.

Fixed the "Pretend Mode" option: triggers will no longer continue to run on an item after pretending to destroy, deconstruct, sell/fence, or deposit it.

1.0.3
Added a theme switcher to the add-on's options menu.

Added a dark theme.

Added more pre-made triggers to the Trigger Gallery accessible via the "Import" button.

Fixed some pre-made triggers that would've logged errors if run on locked items.

Fixed a bug with the "Esc force-closes the editor" option that made it always take effect even if disabled.

Fixed spacing on the validation tooltip in the opcode argument editor.

Deprecated the "Priority Sell" condition.

1.0.2
Fixed a packaging mistake with the mod.

The "Sell or Fence" action will now fail on locked items.

1.0.1
Fixed the sort order for the rarities in the "Item Rarity" condition.

The "Sell or Fence" action's explanation text now properly identifies it as being usable in the merchant or fence menus.

Fixed internal issues with quantity options (e.g. "at most 5," "at least 1") for conditions and actions.
Optional Files (0)


Archived Files (10)
File Name
Version
Size
Uploader
Date
1.0.10
171kB
DavidJCobb
06/22/19 06:01 PM
1.0.9
170kB
DavidJCobb
05/02/19 02:34 PM
1.0.8
168kB
DavidJCobb
04/30/19 04:01 PM
1.0.7
168kB
DavidJCobb
04/25/19 06:57 PM
1.0.6
168kB
DavidJCobb
04/25/19 05:29 PM
1.0.5
165kB
DavidJCobb
04/07/19 03:04 PM
1.0.4
162kB
DavidJCobb
03/28/19 03:08 PM
1.0.3
159kB
DavidJCobb
03/23/19 07:25 PM
1.0.2
152kB
DavidJCobb
03/22/19 07:04 PM
1.0.1
151kB
DavidJCobb
03/22/19 01:12 PM


Post A Reply Comment Options
Unread 03/31/19, 10:39 AM  
Lifeseeker128
 
Lifeseeker128's Avatar

Forum posts: 7
File comments: 11
Uploads: 0
Great addon. Could use more work.

Found this addon during my search for an up to date alternative to Inventory Manager. ItemTrig is a nice one to be sure. There's a bit of a learning curve to it, much like any addon of its kind, and I was wondering if there is a way to have ItemTrig withdraw certain items from the bank, say if I wanted to have all known recipes deposited to my bank while all the unknown recipes get withdrawn. As of now, I haven't been able to identify a method for performing this action to withdraw, only to deposit.
Report comment to moderator  
Reply With Quote
Unread 03/30/19, 06:15 PM  
Kyoma
AddOn Author - Click to view AddOns

Forum posts: 88
File comments: 219
Uploads: 10
There is SPECIALIZED_ITEMTYPE_TROPHY_MUSEUM_PIECE, tho I don't know which museum items exactly we are talking about and if they have this specialized item type.
Report comment to moderator  
Reply With Quote
Unread 03/30/19, 05:56 PM  
DavidJCobb
 
DavidJCobb's Avatar
AddOn Author - Click to view AddOns

Forum posts: 0
File comments: 19
Uploads: 1
Re: Museum Items

Originally Posted by Kyndrith
Question - What option would I use to prevent the museum (unique) pieces from being auto-destroyed based on zero gold items.
Currently there isn't a way (that I can think of) to detect museum pieces. I think I know of something I can implement for this, so I'll put it on my to-do list.

Originally Posted by wazoo
Hi. Great addon!
I can't find "Refine" action. Does one exist?
There is no Refine action.
Report comment to moderator  
Reply With Quote
Unread 03/30/19, 02:35 AM  
wazoo

Forum posts: 0
File comments: 43
Uploads: 0
Hi. Great addon!
I can't find "Refine" action. Does one exist?
Report comment to moderator  
Reply With Quote
Unread 03/29/19, 08:45 PM  
Kyndrith

Forum posts: 0
File comments: 43
Uploads: 0
Museum Items

Question - What option would I use to prevent the museum (unique) pieces from being auto-destroyed based on zero gold items.
Report comment to moderator  
Reply With Quote
Unread 03/28/19, 06:58 PM  
DavidJCobb
 
DavidJCobb's Avatar
AddOn Author - Click to view AddOns

Forum posts: 0
File comments: 19
Uploads: 1
Re: Re: Deconstruction Triggers

Originally Posted by vakisari
You are the best. Thanks for the quick answer and update! Look forward to installing the update when you release it.
It should already be available for download -- version 1.0.4.
Report comment to moderator  
Reply With Quote
Unread 03/28/19, 06:50 PM  
vakisari

Forum posts: 0
File comments: 2
Uploads: 0
Re: Deconstruction Triggers

Originally Posted by DavidJCobb
Originally Posted by vakisari
Hi! Love the mod, but I'm curious why my triggers dealing with deconstructing items only deconstructs one item each time the crafting interface is opened? The log SAYS that all relevant items meeting my conditions are deconstructed, and yet only one instance actually occurs.
Sounds like a bug. I'll take a look at it as soon as I'm able.

My guess would be that crafting tables only allow add-ons to deconstruct one item at a time, but don't give any indication that any limit has been reached. It looks like there's an event I can use to detect when a deconstruction finishes, so it should be relatively easy to fix this:

1. I'll need to make it so that the "Deconstruct" action doesn't directly deconstruct the item, but instead adds it to a queue.

2. Once the trigger list finishes running, I'll need to run that queue, listening for events and deconstructing the items one-by-one.

EDIT: I should also update the wiki docs for the deconstruct API...

Thanks for reporting this issue.

EDIT: Should be fixed in the latest update.
You are the best. Thanks for the quick answer and update! Look forward to installing the update when you release it.
Report comment to moderator  
Reply With Quote
Unread 03/28/19, 10:10 AM  
DavidJCobb
 
DavidJCobb's Avatar
AddOn Author - Click to view AddOns

Forum posts: 0
File comments: 19
Uploads: 1
Re: Deconstruction Triggers

Originally Posted by vakisari
Hi! Love the mod, but I'm curious why my triggers dealing with deconstructing items only deconstructs one item each time the crafting interface is opened? The log SAYS that all relevant items meeting my conditions are deconstructed, and yet only one instance actually occurs.
Sounds like a bug. I'll take a look at it as soon as I'm able.

My guess would be that crafting tables only allow add-ons to deconstruct one item at a time, but don't give any indication that any limit has been reached. It looks like there's an event I can use to detect when a deconstruction finishes, so it should be relatively easy to fix this:

1. I'll need to make it so that the "Deconstruct" action doesn't directly deconstruct the item, but instead adds it to a queue.

2. Once the trigger list finishes running, I'll need to run that queue, listening for events and deconstructing the items one-by-one.

EDIT: I should also update the wiki docs for the deconstruct API...

Thanks for reporting this issue.

EDIT: Should be fixed in the latest update.
Last edited by DavidJCobb : 03/28/19 at 03:11 PM.
Report comment to moderator  
Reply With Quote
Unread 03/28/19, 09:26 AM  
vakisari

Forum posts: 0
File comments: 2
Uploads: 0
Deconstruction Triggers

Hi! Love the mod, but I'm curious why my triggers dealing with deconstructing items only deconstructs one item each time the crafting interface is opened? The log SAYS that all relevant items meeting my conditions are deconstructed, and yet only one instance actually occurs. If I exit the table and re-activate it, the next item that would have been deconstructed actually gets done, and so on and so on. This occurs with all tables and doesn't seem to matter how many items meet the criteria, only one Deconstruct Item action actually gets taken. Again, the log output in the chat window correctly identifies, and lists all items that the action would have occurred against (and claims they are all deconstructed) but only the first item in the list is actually deconstructed. Is there something I'm not adding to my conditions to cause it to continue to repeat the action until no more items meet the conditions? I've tried simply using an 'always true' condition and using a bunch of nest actions to cause it to re-iterate through the trigger multiple times but the same behavior occurs.. it executes the first nest but no more.
Report comment to moderator  
Reply With Quote
Unread 03/24/19, 11:53 AM  
DavidJCobb
 
DavidJCobb's Avatar
AddOn Author - Click to view AddOns

Forum posts: 0
File comments: 19
Uploads: 1
Re: Updated Pre-made triggers

Originally Posted by Kyndrith
Do we need to re-import the triggers on all of our characters when a change is made to a pre-made trigger?
Yes, currently.
Report comment to moderator  
Reply With Quote
Unread 03/24/19, 06:32 AM  
Kyndrith

Forum posts: 0
File comments: 43
Uploads: 0
Updated Pre-made triggers

Do we need to re-import the triggers on all of our characters when a change is made to a pre-made trigger?
Report comment to moderator  
Reply With Quote
Unread 03/23/19, 08:27 PM  
DavidJCobb
 
DavidJCobb's Avatar
AddOn Author - Click to view AddOns

Forum posts: 0
File comments: 19
Uploads: 1
Re: Finally, also future plans?

Originally Posted by jubalfh
Hey,

Thank you for this plugin – it finally does the right thing, i.e. implements straightforward triggers!

Do you plan to expand the functionality (already huge) further, for example to allow currency manipulations at bank, or to allow wider range of conditionals (akin to autoinventory), or, by any chance, to store the state and interval from last succesful run of the same trigger? (I'm looking forward to replace a number of plugins that I'm using right now with yours… ;-))
Currency -- no. Entry points other than "item added" involve running your full trigger list against every item in your bag, so you'd be able to deposit x amount of gold per item meeting your conditions, but not y-and-only-y amount of gold each time the bank is opened -- if that's at all clear.

More conditions -- if I think of any decent ones.

Storing state -- probably not.

I want to avoid feature creep. It's always tempting to try and do absolutely everything, but I don't want this project to become some runaway thing that tries to do everything and does little of it well. You complimented it for being straightforward; I want to be quite careful to keep it that way.
Report comment to moderator  
Reply With Quote
Unread 03/23/19, 02:53 PM  
jubalfh
 
jubalfh's Avatar

Forum posts: 0
File comments: 6
Uploads: 0
Finally, also future plans?

Hey,

Thank you for this plugin – it finally does the right thing, i.e. implements straightforward triggers!

Do you plan to expand the functionality (already huge) further, for example to allow currency manipulations at bank, or to allow wider range of conditionals (akin to autoinventory), or, by any chance, to store the state and interval from last succesful run of the same trigger? (I'm looking forward to replace a number of plugins that I'm using right now with yours… ;-))
Report comment to moderator  
Reply With Quote
Unread 03/22/19, 07:06 PM  
DavidJCobb
 
DavidJCobb's Avatar
AddOn Author - Click to view AddOns

Forum posts: 0
File comments: 19
Uploads: 1
Originally Posted by Shinni
Could you reupload you zip, so it contains an ItemTrig folder?
I've uploaded a fixed version, which as of this writing is pending the usual review. Thanks so much for catching this!
Report comment to moderator  
Reply With Quote
Unread 03/22/19, 06:12 PM  
Shinni
AddOn Author - Click to view AddOns

Forum posts: 140
File comments: 462
Uploads: 21
Could you reupload you zip, so it contains an ItemTrig folder?
Currently all files are at top level instead of inside an extra ItemTrig folder, as a result Minion will extract your addon like this:


Eso will only detect your addon, if it is contained in a folder called ItemTrig (the same name as your addon's .txt manifest).
So even if a user were to extract your zip by hand instead of using Minion, it would either end up as in the screenshot above or inside a folder called "ItemTrig v1.0.1" (the zip name). In both cases eso will fail to load your addon.
Last edited by Shinni : 03/22/19 at 06:18 PM.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: