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 Features

•  3.1.1 For Players not in a Trading Guild:

•  3.1.2 For Trading Guilds:

•  3.1.3 For Trade Guild Members:

•  3.2 Guild History UI Overview

•  3.2.1 LibHistoire UI

•  3.2.2 Guild History UI

•  3.2.3 Data Is Available

•  3.2.4 Show More is available

•  3.3 LibHistoire UI

•  3.3.1 Reset Linked Range

•  3.3.2 Clear Cache

•  3.3.3 Request Mode

•  3.4 States of the LibHistoire cache

•  3.4.1 Unlinked

•  3.4.2 Linking in progress

•  3.4.3 Linking in progress, with 0 events left

•  3.4.4 Linked

•  3.5 Obtaining Guild History

•  3.6 Unlinked Events Notification

•  3.7 Setup Master Merchant 3.0

•  3.7.1 What is required

•  3.7.2 What to disable when MM is not needed

•  3.7.3 Importing older Master Merchant Data

•  3.7.3.1 MMxxData modules needed for importing

•  3.7.4 What to expect after you log in for the first time

•  3.8 Master Merchant Window

•  3.8.1 Guild Sales and Personal Sales

•  3.8.2 Item Report

•  3.8.2.1 What The Columns Mean

•  3.8.3 Seller's Report

•  3.8.3.1 Top Buyers and Sellers

•  3.8.3.2 Top Items

•  3.8.3.3 Personal Sales - Seller's Report

•  3.8.3.4 What The Columns Mean

•  3.8.4 Guild Sales Date Filter Ranges

•  3.8.5 Date Ranges

•  3.9 Statistics Window

•  3.10 Settings

•  3.10.1 Master Merchant

•  3.10.1.1 Master Merchant Window Options

•  3.10.1.2 Sales Format Options

•  3.10.1.3 Time Format Options

•  3.10.1.4 Alert Options

•  3.10.1.5 On-Screen and Chat Alert

•  3.10.1.6 Calculation Display Options

•  3.10.1.7 Timeframes

•  3.10.1.8 Guild & Account filter

•  3.10.1.9 Deal Calculator Options

•  3.10.1.10 Tooltips

•  3.10.1.11 Tooltip Options

•  3.10.1.12 Outlier Options

•  3.10.1.13 Price To Chat Options

•  3.10.1.14 Inventory Options

•  3.10.1.15 Guild Store Options

•  3.10.1.16 Guild Master Options

•  3.10.1.17 MM Debug Options

•  3.10.2 LibGuildStore

•  3.10.2.1 Sales Management Options

•  3.10.2.2 Data Management Options

•  3.10.2.3 LGS Debug Options

•  3.10.2.4 Import MM Data

•  3.10.2.5 Import ATT Data

•  3.10.2.6 Import ATT Purchases

•  3.10.2.7 Refresh LibHistoire

•  3.10.2.8 Import ShoppingList Data

•  3.10.2.9 Import Pricing Data

•  3.10.2.10 Reset Data

•  3.11 Shopping List

•  3.12 Bonanza!

•  3.12.1 Bonanza Name Filter

•  3.12.2 Bonanza Type Filter

•  3.12.3 Bonanza - Using BeamMeUp

•  3.13 Outliers

•  3.13.1 Controlling skewed prices

•  3.14 MM Price vs TTC vs Bonanza

•  3.14.1 Evaluating the Bonanza price

•  3.14.2 Price Sold vs. Price Listed

•  3.14.3 Comparisons between Bonanza, TTC, and MM

•  3.15 Misc

•  3.15.1 Popup Item Data

•  3.15.2 Level Quality Selectors

•  3.15.3 Erroneous timestamp

•  3.15.4 What is being scanned

•  3.15.4.1 A few days of sales from 109 entries

•  3.15.4.2 4 days of sales from 8031 entries

•  3.15.5 Sales Week

•  3.16 Slash commands

•  3.16.1 3.7.x Sorting Writs by voucher count

•  3.16.2 Export Sales Report

•  3.16.3 Export Sales Activity

•  3.16.4 Export Personal Sales

•  3.16.5 Export Purchases

•  3.17 Troubleshooting

•  3.17.1 Duplicate Indexes Detected

•  3.17.2 LibGuildStore.lua:316: attempt to index a nil value

•  3.17.3 Lua errors

•  3.17.4 OneDrive

•  3.18 Technical Information

•  3.18.1 Backup LibGuildStore Data

•  3.18.2 Locating LibExecutionQueue

•  3.18.3 Unintentional ZOS Bug

•  3.19 Version History

•  3.20 Deprecated

•  3.20.1 Legacy Data Behavior from Update 41

•  3.20.1.1 Impact on Users During Update 41

•  3.20.1.2 Bricked Guild Trader / Stuck History Segments

•  3.20.2 Background Scanning

•  3.20.3 Backup Master Merchant 2.x Data

•  3.20.4 Uninstall Master Merchant 2.x

•  3.20.5 Alternate Upgrade Method

•  3.20.6 Optional Mods For This Procedure

•  3.20.7 Optional Debug Settings

•  3.20.8 The Procedure

•  3.21 Authors

•  3.22 Translators

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 - Guild History UI Overview

3.2.1 - 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.2 - Guild History 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.3 - 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.4 - 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.3 - 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.3.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.3.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.3.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.4 - States of the LibHistoire cache

3.4.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.4.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.4.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.4.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.5 - 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.6 - 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.7 - 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.7.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

•  LibItemLink

•  LibRecipe

3.7.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.8.x

•  LibExecutionQueue

•  LibGuildStore

•  LibGuildStore Data File GS00Data, LibGuildStore Data File GS01Data, etc.

3.7.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.7.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.7.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.8 - 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.8.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.8.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.8.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.8.3 - Seller's Report

3.8.3.1 - Top Buyers and Sellers

3.8.3.2 - Top Items

3.8.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.8.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.8.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.8.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.9 - Statistics Window

3.10 - Settings

3.10.1 - Master Merchant

3.10.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.10.1.2 - Sales Format Options

Master Merchant provides several ways to view and calculate pricing data based on your current sales history. These options determine how item averages, deal values, sales totals, and other pricing details are processed using the id53 sales data provided by the game's Guild History system.

Use the Sales Format Options menu to choose how pricing is calculated. Each option controls how Master Merchant evaluates your local sales history when determining averages, trends, and suggested prices.

This option applies to current id53 sales data. If you imported old Master Merchant archives from before Update 41, see Legacy Data Behavior from Update 41.

3.10.1.3 - Time Format Options

3.10.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.10.1.5 - On-Screen and Chat Alert

3.10.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.10.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.10.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.10.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.10.1.10 - Tooltips

3.10.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.10.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.10.1.13 - Price To Chat Options

3.10.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.10.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.10.1.16 - Guild Master Options

3.10.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.10.2 - LibGuildStore

3.10.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.10.2.2 - Data Management Options

3.10.2.3 - LGS Debug Options

3.10.2.4 - Import MM Data

3.10.2.5 - Import ATT Data

3.10.2.6 - Import ATT Purchases

3.10.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.10.2.8 - Import ShoppingList Data

3.10.2.9 - Import Pricing Data

3.10.2.10 - Reset Data

3.11 - 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.12 - 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.12.1 - Bonanza Name Filter

3.12.2 - Bonanza Type Filter

3.12.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.13 - 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.13.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.14 - MM Price vs TTC vs Bonanza

These examples demonstrate how MM, TTC, and Bonanza each calculate prices differently. Since Bonanza is newer, the examples help show how to interpret its values. I recommend looking through all of them before making pricing decisions.

•  The MM price is shown in yellow text. It is based on actual sales recorded in your guild history. It does not use any TTC information.

•  The TTC price comes from their client application. They remove outliers using their own method and calculate an average based on the remaining listings.

•  The Bonanza price is shown in blue text. It is based on the listings you personally saw while checking traders. It reflects what you have encountered yourself, not data from other players.

In the first example with the Hlaalu Bookcase, the Bonanza prices you saw were all in a reasonable range. If most traders offered it around 17K to 19K, that price range is far more reliable than a single inflated listing at 100K.

The second and third examples show how TTC values can differ from what you actually found. When a TTC average includes a wide range of prices, the Bonanza window becomes useful because it shows the listings you personally verified at traders.

Bonanza prices may appear to match TTC at times, but they will vary depending on how many traders you visit and how often the item is listed. Some items appear frequently and require only a few trader visits. Others are uncommon and may need more sampling to get an accurate picture.

You do not need thousands of MM sales to understand a price. Even a few hundred data points for a common item, such as Blessed Thistle, are enough for MM to calculate a stable average.

The same idea applies to the statistical mean. Repeating the same value many times will still lead to the same average. This is known as the Law of Large Numbers, and it explains why a consistent price will stay consistent even when the sample size is moderate.

Pricing does not have to be complicated. Visiting a few traders across different cities is usually enough to identify the normal price range for an item. What matters is demand and how frequently the item appears.

Bonanza has an additional advantage: it shows the listings you actually saw. This helps you choose realistic prices and stay competitive with other guilds without relying on external websites.

While all this information may seem like a lot at first, each tool provides valuable insight. MM, TTC, and Bonanza together give you a complete understanding of the market without needing to leave the game.

3.14.1 - Evaluating the Bonanza price

If these images appear too small, right click and open them in a new tab to view them at full size.

In the first screenshot, the TTC range shows 74K to 93K, while the Bonanza average reflects what you actually saw while visiting traders. When the TTC range is wide or influenced by extreme listings, Bonanza helps verify what you found during your searches.

To evaluate Bonanza correctly, search for the item in the game. For example, you can look up style zero cuirass in the Bonanza window. This allows you to confirm the prices you have personally seen and compare them to the TTC values.

In the middle image, the listings range from 50K to 125K. By checking several traders, you can quickly see that most listings fall around the middle of that range. It does not require two monitors or outside tools, and it only takes a few minutes to gather reliable results.

From these listings, it is clear that 70K is a realistic average. If you list your item at 70K, you are matching the prices found at the majority of traders you visited. Even if an occasional outlier exists, you are still pricing close to the true market value.

If the Bonanza price appears higher than your estimate, such as showing 158K instead of 70K, this does not mean it is incorrect. It simply means your sample of traders included higher listings. Always compare the range of prices you saw and make a judgment based on the most common values.

3.14.2 - Price Sold vs. Price Listed

The examples above highlight items with unusually large price ranges. These cases help explain the difference between what an item sells for and what players choose to list it for. Anyone can list an item at any price, but that does not mean the item will actually sell at that amount.

The Bonanza and TTC prices are both useful, but they are not the same. Bonanza shows the prices you personally saw at traders, while TTC gives an average after removing outliers. Neither of these values tells you the final sale price unless you combine them with your own observations.

When evaluating an item, think about the intent behind the listings you see. Some players price items very high in the hope that someone will overpay. Others list too low because they want a quick sale. The goal is to find the realistic range where sales actually occur, not the extreme values.

Bonanza helps with this because it lets you compare multiple listings quickly. If most prices fall within a narrow range, that is usually the true value of the item. The extremes on either end are rarely reliable indicators of what the item will sell for.

Keep this in mind when deciding how to price your own items. A high listing does not guarantee a high sale, and a low listing does not mean the market value is low. Use the patterns you see across several traders to determine a fair and accurate price.

3.14.3 - Comparisons between Bonanza, TTC, and MM

Some players will list an item for an extremely high or unrealistic price. These listings do not reflect the true value of the item and can distort the TTC averages. Ideally the TTC developers would filter out these extreme cases more aggressively, but since they appear in the raw data, items with no consistent history or items that people believe should sell for millions are naturally harder to evaluate.

This section does not focus on those unusable listings. Instead, it looks at situations where TTC, MM, and Bonanza all provide helpful and consistent information.

Below are two examples of the Bonanza price:

In this example, the Bonanza value is within about 1K of both TTC and the MM average. This shows how closely all three systems can align for commonly traded materials.

Here, the Bonanza value is only 1 gold away from the TTC average. Even though TTC has thousands of data points for this material, the value is still consistent with what Bonanza shows from the traders you actually visited.

A common misconception is that you need years and years of sales data stored in Master Merchant in order to get accurate results. That is not true. In the Dreugh Wax example, TTC shows more than 15,000 data points, and in the Blessed Thistle example, TTC shows around 2,800. Yet MM is able to show the same price for Blessed Thistle using only a few hundred sale records.

You could demonstrate this with a simple Lua script by adding sets of numbers that average around 100. Even if you mix different values, such as 100, 99, 90, 95, and similar numbers, the average will remain close to the same. No matter how many times you add 100 + 100 + 100, the result does not change.

In statistics this is related to the Mode, the value that appears most often. For commonly sold materials like Chromium Grains, Dreugh Wax, Clam Gall, Blessed Thistle, and others, the data is consistent enough that thousands of points are not required to determine the true average.

Pricing should not be difficult. If you visit three or four cities and check the main traders for key items, you will usually gather enough information to see the normal price range. TTC and Bonanza should agree in most cases, depending on how people choose their listing prices. Some players use the TTC Suggested value, others use the Average value, and it depends on demand and current availability.

Another advantage of Bonanza is that it allows you to view actual listings. As shown earlier in the section Evaluating the Bonanza price, you can always verify prices right in the interface. If you see that most traders list a style page for 50K, then 50K is the real going rate. You can then list your item competitively without guessing.

Overall this may seem like a lot of information, but the point is that you do not need extra monitors, external websites, spreadsheets, google docs, or exporting MM data. The Master Merchant interface itself provides everything you need. Using the information on the tooltip makes it fast and easy to compare MM, TTC, and Bonanza prices without leaving the game.

3.15 - Misc

3.15.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.15.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.15.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.15.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.15.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.15.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.15.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.16 - Slash commands

3.16.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.16.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.16.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.16.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.16.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.17 - Troubleshooting

3.17.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.17.2 - LibGuildStore.lua:316: 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.17.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:455: operator .. is not supported for string .. nil
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.17.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.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 - Deprecated

3.20.1 - Legacy Data Behavior from Update 41

During Update 41 (March 2024), Zenimax reset the Guild History server database and switched from id64 to id53 sales identifiers. Because of this reset, Master Merchant could not deduplicate sales across the boundary between pre-U41 id64 data and the new id53 format.

If you still have archived Master Merchant data from before Update 41 (March 2024), be aware that mixed id64/id53 records cannot be deduplicated. This does not affect users who started fresh after Update 41.

3.20.1.1 - Impact on Users During Update 41

During the transition to Update 41, most users experienced little to no disruption because their binary cache already contained recent sales data. Players who typically retained only 30 to 90 days of history saw minimal data loss, and Guild Masters were still able to evaluate recent weekly activity without issue.

However, users with extensive archival data, years of sales or "library of congress"-style collections, experienced inaccurate averages when mixed id64 and id53 records overlapped. Because the identifier formats could not be matched across the Update 41 boundary, Master Merchant was unable to reliably deduplicate these overlapping records.

This behavior is now legacy and only applies to users who retained significant pre-U41 archived data.

3.20.1.2 - Bricked Guild Trader / Stuck History Segments

During Update 41 there was also a bug in the base game where the Guild History could become "bricked" when the server pushed new events that could not be merged with the user's already-cached data. This occurred when the cache contained two segments that were supposed to join, but the server reported them as touching with no events in between. When this happened:

•  The history bar showed a blue/green segment nearly touching a red segment.

•  "Show More" stopped appearing on the last page.

•  The player could not advance the trader history.

•  Reloading the UI did not resolve it.

Because this bug came from the base game and not addons, it may still occur if the server pushes guild history segments that cannot be merged with your local cache. If this happens, you can use the Clear Cache option in the LibHistoire UI to rebuild your local history data. This will clear the affected cache entries and automatically reload the UI.

3.20.2 - 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.3 - 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.4 - 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.

 

Master Merchant Folders

 

 

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.

 

New Libraries

 

 

 

After you install Master Merchant 3.0 verify it is the only Master Merchant showing in Minion.

3.20.5 - Alternate Upgrade Method

Due to Update 41 and LibHistoire 2.x, this procedure is no longer possible.

/debuglogger stack on
/debuglogger level debug

3.21 - Authors

Philgo68, Khaibit, dOpiate, sirinsidiator, Garkin, Aldanga, Sharlikran, Dolgubon

3.22 - Translators

mychaelo, svenpanne, tomkolp, mlsevero, Baertram, jupiter126, Otxics, Jakez