Download
(139 Kb)
Download
Updated: 03/30/24 03:21 PM
Pictures
File Info
Compatibility:
Scions of Ithelia (9.3.0)
Updated:03/30/24 03:21 PM
Created:10/25/20 04:32 PM
Monthly downloads:91,450
Total downloads:938,753
Favorites:313
MD5:
Categories:Libraries, Data Mods
9.3.0
LibHistoire - Guild History  Popular! (More than 5000 hits)
Version: 2.3.0
by: sirinsidiator [More]
New guild history
The original guild history API was written more than 10 years ago and never had any of the things addons (ab)use it for in mind.
A few years ago in 2020 the amount of requests generated by addons reached the point where it destabilized the game servers and as a result the API was even disabled completely for a while, until ZOS implemented limits on how many requests can be sent.
This was when I wrote the first version of LibHistoire to provide a cache for guild history data, which different addons could use to avoid sending unnecessary requests to the server and avoid even more restrictions for addons.

Starting with Update 41 in early 2024, the game finally received its own guild history cache. Due to that the library won't need to store event data any more and instead just offers features to inspect and manage the ingame cache as well as a compatibility layer to make transitioning old addons to the new API easier.
Any data that was collected by old versions of LibHistoire in the past will be deleted the first time you log in with version 2 enabled, in order to improve loading times.

Currently the game stores its cache files outside of the usual live folder and they can be found in the following location:
Windows:
Code:
%AppData%/../Local/Elder Scrolls Online/live/CachedData/GuildHistory
MacOS:
Code:
~/Documents/Elder Scrolls Online/live/CachedData/GuildHistory
You should always back them up together with your LibHistoire saved variable file to ensure proper operation.
The cache is stored per account, so data received for a guild on one account currently won't be shared with another who's in the same guild and will have to be requested again from the server.

The new API allows to receive up to 500 events (from previously 100) with each request, but at the same time the cooldown for addon requests has been increased to 2 minutes (from 30 seconds).
This means automated requests will be effectively 25% faster for busy categories, but may currently take a bit longer overall to finished for all categories.
Depending on how well the new history performs on the server, this cooldown is subject to change and we may see less waiting time between requests in the future.

So what is this library for now?
The main purpose of the library is currently to coordinate server requests and event processing between different addons via a common interface, to reduce waiting time and improve game performance.
It also provides a variety of functions and settings for users to see what is going on in the background and to interact with and control the cache behaviour.

Dependencies
The following dependencies are required by LibHistoire:
  • LibAsync - to minimize fps loss while processing history events
  • LibCustomMenu - for the options menu of the status window
  • LibDebugLogger - for logging useful debug information in case something goes wrong
  • LibAddonMenu-2.0 - Provides settings menus for addons

User Interface

The status icon on the bottom right of the guild history symbolizes the link status of the currently viewed category in the selected guild. On hover it will show a tooltip that gives information about the stored history and unlinked events.


The new guild history status panel will provide an overview of the cache status for each guild and category.

On the left side it will show each guild and the overall progress, on the right side it will show the individual categories for the currently selected guild.
Clicking on a guild or category will update the selection in both the status window and the guild history menu accordingly.

The category status bar shows all the time ranges which are stored in the cache, as well as queued requests and currently processed events. It also uses different colors to symbolize different states for each segment.

Guild status colors:
Pink - Waiting for server requests to finish
Red - No more requests queued, but not everything is linked
Yellow - Processing events
Green - Everything is linked up

Category status colors:
Blue - Linked range, but has not been connected with newest events yet
Red - Events after the linked range, but not connected to the linked range
Green - Linked range is up to date with newest events
Dark green - Last part of the linked range which does not contain any events
Grey - Events before the linked range, or events in a category with no listeners or which is forced off
Purple - Pending server request
Pink - Part of the request range which already contains events
Yellow - Already processed events
Dark Yellow - Events to be processed

Examples for all the colors:
Warning: Spoiler


When you hover over any of the entries, a tooltip will show you the same information as the tooltip in the guild history menu.
The category entries also offer a menu with some options.
On the bottom of the panel you can see an icon which symbolizes the overall state and gives some general information about what is happening when you hover over it.
The cog button on the top right will open a context menu with an option to unlock the window so it can be moved and an option to hide it (same as the button on the bottom left of the guild history)

Special Thanks
FooWasHere who helped me test how the history behaves on rank and permission changes
ZOSDanBatson and ZOSSethL for answering my many questions about the history API
Everyone else who helped me test this and gave me feedback

For Developers
Why should you use it?
  • It minimizes the cooldown for server requests sent by addons to the absolute minimum and if every addon starts using it, everyone gets their data faster.
  • It takes care of all the complexity that comes with requesting the history. There are many special cases you probably didn't even think about. The lib will handle them all for you.
  • It makes it easy to process a specifc time range, or continuously follow the history in chronological order.
  • It automatically spreads out event processing over multiple frames via LibAsync, so you don't have to worry about fps impact.

How does it work
The library keeps track of which events have already been sent to listeners and ensures that it doesn't skip anything in case newer events are received before it caught up.
When a listener starts, it will first iterate over available "linked" events, then wait for "unlinked" events to get linked before it iterates over those and finally start passing along newer events whenever they arrive. This is all done via LibAsync, so you will only get as many events per frame as you can safely process without affecting performance.
To ensure an addon only starts processing from where it left off, it offers ways to select a starting point either by specifying an eventId or a timestamp.

If you find a problem, feel free to open an issue over on github, or leave a comment here on ESOUI.

Migration Guide
Here is a short guide on how to migrate your addon to the new processor api.

The GUILD_HISTORY_* and GUILD_EVENT_* constants used by the old history api are not compatible with the new processor api and need to be replaced with the appropriate new constants.
You can use the mapping for the legacy listener api found in compatibility.lua as a starting point to figure out what to replace them with.

The new processor class is very similar to the legacy listener class, but has a few key differences:
  • You now have to specify an addon name which is shown in the status UI and debug information to help identify who is registered to a category.
  • SetBeforeEventTime has been changed to exclude the specified time. Keep that in mind when updating code that uses this function directly.
  • The iterationCompletedCallback has been removed in favor of a new onStopCallback which passes a StopReason to inform you why the processor has stopped.
  • SetStopOnLastEvent has been renamed to SetStopOnLastCachedEvent to better communicate what it does.
  • A new registeredForFutureEventsCallback was added to inform you when the processor has finished passing all cached events and is now waiting for new events to arrive.
  • A new receiveMissedEventsOutsideIterationRange flag was added to give you a way to listen to incoming events that are not included in the specified iteration range.
  • SetTimeFrame was removed in favor of StartIteratingTimeRange which simplifies configuration and directly starts the processor.
  • A new StartStreaming function was added to simplify the most common use case of processing cached events since the last time the addon was loaded and then waiting for new events to arrive.
  • The event callbacks now directly receive the new event objects specified in the ingame ui code. These are shared between all addons and can point to a different event after the callback has ended, so make sure you do not modify or store them and instead extract the information you need in the context of the callback.
Check the examples and the API reference section below for more details on how you can use the new processor api.

In case you have stored any eventIds received via the legacy listener api, you will also want to convert these the first time a user starts the new version of your addon.
You can use the new LibHistoire:ConvertArtificialLegacyId64ToEventId() function to attempt converting id64 eventIds to the new id53 values.
Keep in mind that the original id64s from the old history api cannot be mapped to the new id53s, so the function may return nil for values that are not produced by the legacy listener api.

The library now also offers a new OnReady function which simplifies ensuring that it has fully loaded before you start using it.

There are now also new callbacks for when the library has linked a category to present events, as well as when the managed range has been lost, or a new managed range has been established.
Check the MANAGED_RANGE_LOST, MANAGED_RANGE_FOUND and CATEGORY_LINKED callbacks in the API reference section below.

Examples
Iterating a specific time range
This example outlines how a processor can iterate over all currently cached events in a specific time range. It will automatically stop in case the time range is not fully cached, so make sure to handle early stops as needed.

This could for example be used together with LibDateTime's GetTraderWeek function to iterate over all donations in a specific trading week and do something with them.
Lua Code:
  1. LibHistoire:OnReady(function(lib)
  2.     local guildId = GetGuildId(1)
  3.     local category = GUILD_HISTORY_EVENT_CATEGORY_BANKED_CURRENCY
  4.     local addonName = "MyAddon"
  5.  
  6.     local processor = lib:CreateGuildHistoryProcessor(guildId, category, addonName)
  7.     if not processor then
  8.         -- the processor could not be created
  9.         return
  10.     end
  11.  
  12.     local started = processor:StartIteratingTimeRange(startTime, endTime, function(event)
  13.         local info = event:GetEventInfo()
  14.         assert(info.currencyType == CURT_MONEY, "Unsupported currency type")
  15.  
  16.         local eventType = info.eventType
  17.         if eventType == GUILD_HISTORY_BANKED_CURRENCY_EVENT_DEPOSITED then
  18.             local amount = info.amount
  19.             local displayName = DecorateDisplayName(info.displayName)
  20.             ProcessDeposit(guildId, displayName, amount)
  21.         end
  22.     end, function(reason)
  23.         if (reason == LibHistoire.StopReason.ITERATION_COMPLETED) then
  24.             -- all events in the time range have been processed
  25.         else
  26.             -- the iteration has stopped early for some reason and not all events have been processed
  27.         end
  28.     end)
  29.     if not started then
  30.         -- the processor could not be started
  31.     end
  32. end)

Listening to all events in a category
This example shows how to use the new processor api to start a processor for each guild and process guild store events starting from the last time the addon was loaded and without an explicit end.

The processor may still be stopped in case the user does something that requires to evaluate how to continue without data loss. You can either handle that case by registering the onStopCallback before calling StartStreaming, or just ignore it and let the addon resume the next time the user logs in.
Lua Code:
  1. LibHistoire:OnReady(function(lib)
  2.     local category = GUILD_HISTORY_EVENT_CATEGORY_TRADER
  3.     local addonName = "MyAddon"
  4.  
  5.     local function SetUpListener(guildId)
  6.         local processor = lib:CreateGuildHistoryProcessor(guildId, category, addonName)
  7.         if not processor then
  8.             -- the processor could not be created
  9.             return
  10.         end
  11.  
  12.         local key = processor:GetKey()
  13.         local started = processor:StartStreaming(saveData.lastEventId[key], function(event)
  14.             local info = event:GetEventInfo()
  15.             if info.eventType == GUILD_HISTORY_TRADER_EVENT_ITEM_SOLD then
  16.                 ProcessItemSold(info)
  17.             end
  18.             saveData.lastEventId[key] = info.eventId
  19.         end)
  20.         if not started then
  21.             -- the processor could not be started
  22.         end
  23.     end
  24.  
  25.     for i = 1, GetNumGuilds() do
  26.         SetUpListener(GetGuildId(i))
  27.     end
  28. end)

API Reference
You can also use the api.doc.lua file in the addon folder to get autocompletion with IDEs that support it.
Warning: Spoiler
v2.3.0
- added new LibAddonMenu settings panel with
- sliders to set how long the guild history cache should retain data
- a button to allow resetting all caches at once
- the path to the cache files
- fixed managed range reset not working correctly in some cases
- fixed assertion errors during processing not getting displayed
- now it will properly explode instead of silently getting stuck when invalid timestamps are received
v2.2.1
- fixed error when resetting managed range while a legacy listener is registered

v2.2.0
- re-enabled the selection of guilds and categories via the status window, now that the game has been fixed
- NOTE: switching guilds and categories via the status panel won't send requests automatically. You'll have to manually hit E or use the ingame ui to do so
- added new entry to status window menu to show debug information
- added new API callback "CATEGORY_LINKED" for when a category has been linked to present events
- added new API functions "IsReady" and "OnReady" for easier initialization
- added new guild history event processor API
- NOTE: it's still a bit experimental, so let me know if you encounter any issues and be prepared to update your code if necessary
- check the addon description for more information and a migration guide
- there is also an api.doc.lua file which can be used with language servers to provide autocompletion without having to include the full source code
- fixed legacy listener SetBeforeEventTime, SetTimeFrame and iterationComplete callback behaving slightly different from version 1
- fixed default position for status window

v2.1.1
- made status window more compact
- fixed link status icon being rendered behind the background
- fixed logout dialogue unintentionally showing up in some cases when it should not
- added workaround for error in ATT until it can be fixed properly

v2.1.0
- renamed "linked range" to "managed range" and "listener" to "processor"
- NOTE: legacy listeners will continue to be called just that
- changed exit warning dialogues to show up less frequently and be more clear about why you should care
- added exit warning dialogues to slash commands and gamepad mode logout
- added assertion to check incoming events for invalid timestamps
- NOTE: everything will explode for now when it happens. Please make sure to report it, so I can get an idea when and how often it occurs and decide what to do about it
- added shift modifier to pagination buttons in the vanilla history UI to allow jumping to the first or last page quickly

v2.0.7
- improved warning text for "reset linked range" and "clear cache" actions with some explanations
- fixed automated requests not getting discarded when they already got their range received via manual requests
- fixed errors after restoring a backup of the cache without restoring a backup of the library save data
- fixed incorrect zoom mode getting used when linked range is reset
- fixed status bar not properly showing progress when processing events older than the linked range

v2.0.6
- added version label to status window
- fixed a case where automated requests did not properly fill in gaps
- fixed automated requests getting discarded too early in some cases

v2.0.5
- fixed automated request getting queued for categories that are forced off
- fixed categories not getting linked properly in some cases
- fixed problems when switching between different accounts that share one or more guilds
- fixed incorrect status color for linked range that has not been connected to latest events yet
- fixed and improved information shown in status tooltip

v2.0.4
- fixed error while processing events

v2.0.3
- added request prioritization to prefer sending requests that matter the most first
- as long as the guild history menu is open, LibHistoire will now prefer requests for the currently visible guild
- other than that it will prioritize requests by how many listeners are registered for a category as well as a base priority (trading > bank gold > bank items > roster > others)
- further reduced amount of automated requests by not sending them to categories that won't produce any events (e.g. guild without bank or store)
- fixed various cases of automated requests getting stuck
- fixed an issue where requests used the wrong time range when the game has just been started
- fixed requested time ranges not showing correctly in the category status bars
- fixed how linked status is determined for categories
- fixed no new linked range getting selected on reset
- fixed linked range getting lost on login when the game has pruned data from the cache

v2.0.2
- fixed error when listener tries to iterate over a range without any events
- fixed "missing range" zoom mode not showing the intended range, making it appear as if there is no data stored at all
- fixed request time optimization producing incorrect time ranges
- reduced how often empty categories are requested to once a week

v2.0.1
- added option to delete all pending automated requests
- temporarily disabled the selection of guilds and categories via the status window
- fixed manual requests getting stuck with the addon cooldown of 2 minutes
- fixed automated requests blocking manual requests
- removed some unused code

v2.0
- rewrite for the new history api (check this post for more details)
- automatic removal of old history save data
- removed rescan and force link features
- compatibility layer for old history api
- new api callbacks
- smart history requests
- skip requests for categories with no listening addons
- fetch oldest events first after prolonged absense
- new category cache menu
- reset linked range button
- clear cache button
- request mode setting
- improved cache status bar
- cache segmentation display
- automated request visualization
- animated progress bar
- zoom level setting (in main menu)
- new colors
v1.5.1
- fixed issue that prevented other addons from receiving data

v1.5.0
- added warning about upcoming changes
- added code to disable current library version in update 41
- updated for Secret of the Telvanni

v1.4.1
- fixed progress bar not updating when linking starts

v1.4.0
- fixed history rescan not updating the status window
- added rescan progress metrics in tooltip
- improved rescan speed dramatically (~100 times faster)
- added warning on exit and UI reload when events are currently being processed
- updated for Necrom

v1.3.0
- fixed error due to unused event types being removed in the latest game update
- fixed HISTORY_RESCAN_ENDED callback not firing when no events are detected during a rescan
- added stopOnLastEvent flag which makes the library stop the iteration when the last stored event is reached, instead of waiting for new events to appear
- updated for Firesong

v1.2.2
- fixed error when serializing unexpected event types

v1.2.1
- fixed an error preventing events from getting stored for new users or when joining a new guild
- fixed progress bars flickering yellow on initial load
- fixed event listener getting stuck in a loop in some cases
- fixed game freezing when storing missing events during a rescan in categories with lots of stored events
- fixed typo in logout warning dialog

v1.2.0
- fixed an issue that would cause some players to get kicked from the PTS (public test server)
- fixed progress bar not immediately filling to 100% when the last batch of missing events are received in a category
- fixed a rare error that could occur when stored data is deserialized and added some assertions to find the underlying reason
- changed progress bars on status window to show in a red color while events are missing and yellow while events are being processed
- added a confirmation dialog when trying to logout or quit the game while history events are not yet linked, which will send players to the history menu
- updated api version

v1.1.3 (dedicated to Sharlikran who found all these problems)
- fixed codec storing item links in an uncompressed form
- fixed several codec bugs that caused item links to get decoded into invalid links
NOTE: No data was lost and I believe I've found and fixed all incorrect cases and added unit tests to guard against regressions. As an additional measure the lib will now also throw an assertion error if it encounters links that cannot be decoded. Please make sure to report these so I can add them to the test cases and fix them!

- fixed several more bugs in the new GetPendingEventMetrics function

v1.1.2
- fixed error when rescanning a category

v1.1.1
- fixed error in new GetPendingEventMetrics function

v1.1.0
- improved event decoding speed
- changed some logging to reduce log spam
- fixed afterEventTime not returning the correct event when multiple events have the same timestamp
- fixed status tooltip not updating when linking process begins
- added progress info to tooltip while linking
- added log warning when trying to start a listener without an event callback
- added new functions to EventListener API
- GetKey - returns an identifier which can be used to store the last seen eventId for a listener
- GetGuildId - returns the guildId of a listener
- GetCategory - returns the category of a listener
- GetPendingEventMetrics - returns
the amount of stored or unlinked events that are currently waiting to be processed by the listener
the average processing speed in events per second or -1 if not enough data is yet available
the estimated time in seconds it takes to process the remaining events or -1 if no estimate is possible
- SetBeforeEventId, SetBeforeEventTime
these can be used to limit the iteration range and automatically stop the listener when they are passed
they will also ensure the correct data is returned by the GetPendingEventMetrics function when only a subset of the data is requested (otherwise it will consider all available events)
- SetIterationCompletedCallback
when an end criteria is set, this callback will fire when the listener has stopped automatically
- SetTimeFrame(startTime, endTime)
a convenience method to specify a range which includes the startTime and excludes the endTime
v1.0.2
- added new callback for when Histy is ready

v1.0.1 - initial release
Optional Files (0)


Archived Files (26)
File Name
Version
Size
Uploader
Date
2.3.0
137kB
sirinsidiator
03/28/24 01:58 PM
2.2.0
137kB
sirinsidiator
03/27/24 01:58 PM
2.1.1
128kB
sirinsidiator
03/23/24 07:40 AM
2.1.0
128kB
sirinsidiator
03/21/24 05:53 PM
2.0.7
127kB
sirinsidiator
03/17/24 12:11 PM
2.0.6
127kB
sirinsidiator
03/16/24 10:48 AM
2.0.5
127kB
sirinsidiator
03/15/24 05:02 PM
2.0.4
126kB
sirinsidiator
03/15/24 06:05 AM
2.0.3
126kB
sirinsidiator
03/14/24 07:24 PM
2.0.2
126kB
sirinsidiator
03/13/24 07:20 PM
2.0.1
126kB
sirinsidiator
03/12/24 07:06 PM
2.0.0
124kB
sirinsidiator
03/11/24 04:49 AM
1.5.1
120kB
sirinsidiator
11/02/23 11:51 AM
1.5.0
120kB
sirinsidiator
11/01/23 03:20 PM
1.4.1
118kB
sirinsidiator
06/14/23 12:54 PM
1.4.0
118kB
sirinsidiator
04/19/23 12:44 PM
1.3.0
118kB
sirinsidiator
11/01/22 08:16 AM
1.2.2
118kB
sirinsidiator
04/25/21 06:41 AM
1.2.1
118kB
sirinsidiator
04/24/21 03:01 PM
1.2.0
118kB
sirinsidiator
04/22/21 01:22 PM
1.1.3
119kB
sirinsidiator
12/12/20 11:12 AM
1.1.2
118kB
sirinsidiator
12/05/20 02:33 PM
1.1.1
118kB
sirinsidiator
12/05/20 09:47 AM
1.1.0
118kB
sirinsidiator
12/04/20 07:01 AM
1.0.2
115kB
sirinsidiator
10/31/20 05:32 AM
1.0.1
115kB
sirinsidiator
10/25/20 04:32 PM


Post A Reply Comment Options
Unread 03/17/24, 01:58 PM  
sirinsidiator
 
sirinsidiator's Avatar
AddOn Author - Click to view AddOns

Forum posts: 1578
File comments: 1129
Uploads: 41
The library is working fine and the latest incremental seemingly fixed the game too.

If you still encounter issues where it won't link up a category, please let me know.

When reporting a problem, please always make sure you are using the latest version and include a screenshot of the whole status window, otherwise you'll get ignored like how you ignored this last sentence.
Last edited by sirinsidiator : 04/22/24 at 01:51 PM.
Report comment to moderator  
Reply With Quote
Unread Yesterday, 11:55 AM  
Sharlikran
 
Sharlikran's Avatar
AddOn Author - Click to view AddOns

Forum posts: 644
File comments: 2021
Uploads: 15
It appears that Guild History is stable irrespective of current outstanding issues. Players should be able to request data without guild categories breaking and requiring you to clear the cache.

For anyone that has been waiting, now is the time to request all 30 to 180 days of data. (depending on category and LibHistoire settings) Try not to clear the cache unless you actually need to do so.
Report comment to moderator  
Reply With Quote
Unread 04/21/24, 05:48 PM  
DewiMorgan
 
DewiMorgan's Avatar
AddOn Author - Click to view AddOns

Forum posts: 14
File comments: 83
Uploads: 1
Using 2.3.0 (latest according to Minion)

Code:
UI Error: FF4C8BBD
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:773: operator < is not supported for number < nil
stack traceback:
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:773: in function 'GuildHistoryCacheCategory:FindRangeIndexForEventId'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:438: in function 'GuildHistoryCacheCategory:StartProcessingEvents'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:563: in function 'GuildHistoryCacheCategory:RestartProcessingTask'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:331: in function 'GuildHistoryCacheCategory:OnCategoryUpdated'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCache.lua:38: in function 'callback'
/EsoUI/Libraries/Utility/ZO_CallbackObject.lua:132: in function 'ZO_CallbackObjectMixin:FireCallbacks'
/EsoUI/Ingame/GuildHistory/GuildHistory_Manager.lua:159: in function 'ZO_GuildHistory_Manager:OnCategoryUpdated'
/EsoUI/Ingame/GuildHistory/GuildHistory_Manager.lua:150: in function '(anonymous)'
/Reloadui gives the similar-but-different:

Code:
UI Error: FF4C8BBD
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:773: operator < is not supported for number < nil
stack traceback:
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:773: in function 'GuildHistoryCacheCategory:FindRangeIndexForEventId'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:438: in function 'GuildHistoryCacheCategory:StartProcessingEvents'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:563: in function 'GuildHistoryCacheCategory:RestartProcessingTask'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:331: in function 'GuildHistoryCacheCategory:OnCategoryUpdated'
user:/AddOns/LibHistoire/guildHistoryCache/GuildHistoryCacheCategory.lua:399: in function 'func'
/EsoUI/Libraries/Globals/globalapi.lua:263: in function '(anonymous)'
But a second /rl gives no error.
Report comment to moderator  
Reply With Quote
Unread 04/16/24, 04:32 PM  
Thrasher

Forum posts: 8
File comments: 208
Uploads: 0
The last couple days I have been having a problem with one guild trader not requesting guild sales while on automatic.

The status is "waiting for request to sent".

No other requests are active as far as I can tell.

The bar is all purple on the right, and the button to request more history manually with 'E' is not available.

Is there a workaround for this?

Please let me know.

UPDATE: The bar turned red. So am guessing it's the reported bug on ZOS's end stopping it now.

UPDATE 2: Well maybe not. The histories were able to be updated today by manually fetching. Very strange.
Last edited by Thrasher : 04/17/24 at 03:37 PM.
Report comment to moderator  
Reply With Quote
Unread 04/12/24, 09:28 AM  
jumi01

Forum posts: 2
File comments: 77
Uploads: 0
Originally Posted by sirinsidiator
Originally Posted by jumi01
I'm trying to create a backup of my cached data, as suggested. I have two accts in ESO, but I only see one Guild History folder in the CachedData file. Is the data for both accts in there, then? Same with LibHistoire saved variables. I was expecting to see two, since you said it was saved separately. TIA
Yes. The cache folder is the same for both accounts, but the files are different. The name scheme is (probably) "<serverId>_<accountId>_<guildId>.dat".
The lib on the other hand has to store all of its data in the same file, since that's how addon save data works.
Ah excellent. Yes I see that pattern. Thanks for the info!
Report comment to moderator  
Reply With Quote
Unread 04/12/24, 08:15 AM  
sirinsidiator
 
sirinsidiator's Avatar
AddOn Author - Click to view AddOns

Forum posts: 1578
File comments: 1129
Uploads: 41
Originally Posted by jumi01
I'm trying to create a backup of my cached data, as suggested. I have two accts in ESO, but I only see one Guild History folder in the CachedData file. Is the data for both accts in there, then? Same with LibHistoire saved variables. I was expecting to see two, since you said it was saved separately. TIA
Yes. The cache folder is the same for both accounts, but the files are different. The name scheme is (probably) "<serverId>_<accountId>_<guildId>.dat".
The lib on the other hand has to store all of its data in the same file, since that's how addon save data works.
Report comment to moderator  
Reply With Quote
Unread 04/12/24, 06:56 AM  
jumi01

Forum posts: 2
File comments: 77
Uploads: 0
Originally Posted by sirinsidiator
The library is working fine, however there is still one (hopefully) last bug left in the game that "bricks" your history when new events are pushed by the server.

In case there are no more events between the pushed data and the already cached data, the game currently won't be able to merge the two resulting segments in some cases. You can recognize it when the status bar has a blue (or green) and a red segment that nearly touch and the ingame UI won't show the "Show more" button on the last page.


A fix for this issue will be included in an upcoming incremental (likely the one on May 6th).

Until then the best course of action is to try to manually request history data right after login, before the server has any chance to push new events.
In case you get into the bricked state, you have currently three options.
  • Restore a backup
    My personal recommendation, as it ensures you keep all data in perfect condition and takes minimal effort. I simply check if everything has linked before I log out for the day and if it did, I create a new backup of the cache files (check the library description for where to find them) and the LibHistoire saved variable file. Otherwise I restore the previous working version of these files and just try again the next day.
  • Reset the managed range
    Since there are no missing events between the two segments, you can just do this without missing any data and I am told the segments should get merged automatically when the fix goes live. Not all addons may support this properly, it won't show the whole bar as green any more and you'll have to trust on ZOS' word that it will automatically merge the segments, so may not be to everyone's taste.
  • Clear the cache
    The objectively worst option out of the three. You will loose all data beyond the server range and may even feel compelled to waste your time manually requesting the full 30 day range again, just for it to break once more the next time you log in. Honestly, if you do this, don't complain to me. Use the other two options instead!

When reporting a problem, please make sure you are using the latest version and include a screenshot of the whole status window, otherwise you'll get ignored like how you ignored this last sentence.
I'm trying to create a backup of my cached data, as suggested. I have two accts in ESO, but I only see one Guild History folder in the CachedData file. Is the data for both accts in there, then? Same with LibHistoire saved variables. I was expecting to see two, since you said it was saved separately. TIA
Report comment to moderator  
Reply With Quote
Unread 04/12/24, 06:18 AM  
Octopuss
 
Octopuss's Avatar

Forum posts: 176
File comments: 817
Uploads: 0
Thanks.
I wasn't sure the sticky applied to me because the left part of the bar in my case is not blue.
Report comment to moderator  
Reply With Quote
Unread 04/11/24, 08:03 AM  
sirinsidiator
 
sirinsidiator's Avatar
AddOn Author - Click to view AddOns

Forum posts: 1578
File comments: 1129
Uploads: 41
Originally Posted by Octopuss
Originally Posted by sirinsidiator
Originally Posted by Octopuss
3 hours later still nothing, only I am stuck with the bar showing small green part and the rest is orange.
"History has not linked to present events yet".
So I take it's the addon that's the problem?

Resetting the cache is horrible thing to do, because in the guilds I am in, I would have to manually click through 600 or so pages worth of sales. I miss the old interface where I could simply keep pressing E and wouldn't have to gho through pages.
You certainly like to make it hard for yourself. If you simply followed my instructions, you wouldn't have to click through 600 pages or loose any data at all.
I have not had to clear my own cache a single time since the update landed and have all the data we could get. It does get stuck from time to time, but I simply do as I wrote in the sticky post and after a few days it always manages to link up on its own and I can create a new good backup to restart from.
Uh, the sticky post literally says to clear the cache. If I do that, I have to manually go through the entire history in order for the addon to recognize the data.
Or I don't really understand what part of it covers my situation since you talk about few different things there.

edit:
I mean this cannot be normal, especially since the third trading guild is green.

I've updated the sticky. Hope it's more clear now.
Report comment to moderator  
Reply With Quote
Unread 04/11/24, 06:51 AM  
Octopuss
 
Octopuss's Avatar

Forum posts: 176
File comments: 817
Uploads: 0
Originally Posted by sirinsidiator
Originally Posted by Octopuss
3 hours later still nothing, only I am stuck with the bar showing small green part and the rest is orange.
"History has not linked to present events yet".
So I take it's the addon that's the problem?

Resetting the cache is horrible thing to do, because in the guilds I am in, I would have to manually click through 600 or so pages worth of sales. I miss the old interface where I could simply keep pressing E and wouldn't have to gho through pages.
You certainly like to make it hard for yourself. If you simply followed my instructions, you wouldn't have to click through 600 pages or loose any data at all.
I have not had to clear my own cache a single time since the update landed and have all the data we could get. It does get stuck from time to time, but I simply do as I wrote in the sticky post and after a few days it always manages to link up on its own and I can create a new good backup to restart from.
Uh, the sticky post literally says to clear the cache. If I do that, I have to manually go through the entire history in order for the addon to recognize the data.
Or I don't really understand what part of it covers my situation since you talk about few different things there.

edit:
I mean this cannot be normal, especially since the third trading guild is green.

Last edited by Octopuss : 04/11/24 at 07:42 AM.
Report comment to moderator  
Reply With Quote
Unread 04/11/24, 04:58 AM  
sirinsidiator
 
sirinsidiator's Avatar
AddOn Author - Click to view AddOns

Forum posts: 1578
File comments: 1129
Uploads: 41
Originally Posted by Octopuss
3 hours later still nothing, only I am stuck with the bar showing small green part and the rest is orange.
"History has not linked to present events yet".
So I take it's the addon that's the problem?

Resetting the cache is horrible thing to do, because in the guilds I am in, I would have to manually click through 600 or so pages worth of sales. I miss the old interface where I could simply keep pressing E and wouldn't have to gho through pages.
You certainly like to make it hard for yourself. If you simply followed my instructions, you wouldn't have to click through 600 pages or loose any data at all.
I have not had to clear my own cache a single time since the update landed and have all the data we could get. It does get stuck from time to time, but I simply do as I wrote in the sticky post and after a few days it always manages to link up on its own and I can create a new good backup to restart from.
Report comment to moderator  
Reply With Quote
Unread 04/11/24, 03:32 AM  
Octopuss
 
Octopuss's Avatar

Forum posts: 176
File comments: 817
Uploads: 0
3 hours later still nothing, only I am stuck with the bar showing small green part and the rest is orange.
"History has not linked to present events yet".
So I take it's the addon that's the problem?

Resetting the cache is horrible thing to do, because in the guilds I am in, I would have to manually click through 600 or so pages worth of sales. I miss the old interface where I could simply keep pressing E and wouldn't have to gho through pages.
Last edited by Octopuss : 04/11/24 at 03:33 AM.
Report comment to moderator  
Reply With Quote
Unread 04/11/24, 03:21 AM  
Jysoul

Forum posts: 5
File comments: 24
Uploads: 0
Originally Posted by Octopuss
What is the difference between purple and dark purple bar?

Also is this normal?


It's just stuck. I can't request any history, the E button prompt is not showing, I've been online for about 15 mins and nothing happened.
I experienced the same and had to Clear Cache for Trader for each Guild Trader I'm part of. Then go to each Guild Trader and Show More repeatedly until 30 days is reached to get the full Green bar.

Though as noted below, it may break again and ZOS to provide another fix.
Last edited by Jysoul : 04/11/24 at 03:22 AM.
Report comment to moderator  
Reply With Quote
Unread 04/11/24, 12:36 AM  
Octopuss
 
Octopuss's Avatar

Forum posts: 176
File comments: 817
Uploads: 0
What is the difference between purple and dark purple bar?

Also is this normal?


It's just stuck. I can't request any history, the E button prompt is not showing, I've been online for about 15 mins and nothing happened.
Last edited by Octopuss : 04/11/24 at 12:47 AM.
Report comment to moderator  
Reply With Quote
Unread 04/10/24, 04:51 AM  
sirinsidiator
 
sirinsidiator's Avatar
AddOn Author - Click to view AddOns

Forum posts: 1578
File comments: 1129
Uploads: 41
Re: Possible bug still after 9.3.7

Originally Posted by Jysoul
As a steam user, I cannot see how to login in ESO forums to log a bug. Logged into elderscrollsonline.com but cannot see Post option in the forums.

Anyway, after 5 hrs logging into ESO since log off, and passing time with 45 mins ingame, one Guild Trader history won't refresh and provide option to Show More. Prior to login all Guild Traders were Green with 30 days history.

https://imgur.com/a/ceh4R29
We have identified one more bug that prevents the history from merging newly received data and already cached data. A fix is already on its way to make it into the game.
So for now my advice to keep a backup of a working cache and restore that when it breaks is still the best solution we have.
They will also be adding a new api function that allows me to repair the cache by removing only part of the data, so even if it's not the last problem that keeps the system from working properly, we'll at least have a way to work around it without too much hassle.
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.