From c70f340eb84a8271832f2c6626d93c5f3d052bc3 Mon Sep 17 00:00:00 2001 From: Durel Date: Tue, 26 Sep 2017 21:35:28 -0400 Subject: [PATCH] Initial checkin of plugin at github This is considered version 0.1.3 --- aard_inventory.xml | 18928 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 18928 insertions(+) create mode 100644 aard_inventory.xml diff --git a/aard_inventory.xml b/aard_inventory.xml new file mode 100644 index 0000000..b1fe01f --- /dev/null +++ b/aard_inventory.xml @@ -0,0 +1,18928 @@ + + + + + + + + + + + + +". + + +Usage +===== + + Inventory table access + dinv build [confirm] + dinv refresh [on | off | all] + dinv search [id | full] + + Item management + dinv get + dinv put + dinv store + dinv keyword [add | remove] + dinv organize [add | clear | display] + + Equipment sets + dinv set [display | wear] + dinv snapshot [create | delete | list | display | wear] + dinv priority [list | display | compare] + + Equipment analysis + dinv analyze [list | create | delete | display] + dinv usage + dinv compare + dinv covet + + Advanced options + dinv backup [list | create | delete | restore] + dinv reset [list | confirm] + dinv forget + dinv notify [none | light | standard | all] + dinv cache [reset | size] [recent | frequent | all] <# entries> + dinv tags [on | off] + + Using equipment items + dinv consume [add | remove | display | buy | small | big] + dinv portal [use] + dinv pass <# of seconds> + + Plugin info + dinv version + dinv help + + +Release Notes +============= + +1) There currently is no mechanism to change stat prioritization other than manually modifying the + plugin. This is high on the list of new features and a GUI supporting this will hopefully be + coming in the future. + +2) If you give an item to an enchanter to boost the item's stats, you may pull the old stats from a + cache instead of using the new enchantments when you get the item back. In this case, you may use + the "dinv forget " option to remove that item from your inventory table and its related caches. + The next inventory refresh will pick up the new stats for the item. + +3) Most aard operations that modify an item's stats are detected and automatically trigger a + re-identification. For example, enchantment spells, sharpening, reinforcing, tpenchanting, and wset + all are handled transparently. The one known exception is the setweight command which is not + currently handled by aard's invitem system. Until this is changed (or until we include a trigger + watching for setweight) you will need to use the "dinv forget " option on an item that changes + weight in order to "forget" the old stats and then pick up the correct weight (and other stats) on + the next inventory refresh. + +4) Wands and staves are not re-identified as they are used. As a result, the number of charges + shown in the item's display may not match reality as the item is used. If this mode is not added + to the aard invitem system, we may need to add a trigger to watch for this and update charges + accordingly. + +5) The plugin does not automatically open containers that are closed. As a result, you won't be able + to get/put items in a closed container. Keep your containers open! :) + +6) If you add a keyword to an item, drop it, and then pick it back up, the new keyword will still + be available on the item if it is still in your cache. However, this is not the case for common + consumable items. For example, we treat all duff beer potions as being identical so that you don't + need to individually identify each potion. As a result, the cached versions of those common items + won't maintain custom keywords. + +7) If the plugin tags are enabled, they will echo an end tag at the conclusion of an operation. However, + if the user goes into a state that doesn't allow echoing (e.g., AFK) then the plugin cannot report the + end tag. In this scenario, the plugin will notify the user about the end tag via a warning notification + instead of an echo. Triggers cannot catch notifications though so any code relying on end tags should + either detect when you go AFK or cleanly time out after a reasonable amount of time. + + +Feature Wishlist +================ + +1) Add a way to create and update stat prioritizations. A GUI would be a very convenient way + to handle this. + +2) Implement a mechanism to (more) fully identify items if the identify wish is not available. + For example, we could use lore, the identify or object read spells, or Hester's identify + service found at "runto identify". This would be a manual process to "clean up" partially + identified items. + +3) Add a display option to de-duplicate potions and pills in search results + + +]]> + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +