Master Merchant
Main Table of Contents
ESOUI Mod Documentation
Localized Suplimental Documentation
Under Construction
The website is being updated to reflect changes in the images for LibHistoire 2.1.1 and Master Merchant 3.8.x, thus the screenshots, icons, settings menus, and menu descriptions may not mirror those found in-game.
A bit of light reading
Master Merchant is pretty complex. While I try to keep it somewhat simple, you do need to read carefully as this is not just a bit of light reading.
Contents
• 3.1.1 For Players not in a Trading Guild:
• 3.1.3 For Trade Guild Members:
• 3.2 Major Changes with Update 41!
• 3.2.1 Known issues with Update 41
• 3.2.3 Reset the managed range
• 3.2.5 Things to know about Update 41
• 3.2.9 Show More is available
• 3.2.10 Details about Update 41
• 3.2.11 Preface: Understanding the Zenimax Database Changes
• 3.2.14 Transition from id64 to id53
• 3.2.15 Adapting Master Merchant to the Changes
• 3.2.16 Impact on Master Merchant Users
• 3.3 Setup Master Merchant 3.0
• 3.3.2 What to disable when MM is not needed
• 3.3.3 Importing older Master Merchant Data
• 3.3.3.1 MMxxData modules needed for importing
• 3.3.4 What to expect after you log in for the first time
• 3.4.1 Duplicate Indexes Detected
• 3.4.2 LibGuildStore.lua:309: attempt to index a nil value
• 3.7.3 Bonanza - Using BeamMeUp
• 3.8.1 Controlling skewed prices
• 3.9 MM Price vs TTC vs Bonanza
• 3.9.1 Evaluating the Bonanza price
• 3.9.2 Price Sold vs. Price Listed
• 3.9.3 Comparisons between Bonanza, TTC, and MM
• 3.10 States of the LibHistoire cache
• 3.10.3 Linking in progress, with 0 events left
• 3.11 Obtaining Guild History
• 3.12 Unlinked Events Notification
• 3.13.1 Guild Sales and Personal Sales
• 3.13.2.1 What The Columns Mean
• 3.13.3.1 Top Buyers and Sellers
• 3.13.3.3 Personal Sales - Seller's Report
• 3.13.3.4 What The Columns Mean
• 3.13.4 Guild Sales Date Filter Ranges
• 3.15.1.1 Master Merchant Window Options
• 3.15.1.2 Sales Format Options
• 3.15.1.3 Time Format Options
• 3.15.1.5 On-Screen and Chat Alert
• 3.15.1.6 Calculation Display Options
• 3.15.1.8 Guild & Account filter
• 3.15.1.9 Deal Calculator Options
• 3.15.1.13 Price To Chat Options
• 3.15.1.15 Guild Store Options
• 3.15.1.16 Guild Master Options
• 3.15.2.1 Sales Management Options
• 3.15.2.2 Data Management Options
• 3.15.2.6 Import ATT Purchases
• 3.15.2.7 Refresh LibHistoire
• 3.15.2.8 Import ShoppingList Data
• 3.15.2.9 Import Pricing Data
• 3.16.2 Level Quality Selectors
• 3.16.4 What is being scanned
• 3.16.4.1 A few days of sales from 109 entries
• 3.16.4.2 4 days of sales from 8031 entries
• 3.17.1 3.7.x Sorting Writs by voucher count
• 3.17.3 Export Sales Activity
• 3.17.4 Export Personal Sales
• 3.18.1 Backup LibGuildStore Data
• 3.18.2 Locating LibExecutionQueue
• 3.18.3 Unintentional ZOS Bug
• 3.20.2 Backup Master Merchant 2.x Data
• 3.20.3 Uninstall Master Merchant 2.x
• 3.20.4 Alternate Upgrade Method
• 3.20.5 Optional Mods For This Procedure
• 3.20.6 Optional Debug Settings
3.1 - Features
Master Merchant offers additional features for the Traders of trading guilds. However, the Bonanza module can be used by anyone looking for deals in Tamriel.
3.1.1 - For Players not in a Trading Guild:
Use Bonanza to search for deals. It creates a virtual Auction House of sorts. Searches remain in the Bonanza window for 24 hours. An average price is generated depending on how many of each item you find. However, you will want to filter for items in the Bonanza window to seek out the cheapest price for items found.
• View items purchased from any kiosk (Shopping List)
• View items listed at kiosks you have visited (Bonanza)
• Right click menu to quickly search Bonanza for the item
• Mark writs on the Guild Store menu you can craft (Writ Worthy required)
• Mark items sold for more then the vendor price
3.1.2 - For Trading Guilds:
• See who your Guild’s top sellers are and what they are selling
• See your total Guild Sales and Sales Tax income
• Export Sales Report or Sales Activity
3.1.3 - For Trade Guild Members:
• View your personal sales
• View items you have listed for sale
• View your canceled items
• View Guild Sales by other members
• Show sales by total price or price each
• View a ranked report of items sold by other Guild Members
• Deal Calculator flags items at kiosks
• Use TTC, MM, or Bonanza prices
• Custom Deal Calculator settings available
• Sort by Deal Percentage
• Writs are separated by voucher count
• Craft cost added to tooltip, including Potions and Poisons
• Material Cost for Winter Festival Writs (BETA)
• Autofill a price check into chat to share with other members
• MM automatically saves the last price of any item you list for sale (Awesome Guild Store overrides this feature but provides a similar function)
• View suggested MM price when listing items for sale
• Search any item from any view and filter for specific items
• Toggle to ignore outlier prices (Can be defeated, view documentation)
• Set custom time ranges for SHIFT, CTRL or both.
• Toggle for additional Guild Roster Columns
• Show condensed TTC information in tooltip
• When using this option it is recommended that you toggle the TTC default tooltip off
• Replace inventory prices with TTC or MM average price (Will affect performance)
• Toggle whether or not to show the unit price
• Stack Price calculator (Awesome Guild Store overrides this feature but provides a similar function)
• Add sellers to the Guild & Account filter from Graph and some MM UI Views
• Import ATT sales
• Import old MM Sales prior to 06/01/2021
• Prior to version 3.6.46
• Export Personal Sales or Purchases
Craft cost will be affected by your skill in Chemistry, Chef, and Brewer.
3.2 - Major Changes with Update 41!
With Update 41 all of your previously stored LibHistoire sales data will be deleted. You can read more about the changes in this thread.
Your Master Merchant sales data will not be deleted or reset once U41 is released.
3.2.1 - Known issues with Update 41
The recent incremental patch on April 08, 2024 resolve some issues. Patch Notes
• Mod authors cannot check duplicate sales between old and new server data
• Guild history categories may become unusable
With Update 41, mod authors can not cross reference any previous sales data with the current sales data from the server and look for duplicate sales. You may have all green bars but switch characters and any Trader category could become stuck and you won't be able to use the forward arrow key or E Show More to request more data.
sirinsidiator
...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.
3.2.2 - Restore a backup
Restoring a backup ensures you keep all data in perfect condition and takes minimal effort. Simply check if everything has linked before you log out for the day and if it did, create a new backup of the cache files. Otherwise, restore a previous working version of these files and try again the next day.
3.2.3 - Reset the managed range
ZOS has said there are no missing events between the segments that did not merge properly. ZOS has said that any data 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.
3.2.4 - Clear the cache
Using this option means you will loose all data beyond the server range. Manually requesting the full 30 day range again takes a great deal of time and any sales data already in MM will be treated as a duplicate and ignored.
3.2.5 - Things to know about Update 41
The following sections go into more detail. With update 41 the server database for all guild history was reset and ZOS created a new database on their server. Mod authors can not cross reference any previous sales data with the current sales data from the server and look for duplicate sales.
Changing that will reload the UI because it's not a soft toggle.
When the setting Use historical and recent sales data is enabled historical and current sales data will be combined but all duplicate data will affect the totals. While users may not mind mixing the data for pricing, your weekly sales totals will reflect an incorrect total unless the option is disabled.
All the pricing data and guild sales totals are calculated during initialization so you can not toggle between using and not using historical data in addition to the current server data without another full initialization of all data.
For that reason, unless you feel you must be the library of congress of data I recommend to leave that feature OFF or disabled.
3.2.6 - New LibHistoire UI
There is a new interface for LibHistoire and I will be updating more documentation as time permits. The important difference is the Rescan button has been removed and you have a settings button instead.
3.2.7 - New Vanilla UI
There is a new interface for Guild History. There are arrows for navigating the various pages of guild history and the Show More option only appears when you are on the last page of data.
3.2.8 - Data is available
If no arrows appear then the data is not ready and this is not a mod error. The server may not have information and ZOS may need to make updates to the game. If reloading the UI does not correct the issue you will have to wait for authors to communicate with ZOS to see if there is a resolution.
3.2.9 - Show More is available
To request more data you will need to go to the last page available. Then the E Show More option will appear.
3.2.10 - Details about Update 41
3.2.11 - Preface: Understanding the Zenimax Database Changes
Before delving into the details, it's crucial to clarify that the transition from id64 to id53 for sales identifiers is not the main reason behind their reset. Even if the identifier type remained unchanged, the same issue would persist. Zenimax introduced a new database structure for storing guild history data on the server to enhance the efficiency of handling sales. In addition they changed the type of sales identifiers.
I will focus on why this matters to you as a Master Merchant user. If you notice duplicate sales in the interface, rest assured that it's not an error caused by the id64 to id53 transition. This unavoidable situation stems from the changes in how Zenimax stores sales data.
3.2.12 - Important Reminder!
Because the changes to the Zenimax server's database are significant, it's recommended to have a backup made prior to Update 41 (March 11 2024) to restore if changes are made to Master Merchant functionality after launch. Likewise, if Zenimax makes any changes that would directly impact how the data is obtained from the local binary file stored on each user's hard drive.
For more information review how to Backup LibGuildStore Data.
3.2.13 - Introduction
In the upcoming Elder Scrolls Online Update 41, Zenimax is making changes to the Guild History data. The server database for sales data has been updated, and due to that, the unique sales identifiers will not continue from where they left off prior to the update. One significant consequence for users is the inability to check for duplicate sales between the old and new database entries.
Using the image as an example, without the timestamp (1709606076) and without the unique identifier, the sales would be duplicates because they are all from the same seller, buyer, for the same item, and the same amount.
3.2.14 - Transition from id64 to id53
In Update 41, Zenimax is implementing significant changes to the Guild History data, introducing a new guild history format and resetting the server's database. Consequently, unique sales identifiers are starting over, and the system will now use the id53 format. This shift is not solely about the transition from id64 to id53; it's part of a broader move toward a more efficient guild history database structure.
3.2.15 - Adapting Master Merchant to the Changes
With these changes, and because the id53 identifiers have started over, Master Merchant will be separating data using the id64 and id53 identifiers. Master Merchant will be able to check duplicates only when the same type of data is compared, meaning id64 and id64 or id53 and id53 because the Zenimax server database is different.
All item averages used for evaluating item pricing and weekly sales totals for Guild Masters will only be accurate when using data from the new Zenimax cache and the id53 identifiers.
While there will be a toggle to utilize the old sales data, without the ability to properly check for duplicate sales, data using id53 mixed with the older id64 data will mean those totals will not be accurate.
3.2.16 - Impact on Master Merchant Users
For the majority, the changes will have minimal impact because the binary cache should already contain data. Users that retain 30 to 90 days of data will not have a significant loss of data, and Guild Masters will be able to accurately track recent weeks for evaluating user contribution in sales.
However, users archiving extensive sales data, trying to be the library of congress of data, will have inaccurate averages when the id53 and id64 data overlap.
Additionally, I would like to remind users that maintaining an excessive amount of sales data in the Zenimax binary cache will negatively impact load times during login, even if Master Merchant is disabled.
3.3 - Setup Master Merchant 3.0
If you are installing Master Merchant for the first time please follow these steps.
• Install Master Merchant 3.0
• Log In
• Wait for Refresh to finish
• Read the section on Obtaining Guild History
What is described in Obtaining Guild History is how you request data from the server for use.
3.3.1 - What is required
You can still use ATT and MM at the same time if you chose. There is a toggle to disable the notification under Debug Options under the MasterMerchat settings.
• Master Merchant 3.7.x
• LibExecutionQueue
• LibGuildStore
• LibGuildStore Data File GS00Data, LibGuildStore Data File GS01Data, etc.
• LibAddonMenu
• LibMediaProvider
• LibGuildRoster
• LibHistoire
• LibAsync
• LibDebugLogger
• LibAlchemy
• LibPrice
3.3.2 - What to disable when MM is not needed
If you are with a trial group or doing daily writs you may not want MM running in the background to reduce loading times. If you do make sure to disable all of the following.
• Master Merchant 3.7.x
• LibExecutionQueue
• LibGuildStore
• LibGuildStore Data File GS00Data, LibGuildStore Data File GS01Data, etc.
3.3.3 - Importing older Master Merchant Data
Caution, the more data you import the longer MM will need to load.
Download Importers for Master Merchant 3.0 which includes all the Master Merchant Data File modules MM00Data, Master Merchant Data File MM01Data, etc. and ShoppingList.
You can import older Master Merchant Data if you have backups for those who like being the library of congress of data. Just know that it will increase load times and the game will take longer to log out as well while saving the data.
If you are experiencing issues after trying the following steps you can review the section Alternate Upgrade Method.
3.3.3.1 - MMxxData modules needed for importing
The MMxxData (MM00Data, MM01Data, etc.) modules are used for importing data only. After your import your data, these old modules should be deactivated.
Because of how saved variables work you have to enable the old MMxxData modules to load the data into memory.
3.3.4 - What to expect after you log in for the first time
once you log in the LibHistorie Refresh will start. You will know when the refresh has finished when you see, LibGuildStore Refresh Finished appear in the chat window. You will need to obtain guild history data from the server.
Once the initial refresh is finished you can import sales from MM. This is to accommodate people who may have more history in their MM data files then they do in LibHistorie. You can also import from ATT for the same reason. If you have been using ATT and have never used MM then you could have 30 days of data in your ATT data files. After you import your ATT data and do a Ten Day with LibHistorie you will have the most data possible. You can also import purchases from ATT and the old standalone ShoppingList for MM. There will be notifications to disable the old MMxxData modules, the old ShoppingList standalone module, and ATT. There is an option to disable the ATT notification if you prefer to use both MM and ATT at the same time.
3.4 - Troubleshooting
3.4.1 - Duplicate Indexes Detected
If this notification appears then you either need to cancel and restore a backup or allow Master Merchant to reset all its internal data files and refresh sales data from LibHistorie.
Your LibHistorie cache will not be reset by accepting to reset Master Merchant data files.
3.4.2 - LibGuildStore.lua:309: attempt to index a nil value
user:/AddOns/MasterMerchant/Libs/LibGuildStore/LibGuildStore.lua:309: attempt to index a nil value user:/AddOns/MasterMerchant/Libs/LibGuildStore/LibGuildStore.lua:316: operator < is not supported for nil < number
If you have the above error then that means you deactivated Master Merchant but not the rest of the required modules. You need to deactivate all of the GSxxData modules and LibGuildStore. This is mentioned in What to disable when MM is not needed
If you intend to use Master Merchant and you have the above error then you need to update or activate the required modules for Master Merchant.
3.4.3 - Lua errors
There are times when the game for some reason will corrupt GS16Data.lua or GS17Data.lua and when that happens ESO will reset the file. Once that happens nothing about Master Merchant will work with the existing data. You won't be able to open the Master Merchant UI to view sales data or if you hover over the dots on the Graph you will have errors similar to what is shown below.
user:/AddOns/MasterMerchant/MasterMerchant_UI.lua:458: operator .. is not supported for string .. nil user:/AddOns/MasterMerchant/MasterMerchant_UI.lua:573: operator .. is not supported for string .. nil user:/AddOns/MasterMerchant/MasterMerchant_UI.lua:970: operator .. is not supported for string .. nil user:/AddOns/MasterMerchant/Libs/LibGuildStore/Data.lua:337: attempt to index a nil value
While in game go to the LibGuildStore settings menu and look for the heading Reset LibGuildStore.
After you click the Reset LibGuildStore Data button the UI will reload and Master Merchant will get information from the LibHistoire cache. After the UI reloads about every minute you will see that Master Merchant is still refreshing data. There will be an approximated time remaining that will go up and down because it's not perfect.
Do not log out, do writs, open a guild trader, update LibHistorie data, or do anything else until the refresh is complete. Do nothing except maybe move enough or type in guild chat so you don't go AFK.
3.4.4 - OneDrive
OneDrive is great for many reasons however, for ESO it can create a situation where the GS16Data.lua and GS17Data.lua files are not synced properly. I would think this would affect any of the GSxxData.lua saved variable files because of their size. They may not syncronize quickly with some internet users because of upload and download speeds being limited. To resolve this you need to change settings so that OneDrive will no longer try to backup your Documents folder where all your Addons and SavedVariables file are located.
I will admit I do not have Windows 10 or Windows 11 so this is peiced together from helping someone.
First open the OneDrive settings by clicking the Cloud icon for OneDrive.
Click the Manage Backup button.
As shown in the above screen shot all three folders are being monitored by OneDrive. You want to disable the backup for the Documents folder.
Now OneDrive will no longer try to backup the Documents folder.
If prompted, chose This Computer Only so that OneDrive will not attempt to backup your Documents folder.
You do not have to pay for OneDrive or update to get more space. If you have any issues pausing or stoping OneDrive so that you can change the settings just wait longer until it pauses or stops. It may take a while but it will happen.
3.5 - LibHistoire UI
The new interface has all the new categories from guild hsitory.
There are options to lock and unlock the window to move it and then lock its position.
Each category has a popout menu that will be explained below.
3.5.1 - Reset Linked Range
This feature should not be used. I am having a hard time understanding when to use it.
Here are some reasons not to click it:
• You are missing less than 1 day of data
• You are missing 5 days of data
• You have not played for 2 monts, the ZOS chace was set at 30 days, and you cannot obtain data for 2 months because too much time has passed
LibHistoire is smart enough to know what to do in either case. So it is recomended to not use that option.
In all cases Obtaining Guild History from the server is the best option and LibHistoire will process the data.
3.5.2 - Clear Cache
This feature will clear the cache stored on your local hard drive. It does not delete any data from the server. Should you want the data from the server again, you would need to manually request it.
3.5.3 - Request Mode
Automatic: means data will be requested based on the Addon requesting the data from LibHistoire
Force Off: means data will not be requested whether or not an Addon uses the data
Force On: means data will be requested from the server and kept in the binary cache so that a mod can access it
LibHistoire automatically requests data from the server and depending on LibHistoire options and features used the requests may be interupdated.
3.6 - Shopping List
Adds a new icon allowing you to view purchases you make from guild stores.
The Shopping List icon allows you to select the installed extension and view purchases you have made from guild stores.
The by old Shopping List extension by MildFlavour is not longer used and can be disabled after you import your purchases.
3.7 - Bonanza!
Shop all of Tamriel with Beam Me Up and Bonanza. Master Merchant is not just for high end traders anymore. If you are shopping for the best deal you can find it in the Bonanza window.
With MM 3.7.x the Bonanza 
icon allows you to view items you have seen at traders as you shop for items to purchase.
3.7.1 - Bonanza Name Filter
3.7.2 - Bonanza Type Filter
3.7.3 - Bonanza - Using BeamMeUp
If you have BeamMeUp installed you can right click the Location column to travel to the zone the trader is located in with the usual BeamMeUp restrictions. If there are no players in the zone to jump to BeamMeUp will notify you and you may travel to a wayshrine that is not close to the trader.
3.8 - Outliers
With only 5 sales the obvious outlier is not ignored.
There must be at least 6 sales before Master Merchant can ignore outliers.
With 8 sales of the same item you can see that the obvious outlier is being ignored.
When ignoring outliers with 6 or more sales that does not mean the highest and lowest sale will be ignored. The lowest and highest price may be well within range and reasonable prices. The above example is a good example to show the remaining 7 are well within tolerance of one another.
3.8.1 - Controlling skewed prices
People will intentionally try to sell items much higher then they are worth. Use the resources available rather then squint at the scatter plot.
While viewing a graph as shown above find out who is skewing the price and add them to the Guild & Account filter.
Once the seller is added to the Guild & Account filter you can see that the graph is much more useful.
The absence of the Bonanza price is not what corrected the graph. The Bonanza average changed because the seller of the item listed for 3000g is being ignored. Other listings of the same item for 200g would not have the same drastic affect as the listing for 3000g.
For convenience you can add sellers to the Guild & Account filter from the Bonanza menu.
3.9 - MM Price vs TTC vs Bonanza
There are several examples because I feel Bonanza is new and it may be hard to understand the various ways to use it. I highly suggest reading all of the following sections.
• The MM price is in yellow text, and it is the price the item sold for in one of the guilds you are in. It is not a price from other outside sources like other guilds on the server and it is not from TTC.
• The TTC Price is from their own data collected by their EXE and transmitted to their server. They trim outliers using their own method and then make an average of the remaining data.
• The Bonanza Price is in blue text and it is an average from a 24 hour snapshot of all the listings you have seen of that specific item from the traders you have visited.
Looking at the first example of the Hlaalu Bookcase you see it sold 1 time out of all the guilds I am in. So there is no way to get a reasonable price for it. Someone listed it 56 days ago for 100K and it sold. That is one of the drawbacks of the MM price. If you do not have many sales from the guilds you are in then the MM price won't be very helpful. Also from the first example you see that the TTC price is about 19K and the Bonanza price is 17K. There are 9 listings from TTC and 1 from another trader. Once you have more data the Bonanza price may change but you can more easily see that 17K to 19K would probably be a more reasonable price then 100K.
From the second and third examples you will note that the TTC price is useless for these items. The TTC price can sometimes be very helpful. The bonanza price is also higher then the MM price. This is where the Bonanza window will be needed because you will need to search for the exact item and look at the prices you have found. This is discussed in the section Evaluating the Bonanza price
The Bonanza price while similar to TTC is the average of what you have found at the traders you have visited in the last 24 hours. Bonanza itself is intended to be a shopping tool but since the data is there it is displayed on the graph for you to use as another way to evaluate what the item is currently selling for. If you only have 1 to 3 sales you can not compute an average from that I'd suggest 5 or more depending on how popular it is on traders at the time.
For the last example you will note that the Bonanza price for Chromium Plating is only about 22K above the MM price. With more data it may even fall exactly in line with the MM price. The TTC suggested price is 239Kwhich is 2K different then the Bonanza average. For items that normally do not have a lot of skew to the pricing data this will be common. For items that have more outliers skewing the pricing data you will need to evaluate the TTC and Bonanza prices to get a better idea of what may be a good price to sell the item for.
3.9.1 - Evaluating the Bonanza price
If those are too small, right click the image and show it in a new tab to see the full size.
Looking at the tooltip TTC shows 74K to 93K, the Bonanza average is 158K, and the MM price is 70K. Then the highest and lowest listing in TTC is 446 to 5M. With TTC you can not view the current prices being used for their suggestion. You can view the Bonanza prices to evaluate what other people are selling the item for. For this example you would open the Bonanza window and search for style zero cuirass.
As you see in the middle screenshot the prices range from 50K to 80K. In the last screen shot the highest prices are 1M to 3.9M. So now you have three prices all in about the same range. 1) 50K to 80K 2) 70K 3) 74 to 93K and all without opening external websites, google docs pages, or spreadsheets. It didn't require two monitors and it took only a few moments.
It is easy to see that 70K is probably the best average price to sell the style page for. If you want it to see faster because you want it out of your inventory, 50K won't bee too low that someone might flip it and even if they do you still made close to the going rate of 70K.
Just because the Bonanza price is not 70K and is showing 158K doesn't mean it is inaccurate. In this example it is being affected by all the prices above 1M. Although you can not see the data you will be able to view your own. For the data used in the screen shots 99 of the prices were above 100K which will affect the average significantly. This is why I recommend you evaluate the price in the manner described.
3.9.2 - Price Sold vs. Price Listed
The above items are meant to show items that have an unusual range for the TTC price or Bonanza price because it is the listed price. For items like style pages if there are 124 listings and 99 of them are 100K and above you may wonder if you could make more from selling the item. Maybe and maybe not. This is the difference between what the item sold for which is the MM price and what the item is listed for which it the Bonanza or TTC price. Think of how an author might write a book. They write the book so it is appealing to their audience. So imagine who will be buying your items. Do they have 6M to spend on something and plenty of gold left over? Does your buyer have 6M at all? Have they ever had 6M at one time? Are they willing to spend 6M for the item? It is simple common sense that if someone has 124 items to choose from they will buy the cheapest one. Just because something sold for 5M or 6M 60 days ago when the item was scarce and someone had that much to spend on the item doesn't mean people will pay that price when the item is less scarce.
The above examples don't represent things like crafting materials where the pricing is more consistent and the MM price is more reliable. With the example of crafting materials that is simple supply and demand. If you want to read an article on it be my guest and you can enjoy such wonderful words as equilibrium and elasticity, knock yourself out. There are a lot of crafting materials on guild stores so there is a large supply and there is a large demand for them. Because there is a consistent need for them people purchase the cheapest listed items and the price remains rather consistent.
This is not the case for everything. Take your time and use the different prices and tools to evaluate what you are selling, what others are selling it for, and what others are buying it for.
3.9.3 - Comparisons between Bonanza, TTC, and MM
To start with you will have people that list an item for something stupid and it just contaminates the TTC database. They should be prevented from uploading TTC prices from the TTC developers. When you have items with no data or items that people feel should sell for millions of gold then those are harder to evaluate.
That isn't what I will cover in this section because that kind of data is not usable.
Look at these examples of the Bonanza price
Bonanza is within 1K approximately from TTC and the MM average.
Bonanza is 1g away from the TTC average.
Most sales noobs feel you have to have millions of sales in your database, years and years of stuff, and preserve data like you are the library of congress or something. If you look at both of those screen shots TTC has data points in the thousands. 15,000 for the Dreugh Wax, and 2,800 for the Blessed Thistle. Yet I have the same price for the Blessed Thistle with only a few hundred data points.
I could write Lua code that anyone could copy and paste into an online Lua compiler that could show you how I can add a variety of numbers and come out with a certain average, say 100. Then I could add together another set of data that has different and more numbers, and still come within approximately 5g of the average I am looking for. A range of 95g - 105g more or less.
The example would be bias of course because I am demonstrating that if you when you add 100, 99, 90, 95 and so on.. together that you get a specific average. If you load more of the same numbers you will get the same average. I don't care how many times you add 100 + 100 + 100, it will be the same outcome.
In statistics this is called the Mode. So the value that appears most often. Commonly sold materials such as Chromium Grains, Dreugh Wax, Clam Gall, Blessed Thistle and such that the data is fairly consistent. When data is more consistent you don't need thousands of data points to get the proper average.
Don't make it work. If you visit 3 or 4 cities and search for key items at all traders then you should have enough data to work with. TTC and Bonanza should be close however, it depends on the pricing people use. Some people post the TTC Suggested price and some post the Average price. It depends on the demand of the item and the price.
The other benefit of Bonanza is that you can view the prices. Which is what I show in my documentation under Evaluating the Bonanza price. If you feel the price is not in line with TTC or listings from other traders then look. If other traders list a style page for 50K and that is the most common value then that is the going rate. You can then price your items to be competitive with other guilds.
So it may be a bit of information overload but without the need for two monitors, viewing the TTC website, viewing google docs, viewing spreadsheets, exporting prices from MM to paste on websites, just use the Master Merchant interface. It is simple and easy to switch views and search for things to compare information without leaving the game to look at outside sources for information.
3.10 - States of the LibHistoire cache
3.10.1 - Unlinked
In the Unlinked state you can either wait for the server to grant the requests for offline data that LibHistoire requests, or you can manually request guild history for the time you were offline.
3.10.2 - Linking in progress
Once LibHistoire has what it feels it needs, then it will begin processing the guild history events and attempt to link to the last known event.
3.10.3 - Linking in progress, with 0 events left
If you ever see it processing 0 events for a while you will just need to wait for the events to link. If there are external factors involved then nothing will process until that is no longer affecting LibHistoire.
3.10.4 - Linked
Once LibHistoire has linked to its stored events you should see green text. This means that LibHistoire has finished processing the guild history.
You can still request additional history and ask LibHistoire to check the guild history for any missing sales events using the rescan button.
3.11 - Obtaining Guild History
To obtain sales data the page number and right arrow (or forward arrow) must be showing. You will need to use the arrow to go to the last page of available data.
Once you have done that the E Show More option will appear. Even if there is no right arrow showing press E to request more data.
After you have enough guild history to cover the time you have been offline the right arrow will appear. This means you have requested all the missing data. Using the right arrow to go to the end of all the history stored in your binary cache will not request more data from the server. It simply displays the data. You can go all the way to the end if you like but it is not needed.
If you have not been keeping your data up to date and you have multiple gaps in data the LibHistoire UI will show you and you may need to advance to the next gap and request more data.
3.12 - Unlinked Events Notification
With LibHistoire 1.2.0 there is a new notification when you log off.
You could have any amount of time that has not been linked with your Guild History Events. If you chose to log off that is fine but pay close attention to the notification. Any gap in information will still be there when you log back in and you will have to take additional steps to obtain any missing sales data.
3.13 - Master Merchant Window
Search Box
Cycles through: Seller, All sales totals by Seller. Item Sold, Top selling ITEMS. Buyer, All purchase totals by Buyer.
Opens the Statistics Window.
Seller Info Guild Ranks, Item Info Your Info or All Info.
Sales view shows Personal Sales or Guild Sales. Use the Seller Info/Guild Ranks toggle to change views from Item Report to Sellers Report.
The Shopping List icon allows you to view purchases you have made from guild stores.
The Bonanza icon allows you view trader listings you have seen at other guild stores.
The Management view lets you see posted and canceled sales.
Sends mail to the author with an optional donation amount.
The Moneybag icon means the purchaser is not a member of that guild.
Item Sold is only available from a Seller's Report.
Donations should be voluntary. People that struggle to make 25K gold a week, feel free to just say thanks. I'd rather receive a 50K donation from top sellers making millions a week.
3.13.1 - Guild Sales and Personal Sales
First select what information you would like to see. Show Personal Sales will display info ONLY about You. Show Guild Sales will display data from all members of all of your guilds.
When the button says Show Guild Sales, that means you are currently viewing YOUR information and vice-versa. You can toggle back and forth between Personal Sales and Guild Sales while viewing any report.
3.13.2 - Item Report
If you have ever opened the Master Merchant window you have probably seen the list of your personal sales. This is an Item Report and if you click the People Icon you will change between the Buyer and the Seller.
3.13.2.1 - What The Columns Mean
• Buyer: The purchaser of the item.
• Guild: The guild associated with the sale of the item.
• Item Sold: To the left of the Item Sold is the items icon. The number indicates how many of that item was sold.
• Sale Time: The approximate time the item was sold. The game stores all sales using epoch time so the UI just approximates the sale after the first hour.
• Price: The price the item sold for. You can view the individual price by clicking the Show Unit Price button.
Toggle between the Unit Price and Total Sale.
3.13.3 - Seller's Report
3.13.3.1 - Top Buyers and Sellers
3.13.3.2 - Top Items
3.13.3.3 - Personal Sales - Seller's Report
You can also view a Seller's Report for your personal sales only the items will be YOUR top selling items.
Clicking the People Icon will cycle through Seller, Buyer, and Item Sold.
3.13.3.4 - What The Columns Mean
• Rank: The rank of the member or item for the guild listed. For example, if you are viewing a seller's report and your rank is 7, it means you are the 7th biggest seller in the guild for the time selected. If you are viewing an item report for and Dreugh Wax is the 1st item in the list, then Dreugh Wax is the biggest seller for the guild showing.
• Sales/Purchases: Total Sales or Purchases for that guild or member for the time selected.
• Tax: Total Tax generated for that guild or member for the time selected.
• Count: The number on the left is the number of transactions, while the number on the right is the number of items. For example @TradingDude had 10 Dreugh Wax transactions and sold 100 Dreugh wax total.
• Percent: This shows what percent of total guild sales or purchases each member is responsible for.
3.13.4 - Guild Sales Date Filter Ranges
• Default: Default uses the amount of days for Default set in Calculation Display Options. However, if you open the Master Merchant window while holding a Focus key such as SHIFT, CTRL or both, then opening the window will use the amount of days you set for that Focus.
• 30 Days: 30 Days.
• 30-60 Days: 30 to 60 Days.
• 60-90 Days: 60 to 90 Days.
• Custom: Custom uses the amount of days set in Master Merchant Window Options
3.13.5 - Date Ranges
There are several date ranges you can choose from. This Week, Last Week and Prior Week start from the ZOS trader flip for the current Sales Week. However, the last option is customizable under the Master Merchant settings under Calculation Display Options.
Days are calculated from midnight and weeks are calculated from each kiosk flip on Tuesday. For example the option 7 Days would be the last 7 days of sales while Last Week will be from the previous kiosk flip to the most recent kiosk flip. Both of which will be a Tuesday.
3.14 - Statistics Window
3.15 - Settings
3.15.1 - Master Merchant
3.15.1.1 - Master Merchant Window Options
• Open With Mail: Whether or not to open the Master Merchant Window when you open your mail.
• Open With Store: Whether or not to open the Master Merchant Window when you interact with a guild store.
• Show Full Sale Price: Show the full price of the sale rather then the amount after the store cut is deducted.
• Window Font: The font for the Master Merchant Window. You may have other fonts if you have mods that use LibMediaProvider like one of my other mods Advanced Nameplates.
• Custom Filter Timeframe: The amount of days to use for the Custom dropdown for the Guild Sales Date Filter Ranges
If you sold a Crafting Motif 63: Dremora Bows for 11,000 
the master merchant window will show what you received in the mail which would be 10,230
.
3.15.1.2 - Sales Format Options
When the setting Use historical and recent sales data is enabled historical and current sales data will be combined but all duplicate data will affect the totals. While users may not mind mixing the data for pricing, your weekly sales totals will reflect an incorrect total unless the option is disabled.
All the pricing data and guild sales totals are calculated during initialization so you can not toggle between using and not using historical data in addition to the current server data without another full initialization of all data.
For that reason, unless you feel you must be the library of congress of data I recommend to leave that feature OFF or disabled.
3.15.1.3 - Time Format Options
3.15.1.4 - Alert Options
• On-Screen Alerts: Show On-Screen popup alerts when you receive a sale. See examples below.
• Show Alerts in Cyrodiil: Enable or Disable Alerts in Cyrodiil. Useful if you watch for specific PVP alerts and do not want MM Alerts to show up.
• Chat Alerts: Show chat alerts when you receive a sale. See examples below.
• Alert Sound: Choose the Alert sound to differentiate it from other mod added Alerts.
• Show Multiple Alerts: Investigating
• Offline Sales Report: Show Alerts for sales received while offline. See note.
• Display Listing Message: Show chat alert when you list an item for sale.
Show Multiple Alerts and Offline Sales Report may not function as intended with the addition of LibHistoire. However, you will still see notifications of sales as they are received.
3.15.1.5 - On-Screen and Chat Alert
3.15.1.6 - Calculation Display Options
WARNING: All sales have already been sorted by the Custom Timeframe at startup. See documentation for more information.
Custom Timeframe requires a reload because all of the sales have been placed into all the date ranges as shown in Date Ranges and therefore changing the value means that all the sales would have to be calculated again. This process is difficult to begin with so to avoid any miscalculations (attempting to clear all sales and stats variables) a reload is required.
3.15.1.7 - Timeframes
For the Custom Timeframe dropdown, Hours, Days, and Weeks are based off of Midnight for the current day. Full Guild Weeks are based off of the current Kiosk Flip.
3.15.1.8 - Guild & Account filter
Right click the dots on the graph to add the Seller to the Guild & Account filter.
There is a limit of 2000 characters for the filter. You will need to manage it from time to time.
You can add the Guild or Seller to the Guild & Account filter from the trader menu with either vanilla or Awesome Guild Store installed.
You can add the Seller to the Guild & Account filter from the Bonanza window.
The Seller is located on the tooltip if you do not have Awesome Guild Store installed.
3.15.1.9 - Deal Calculator Options
• Deal Calculator Type: Choose from MM Average, TTC Average, TTC Suggested, and the Bonanza Price.
• Modify TTC Suggested Price by 25 percent: When enabled will add 25 percent to the Suggested Price used for the Deal Calculator and the ToolTip. This is the same value as shown in the TTC Tooltip. See the Modified Suggested Price spoiler below for an example.
There is no function to check if you set an incorrect value or not. Meaning if Okay Deal Range is 25 percent and the Reasonable Deal Range is 20 percent, nothing will tell you that's not going to work. You will need to keep the values in order yourself from lowest to highest.
3.15.1.10 - Tooltips
3.15.1.11 - Tooltip Options
• Level/Quality Selectors: Adds Level and Quality selectors to the tooltip window. You can bring up the window by clicking a link in chat or when you right click an item and choose Popup Item Data. See the Level Quality Selectors section for example of the selectors that appear on the tooltip window.
3.15.1.12 - Outlier Options
• Trim by percentile only: When enabled you can specify the outer percentile to trim from the sales data without using additional outlier removal methods.
• Percentile: Specify the outer percentile 1 to 15 percent.
• Ignore Outlier Prices: When enabled MM will use fairly standard methods to remove outliers.
• Enable Aggressive Restrictions: When enabled additional restrictions will be used when trimming outliers.
3.15.1.13 - Price To Chat Options
3.15.1.14 - Inventory Options
• Modify TTC Suggested Price by 25 percent: When enabled will add 25 percent to the Suggested Price shown in the inventory. This is the same value as shown in the TTC Tooltip. See the Modified Suggested Price spoiler above for an example.
3.15.1.15 - Guild Store Options
• Show Stack Price Calculator: Adds UI to the guild store if you are not using Awesome Guild Store that aids you in setting the stack price of the item listed
• Save Central Pricing Data: When Enabled all pricing data is stored and available to all guilds. When Disabled all pricing data is stored separate for each guild.
• Display Profit Filter: Adds the Profit to the Time column for the guild store.
• Display profit instead of margin: Enabled shows the profit value in gold pieces, and disabled shows a percentage.
The Price Calculator will not show up with Awesome Guild Store. The Profit Filter is AGS only. Adding the profit margin or the total profit will be shown with or without AGS.
Awesome Guild Store uses its own internal pricing routines and only uses the MM Pricing Data when there is not AGS information. Because of that it may appear that the MM pricing data is malfunctioning when it isn't.
3.15.1.16 - Guild Master Options
3.15.1.17 - MM Debug Options
• Activate Custom Debug Logging: The Custom Debug information is really not intended for normal use and should be left disabled.
• Disable ATT Warning: If you enjoy using both MM and ATT together then please disable the warning that ATT files are active with this toggle.
3.15.2 - LibGuildStore
3.15.2.1 - Sales Management Options
• Use Sales History Size Only: This will ignore the minimum and maximum count for sales. If there are 4698 sales of an item with the day range selected for retaining data, then the sales will not be trimmed.
• Minimal Indexing: Does not add search words for items. It only adds the player search word for displaying personal sales. Searching in the Master merchant window is still possible but will take extra time.
• Sales History Size: The days range to retain data.
• Min Item Count: The minimum count of sales for a specific item before the days range is considered. If you select 90 days to retain data, but you have seen only 1 sale and the only recorded sale is 120 days old it will not be trimmed.
• Max Item Count: The maximum count of sales for a specific item before the days range is considered. If you select 90 days to retain data, and you choose 1000, then the oldest sale once the threshold is reached will be trimmed. Meaning if you have 1001 sales for an item, 1 will be trimmed and 1000 will remain.
• Min Sales Interval: When this value is greater then 0 the Min item count and the sales interval (in Days) will be considered first before truncating. If the interval is set to 10 days and the sale is less then 10 days old the sale will be retained the same as a sale below the Min Item Count.
3.15.2.2 - Data Management Options
3.15.2.3 - LGS Debug Options
3.15.2.4 - Import MM Data
3.15.2.5 - Import ATT Data
3.15.2.6 - Import ATT Purchases
3.15.2.7 - Refresh LibHistoire
The Refresh button tells LibHistoire to send all the data from the zos binary cache. The more data in the cache, the longer it will take to transmit.
The refresh button is only a fail safe mechanism in case a user uses a feature that interupts LibHistoire, preventing it from transmitting data to MM. It should not be clicked every so often or every once and a while. Clicking this does not refresh the Master Merchant window or cause the server to send any Guild History.
3.15.2.8 - Import ShoppingList Data
3.15.2.9 - Import Pricing Data
3.15.2.10 - Reset Data
3.16 - Misc
3.16.1 - Popup Item Data
This context menu is from having Master merchant and Awesome Guild Store installed. The menu will vary depending on the mods you have installed.
3.16.2 - Level Quality Selectors
I will try to update the selector so that there are graphics to click on but for now it is just text.
The images below show a Hat of a Mother's Sorrow and the Legendary version does not have buttons on the right because there is no Mythic version. The Epic version has selectors on both the left and right to view the Superior or the Legendary version.
While the selectors do not seem to be dependant on the sales in your Master Merchant Data, there may be unknown factors that prevent the selector from showing. The code is extremely old and dates back to the introduction of the Champion Points system.
Hat of a Mother's Sorrow
Hat of a Mother's Sorrow
3.16.3 - Erroneous timestamp
When you see an erroneous timestamp, LibHistoire will handle this internally. It will not be processed until the timestamp is updated properly by the server.
LibHistoire will send the sale to MM after it checks that the erroneous timestamp is no longer present.
3.16.4 - What is being scanned
When LibHistoire is scanning the guild history it is obtaining the sales from all the guild history that you have loaded into memory.
3.16.4.1 - A few days of sales from 109 entries
LibHistoire simply scan entries from the guild history. With another mod installed called Shissu's Guild Tools a count of the amount of entries is showing. As shown there are 109 entries which only covers a few minutes of sales.
3.16.4.2 - 4 days of sales from 8031 entries
However, as shown in the above screen shot there are 8031 entries which covers 4 days of sales. If you feel you are missing sales from 7 days ago then you will need more sales showing on the guild history tab.
3.16.5 - Sales Week
As of August 11 2020 the kiosk flip is now every Tuesday. All sales totals are calculated from the time indicated by ZOS. Refer to the date ranges section for information on the timeframes.
You should not try to calculate your sales yourself. Each sale is saved with the exact time stamp the sale occurred. All sales even a few seconds prior to the kiosk flip would not show if you selected to see sales from This Week.
On the day of the kiosk flip sales for This Week will only reset after Zenimax transmits the new kiosk flip time. This can occur several hours after the kiosk flip.
3.17 - Slash commands
3.17.1 - 3.7.x Sorting Writs by voucher count
/lgs clean, which is /LGS CLEAN but use lowercase.
To reorganize Writs by voucher after upgrading to 3.7.02 you need to use the slash command shown above. After the process is complete you should reload your UI.
This only applies if you are upgrading from 3.7.01 or earlier.
3.17.2 - Export Sales Report
Master Merchant can export a general summary of sales for use with spreadsheets. Full disclosure I am not a spreadsheet guru so I can not help with this feature. To use the export feature choose a guild to work with, then select the time and range like This Week or Last Week. Then use /mm export # to export the guild's information. As an example the screen shot shows a 2 for the 2nd guild in your list, therefore the syntax would be /mm export 2.
Once exported the data is saved in MasterMerchant.lua in your SavedVariables folder.
Without Taxes:
["EXPORT"] =
{
["version"] = 1,
["YourGuildName"] =
{
[1] = "@GuildMember&Sales&Purchaces&Rank",
},
With Taxes:
["EXPORT"] =
{
["version"] = 1,
["YourGuildName"] =
{
[1] = "@GuildMember&Sales&Purchaces&Taxes&Rank",
},
Taxes is new as of 3.2.7 and you toggle the feature on in addon settings.
Since I have never used this feature with a spreadsheet I do not know how easy that is to use as Lua saves it. You may need to copy and paste it into another text file and use regular expressions to clean that up.
Some of my GMs have explained if this format changed it would break what they currently use so it will not be altered.
3.17.3 - Export Sales Activity
You would use /mm sales # to export the sales activity. As an example the screen shot shows a 2 for the 2nd guild in your list, therefore the syntax would be /mm sales 2.
Once exported the data is saved in MasterMerchant.lua in your SavedVariables folder.
["SALES"] =
{
["version"] = 1,
["YourGuildName"] =
{
[1] = "@Ashjunkie&@Lcs_Flores&|H0:item:46129:30:1:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0|h|h&200&1630085615&false&4000&Real Guild Best Guild&Quicksilver Ingot&rr01 white normal materials",
},
3.17.4 - Export Personal Sales
You would use /mm personal # to export your personal sales. As an example the screen shot shows a 2 for the 2nd guild in your list, therefore the syntax would be /mm personal 2.
Once exported the data is saved in MasterMerchant.lua in your SavedVariables folder.
["PERSONALSALES"] =
{
["version"] = 1,
["GuildName"] =
{
[1] = "Seller&Buyer&Guild&Quantity&ItemDesc&Price&Timestamp"
},
3.17.5 - Export Purchases
You would use /mm purchases to export your purchases from traders. Only the time dropdown affects the export for purchases.
Once exported the data is saved in MasterMerchant.lua in your SavedVariables folder.
["PURCHASES"] =
{
["version"] = 1,
["data"] =
{
[1] = "Seller&Buyer&Guild&Quantity&ItemDesc&Price&Timestamp"
},
3.18 - Technical Information
3.18.1 - Backup LibGuildStore Data
To backup your LibGuildStore data you will need to navigate to the SavedVariables folder. Usually C:\Users\Your User Name\Documents\Elder Scrolls Online\live. The files can be easily found going to MyDocuments in windows first.
I am sorry I don't know where it is located on a Mac.
Once you are in the SavedVariables folders, you will need to copy the 18 GSxxData files named GS00Data.lua to GS17Data.lua as shown in the screen shot. Copy these to a separate folder outside of SavedVariables and do not place them in a subfolder under SavedVariables. You will also want to keep a copy of LibGuildStore.lua, LibHistoire.lua, and MasterMerchant.lua.
3.18.2 - Locating LibExecutionQueue
LibExecutionQueue is included with Master Merchant as shown in the zip below.
LibExecutionQueue is sorted alphabetically by the base game.
If you have LibVotansAddonList installed then it will look close to the base game.
3.18.3 - Unintentional ZOS Bug
Unfortunately from time to time ZOS introduces or reintroduces a bug in the saved vars where the apostrophe is converted to HTML code. Which will mean your sales may or may not display properly. Which is a game bug and you are out of luck until or unless they fix it.
Since this can occur I highly recommend changing your user name to only contain letters as it will make it easier for you in the long run.
This also includes creative names that contain things like Æ or æ. As those are not individual letters.
3.19 - Version History
Apparently for version 2.2.0 there was an experimental turbo mode added to MM. From the change log it appears that this was removed by request from Zenimax. However, even I noticed when you tried to download 2.2.1 which had turbo mode removed, you received a file named Master Merchant 2.2.0.zip. If you tried to engage turbo mode it was still available even if it didn't work as expected.
Aug 01 2020 after the kiosk flip was announced Philgo68 posted that he would be uploading a new version, which would be 2.3.1. From the start it had a small bug in it that prevented it from working. Then after that was fixed people started reporting that the Master Merchant window would not update when you were viewing your personal sales but that all guild sales was still updating properly.
Upon examination of the code 2.3.1 had turbo mode removed which was not really removed in 2.2.1 (2.2.0). In addition to that on the description page it was mentioned that there was Simple Indexing and Simple Scanning. Oddly those options included new options in the Addons menu to toggle the features on and off. These options were not present in 2.2.1.
This makes me believe that 2.3.1 was really intended to be the proposed 2.2.1 but somehow the upload never went through properly. I am glad Philgo68 uploaded the version as it has helped me understand the code a bit more.
3.20 - Depreciated
3.20.1 - Background Scanning
As of version 3.0.0 there is no /mm missing and no background scan. The background scan would get hung up by repeated attempts to request more sales data from the server. When the server denied the request MM would continue to wait for the request to be approved.
After starting a new library LibGuildHistoryCache I observed that the cache mod would see some new sales. Usually there were only a few sales maybe 1 or 2 and occasionally less then 10. The cache mod would update showing that the guild history events were not duplicates but MM would not see them as new sales.
One other calculation previous versions of MM made was to try and get the first entry in the guild history and the last. This was used to attempt to determine whether or not to scan from the start of the guild history array, or the end. Whether or not you have 1, 100, or more then 1000 events the first event will always be the same. All guild history events are appended onto the end of the list.
For reasons like these MM no longer uses a background scan as it attempted to scan from a specific point in time and loop over the guild history events.
3.20.2 - Backup Master Merchant 2.x Data
This backup procedure is exclusively intended for version 2.x or for maintaining a historical backup for importing into 3.x.
To backup your Master Merchant data you will need to navigate to the SavedVariables folder. Usually C:\Users\Your User Name\Documents\Elder Scrolls Online\live. The files can be easily found going to MyDocuments in windows first.
I am sorry I don't know where it is located on a Mac.
Once you are in the SavedVariables folders, you will need to copy the 17 MMxxData files named MM00Data.lua to MM16Data.lua as shown in the screen shot. Copy these to a separate folder outside of SavedVariables and do not place them in a subfolder under SavedVariables.
3.20.3 - Uninstall Master Merchant 2.x
For historical reference, as of August 2020, it was expected that users would have already updated to version 3.x, rendering this procedure unnecessary.
Currently there is some confusion about how to uninstall Master merchant 2.x and install 3.x. First you need to open minion. If you see both versions installed as shown below, uninstall both. The reason you uninstall both is because MM 3.x is a continuation of 2.x. It is the same mod with the same file names and the same folder names. Minion will not understand how to handle this.
If you manually install your mods, of if you want to know which folders belong to Master merchant, click the spoiler.
When using Minion to uninstall Master Merchant right click and choose Uninstall.
Do not check that box or it will remove your MM data files! Only click Delete!
As you see above, both versions of Master merchant are now uninstalled.
You have to close Minion because it will be confused about uninstalling both versions.
Open Minion again and click Find More and search for Master Merchant 3.0 as shown above. Make sure the author's name is Sharlikran. Then click the Install button.
As noted on the description page you need to install LibAddonMenu, LibMediaProvider, LibGuildRoster, and LibHistoire.
I won't be showing how to install all the required libraries. If you need examples images of the two new libraries LibGuildRoster, and LibHistoire click the spoiler.
After you install Master Merchant 3.0 verify it is the only Master Merchant showing in Minion.
3.20.4 - Alternate Upgrade Method
Due to Update 41 and LibHistoire 2.x, this procedure is no longer possible.
Thanks to Shadowshire for sharing this workaround. While I did alter most of the steps I wanted to preserve his suggestion because it could provide a good alternative to importing LibHistoire data for those experiencing issues.
This alternate method will primarily use data from the old Master Merchant Data files located in SavedVariables as shown in the depreciated section, Backup Master Merchant Data.
It is recommended that only Master Merchant 3.7.x, ShoppingList (older standalone version), the original MMxxData modules, LibGuildStore, all GSxxData modules, and the required library files for Master Merchant are enabled to avoid potential interference while this procedure is performed.
It is recommended to store any backup copies of Master Merchant data outside of SavedVariables in its own folder. For example .\Documents\Elder Scrolls Online\live\Backups\MM_Backup_01
3.20.5 - Optional Mods For This Procedure
Circonians Addon Selector will allow you to save your current active mods before performing this procedure.
3.20.6 - Optional Debug Settings
The sticky post for Master Merchant 3.0 mentions some slash commands for LibDebugLogger. When these settings are changed this helps provide additional debug information in the event of any errors. Only use these slash commands as a precaution if you have been having issues upgrading.
/debuglogger stack on /debuglogger level debug
You should see a confirmation of each command in the chat window. For users with chat mods installed check your mods settings. System might be redirected to other tabs such as Zone chat.
3.20.7 - The Procedure
During this procedure Master Merchant will check for duplicate sales. Please remember it is recommended that you exit the game before you install any add-on or alter the SavedVariables folder.
Version 3.7.x will not alter the previous MMxxData files or any purchase data for the older standalone ShoppingList module. If you are concerned about loosing any data then please backup your MM file as shown under Backup Master Merchant Data. Purchase data for the standalone ShoppingList module is located in the same folder as the Master Merchant data files in SavedVariables under the name ShoppingList.lua.
Remove the data file LibHistoire.lua from the SavedVariables folder. If you did not make a backup it is recommended you move the file to another location where you can find it. Depending on the results of this procedure you may want to restore it even though the primary focus is to use the older MMxxData files.
Verify you have the most recent version of Master Merchant 3.0 installed.
Log in and from the character selection screen click the dropdown for All Characters. Choose a character from the dropdown. This will be the character you log into when performing the procedure. Reduce the amount of mods running by unchecking only what is required.
If you have Circonians Addon Selector installed you will be able to enable all your preferred mods after all your data is imported.
After you log in and the user interface is shown, you should see Chat messages displayed by LibGuildStore and by Master Merchant, followed by one or more of the message "LibGuildStore Refresh Not Finished Yet". Wait for until you see Master Merchant Initialized and the total Sales, Purchases, Listings, and Posted and Canceled items that are being retained.
Press ESC and go to Settings then LibGuildStore to verify that the Sales Management Options are configured to meet your personal preferences.
Further down under LibGuildStore settings is a button to Import MM Data click it and wait for the data to be imported.
Version 3.7.x was released on 09/03/21 you will not have any sales newer then Sep 3rd and because of that you will need to obtainin Guild History. When complete you will have all the MM data that existed up until 09/03/21 and then all the sales that exist on the server. Then you will begin to accumulate data the same as you did with 3.5.x.
At this point you can also Import ATT Data if that is available to you.
You will also want to Import Pricing Data and Import ShoppingList Data as well.
If you chose to use the debuglogger slash commands and you did not encounter any errors then it is recommended that you type into chat /debuglogger level info to avoid having unneeded debug messages from mods that use LibDebugLogger to output detailed debug messages. These detailed debug messages are not needed during normal operation.
At this point you will have to log out to the character screen and enable your preferred mods or use Circonians Addon Selector and restore the saved package of add-ons that you normally use.
If they are enabled, then disable the add-on ShoppingList, and each of the Master Merchant Data File MM00Data through Master Merchant Data File MM16Data files in the Libraries section to decrease load times
This will leave you with a gap in your sales from 09/03/21 until now. If that gap is too much for you then you can try to import your old LibHistoire information. To do that you will need to exit the game, backup your LibGuildStore data and your current LibHistoire data. Once you restore the copy of your old LibHistoire data that you moved to a safe place attempt to Refresh LibHistoire again. If you do not have better results then exit the game, restore your LibGuildStore and LibHistoire backups and you won't be able to use the old LibHistoire data.
3.21 - Authors
Philgo68, Khaibit, dOpiate, sirinsidiator, Garkin, Aldanga, Sharlikran, Dolgubon
3.22 - Translators
mychaelo, svenpanne, tomkolp, mlsevero, Baertram, jupiter126, Otxics, Jakez