File Details
MarketSync Beta v0.4.2
- B
- Feb 20, 2026
- 44.58 KB
- 14
- 2.5.5
- Classic TBC
File Name
MarketSync.0.4.2-beta.zip
Supported Versions
- 2.5.5
[0.4.2] - 2026-02-19
Fixed
- Fixed: Decoupled the MarketSync
Personal Scancache from the Live Swarm database. When you visit the Auction House, the addon now takes a rigid snapshot of your data and clones it into an isolatedPersonalDatamemory pool. - Fixed: Personal scans and Guild Sync data are now strictly and physically separated in the Browse tabs.
- The
Personal Scantab physically reconstructs its search index from your isolated snapshot pool. Incoming Guild Syncs can aggressively overwrite Live prices without ever touching or shrinking your Personal UI tab data. - The
Guild Synctab strictly builds its index by filtering the most up-to-date live Swarm metadata.
- The
- Improved: First-launch protection. If you install MarketSync
0.4.2and have an existing Auctionator database but no offline snapshot, the addon will automatically clone your existing live data within 5 seconds of logging in so your UI does not appear blank. - Improved:
Personal Scantab now displays a clean, user-friendly prompt requesting the player to visit the Auction House if their offline cache is 100% empty, instead of simply saying "No results found." - Improved: Leaderboard UI has been redesigned. Filter buttons have been moved into the frame layout (instead of crowding the title bar window controls), added column titles, and implemented subtle row highlights.
- Improved: The Version Guard system now continuously tracks legacy clients that attempt to sync with the swarm. Your client will correctly ignore their outdated data payloads, but will now explicitly list the user as "Legacy (vX.X.X)" in your real-time Swarm Queue so you can politely inform guildmates they need to update.
- Fixed: A data parsing crash where Swarm Syncs would randomly halt perfectly in the middle of a chunk transmission. This occurred when the core engine encountered a rare corrupt Auctionator item entry containing a history array
hbut completely lacking a local market pricem. - Improved: Implemented deep Swarm Trace Logging. If the Swarm Coordinator experiences a catastrophic coroutine failure while transmitting data, the exact
dbKeycausing the database loop to crash will now be visibly pushed to the Network Monitor event log so users and developers can easily track corrupted edge-case table data. Furthermore, the broadcaster will send a network-wideERRpulse instantly notifying the receiving player exactly why their sync stream halted mid-transfer. - Improved: Swarm throttle has been safely balanced from 20 transfers per second (300 items/s) down to 10 transfers per second (150 items/s) to ensure massive legacy databases do not quietly exceed the World of Warcraft server's hardcoded bandwidth data limits, which was resulting in silent message drops.
- Added: A "Reset Data" button has been added to the Settings tab. This securely wipes all MarketSync tables and immediately processes a fresh Personal Scan snapshot, entirely without deleting or tampering with your legacy Auctionator system data.
- Added: A "Rebuild Caches" button has been added to the Settings tab. This lets you manually trigger a re-index of the Personal and Guild databases so you can see the cache processing status update in real-time.
- Improved: The Network Monitor window has been expanded into a full Debug Console. It now contains three panels: the Sync Network event log, the Swarm Queue tracker, and a new Cache Processing Stream that emits live timestamped entries as the index builder reads, resolves, and commits Personal and Guild data — so you can see exactly what the cache engine is doing at any given moment.
- Improved: Item history attribution has been upgraded from a single flat "last writer wins" source stamp to a per-scan-day attribution model. Each day in an item's history now independently credits the player who actually contributed that specific day's price data, so the History popup correctly displays the original contributor per day rather than crediting the most recent sync partner for every row. Old save data gracefully falls back to legacy attribution.