Quantcast
Download
(43 Kb)
Download
Updated: 01/19/21 11:30 AM
Pictures
File Info
Compatibility:
Markarth (6.2.5)
Stonethorn (6.1.5)
Greymoor (6.0.5)
Updated:01/19/21 11:30 AM
Created:08/14/16 10:23 AM
Monthly downloads:48,542
Total downloads:288,828
Favorites:197
MD5:
Categories:Bags, Bank, Inventory, Group, Guild & Friends
6.2.5
Loot Log  Updated this week!  Popular! (More than 5000 hits)
Version: 3.6.6
by: code65536 [More]
Loot Log helps players track their loot drops and those of group members.




Dependencies

Required:
  • None

Recommended/Optional:

What's New: Making Gear Trading Easier

New in Loot Log 3 are a few features to help players trade set items and other collectibles more efficiently.

Flagging uncollected items that other players have linked in chat

First, Loot Log will now flag uncollected items that other players have linked in chat. This includes set items, style pages, and runeboxes.
  • The goal is to facilitate trade with other players, not clutter a player's chatbox with bling.
    • Only incoming messages from other players are processed. Outgoing messages and system messages (from addons) are ignored.
    • Items that are bound and not tradeable will not be flagged.
    • If the player already has an "unused" copy of an item in their inventory or bank, that item will not be flagged.
  • If a message contains uncollected items, Loot Log will append a "Request" link to the message. Clicking this link will initiate a whisper with the message sender, requesting the uncollected items in that message.
    • NOTE: This Request feature works only for items that other players have linked in chat. I.e., items that other players are actively offering for trade. I am mindful of how some people feel about addons that monitor loot and the unsolicited requests for gear that such addons enable, which is why the Request feature is not—and will never be—added to loot notifications; this is a deliberate decision to draw a line at how much I'm willing to facilitate behaviors that some people feel uncomfortable with.

/linktrade: The easy way to offer unneeded set items for trade

Next is the new /linktrade (or /lt) chat command, to link your tradeable set items in chat.
  • /linktrade is designed to offer up for trade only the items that you don't need, so if you have an uncollected item in your inventory, it won't be linked.
  • If you have multiple copies of an item, /linktrade will consolidate them.
    • For example, it will output "[Arkasis's Sabatons]x3" instead of linking it three separate times if you have three unbound copies of those sabatons.
    • This consolidation ignores trait, quality, level, and even name (for uniquely-named items), since it assumes that these details are irrelevant to players seeking items for their set collection.
    • If you have multiple copies of an item that you have not yet collected, it will reserve one copy for yourself. So, in the example above, if you have not yet collected those sabatons, /linktrade will output "[Arkasis's Sabatons]x2", offering for trade two of the three copies that you have and reserving one copy for your own collection.
  • Items that have been linked will not be linked again for 1 hour. This is to prevent unnecessary chat clutter caused by relinking items that you had already linked earlier. If you do want to relink items, you can use the /linktrade reset (or /lt reset) chat command to clear away the cooldown on relinking. (Relogging or reloading the UI will also clear the cooldown.)
  • Because the chatbox is limited in size, it's not uncommon for the number of items that you can offer up for trade to exceed the size of the chatbox. In this case, /linktrade will link as many items as possible into your chatbox and let you know that there are still items remaining. Simply run the command again to link the remaining items.
  • By default, /linktrade will only link tradeable bind-on-pickup items, such as those found in dungeons and trials. Users who want to use /linktrade to link bind-on-equip items can do so via the Loot Log addon settings panel.
With /linktrade, there is no more need to manually dig through your bag, linking items one by one.

/binduncollected: Bind uncollected items in a character's inventory

The new /binduncollected (or /bunc) chat command will bind every uncollected set item in your character's inventory.
  • If you have multiple copies of an item, only one copy (the first copy that it happens to find) will be bound.

Flagging uncollected items in item lists

Finally, Loot Log can flag uncollected collectible items in various in-game item lists, which include player inventory, banks, vendor inventory, and loot windows.
  • For inbound contexts, Loot Log will use a "smart" determination of collection status, where an uncollected item will not be flagged as uncollected if the player already has an "unused" copy of that item in their inventory or bank.
    • The reasoning for this is that in these contexts, similar to the flagging of uncollected items linked in incoming chat, the uncollected indicator is supposed to help a player determine if they should acquire an item that they do not already have.
    • These are the inbound contexts in which this "smart" flagging is active:
      • Loot windows
      • Guild store listings
      • NPC vendor inventories
      • Inbound trade slots from the other player in the trade window (outbound trade slots from the player are not affected)


Support for Item Set Collections

New in Loot Log 2.4 are a number of features to support the new Item Set Collections. First, set items that are not yet collected by your account will be flagged in the Loot History browser with an indicator near the item's icon.

Second, there is a new filtering option in the Loot History browser to only show uncollected items.

Finally, uncollected set items can now be optionally flagged in chat notifications.



Searchable Loot History

New in Loot Log 2 is a searchable, sortable Loot History.



How do I access the Loot History?

There are three different ways to access the Loot History browser:
  • Option 1: Type /lootlog (or /ll) into chat.
  • Option 2: Bind a shortcut key, via the game's "Keybindings" setting panel under "Controls". There, you will find, under the "User Interface" category, a keybind option for Loot Log. Bind it to a key, and you can then use that key to open and dismiss Loot Log's user interface.
  • Option 3: When you see a loot notification in chat, you can click on the "[Loot Log]" tag at the beginning of the message to open Loot Log's user interface.



How far back does the Loot History go?

By default, Loot Log will keep a minimum of 2 hours of loot history. The length of this retention period can be changed through the addon settings for Loot Log.

(Note: Depending on when Loot Log goes through to expire old entries, old entries may remain visible in the history for up to an hour after they become eligible for expiration.)

Searching and filtering the Loot History

To help players find what they need, the Loot History browser includes a text search filter as well as drop-down general view filter.


Multi-Account Support

Note: This features requires LibMultiAccountSets

Users with multiple accounts and LibMultiAccountSets installed can optionally enable Loot Log's Multi-Account Support.

At the center of multi-account support is the notion of account priorities. If your alt account gets a piece of gear, you generally want to make sure that your main account has collected that piece of gear before collecting it on your alt. Account priorities allow the player to designate which account is important and which accounts are not. The first thing a user must do after enabling multi-account support is configure the priorities for their account.

Enabling multi-account support will affect the following components of Loot Log:
  1. Loot History browser and loot notifications in chat:
    • The collection status of bind-on-equip set items will now be flagged according to account priorities.
    • The collection status of bind-on-pickup set items will continue to be flagged as before.
      • Developer note: The main reason BoP items are not given the multi-account treatment in the Loot History browser and chat notifications is because it is impossible to reliably determine trade eligibility of BoP items from the game's loot events. The second reason is that accounts that can be eligible for a BoP item will be there with you in the run, and they can monitor the incoming loot stream themselves. There isn't a get-an-item-for-someone-who-wasn't-there use case for BoP like there is for BoE.
    • The collection status of other collectibles (e.g., style pages) will continue to be flagged as before.
      • Developer note: Cross-account collection information only covers item set knowledge and not general collectibles knowledge.
  2. Flagging/requesting items linked by others in chat:
    • Bind-on-equip set items will now be flagged if the current account (if its priority is not set to Off), or an account with the same or higher priority, has not collected it.
      • Developer note: Usually, players use alt accounts collect gear for the main account, and flagging all the gear that an alt account doesn't know, while on the main account, proved to be too "noisy" in play testing.
    • Bind-on-pickup set items will continue to be flagged as before.
      • Developer note: In a dungeon or trial, any account eligible for trade is likely to belong to a friend who has shared their data; it makes no sense for a player to watch for and request an item on a friend's behalf when their friend is in that instance with and capable of doing it for themselves.
  3. /binduncollected chat command:
    • If an item that is uncollected by the current account is also uncollected by an account with a higher priority than the current account, /binduncollected will reserve a copy for that higher-priority account and not bind the item.
      • Developer note: This should avoid the problem of alt accounts binding items that are needed by the main account.
  4. Flagging items in item lists (inventory, loot windows, etc.)
    • All set items in inventory, banks, and deconstruction will be flagged according to account priorities; this includes both bind-on-equip and bind-on-pickup items.
      • Bind-on-pickup items that are uncollected by another account will be flagged only if the item is eligible for trade with that account.
    • Bind-on-equip set items in store inventories will be flagged according to account priorities.
    • Bind-on-pickup set items in store inventories will continue to be flagged as before.
    • If a bind-on-pickup set item is uncollected by the current account and is not flagged for any account with priority (i.e., if the current account's priority is set to Off), then the item will continue to be flagged as before.
      • Developer note: Since bind-on-pickup items have limited tradeability, you might as well collect an unwanted item on an alt account that would otherwise not collect items.

Finally, users who have multiple accounts are highly encouraged to also install Item Set Browser, which will add information about which accounts have collected a particular item to an item's tooltip. Item Set Browser and Loot Log are designed to complement each other.


Loot Notifications in Chat



Additionally, players have the option to see loot notifications in their chatbox. Through the addon settings for Loot Log, players can configure which type of loot should appear in their chatbox, if any at all (this feature can be disabled, for players who prefer their chat to be free of the clutter of loot notification messages).

Disabling loot notifications in chat will not affect the Loot History. For example, if you turn off chatbox loot notifications for items that group members loot, you can still see this information when you consult the Loot History browser.

Clicking on the "[Loot Log]" tag that appears at the start of every chatbox loot notification will open the Loot History.
  • Version 3.6.6 (2021/01/19)
    • Improved handling of the collection state of collectible fragments
    • Updated Russian localization by @mychaelo

  • Version 3.6.5 (2021/01/15)
    • The /linktrade chat command will now automatically link any remaining items after the current message is sent, if the number of tradeable items to link exceed the message limit, thus eliminating the need to manually reinvoke the command

  • Versions 3.6.3 to 3.6.4 (2021/01/14)
    • Added visual previews of the uncollected indicators to the Loot Log addon settings panel
    • The "Show only uncollected items" filter in the Loot History browser will no longer show items that are flagged for accounts with lower priority than the current account when the optional multi-account mode is enabled

  • Version 3.6.2 (2021/01/13)
    • The behavior of the optional multi-account mode has been changed so that priority-based icons and colors will be used only for items that are not intended for collection by the current account (i.e., items that are uncollected by another higher-priority account or items that are already collected by the current account); this should result in a more coherent flagging ruleset when the optional multi-account mode is enabled

  • Version 3.6.1 (2021/01/11)
    • Players can now optionally supply the /linktrade chat command with the "wep" (or "w") parameter to link only BoP weapons, to reduce the amount of "noise" if everyone in a trial or group dungeon has already collected all of the easier-to-acquire body and jewelry pieces

  • Version 3.6.0 (2021/01/09)
    • Updated iconography for the uncollected indicators
    • Uncollected items attached to mails will now be flagged if "Flag uncollected items in item lists" is enabled

  • Version 3.5.4 (2021/01/06)
    • Updated French localization by @jakez31

  • Versions 3.5.2 to 3.5.3 (2021/01/04)
    • Players can now optionally supply the /binduncollected chat command with the "junk" (or "j") parameter to mark any items that are bound by the command as junk, so that the items can be easily identified for later disposal
      • Examples: /binduncollected junk or /bunc j
    • If the optional multi-account support is enabled and the current account's priority is set to "Off", then the /binduncollected chat command will no longer bind any BoE items, as an additional safeguard against mule accounts binding the gear that they are storing

  • Version 3.5.1 (2021/01/01)
    • Fixed a settings-related Lua error introduced in version 3.5.0

  • Version 3.5.0 (2021/01/01)
    • For players with multiple accounts, Loot Log can now flag uncollected set items based on the set collections of other accounts; this feature is disabled by default and can be enabled via the Loot Log addon settings panel
      • Note: This option will be visible only if LibMultiAccountSets 1.7 or newer is installed and there is item set collection data for at least two different accounts
    • Players can now optionally supply the /linktrade chat command with the "boe" (or "e"), "bop" (or "p"), or "all" (or "a") parameters to link only BoE, only BoP, or all items, allowing users to temporarily bypass the current /linktrade settings
      • Examples: /linktrade boe or /lt a

  • Version 3.4.0 (2020/12/28)
    • New feature: Flag uncollected items in item lists: Loot Log will now flag uncollected collectible items (i.e., set items, style pages, and runeboxes) in various in-game item lists (which include player inventory, banks, vendor inventory, and loot windows); this feature can be configured (or disabled) via the Loot Log addon settings panel

  • Version 3.3.0 (2020/12/23)
    • Removed the quantity column from the Loot History browser; entries that have a quantity greater than one will have the quantity displayed in front of the item

  • Versions 3.2.1 to 3.2.2 (2020/12/21)
    • After using the /binduncollected chat command to bind uncollected set items, players are presented with the option to view a report listing the items that were bound
    • When scanning incoming chat messages to flag uncollected items linked by other players, Loot Log will no longer flag an uncollected item if an "unused" copy of that item is currently in the player's inventory or bank
    • Improved the clarity of some of the wording in the Loot Log addon settings panel

  • Version 3.2.0 (2020/12/20)
    • New feature: /binduncollected chat command: Players can use the /binduncollected (or /bunc) chat command to bind the first copy of every uncollected set item in their character's inventory
    • The /linktrade reset command is now more discoverable

  • Version 3.1.0 (2020/12/17)
    • If "Flag uncollected items linked by others" is enabled, Loot Log will now append a link to the end of messages containing uncollected items that, when clicked, will initiate a whisper with the message sender, requesting the uncollected items in that message; this feature can be configured (or disabled) via the Loot Log addon settings panel
    • /linktrade will now switch chat to the group channel if the player is currently grouped inside a dungeon, trial, or arena
    • Reduced the /linktrade relinking cooldown from 75 to 60 minutes
    • Fixed a potential Lua error with the processing of incoming chat messages

  • Version 3.0.0 (2020/12/16)
    • New feature: Flag uncollected items linked by others: Loot Log will now flag unbound uncollected collectible items (i.e., set items, style pages, and runeboxes) that other players have linked in chat; this feature can be configured (or disabled) via the Loot Log addon settings panel
    • New feature: /linktrade chat command: Players can use the /linktrade (or /lt) chat command to link in chat their tradeable set items (items needed for the player's own collection will be excluded), with intelligent handling of duplicate items; by default, this feature will only link BoP-tradeable items, but it can be configured to include BoE items via the Loot Log addon settings panel

  • Version 2.5.2 (2020/12/04)
    • Updated Russian localization by @mychaelo

  • Version 2.5.1 (2020/12/03)
    • Uncollected style pages and runeboxes will now be flagged in chat, using the same setting that controls the flagging of uncollected set items in chat
    • Fixed an issue where the collection states of style pages and runeboxes were not being correctly updated in the Loot History browser

  • Version 2.5.0 (2020/12/03)
    • The uncollected indicators that appear in the Loot History browser and in chat notifications will now use different colors, depending on whether the item was looted personally or by another group member
    • The colors of the uncollected indicators can now be configured in the Loot Log addon settings panel

  • Version 2.4.5 (2020/11/25)
    • Compatibility with Item Set Browser 3

  • Version 2.4.4 (2020/11/17)
  • Version 2.4.3 (2020/11/06)
    • Added French localization by @jakez31

  • Version 2.4.2 (2020/11/05)
    • Improved integration with Item Set Browser by preventing other addons from also modifying tooltips that are being modified by Item Set Browser (other tooltips are unaffected)

  • Version 2.4.1 (2020/11/04)
    • For players who have Item Set Browser 2.2.1 installed and enabled, item set collection information will now be added to the Loot History browser's item tooltips

  • Version 2.4.0 (2020/11/04)
    • The Loot History browser will now visually flag collectible items (i.e., set items, style pages, and runeboxes) that your account has not yet collected
    • Added an option (enabled by default) to visually flag uncollected set items in chat notifications; additionally, when enabled, this option will cause uncollected set items looted by others to appear in chat even if the chat notification mode is set to personal
    • The personal filter modes in the Loot History browser will no longer show items looted by other accounts played from the same game installation

  • Version 2.3.4 (2020/09/14)
    • Added the /ll chat command as a shorthand alternative to /lootlog
    • Removed the filtering of collectibles looted by others, now that Stonethorn has fixed the issue of already-acquired collectibles generating loot events

  • Version 2.3.3 (2020/08/26)
    • Added German localization by @ninibini
    • Added Russian localization by @mychaelo

  • Version 2.3.2 (2020/05/09)
    • Reordered the columns of the Material Summary display
    • Reorganized the Loot Log addon settings panel

  • Version 2.3.1 (2020/05/08)
    • The option to display the current stock of crafting materials in chat notifications will now report the sum of materials in the bag, bank, and craft bag instead of only reporting the quantity in the craft bag

  • Version 2.3.0 (2020/05/08)
    • Added an option (disabled by default) to display icons in chat notifications
    • Added an option (disabled by default) to display the craft bag stock of crafting materials in chat notifications
    • The Material Summary display will now also display the combined total amount of crafting materials that a player currently has in their bag, bank, and craft bag

  • Version 2.2.1 (2020/05/07)
    • Undaunted Plunder will no longer be classified as notable loot
    • Reordered the options for the Loot History browser filter and chat notifications

  • Version 2.2.0 (2020/05/06)
    • Added item icons to the Loot History browser and Material Summary display
    • Added an "All Logged" option for the Loot History browser filter and for chat notifications; this will show all personal loot and notable group loot

  • Versions 2.1.2 to 2.1.3 (2020/05/05)
    • Optimized performance

  • Version 2.1.1 (2020/05/04)
    • The Loot History browser's search filter will now also match set names, in order to better accommodate items whose display names differ substantially from their set names (e.g., Bonehand's Amulet from the Ebon Armory set)

  • Version 2.1.0 (2020/05/02)
    • Added support for antiquity leads; since there are no in-game tooltips for the antiquity leads themselves, the Loot History browser will instead show tooltips for the rewards that the leads will ultimately grant

  • Versions 2.0.1 to 2.0.5 (2020/04/27)
    • Invoking the Loot Log window via a clicked link will now also switch the mode to Loot History
    • Added an indicator to the Loot Log window showing the history retention period; clicking on this indicator will open the addon settings panel
    • Chat notifications will no longer report the recipient, if the player has configured chat notifications to show only personal loot
    • Removed some alchemical reagents from the notability whitelist
    • Added a button to the addon settings panel to manually clear all history data
    • Item tooltips shown in the Loot History browser are now compatible with addons such as Craft Store that add additional information to item tooltips

  • Version 2.0.0 (2020/04/26)
    • Complete re-write of Loot Log, adding a new searchable Loot History

  • Version 1.1.12 (2020/02/05)
    • API version bump for Update 25 (Harrowstorm)

  • Version 1.1.11 (2019/10/23)
    • API version bump for Update 24 (Dragonhold)

  • Version 1.1.10 (2019/08/20)
    • API version bump for Update 23 (Scalebreaker)

  • Version 1.1.9 (2019/05/20)
    • API version bump for Update 22 (Elsweyr)

  • Version 1.1.8 (2019/02/25)
    • API version bump for Update 21 (Wrathstone)

  • Version 1.1.7 (2018/10/22)
    • API version bump for Update 20 (Murkmire)

  • Version 1.1.6 (2018/08/12)
    • API version bump for Update 19 (Wolfhunter)

  • Version 1.1.5 (2018/05/28)
    • API version bump for Update 18 (Summerset)

  • Version 1.1.4 (2018/02/12)
    • API version bump for Update 17 (Dragon Bones)

  • Version 1.1.3 (2017/10/23)
    • API version bump for Update 16 (Clockwork City)

  • Version 1.1.2 (2017/08/14)
    • API version bump for Update 15 (Horns of the Reach)

  • Version 1.1.1 (2017/05/22)
    • The names of other players will now be shown either as character names or as user IDs, based on the current preferred display name setting in the game; this can be optionally overridden via a slash command
    • Added new options, accessed via slash commands, to suppress the logging of your own loot and/or your group members' loot
    • The old verbosity toggle, along with the newly-added options, will now persist as installation-wide saved settings
    • Adjusted to the criteria for item notability:
      • Laurels are no longer considered notable items by the default filter and will no longer be logged
    • API version bump for Update 14 (Morrowind)

  • Version 1.0.4 (2016/09/02)
    • Adjusted to the criteria for item notability:
      • Collectibles (e.g., the Stonefire Scamp), Nirncrux trait stones, Hakeijo runes, monster trophies, and blue-quality fish are now considered notable items by the default filter and will be logged
      • Key fragments are no longer considered notable items by the default filter and will no longer be logged
    • API version bump for Update 12 (One Tamriel)

  • Version 1.0.3 (2016/08/19)
    • Added German translation (thank you, Scootworks)

  • Version 1.0.2 (2016/08/17)
    • Log entries are now classified as system messages so that they can appear across multiple chat tabs

  • Version 1.0.1 (2016/08/15)
    • Added support for future localization/translations

  • Version 1.0.0 (2016/08/14)
    • Initial version
Optional Files (2)
File Name
Version
Size
Author
Date
Type
1.1.13
4kB
03/04/20 05:47 AM
Patch
1.0
5kB
10/20/16 12:27 PM
Patch


Archived Files (56)
File Name
Version
Size
Uploader
Date
3.6.5
42kB
code65536
01/15/21 07:02 AM
3.6.4
41kB
code65536
01/14/21 11:19 AM
3.6.3
41kB
code65536
01/14/21 06:50 AM
3.6.2
41kB
code65536
01/13/21 01:14 PM
3.6.1
41kB
code65536
01/11/21 10:40 AM
3.6.0
41kB
code65536
01/09/21 03:59 AM
3.5.4
32kB
code65536
01/06/21 07:13 AM
3.5.3
31kB
code65536
01/04/21 01:57 PM
3.5.2
31kB
code65536
01/04/21 01:07 AM
3.5.1
31kB
code65536
01/01/21 01:08 PM
3.5.0
30kB
code65536
01/01/21 12:08 PM
3.4.0
27kB
code65536
12/28/20 04:12 AM
3.3.0
25kB
code65536
12/23/20 01:04 AM
3.2.2
25kB
code65536
12/21/20 08:34 PM
3.2.1.1
25kB
code65536
12/21/20 12:18 PM
3.2.0
24kB
code65536
12/20/20 04:27 AM
3.1.0
24kB
code65536
12/17/20 07:38 AM
3.0.0
23kB
code65536
12/16/20 11:01 AM
2.5.2
20kB
code65536
12/04/20 09:26 AM
2.5.1
20kB
code65536
12/03/20 12:09 PM
2.5.0
20kB
code65536
12/03/20 02:17 AM
2.4.5
19kB
code65536
11/25/20 09:12 AM
2.4.4
19kB
code65536
11/17/20 08:35 AM
2.4.3
19kB
code65536
11/06/20 08:18 AM
2.4.2
18kB
code65536
11/05/20 06:32 AM
2.4.1
18kB
code65536
11/04/20 12:25 PM
2.4.0
18kB
code65536
11/04/20 04:44 AM
2.3.4
16kB
code65536
09/14/20 08:00 PM
2.3.3
16kB
code65536
08/26/20 04:22 AM
2.3.2
14kB
code65536
05/09/20 05:05 PM
2.3.1
14kB
code65536
05/08/20 01:03 PM
2.3.0
14kB
code65536
05/08/20 09:46 AM
2.2.1
14kB
code65536
05/07/20 07:51 AM
2.2.0
13kB
code65536
05/06/20 08:15 PM
2.1.3
13kB
code65536
05/05/20 07:45 PM
2.1.1
13kB
code65536
05/04/20 09:52 AM
2.1.0
13kB
code65536
05/02/20 09:05 AM
2.0.5.1
12kB
code65536
04/27/20 04:42 PM
2.0.0
12kB
code65536
04/26/20 02:31 PM
1.1.12
5kB
code65536
02/05/20 10:19 AM
1.1.11
5kB
code65536
10/23/19 02:14 AM
1.1.10
5kB
code65536
08/20/19 07:52 AM
1.1.9
5kB
code65536
05/20/19 02:41 AM
1.1.8
5kB
code65536
02/25/19 09:47 AM
1.1.7
5kB
code65536
10/22/18 07:14 AM
1.1.6
5kB
code65536
08/12/18 06:12 AM
1.1.5
5kB
code65536
05/28/18 08:19 PM
1.1.4
5kB
code65536
02/12/18 07:35 AM
1.1.3
5kB
code65536
10/23/17 07:46 AM
1.1.2
5kB
code65536
08/14/17 09:52 AM
1.1.1
5kB
code65536
05/22/17 06:16 AM
1.0.4
3kB
code65536
09/02/16 09:41 AM
1.0.3
3kB
code65536
08/19/16 06:22 AM
1.0.2
2kB
code65536
08/17/16 02:40 PM
1.0.1
2kB
code65536
08/15/16 11:08 AM
1.0.0
2kB
code65536
08/14/16 11:43 AM


Post A Reply Comment Options
Unread 01/17/21, 08:47 AM  
Indodraakje

Forum posts: 0
File comments: 4
Uploads: 0
Re: Re: Re: Re: Re: Re: bug?

Originally Posted by code65536
Originally Posted by Indodraakje
My Eso copy is like a month old and i use minion to install my add-ons.
It doesn't matter how old your ESO is or whether or not you use Minion. The problem with outdated libraries is that they're bundled with old addons and not separate. Minion doesn't check to see if an addon's package includes a conflicting copy of an old library and selectively deletes parts that it deems to be old--it just installs the entire package.

If you installed an addon that hadn't been updated in years (which is not that unusual, since there are a lot of addons from years ago that still work fine today), and that addon included its own copy of LAM2, then you'd have an old conflicting copy of LAM2 on your system.
Just like you said, i managed to fix it. Thanks a bunch for your great work and help!
Report comment to moderator  
Reply With Quote
Unread 01/17/21, 08:24 AM  
code65536
AddOn Author - Click to view AddOns

Forum posts: 17
File comments: 181
Uploads: 25
Re: Re: Re: Re: Re: bug?

Originally Posted by Indodraakje
My Eso copy is like a month old and i use minion to install my add-ons.
It doesn't matter how old your ESO is or whether or not you use Minion. The problem with outdated libraries is that they're bundled with old addons and not separate. Minion doesn't check to see if an addon's package includes a conflicting copy of an old library and selectively deletes parts that it deems to be old--it just installs the entire package.

If you installed an addon that hadn't been updated in years (which is not that unusual, since there are a lot of addons from years ago that still work fine today), and that addon included its own copy of LAM2, then you'd have an old conflicting copy of LAM2 on your system.
Last edited by code65536 : 01/17/21 at 08:29 AM.
Report comment to moderator  
Reply With Quote
Unread 01/17/21, 08:19 AM  
Indodraakje

Forum posts: 0
File comments: 4
Uploads: 0
Re: Re: Re: Re: bug?

Originally Posted by code65536
Originally Posted by Indodraakje
Changed notification to Notable loot. (default option was "4").
took an item (daily) and got the same thing.
I suspect that if you deleted your Loot Log saved variables file and then used Loot Log without first going into the settings, it would've worked fine.

You see, the default option is not "4"... the default option is "Notable Loot". If you're seeing the original default setting as "4" rather than "Notable Loot", then it means that you have a copy of LibAddonMenu-2.0 (LAM2) on your system that's very, very old--older than r23, which was released over 4 years ago back in October 2016.

This also explains how your saved variables became corrupted in the first place, because you have an incompatible version of LAM2 that's over 4 years old.

Years ago, libraries were bundled with addons and were not downloaded separately. So if you recently downloaded an old addon that had bundled an old version of LAM2, then you'd have multiple copies of LAM2 on your system, and that old copy of LAM2 could be causing this kind of interference. This is the reason why in recent years, libraries were decoupled from addons and downloaded separately, so that people aren't inadvertently installing old libraries.

So what you need to do to fix this:
  1. Delete your Loot Log saved variables again, because it's become corrupted again by the old LAM2.
  2. Use the search function in WIndows File Explorer and look for all the copies of LibAddonMenu in your AddOns directory and subdirectories, and delete any copy that's bundled within another addon.
Thanks for your answer. My Eso copy is like a month old and i use minion to install my add-ons. But i will report with the findings. I'm super greatful for your support!
Report comment to moderator  
Reply With Quote
Unread 01/17/21, 07:58 AM  
code65536
AddOn Author - Click to view AddOns

Forum posts: 17
File comments: 181
Uploads: 25
Re: Re: Re: bug?

Originally Posted by Indodraakje
Changed notification to Notable loot. (default option was "4").
took an item (daily) and got the same thing.
I suspect that if you deleted your Loot Log saved variables file and then used Loot Log without first going into the settings, it would've worked fine.

You see, the default option is not "4"... the default option is "Notable Loot". If you're seeing the original default setting as "4" rather than "Notable Loot", then it means that you have a copy of LibAddonMenu-2.0 (LAM2) on your system that's very, very old--older than r23, which was released over 4 years ago back in October 2016.

This also explains how your saved variables became corrupted in the first place, because you have an incompatible version of LAM2 that's over 4 years old.

Years ago, libraries were bundled with addons and were not downloaded separately. So if you had downloaded an old addon that had bundled an old version of LAM2, then you'd have multiple copies of LAM2 on your system, and that old copy of LAM2 could be causing this kind of interference. This is the reason why in recent years, libraries were decoupled from addons and downloaded separately, so that people aren't inadvertently installing old libraries.

So what you need to do to fix this:
  1. Delete your Loot Log saved variables again, because it had become corrupted again when you tried to change that settiing while the old LAM2 was active.
  2. Use the search function in WIndows File Explorer and look for all the copies of LibAddonMenu in your AddOns directory and subdirectories, and delete any copy that's bundled within another addon.
Last edited by code65536 : 01/17/21 at 08:19 AM.
Report comment to moderator  
Reply With Quote
Unread 01/17/21, 07:10 AM  
Indodraakje

Forum posts: 0
File comments: 4
Uploads: 0
Re: Re: bug?

Originally Posted by code65536
Originally Posted by Indodraakje
Hi, At first, thanks for the great great addon!

unfortunately since last update (i think?) the loot log broke.



the dependencies are up to date. I also tried reinstalling but no joy.

Any idea how this can be fixed?

Thanks a lot!
Based on the error that you posted, it looks like you have a corrupted saved variables file. Log off your current character, then go to "My Documents\Elder Scrolls Online\live\SavedVariables" and delete LootLog.lua. That should fix the problem.
I've done that. Unfortunately didn't work.

I removed lootlog.lua. started the game. Changed notification to Notable loot. (default option was "4").
took an item (daily) and got the same thing.

user:/AddOns/LootLog/LootLog.lua:438: operator < is not supported for number < string
stack traceback:
user:/AddOns/LootLog/LootLog.lua:438: in function 'LootLog.LogItem'
|caaaaaa<Locals> itemLink = "|H0:item:58503:175:32:0:0:0:0:...", quantity = 1, notable = F, receivedBy = "Indodraakje", timestamp = 1610888853, key = 447469, personal = T, userId = "@Indodraakje", hasSet = F, isUncollected = F, uncollectedColor = 13369344, uncollectedIcon = "LootLog/art/uncollected.dds", flags = 2 </Locals>|r
user:/AddOns/LootLog/LootLog.lua:182: in function 'LootLog.OnLootReceived'
|caaaaaa<Locals> eventCode = 131189, receivedBy = "Indodraakje^Mx", itemName = "|H0:item:58503:175:32:0:0:0:0:...", quantity = 1, soundCategory = 27, lootType = 1, self = T, isPickpocketLoot = F, questItemIcon = "", itemId = 58503, isStolen = F, notable = F </Locals>|r
Report comment to moderator  
Reply With Quote
Unread 01/16/21, 09:59 PM  
code65536
AddOn Author - Click to view AddOns

Forum posts: 17
File comments: 181
Uploads: 25
Originally Posted by superalien
Originally Posted by code65536
Originally Posted by superalien
somebody can tell me why I cant see my group loot? I only see my loots.
Make sure the filter mode is not set to a "Personal" mode.
I try in all modes before post, at the momment I have it in log all.
One more thing to keep in mind is that "All Logged" is all personal loot and all notable group loot (set items and "valuable" items); non-notable group loot is never logged or shown.
Report comment to moderator  
Reply With Quote
Unread 01/16/21, 07:22 PM  
superalien

Forum posts: 0
File comments: 2
Uploads: 0
Originally Posted by code65536
Originally Posted by superalien
somebody can tell me why I cant see my group loot? I only see my loots.
Make sure the filter mode is not set to a "Personal" mode.
I try in all modes before post, at the momment I have it in log all.
Last edited by superalien : 01/16/21 at 07:29 PM.
Report comment to moderator  
Reply With Quote
Unread 01/16/21, 07:17 PM  
code65536
AddOn Author - Click to view AddOns

Forum posts: 17
File comments: 181
Uploads: 25
Originally Posted by superalien
somebody can tell me why I cant see my group loot? I only see my loots.
Make sure the filter mode is not set to a "Personal" mode.
Report comment to moderator  
Reply With Quote
Unread 01/16/21, 07:10 PM  
superalien

Forum posts: 0
File comments: 2
Uploads: 0
somebody can tell me why I cant see my group loot? I only see my loots.
Report comment to moderator  
Reply With Quote
Unread 01/16/21, 12:10 PM  
code65536
AddOn Author - Click to view AddOns

Forum posts: 17
File comments: 181
Uploads: 25
Re: bug?

Originally Posted by Indodraakje
Hi, At first, thanks for the great great addon!

unfortunately since last update (i think?) the loot log broke.



the dependencies are up to date. I also tried reinstalling but no joy.

Any idea how this can be fixed?

Thanks a lot!
Based on the error that you posted, it looks like you have a corrupted saved variables file. Log off your current character, then go to "My Documents\Elder Scrolls Online\live\SavedVariables" and delete LootLog.lua. That should fix the problem.
Report comment to moderator  
Reply With Quote
Unread 01/16/21, 10:26 AM  
Indodraakje

Forum posts: 0
File comments: 4
Uploads: 0
Exclamation bug?

Hi, At first, thanks for the great great addon!

unfortunately since last update (i think?) the loot log broke.

user:/AddOns/LootLog/LootLog.lua:438: operator < is not supported for number < string
stack traceback:
user:/AddOns/LootLog/LootLog.lua:438: in function 'LootLog.LogItem'
|caaaaaa<Locals> itemLink = "|H0:item:165576:122:32:0:0:0:0...", quantity = 1, notable = T, receivedBy = "Indodraakje", timestamp = 1610814191, key = 447448, personal = T, userId = "@Indodraakje", hasSet = F, isUncollected = F, uncollectedColor = 13369344, uncollectedIcon = "LootLog/art/uncollected.dds", flags = 6 </Locals>|r
user:/AddOns/LootLog/LootLog.lua:182: in function 'LootLog.OnLootReceived'
|caaaaaa<Locals> eventCode = 131189, receivedBy = "Indodraakje^Mx", itemName = "|H0:item:165576:122:32:0:0:0:0...", quantity = 1, soundCategory = 27, lootType = 1, self = T, isPickpocketLoot = F, questItemIcon = "", itemId = 165576, isStolen = F, notable = T </Locals>|r
the dependencies are up to date. I also tried reinstalling but no joy.

Any idea how this can be fixed?

Thanks a lot!
Report comment to moderator  
Reply With Quote
Unread 01/11/21, 08:52 AM  
erdbeerheld

Forum posts: 0
File comments: 15
Uploads: 0
Feature request

What are your thoughts on adding an additional chat command /ltw that just posts weapons in the chat for trade? Esp. in Trials with lots of chests to loot and armor being completed by more and more people, it would just post the "interesting" things (and reduce potential "junk")

Thanks
Report comment to moderator  
Reply With Quote
Unread 01/01/21, 01:43 PM  
code65536
AddOn Author - Click to view AddOns

Forum posts: 17
File comments: 181
Uploads: 25
Originally Posted by GregariousJB
But, just curious... "without existing settings"? Been using Loot Log for a few weeks now. Did I erase my savedvariables somehow?
After looking at it some more, I see how this bug slipped through my testing (I had been using this new version of Loot Log for a number of days now, so seeing a Lua error was quite a surprise for me).

There are some new settings that were added in 3.5, and the problem is that I tried to change one of those settings before I initialized it. The new features added in 3.5 are aimed at players with multiple accounts, and if Loot Log detects that there isn't actually any data for multiple accounts, it will disable the new features. This is what Loot Log was doing when it crashed--it was turning off the new features. And this is also why I didn't catch it in my testing, because I play with multiple accounts and I always had data for multiple accounts (and that data is stored separately from Loot Log, which is why when I tested the new version with fresh settings, it didn't trigger this bug).
Report comment to moderator  
Reply With Quote
Unread 01/01/21, 01:31 PM  
GregariousJB

Forum posts: 0
File comments: 108
Uploads: 0


Thanks for the quick response, as usual.

But, just curious... "without existing settings"? Been using Loot Log for a few weeks now. Did I erase my savedvariables somehow?
Report comment to moderator  
Reply With Quote
Unread 01/01/21, 01:12 PM  
code65536
AddOn Author - Click to view AddOns

Forum posts: 17
File comments: 181
Uploads: 25
Originally Posted by GregariousJB
I believe the latest update to LibMultiAccountSets broke Loot Log:

Code:
user:/AddOns/LootLog/LootLogMultiAccounts.lua:176: attempt to index a nil value
stack traceback:
user:/AddOns/LootLog/LootLogMultiAccounts.lua:176: in function 'LootLogMulti.BuildSettings'
|caaaaaa<Locals> accounts = [table:1]{1 = "@GregariousJB"} </Locals>|r
user:/AddOns/LootLog/LootLog.lua:923: in function 'LootLog.RegisterSettingsPanel'
|caaaaaa<Locals> LAM = [table:2]{panelId = 101}, panelId = "LootLogSettings", chatModes = [table:3]{1 = 0}, chatModeLabels = [table:4]{1 = "None"}, chatIsDisabled = user:/AddOns/LootLog/LootLog.lua:757, uclr = [table:5]{itemLists = 13369446, lootedGroup = 16777215, lootedPersonal = 38143, linkedChat = 65280} </Locals>|r
user:/AddOns/LootLog/LootLog.lua:114: in function 'OnAddOnLoaded'
|caaaaaa<Locals> eventCode = 65536, addonName = "LootLog" </Locals>|r
Code:
user:/AddOns/LootLog/LootLogTrade.lua:215: attempt to index a nil value
stack traceback:
user:/AddOns/LootLog/LootLogTrade.lua:215: in function 'messageFormatter'
|caaaaaa<Locals> fromDisplayName = "@Akamakus" </Locals>|r
EsoUI/Ingame/ChatSystem/ChatHandlers.lua:247: in function 'ZO_ChatRouter:FormatAndAddChatMessage'
|caaaaaa<Locals> self = [table:1]{fireCallbackDepth = 0}, eventKey = 131104, eventCategory = 6, messageFormatter = user:/AddOns/LootLog/LootLogTrade.lua:213 </Locals>|r
EsoUI/Ingame/ChatSystem/ChatHandlers.lua:212: in function 'OnChatEvent'
|caaaaaa<Locals> eventCode = 131104 </Locals>|r
/ll no longer works and the Loot Log options window is completely blank.

EDIT: It also breaks my interface Character window, inventory, even the ESC key doesn't work until I disable Loot Log. Yikes
Thanks for the report. This is a problem caused by some settings that were not properly initialized in Loot Log and is not related to LibMultiAccountSets. I'm unsure how I failed to catch this in my testing, since an installation without existing settings was one of the scenarios that I tested. In any case, this one slipped through the cracks and I apologize for that. It should be fixed in 3.5.1, which is currently pending file approval.
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump:

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.