EOA Quartermaster — Version 2.5.19

Raid Performance & Synchronization Overhaul

Version 2.5.19 focuses on reducing addon-related latency during active 40-player raids while preserving the existing live DKP ledger without any database migration or rebuild.

Removed Automatic Background Ledger Sync

• Removed the automatic synchronization request that previously ran shortly after login or /reload.

• Established clients no longer perform full or delta ledger synchronization automatically in the background.

• Ledger synchronization now occurs only when a user explicitly:

  • Clicks Sync in the main addon window.
  • Clicks Sync Now in Settings.
  • Runs /dkp sync.
  • Runs /dkp join <Officer-Realm> for initial/bootstrap synchronization.

This prevents unexpected synchronization traffic from occurring during active raids.

Full Sync Restricted to /dkp join

• Full authoritative database synchronization is now reserved exclusively for /dkp join.
• /dkp join <TrustedOfficer-Realm> continues to use the compressed full-sync/bootstrap system introduced in previous releases.
• Normal Sync operations never request the complete transaction ledger.
• Manual /dkp sync and the Sync buttons now always use incremental/delta reconciliation.

This ensures established clients do not accidentally trigger large historical database transfers.

Read-Only Client Sync Improvements

• Read-only addon users now use the same lightweight transaction-delta system when manually requesting synchronization.
• Read-only clients can receive missing transactions and updated synchronized state from trusted officers.
• Read-only clients cannot send their own ledger state upstream or act as authoritative donors.
• Read-only-to-read-only synchronization remains disabled.

Active Raid Performance Improvements

Read-Only Raid Clients

• Read-only clients no longer independently scan the entire WoW raid roster while DKP raid tracking is active.
• Attendance authority remains with trusted/write-enabled officer clients.
• Read-only clients receive the resulting synchronized attendance updates instead of repeatedly recalculating attendance locally.

This removes a significant amount of unnecessary processing from ordinary raid members running the addon.

Officer Raid Tracking

• GROUP_ROSTER_UPDATE events are now coalesced/debounced.
• Multiple roster-change events occurring in a short burst result in one authoritative raid-roster scan instead of repeatedly scanning the full 40-player raid.
• Attendance detection and main/alt resolution continue to operate normally.

This is particularly useful when:

• Players join or leave.
• Groups are reorganized.
• Players disconnect/reconnect.
• Raid assistants move multiple characters between groups.

Attendance Processing Optimization

• Incoming attendance synchronization records are now processed in batches.
• Main/alt attendance reconciliation is deferred and coalesced rather than running after every individual attendance record.
• Receiving a complete raid roster no longer causes dozens of repeated reconciliation passes.
• Attendance state remains synchronized and authoritative after the batched processing completes.

UI Refresh Optimization

• Incoming synchronized records no longer force unnecessary redraws of addon pages that are not currently visible.
• Transaction and attendance refresh events are coalesced where possible.
• The addon now refreshes only relevant visible interfaces instead of repeatedly rebuilding hidden pages during synchronization activity.

Selective Raid History Synchronization

• Added digest comparison for historical raid data.
• Normal Sync can identify which raid records actually differ between clients.
• Only mismatched raid history and attendance data needs to be transferred.
• A single missing or outdated raid no longer causes every historical raid and every attendance record to be replayed.

This extends the incremental synchronization model beyond transactions to raid history.

Transaction Synchronization

The optimized transaction reconciliation introduced in 2.5.15 remains in place:

• Transaction ledgers use deterministic bucket comparison.
• Matching buckets are skipped.
• Only missing or conflicting transactions are transferred.
• Legitimate transactions created independently by different trusted officers are merged.
• Same-ID transaction corruption continues to be repaired using the selected donor's authoritative record.

Live Raid Updates Remain Enabled

Small live synchronization events are intentionally still supported.

Examples include:

• New loot transactions.
• Attendance updates.
• Manual DKP adjustments.
• Other individual synchronized mutations created by trusted officers.

These are individual delta updates and do not trigger a database synchronization or historical ledger replay.

This allows online addon clients to remain reasonably current during the raid without performing expensive background synchronization sweeps.

Existing Ledger Safety

Version 2.5.19 does not change the persistent DKP database format.

The Database.lua persistence layer is unchanged from 2.5.18.

There is:

• No database migration.
• No ledger reset.
• No transaction rewrite.
• No transaction-ID migration.
• No raid-ID migration.
• No DKP balance migration.
• No approval-record migration.
• No player/main-alt mapping migration.
• No reset-generation migration.

Existing EOAQuartermasterDB SavedVariables are loaded directly without rebuilding the ledger.

Upgrade Procedure

Upgrade the addon files normally.

Do not delete SavedVariables. Do not run /dkp reset.

The existing live ledger should remain intact.

Compatibility

Addon Version: 2.5.19 Synchronization Protocol: 19 / DKPLedger19 Database Schema: 14

Because synchronization behavior changed, 2.5.19 intentionally uses a new communication protocol.

All addon users who need to synchronize with each other should upgrade to 2.5.19, particularly read-only raid members who previously experienced latency during active raid tracking.

The database schema remains unchanged from 2.5.18.