ArkInventory
ArkInventory (for The War Within)
:boom: Please ensure you are using the latest alpha version if you have the War Within client.
ArkInventory (for Retail, Classic, and Cataclysm)
ArkInventory's display windows are built from "virtual bars", you assign categories to bars so that items in that category are displayed on the specific bars you want. There is no limit to the number of bars you can have inside a window but obviously you only have so much screen real estate before it becomes "too many".
ArkInventory uses several methods to assign a default category to an item such as what professions you have, tooltip scanning, basic type/subtype and PeriodicTable. You then assign those categories to a virtual bar.
You can also over-ride the default category by creating a rule that matches either a single or multiple items.
Overview:
- user configurable window width and height
- separate keybindings for each location for easy viewing
- assign items to a category of your choice (overrides the default assignment)
- assign categories to the bar of your choice
- unlimited number of bars (there are practical limits though before your screen becomes full)
- sort each bar differently if required
- user configurable bars per row
- sell junk items automatically or manually (delete available via a keybinding or right clicking when at a vendor)
- random pet and mount summons. can also assign a group of them to select from
Key Bindings:
- Press ESCAPE to bring up the blizzard menu
- click on Key Bindings
- scroll down to AddOns > ArkInventory
- bind the keys you want to use
Need Help?
:memo: Wiki
:memo: Frequently Asked Questions
:memo: Sorting
:memo: Rules
:memo: If you are having an issue the first step is to disable all other mods and test with only ArkInventory loaded
:memo: If the issue is still there, please check for an existing issue and create a new issue if required.
:memo: If the issue is gone, re-enable your other mods one by one until the issue comes back, then note the last mod you enabled in your issue as well as notifying the author of the other mod
See ChangeHistory.md for changes to the latest version. See VersionHistory.md for all previous changes.
:boom: The NoLib variant
it seems quite a few people are somehow getting the NoLib variant from their download client when they didn't specifically ask for it, instead of the full variant, and its causing issues as they don't have the required libraries installed separately. Please ensure you are downloading the full. if you see nolib in the filename then its the wrong variant, unless you are actually installing all of the required libraries separately as well. If you have to you can manually download the full variant from CurseForge, WoWInterface, or Wago.
:boom: Junk Sell getting blocked
While auto-destroy remains blocked, From 30960 onwards you can setup a Key Binding to manually sell and destroy your items. Note that blizzard require one keypress per item deletion, so if you have multiple items that need to be deleted you will need to press the Key Binding multiple times. A message will be output if you have remaining items that can still be deleted.
:warning: Ensure you have backup copies of your saved variables file
Sometimes you cannot revert back to a previous version without a backup, especially alpha or beta versions, so before upgrading please make sure you have made a backup of your saved variables file
Your saved variables file is normally located at ...\World of Warcraft\_client_\WTF\Account\yourwowaccountname\SavedVariables\ArkInventory.lua
It is your responsibility to ensure you have adequate backups of your saved variables file. You dont have to do them frequently, just after you've made major changes to your config is probably fine for most people, but you should get into the habit of making backups because when it does corrupt you wont have to reconfigure everything from scratch.
If you have your download client set to automatically download alpha/beta versions you should definitely have backups.
A simple way to back up the saved variables file is to just do a copy and paste then rename the new file (using the version number of ArkInventory or the date is a good idea), eg ArkInventory-30900.lua, or ArkInventory-20191228.lua
Since patch, ArkInventory for whatever reason is destroying my frame rate. Wasn't doing it prior to patch.
Going to be honest, this specific addon has given me and many others nothing but trouble so far through Legion. First it was hiding bag slots/items for ~2 weeks and now it's frame rate issues. Been using Ark since Wrath. Obviously would like to continue using it but certainly won't if it's going to hamper game performance in any capacity.
I'm having frame rate issues/stutter as well. The addon is using a lot more memory than usual, it seems.
He's working on it and things will get fixed eventually, just use something else for now.
Me as well but only when my toons are in combat.
Hey there,
i've been experimenting with rules and wondered if the %d+ tooltip attribute does handle more than 3 digits. Since:
q( 4 )
and ilvl( 730, 900 )
and tooltip( "%+%d+ Intellect" )
would not sort items with more than 999 Intellect.
Did i do something wrong?
Greetings
Still does not recognize fishing bag. constant lua error, persistent since 7.0
is it an actual lua error or an arkinventory warning/error message?
could you post the error?
nvm. created one and i can see the error message. should be fixed in the next release
How do i could track item with BIND_TRADE_TIME_REMAINING in their tooltip ? (soulbound item tradeable)
anyone else have the resize dialog boxes not work?
I just installed ArkInventory today, switching from AdiBags, and on first load and every relaod I'm getting trying to index a nil value 'bagoptions' in 'ArkInventoryUpgrades.lua' in function 'DatabaseUpgradePostLoad' - am I missing a dependency or is this a current bug or something?
Message: ...terface\AddOns\ArkInventory\ArkInventoryUpgrades.lua:1103: attempt to index field 'bagoptions' (a nil value)
Time: 10/23/16 11:43:05
Count: 1
Stack: (tail call): ?
...terface\AddOns\ArkInventory\ArkInventoryUpgrades.lua:1103: in function `DatabaseUpgradePostLoad'
Interface\AddOns\ArkInventory\ArkInventory.lua:2264: in function <Interface\AddOns\ArkInventory\ArkInventory.lua:2255>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[1]"]:9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?
...y\Externals\curse\svn\Ace3-AceAddon\AceAddon-3.0.lua:558: in function `EnableAddon'
...y\Externals\curse\svn\Ace3-AceAddon\AceAddon-3.0.lua:651: in function <...y\Externals\curse\svn\Ace3-AceAddon\AceAddon-3.0.lua:636>
[C]: in function `LoadAddOn'
Interface\FrameXML\UIParent.lua:391: in function `UIParentLoadAddOn'
Interface\FrameXML\UIParent.lua:414: in function `CombatLog_LoadUI'
Interface\FrameXML\UIParent.lua:995: in function <Interface\FrameXML\UIParent.lua:891>
Locals: <none>
its probably a bug in the upgrade code. you may have tried arkinventory a long long time ago and its trying to upgrade your options.
you could probably just delete the arkinventory.lua saved variables file if youve not actually used it before and it should create a new one that doesnt need upgrading
in the mean time i'll see if i can work out what the issue is
Using CurseClient, I did an "Uninstall" and let it delete my settings, then an Install followed by an Update and it seems to not be erroring any more.
I think the smoothness of Blizzard's releases have spoiled us quite a bit, as I still recall the fear I had when BC and LK released, knowing that addons would be hosed for weeks.
Thanks for looking into it!
So... tonight I was raiding and my pc crashed... when I came back online my arkinventory configs were gone... everything is on default... :x
How can something like that happen? :x
it's happened to me numerous times :-( And the .bak file is from like 2 years ago. lol it never updates. not sure why.
I am having a problem with auto-sell gray items. Using the default ArkInventory profile, auto-sell grays is working fine. But when I use my own customized profile, grays aren't auto- selling.
The settings for selling junk in Config->General in my custom profile are the same as the default. They are set to sell grays.
This used to work but now it's not, and I have no idea why. Any suggestions or tips on how to debug this?
OK, I't something to do with my "Category Set" for my bag. When I go to...
Config->Controls->Bag
and Change the Category Set to use [9999] Default then the junk is selling again. But when I use my custom Category Set it stops working. So... something in this Category Set is blocking this. I have no idea what I should be looking for. How do I "fix" my Category Set?
when you go into debug mode are the items assigned to the System>Junk category?
Feature Modification for the masses:
SELL JUNK via Rule:
This allows you to generate a rule named "Junk" and it will autosell the Junk for you when you have the option enabled. Here are the steps to do it:
...\World of Warcraft\Interface\AddOns\ArkInventory\ArkInventoryJunk.lua
cat = ArkInventory.ItemCategoryGet( i )
isJunk = ( cat == cat_junk or rule_name == "Junk")
(ilvl(1,620) and (type("armor") or type("weapon"))) or
(type(0) and (subtype(1) or subtype(5)) and ireq(1,99))
Use at your own risk.
What "order" / priority are system rules?
I have a virtual bag with rule type("armor") and name("of the Unseen Path")
but the items are going into another virtual bag that is set to System Equipable items Soulbound
the items are valid for both bags, how do I give my rule the higher priority?
-----
Follow up: I just created a rule "equip() and soulbound()" since i can set the order for my rule
So, assuming it is not just ignorance/misuse on my part, let me make this a low-priority feature request for system rules to always be order "100" so I can get the behaviour I want by setting my rules to 50 or 200.
system categories are default, rules have a higher priory them - except when you actually assign a system category to an item.
go into debug mode and check the item, if it has the system category assigned to it (and not just as a default) then click on the system category to reset it back to the default