Quantcast
Download
(74 Kb)
Download
Updated: 09/09/20 07:12 PM
Pictures
File Info
Compatibility:
Stonethorn (6.1.5)
Greymoor (6.0.5)
Harrowstorm (5.3.4)
Dragonhold (5.2.5)
Scalebreaker (5.1.5)
Elsweyr (5.0.5)
Updated:09/09/20 07:12 PM
Created:03/13/19 07:00 PM
Monthly downloads:4,395
Total downloads:53,474
Favorites:107
MD5:
Categories:Plug-Ins & Patches, Bags, Bank, Inventory
6.1.5
Auto Category - Revised  Popular! (More than 5000 hits)
Version: 2.9
by: Shadowfen [More]
Depends on the following (separately installed) libraries: LibSFUtils, LibAddonMenu-2.0, LibMediaProvider-1.0, and LibDebugLogger

Auto Category adds categories to your inventory, bank, guild bank, craft bag, and crafting station screens. Fully customizable!

Features
  • Pre-defined rules and settings for beginners, download and use with no more settings required. Just that easy!
  • A nice header is added for each category. Get a clear view of your inventory.
  • Auto group for your set items without adding rules one by one.
  • Use pre-defined or your own rules, applying them to your backpack/bank/guild bank/craft bag/craft station/home storage, it will refresh categories immediately without reloading.
  • Fully customizable rules based on LUA, for advanced users you can categorize items as the way you want.
  • Rule checking to assist you in writing rules that can work.
  • Wiki documentation for learning to create rules.
  • [For Developers] Supports creation of separate plugin addons to integrate between other Addons and AutoCategory. See the new embedded Plugins files (FCOIS, Iakoni, ItemSaver, etc) for examples of simple and complex plugin integration.
  • Believed to auto integrate with all interfaces. Keyboard is fully supported. Gamepad supports most of them, and
    Gamepad with BetterUI is supported.

Integrates with the following addons:
Wiki:
https://github.com/Shadowfen/AutoCategory/wiki

Based on: RockingDice's Auto Category
2.9 (35):
COLOR="MediumSlateBlue"]Enhancement[/color]
  • New value added for
    Code:
    type()
    : "container_currency" allows you to identify a container of transmute crystals. Requested (and code provided) by Drakhyr.

2.8 (33):
COLOR="MediumSlateBlue"]Enhancement[/color]
  • New function isinbackpack() allows you to check if items is in your backpack or is currently being worn. Requested by AlbertVonMoosseedorf. An example of use for this new function could be a "deconstruct inventory" to list things that you want to decon that ignores the items in the bank. For instance:
    Code:
    isinbackpack() and not ismonsterset() and traitstring("intricate","invigorating","training") and ((type("armor","weapon") and not isset()) or equiptype("head","shoulders"))

2.7.2 (32):
  • Corrected the text for Home Storage Chests in German thanks to report by AlbertVonMoosseedorf.

2.7.1 (31):
  • Parameter values "mythic" or "orange" for the function quality() now really does allow you to check if items are mythic quality. (Finally got a mythic item to test with!)

2.7 (30):
Enhancement
  • New parameter values "mythic" or "orange" for the function quality() allows you to check if items are mythic quality.

2.6 (29):
Enhancement
  • New function istreasure() allows you to check if items are considered Treasure (i.e. random junk that you can sell for good money).

2.5 (28):
  • Updated the ITEM_QUALITY_ values to correspond to the change to ITEM_DISPLAY_QUALITY_ values that was brought in by Greymoor.

2.4.6 (27):
  • API bump.

2.4.5 (26):
  • Added Russian language strings courtesy of Ckau.

2.4.4 (25):
  • Set up the character default settings to the same as the account-wide default settings.
  • Add in minimum version checking for UnknownTracker.
  • Removed version checking for a library that we don't even use.

2.4.3 (24):
  • Add in predefined rules for UnknownTracker integration plugin.

2.4.2 (23):
  • Remove annoying debug printout.

2.4.1 (22):
  • Fix problem with isunknown() returning false where none of the toons knew the item.
  • Fix addon version.

2.4 (21):
COLOR="MediumSlateBlue"]Enhancement[/color]
  • Now integrated with the Unknown Tracker Addon to allow you to write rules about if a recipe, motif, style page, furnishing recipes, or runeboxes are unknown to your character(s). Requires version 0.63 of the addon "Unknown Tracker" to be installed for this to work. (Thanks to kadeer for modifications to "Unknown Tracker" to allow this to work!)
  • New function isunknown() with zero or more strings to match knowledge of the recipe to the named characters (names are case sensitive). If you use isunknown() without any parameters, it will return true if the learnable item (recipe, etc) is unknown to ANY of your toons. If you use isunknown("me") with the special parameter "me" then it will return true if the learnable item is unknown to the toon that you are currently logged in on. Finally you can specify specific toon names as parameters so you can tell if the learnable item is unknown to your specific "crafter" toons. (Note that the options for Unknown Tracker to turn off displaying for specific types of items will also turn off AutoCategory's ability to detect them with this rule.)
  • New function isrecipeunknown() which does the same thing as isunknown() except only for food and drink provisioning recipes.
  • New function isfurnishingunknown() which does the same thing as isunknown() except only for furnishing recipes.
  • New function ismotifunknown() which does the same thing as isunknown() except only for motifs.
For those of you who are new to the Unknown Tracker addon, it will add lists of characters to the inventory item information boxes (tooltips) with colors distinguishing the toons who know if from the toons that do not know it. That cannot be turned off at this time. If you have another addon also doing that, it might be possible that the other addon will allow you to turn those off. In particular, ESO Master Recipe List will add character lists to the Recipes, and TraitBuddy will add them to motifs - and both can be turned off.

2.3.1 (20):
  • Set AddonVersion in manifest file.
  • Now checks dependent library versions (where possible) and will write error messages to LibDebugLogger to indicate when a dependent library is out-dated for the current version of AutoCategory. Messages can be viewed with the DebugLogViewer (recommended addon).

2.3 Changes:
COLOR="MediumSlateBlue"]Enhancement[/color]
  • Added an itemstyle() with one or more strings that are the names of motifs. This function will return true if the style of the item matches one of the names in the parameter list of itemstyle(...). Capitalization is ignored, but spelling of the motif name must be correct - to include spaces and punctuations marks - for instance "dro-m'athra" must include both the "-" and the "'", and "dark brotherhood" is two words separated by a space. (Note that with multi-word motif names, the rule checker will probably warn that it does not recognize the words after the first word of the name.)

2.2.2 Changes:
  • Added sort key conflict resolution by request of Mladen90.

2.2.1
  • Fix version to prevent being listed as "Out of Date".

2.2 Changes:
COLOR="MediumSlateBlue"]Enhancements[/color]
  • Added an charname() with one or more strings that are the names of your characters. This function will return true if the current character name matches one of the names in the parameter list of charname(...). This will allow you to write rules which apply to specific characters only.

2.1.1
  • API Bump

2.1 Changes:
Bug Fixes
  • Fixed problem with islockpick() not being recognized as a function. (reported by Amber1019)

Enhancements
  • Modified islockpick() so that it only gets lockpicks (lockpick tools) instead of lockpicks and repair kits (the "other" tools).
  • Added an ischarbound() to items that are marked as "Character Bound" in inventory. Note that items that match ischarbound() will also match isbound() since character bound is a type of binding. If you want bound that are not also character bound, you will need to specify "~ischarbound() and isbound()" for account bound items only.

2.0.5 Changes:
  • Fixed problem with getmaxtraits() returning one more than the number of traits on a crafted potion. (reported by TheMikrobe)
  • API bump

2.0.4 Changes:
  • Fixed bug that was causing bag categories that had been changed in priority or removed from the bag to be replaced or duplicated (with the original priority) if they were part of the default set. (reported by rhaeven and LeinadOrarogep)

2.0.3 Changes:
  • Fixed bug that was causing getpricettc() (reported by Ivo_ESO), getpricemm(), and alphagear() to not work in rules.

2.0.2 Changes:
  • Fixed minor bug in Bag Export.
  • Fixed bug in type() and sptype() where it was ignoring any arguments after the first one.

2.0.1 Changes:
  • Fixed loading bug in integration for SetTracker, TTC, and Master Merchant.

2.0 Changes:
Breaking Changes
  • Now requires the libraries LibSFUtils, LibAddonMenu-2.0, and LibMediaProvider-1.0 to be installed separately.
  • The SavedVariables for version 2.0 have changed formats from 1.37 in order to support multiple servers and character name changing. This means that 2.0 will not be able to read in your 1.37 category definitions. I recommend that you move your live\SavedVariables\AutoCategory.lua somewhere else (or print it) so that you can refer to your old rules to enter them back into the new AutoCategory.

Bug Fixes
  • Fixed error that prevented AutoCategory from working with the Quality Sort addon. (Thanks to Silvereyes for the corrected code.)
  • Included in the patch for Inventory Grid View integration by Provision to properly display the default icons for Ornate, Intricate, Research, etc. on the grid cells instead of next to them.

Enhancements
  • Elsweyr support.
  • Changed the AutoCategory settings page to try to make it easier to understand and use.
  • Created a wiki based on Rockingdice's which I have permissions to update. Updated and revised help content.
  • NEW: Added a "Check" button to the Add Category section so that you can test to see that your rule will compile properly when you write it. If it does not compile correctly, the area to the left of the Check button will show an error message to try to tell you what was wrong with it.
  • Added a "Hide ungrouped items" option to the Bag Settings which will turn on/off the display of inventory items which do not match any of the Categories which you have assigned to that particular bag. These are the items that are typically listed in "Other" (unless you've changed the name in the Appearance Setttings).
  • Modified iscrafted() so that it will return true for crafted potions or poisons so you can:
    type("poison","potion") and iscrafted()
  • Added the base ability to use some convenience items that are actually combinations of several base game items.
  • Added convenience items:
    Item Types (type):
    o enchanting_rune - this will match against enchanting_rune_aspect, enchanting_rune_essence, or enchanting_rune_potency
    Specialized Item Types (sptype):
    o glyph - this will match against glyph_armor, glyph_weapon, or glyph_jewelry
  • Added an islockpick() to detect lockpicks in inventory since, due to a Zenimax bug, lockpicks do not belong to type("lockpick").
  • Added some convenience values to traittype() that combines existing values:
    o intricate - this will match against armor_intricate, jewelry_intricate, or weapon_intricate
    o divines - this will match against armor_divines
    o infused - this will match against armor_infused, jewelry_infused, or weapon_infused
    o ornate - this will match against armor_ornate, jewelry_ornate, or weapon_ornate
    o nirnhoned - this will match against armor_nirnhoned, or weapon_nirnhoned
  • Added support for the development of addon integrations to AutoCategory as separate plugins. Rewrote three of the internally provided integrations (FCOIS, Iakoni, and ItemSaver) in the form that standalone plugin integrations would take to demonstrate how to register the plugin with AutoCategory, provide additional rule functions, predefined rules, and localization strings where necessary.

Predefined Rules
  • Changed the way that predefined rules are loaded so that they are always loaded first and then your customizations are loaded afterwards. This allows you to get new predefined rules automatically added as they come out with addon or plugin updates. It also means that if you accidentally delete a predefined rule, you can get it back by simply reloading ui.
  • Changed the way that predefined rules are loaded so that predefined rules for addon integrations such as FCOIS and Iakoni Gear Changer are only loaded when you have those particular addons installed. (Note that this applies when the addons are first installed - once the predefines get loaded once, they will get saved to your saved variables. Rules in SavedVariables are always loaded after that until they are deleted. A planned enhancement that did not make this version is to only save customized categories that are actually customized, since now predefines always get loaded.)
  • Added predefined rules for FCOIS dynamics 11-30 for when you are starting AutoCategory without preexisting saved variables.

Localization
  • Expanded the remaining alternative language files to include strings for the FCOIS dynamics 11-30.
  • Added additional localization strings for German from Baertram's git pull request.
  • Removed the alternative language files which were still in English. When we get translations, we can add them back with appropriate values.
  • Converted the way that language strings are defined to use the new LibSFUtils.LoadLanguage() function to load the particular language required (or the specified default if the client language is not available).

Internal (non-visible) Changes
  • Moved FCOIS integration into an included plugin file.
  • Moved ItemSaver integration into an included plugin file.
  • Moved GearChangerByIakoni integration into an included plugin file. Moved the GearChanger language strings into the plugin and load them separately using the AutoCategory.LoadLanguage() to supplement the existing string tables. While not strictly necessary, it acts as both a proof-of-concept and an example for how external plugins to AutoCategory can work.
  • Removed specific integration code for DoItAll addon as that integration was moved to the DoItAll addon instead of residing in AutoCategory (Baertram's pull request).
  • Adopted by Shadowfen after prolonged lack of response from the previous authors. Renamed to "AutoCategory - Revised".


1.37 Changes:
Released by Shadowfen
  • New filter function: getmaxtraits()
    When used with posions and potions, such as this rule:
    type("poison","potion") and getmaxtraits() <=2
    it can tell you which are crafted (i.e. having more than one trait).
    This new feature is courtesy of Tonyleila.
  • Updated the specialized item types. This adds:
    Specialized Item Types (sptype):
    o trophy_toy
    o holiday_writ

1.36 Changes:
Released by Shadowfen
  • Updated the item types, specialized types, filter types, and trait types lists with the latest values from Wrathstone. This adds:
    Item Types (type):
    o jewelry_booster
    o jewelry_material
    o jewelry_raw_booster
    o jewelry_raw_material
    o jewelry_raw_trait
    o jewelry_trait
    o recall_stone
    Specialized Item Types (sptype):
    o furnishing_attunable_crafting_station
    o furnishing_material_jewelry
    o recall_stone_keep
    o recipes_jewelry_sketch_furnishing
    o trophy_collectible_fragment
    o trophy_upgrade_fragment
    o weapon
    Filter Types (filtertype):
    o jewelry
    Trait Types (traittype):
    o jewelry_bloodthirsty
    o jewelry_harmony
    o jewelry_infused
    o jewelry_intricate
    o jewelry_protective
    o jewelry_swift
    o jewelry_triune

1.35 Changes:
Released by Shadowfen
  • Bumped API version for Wrathstone
  • LibStub and LibAddonMenu-2.0 must now be installed separately from AutoCategory.
  • Added support for FCOIS dynamics 11-30.
  • Merged in Provision's integration fixes for IGV.
  • Added jewelry crafting materials, raw materials and boosters for the sptype() check
  • Fixed a crash when a rule could not compile.

1.34 Changes:
  • Added itemname() to match items by name. Returns true if the item name contains any of the provided strings (case insensitive), e.g. itemname("Maelstrom", "Alkosh")


1.33 Changes:
  • Bumped API version for Murkmire.


1.32 Changes:
  • More huge performance improvements! Thanks again to Shadowfen who did all the work here. (Pre-compile rules as they are changed)
  • Replaced Set Tracker support function GetSetTrackerState() with IsTracked(). If you used the old function, you will need to update your rule (sorry). This was done to bring the usage inline with the way the other similar functions work. Usage, e.g.: IsTracked("Sell/Decon", "Collecting")


1.31 Changes:
  • Big performance increase (2x or better for me), thank you to Shadowfen for the code change suggestion!
  • Updated libraries


1.30 Changes:
  • Added French translation. Big thanks to Hasgaad!


1.29 Changes:
  • HOTFIX - resolve errors at merchant due to Wolfhunter API changes.


1.28 Changes:
  • Bumped API version for Wolfhunter.


1.27 Changes:
  • Bumped API version for Summerset.
  • Added support for jewelry crafting ingredients. Note: you will need to either create a new rule yourself, or reset AutoCategory to default settings to grab the new default rule.
    To create your own rule, use
    Lua Code:

    filtertype("jewelrycrafting")

    To reset to default settings: In the Auto Category add-on menu, use the Defaults button. Then use the /reloadui command. Important: this will remove any custom rules/settings you have defined.
  • New API function "IsMarkedIS()" - use to test whether an item is marked with Item Saver. Note that FCO ItemSaver users should continue to use "IsMarked()"


1.26 Changes:
  • New API function "islocked()" - use to test whether an item has been locked.


1.24 Changes:
  • Resolve circular dependency issue with DoItAll (requires matching update to DoItAll).



1.23 Changes:
  • Added Set Tracker support! Use "getsettrackerstate()" to retrieve the name of the Set Tracker category, if an item is tracked.
  • Added charlevel() and charcp() to pull current character level and CP. Can be used to compare item level to your character level with a custom rule. (Thanks to VulcanTourist)


1.22 Changes:
  • You can now define separate settings for your home storage chests (they will take their initial settings from your bank settings, but can be customized at will).


1.21 Changes:
  • Added support for home storage chests (big thanks to raj72616a). Currently, they will use the settings selected for your bank (no custom settings for home chests yet).
  • Bumped API version for Dragon Bones.
  • New maintainer (crafty35a).



1.19 Changes:
  • Fixed Localization.
  • New Feature: Collapsed/Expanded status can be saved now. You can turn it on in the general setting menu.


1.18 Changes:
  • Fixed Bug: IGV will show the last category correctly.
  • Fixed Bug: Items Count can be turned off permanently.
  • Fixed Bug: Quest Panel will not complain about lua error.


1.17 Changes:
  • Removed debug logs in destruct/improvement panel


1.16 Changes:
  • New Feature: Collapsible Category. You can now click the header to fold all items inside. Get an overall view of your inventory! Context Menu is available, you can collapse/expand all headers with one click.
  • New Feature: Hide-able Category. You can hide some categories to focus on the items you need to deal with. Also you can hide the items that are not matched in the 'Other' category. Can be set in bag setting menu.
  • New Feature: Items Count. You can get a total number about how many items inside the category. This can be turned off in the general setting menu.
  • Account Wide setting changed: You can switch account wide/character wide for each of your characters. (* Need to select again if you use character setting before, don't affect the bag settings)
  • Fixed bug: Removed duplicated rules in bag setting.
  • Fixed bug: German set names should be able to be matched now.
  • Changed api:keepresearch()
  • After a lot of tests, the api is not working fine. So I decided to make the api work more simple: It will match all the items can be researched. If you want better result, please use it with other api together. This is a basic idea to filter the item that is not part of a set and can be researched:
    Lua Code:

    keepresearch() and not isset()
  • New api:isset() api:ismonsterset()


1.15 Changes:
  • New feature: Category header's height is customizable!
  • New feature: You can change the name of ungrouped Category.
  • New feature: Added a message in chat when toggling the add-on's function, and a switch for it to turn on/off.
  • Fixed bug: Toggling in Inventory Grid View should not result a bad layout.
  • Fixed bug: Removed tag should not to be restored after relog.
  • New Add-ons Integrated!
    Do It All: You can now use it with AC together.
    Alpha Gear: Added a new api:alphagear
    Master Merchant: Added a new api:getpricemm
    Tamriel Trade Centre: Added a new api:getpricettc
  • New api:isinbank


1.14 Changes:
  • CwC is supported!
  • Fixed integration for Inventory Grid View(3.2).


1.13 Changes:
  • Fixed Bug: Setting for Craft Station is not working.
  • Added API:
    Code:

    getquality

    please see api:getquality
  • Updated localization for Chinese.


1.12 Changes:
  • New Function: Export to all bag settings. You can now replace all bag settings by one of them.
    Added API:
    Code:

    quality

    please see api:quality
  • Fixed Bug: Import from bag setting will incorrectly make settings be linked together.


1.11 Changes:
  • New bags supported: Guild Bank / Craft Bag / Craft Station for both keyboard and gamepad mode.
  • New function: Import from bag setting: you can import from a bag setting to replace current one. No need to create it from the beginning. Make backups by copying your AutoCategory.lua in SavedVariables folder!
  • New add-on supported: Quick Menu you can toggle Auto Category by Quick Menu to save a key binding, check it out!
  • Added API:
    Code:

    sellprice
    islearnable

    please see api:sellprice and api:islearnable for more info.


1.10 Changes:
  • Added custom names from FCO Item Saver
  • Added API:
    Code:

    armortype
    weapontype

    please see api:armortype and api:weapontype for more info.
  • Added deconstruct & improvement support for keyboard mode.


1.09 Changes:
  • Integrated FCO Item Saver
    Added API:
    Code:

    ismarked

    please see api reference and tutorial and examples for more info.
    Added Keybinding to toggle on/off.


1.08 Changes:
  • Fixed Category 'Trait/Style Gems' (If not changed, please try to restore to defaults)
  • Added Localization support.


1.07 Changes:
  • Fixed a rare issue of IGV integration.


1.06 Changes:
  • Fixed Quest tab issue.
  • Adjusted the height of header to the same as item row.
  • Added custom appearance of header text. You can set up them in the setting menu (or type /ac)


1.05 Changes:
  • Fixed multiple add-on compatible issue.
  • Fixed auto set name in different languages.
  • Added API:
    Code:

    iscrafted

    please see api reference and tutorial for more info.


1.04 Changes:
  • Added gamepad trade inventory support. Thanks @catsith105 for testing!


1.03 Changes:
  • Integrated with 'Inventory Grid View'
  • Added a tutorial button.
  • Added a wiki home page and tutorial page.


1.02 Changes:
  • Fixed banking issue with deposit/withdraw items.


1.01 Changes:
  • Updated lib: LibAddonMenu to r24
  • Refined Addon Setting Menu
Optional Files (0)


Archived Files (31)
File Name
Version
Size
Uploader
Date
2.8.1
74kB
Shadowfen
08/08/20 10:43 PM
2.8
74kB
Shadowfen
08/08/20 10:39 PM
2.7.2
74kB
Shadowfen
07/30/20 09:31 PM
2.7.1
74kB
Shadowfen
07/02/20 10:41 PM
2.7
74kB
Shadowfen
06/26/20 04:20 PM
2.7
719kB
Shadowfen
06/25/20 09:19 PM
2.6
74kB
Shadowfen
06/12/20 03:05 PM
2.5
74kB
Shadowfen
05/28/20 04:04 PM
2.4.5
74kB
Shadowfen
04/06/20 06:15 PM
2.4.4
70kB
Shadowfen
03/07/20 11:13 PM
2.4.3
70kB
Shadowfen
02/17/20 06:07 PM
2.4.2
70kB
Shadowfen
02/16/20 10:29 AM
2.4.1
70kB
Shadowfen
02/16/20 12:33 AM
2.4
70kB
Shadowfen
02/15/20 10:16 AM
2.3.1
67kB
Shadowfen
02/07/20 12:26 AM
2.3
66kB
Shadowfen
12/31/19 08:17 PM
2.2.2
66kB
Shadowfen
12/31/19 12:34 AM
2.2.1
66kB
Shadowfen
10/30/19 05:22 PM
2.2
66kB
Shadowfen
10/25/19 03:58 PM
2.1.1
66kB
Shadowfen
10/20/19 05:05 PM
2.1
66kB
Shadowfen
09/17/19 08:32 PM
2.0.5
65kB
Shadowfen
08/15/19 11:44 PM
2.0.4
65kB
Shadowfen
06/08/19 10:29 AM
2.0.3
65kB
Shadowfen
05/27/19 12:48 PM
2.0.2
74kB
Shadowfen
05/20/19 02:22 PM
2.0.2
64kB
Shadowfen
05/20/19 08:25 AM
2.0.1
78kB
Shadowfen
05/19/19 06:57 PM
2.0
77kB
Shadowfen
05/19/19 06:00 PM
1.37
72kB
Shadowfen
03/20/19 02:12 PM
1.36
71kB
Shadowfen
03/16/19 08:24 PM
1.35
71kB
Shadowfen
03/13/19 07:00 PM


Post A Reply Comment Options
Unread 07/02/20, 10:47 PM  
Shadowfen
AddOn Author - Click to view AddOns

Forum posts: 56
File comments: 437
Uploads: 11
Re: Re: Re: possible?

Originally Posted by Gandamir

I have tried this, and am having issues. My setup is as follows:
Rule: quality("mythic")
Bag Setting: 55
All other settings are default.

Mythic items do not show seperatly, but are still included in the autoset() rule listed at bag setting 49.

If you need help testing, please reach out to @Gandamir on the PC/EU server, or via esoui.com if you are on the US server.
Give version 2.7.1 (just released) a try. I believe it's working now.
Report comment to moderator  
Reply With Quote
Unread 06/29/20, 11:14 AM  
Gandamir

Forum posts: 12
File comments: 38
Uploads: 0
Re: Re: possible?

Originally Posted by Shadowfen
You would make a rule (named whatever you like) that checks if the quality of the item is mythic (and possibly is a particular type of item like a weapon).

Code:
quality("mythic")
or

Code:
quality("orange")
It should work, but I don't have any such items to test it with at the moment... so let me know.
I have tried this, and am having issues. My setup is as follows:
Rule: quality("mythic")
Bag Setting: 55
All other settings are default.

Mythic items do not show seperatly, but are still included in the autoset() rule listed at bag setting 49.

If you need help testing, please reach out to @Gandamir on the PC/EU server, or via esoui.com if you are on the US server.
Report comment to moderator  
Reply With Quote
Unread 06/26/20, 04:26 AM  
charlie.montes

Forum posts: 0
File comments: 4
Uploads: 0
Thanks for this awesome addon.
Report comment to moderator  
Reply With Quote
Unread 06/26/20, 02:52 AM  
Baertram
 
Baertram's Avatar
AddOn Author - Click to view AddOns

Forum posts: 3095
File comments: 3718
Uploads: 63
Re: Use AutoCategory also for Quick Access View

Originally Posted by AlbertVonMoosseedorf
Hi @Shadowfen,

My Quick Access View is growing up and it's a completely mess for placing items into the quick slot bar.
Even trash Items which are placed in the trash bag are included into the Quick Access View. Is it possible to use AutoCategory also for the Quick Access View ?

It's not neccessary to define new groupings for that, just use the normal inventory grouping for this. I anyway have no differencies between the bags, I only use one View and export it to all al kind of Views.
You can also ty this simple addon, it addss more filters to the quicklot tab in your inventory:
https://www.esoui.com/downloads/info...otFilters.html
Report comment to moderator  
Reply With Quote
Unread 06/25/20, 09:23 PM  
Shadowfen
AddOn Author - Click to view AddOns

Forum posts: 56
File comments: 437
Uploads: 11
Re: possible?

Originally Posted by kindredspirit
Is it possible to make a mythic item category that will accept the new mythic items from antiquity whether they be rings or gloves etc…?
Version 2.7, just released

2.7 (30):
Enhancement
  • New parameter values "mythic" or "orange" for the function quality() allows you to check if items are mythic quality.

You would make a rule (named whatever you like) that checks if the quality of the item is mythic (and possibly is a particular type of item like a weapon).

Code:
quality("mythic")
or

Code:
quality("orange")
It should work, but I don't have any such items to test it with at the moment... so let me know.
Last edited by Shadowfen : 06/25/20 at 09:23 PM.
Report comment to moderator  
Reply With Quote
Unread 06/25/20, 06:27 PM  
kindredspirit

Forum posts: 3
File comments: 93
Uploads: 0
possible?

Is it possible to make a mythic item category that will accept the new mythic items from antiquity whether they be rings or gloves etc…?
Report comment to moderator  
Reply With Quote
Unread 06/21/20, 04:57 PM  
Shadowfen
AddOn Author - Click to view AddOns

Forum posts: 56
File comments: 437
Uploads: 11
Originally Posted by SnakE
The ismonsterset() function seems to return true for perfected weapons. E.g. it definitely doese that for perfected Maelstrom and perfected Asylum Sanctorium stuff.
Yes. It is also true for the Murkmire Blackrose Prison weapons. It's just how ZOS marks them...

If you want to separate them, you might make one category for

ismonsterset() and type("weapon")

and another for

ismonsterset() and type("armor")
Last edited by Shadowfen : 06/21/20 at 05:01 PM.
Report comment to moderator  
Reply With Quote
Unread 06/21/20, 02:13 AM  
SnakE

Forum posts: 0
File comments: 17
Uploads: 0
The ismonsterset() function seems to return true for perfected weapons. E.g. it definitely doese that for perfected Maelstrom and perfected Asylum Sanctorium stuff.
Report comment to moderator  
Reply With Quote
Unread 06/17/20, 05:37 PM  
Shadowfen
AddOn Author - Click to view AddOns

Forum posts: 56
File comments: 437
Uploads: 11
Originally Posted by SnakE
The standard meaning of a "warning" in compilers/interpreters is that an expression has tricky (often legacy) semantics which the programmer might not expect. The standard practice is that it should be possible to reword the expression to avoid any warnings. A number is a number. There is no way to reword it. In my opinion, if a number appears where a number is expected then the expression is correct and there shouldn't be a warning.
Compilers/interpreters are not typically written in an interpreted language whose only complex type is a table to run in a sandbox provided by another program whose performance is critically important (and easily broken by said sandboxes). Writing the linter that you want would have a severe performance penalty, making the addon and indeed the game prohibitively slow if not completely unplayable.

That is why we have a relatively fast yet simplistic verifier to point out to the more capable human brain points that might need investigation because the verifier is unable to say whether or not something might not be correct.

Originally Posted by SnakE

type("armor","weapon") and not islocked() and ((not equiptype("neck","ring") and quality() < 4) or (equiptype("neck","ring") and quality() < 3))
This expression does not work. It always produces an empty set.
It does not work because quality() takes arguments such as "white", "green", etc and returns either true or false if the quality of the item matches any of the qualities specified in the arguments. The function you were actually looking for was getquality() which does return a number representing the quality level of the item.
Report comment to moderator  
Reply With Quote
Unread 06/16/20, 06:55 PM  
SnakE

Forum posts: 0
File comments: 17
Uploads: 0
Originally Posted by Shadowfen
The warning is an "I see something that I don't recognize, so you'll have to check that it is right". It doesn't mean that the rule is just wrong the way that an Error: does. Numbers and anything that you put in ""s might not be recognized and you will get a warning for (and that's probably okay). If the unrecognized word isn't in quotes, or it's a parameter to a function that we know only takes game-specific values (like "trophy_recipe_fragment") - that's when you have a problem that you need to fix.
The standard meaning of a "warning" in compilers/interpreters is that an expression has tricky (often legacy) semantics which the programmer might not expect. The standard practice is that it should be possible to reword the expression to avoid any warnings. A number is a number. There is no way to reword it. In my opinion, if a number appears where a number is expected then the expression is correct and there shouldn't be a warning.

Originally Posted by SnakE
boundtype("on_equip") and not isbound() and not keepresearch() and getpricettc() > 900
This expression does work correctly even though it shows a warning.

Originally Posted by SnakE
type("armor","weapon") and not islocked() and ((not equiptype("neck","ring") and quality() < 4) or (equiptype("neck","ring") and quality() < 3))
This expression does not work. It always produces an empty set. I had to replace `quality() < N' with `quality("white","green",...)' to make it work.
Report comment to moderator  
Reply With Quote
Unread 06/16/20, 06:32 PM  
Shadowfen
AddOn Author - Click to view AddOns

Forum posts: 56
File comments: 437
Uploads: 11
Originally Posted by SnakE
I'm getting "unrecognized" every time I use a number in a rule. E.g.

boundtype("on_equip") and not isbound() and not keepresearch() and getpricettc() > 900

Warning - Unrecognized: 900

Same here:

type("armor","weapon") and not islocked() and ((not equiptype("neck","ring") and quality() < 4) or (equiptype("neck","ring") and quality() < 3))

Warning - Unrecognized: 4, 3
The warning is an "I see something that I don't recognize, so you'll have to check that it is right". It doesn't mean that the rule is just wrong the way that an Error: does. Numbers and anything that you put in ""s might not be recognized and you will get a warning for (and that's probably okay). If the unrecognized word isn't in quotes, or it's a parameter to a function that we know only takes game-specific values (like "trophy_recipe_fragment") - that's when you have a problem that you need to fix.

(The stuff like partial item names, set names, or mark names for one of the integrating addons cannot be checked as being correct because it would have to be able to do it for all languages - and mark names such as for Item Saver can be any random name at all.)
Report comment to moderator  
Reply With Quote
Unread 06/16/20, 03:36 PM  
SnakE

Forum posts: 0
File comments: 17
Uploads: 0
I'm getting "unrecognized" every time I use a number in a rule. E.g.

boundtype("on_equip") and not isbound() and not keepresearch() and getpricettc() > 900

Warning - Unrecognized: 900

Same here:

type("armor","weapon") and not islocked() and ((not equiptype("neck","ring") and quality() < 4) or (equiptype("neck","ring") and quality() < 3))

Warning - Unrecognized: 4, 3
Report comment to moderator  
Reply With Quote
Unread 06/14/20, 06:55 AM  
AlbertVonMoosseedorf

Forum posts: 2
File comments: 35
Uploads: 0
Use AutoCategory also for Quick Access View

Hi @Shadowfen,

My Quick Access View is growing up and it's a completely mess for placing items into the quick slot bar.
Even trash Items which are placed in the trash bag are included into the Quick Access View. Is it possible to use AutoCategory also for the Quick Access View ?

It's not neccessary to define new groupings for that, just use the normal inventory grouping for this. I anyway have no differencies between the bags, I only use one View and export it to all al kind of Views.
Report comment to moderator  
Reply With Quote
Unread 06/12/20, 04:11 PM  
TagCdog

Forum posts: 17
File comments: 32
Uploads: 0
Originally Posted by Shadowfen
Originally Posted by TagCdog
Hi @Shadowfen,

Would it be possible to add the option for Auto Category to automatically flag all items within a category with a FCO Item Saver flag?

For example, automatically mark all items within the "Armor", "Weapon", "Necklace", and "Ring" categories as Deconstructable?

I don't know of any inventory/filtration/organization/assistant addons that integrate with FCO Item Saver to where it includes the ability to apply flags to items rather than just passively reading existing flags.

I think it could be very useful, especially as a plausible solution for my Grinding Loot Assistant idea.

Thank you for your time and assistance!
FCO Item Saver does not provide access to that kind of functionality from outside of the addon. The access that other addons get to FCO Item Saver is basically read-only.
Wow, this topic makes so much more sense now. Thank you for explaining that! Hopefully that does become a thing eventually.
Report comment to moderator  
Reply With Quote
Unread 06/12/20, 09:01 AM  
Myrthian

Forum posts: 18
File comments: 75
Uploads: 0
Originally Posted by Shadowfen
Originally Posted by Blackwolfe
Originally Posted by Myrthian
I have no idea how precise the rule check is, but sorting Counterfeit Pardon Edicts by partial item name gives a warning, but it sorts the item correctly.

It did the exact same thing for me when I tried tried to make a filter for alphagear sets. It said unrecognized but the filter worked perfectly despite that.
The warning is an "I see something that I don't recognize, so you'll have to check that it is right". It doesn't mean that the rule is just wrong the way that an Error: does. Numbers and anything that you put in ""s might not be recognized and you will get a warning for (and that's probably okay). If the unrecognized word isn't in quotes, or it's a parameter to a function that we know only takes game-specific values (like "trophy_recipe_fragment") - that's when you have a problem that you need to fix.

(The stuff like partial item names, set names, or mark names for one of the integrating addons cannot be checked as being correct because it would have to be able to do it for all languages - and mark names such as for Item Saver can be any random name at all.)
Thanks: I did expect it to be along the lines of "It's not an actual error, more of a warning due to not being able to check a partial string for its correctness".

As improvement: making it more obvious in the description of a warning that a warning can also be displayed if the rule itself is correct or something similar, just to prevent people like me thinking "Why is there a warning when the rule itself works just fine".
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: