EOA Quartermaster — Version 2.5.20

Raid Performance & Passive Client Tracking

Version 2.5.20 further reduces raid-time lag by making read-only clients passive and ensuring that only the officer who actually starts a raid performs automatic raid tracking.

Read-Only Client Behavior

• Read-only clients no longer request ledger synchronization automatically on login or /reload.
• Read-only clients no longer request guild or ledger refreshes during PLAYER_ENTERING_WORLD.
• Releasing to the graveyard, zoning, or other world transitions no longer trigger heavy roster/ledger processing.
• Read-only clients no longer scan the raid roster during active tracking.
• Read-only clients now operate primarily as passive replicas of officer-generated raid and DKP state.

Live Updates Still Received

Read-only users continue to receive live authoritative updates when officers create them, including:

• Raid start state.
• Attendance updates.
• DKP and loot transactions.
• Manual DKP adjustments.
• Raid completion/end state.

Manual synchronization remains available through:

• The Sync button.
• /dkp sync.

These requests use the lightweight delta synchronization path.

Full Sync Behavior

• Full authoritative database synchronization remains restricted to /dkp join.
• Normal Sync operations do not request or replay the complete ledger.

Single Active Raid Tracker

• Only the officer who actually starts a raid performs automatic raid-roster scans and attendance tracking.
• Other online DKP officers receive the resulting authoritative raid updates but do not independently rescan and rebroadcast the same 40-player roster.
• This prevents duplicate raid tracking work and duplicate addon-message traffic.

Example:

• Zerath starts the raid.
• Zerath becomes the automatic raid tracker.
• Fighto remains a passive synchronized officer client.
• Read-only clients remain passive synchronized clients.

Officer Takeover

• Any authorized DKP officer can still manually End Raid.
• If the original tracking officer disconnects or must leave, another officer can explicitly end the raid.
• Manual End Raid performs a final roster scan before finalizing the existing raid.

Stale Raid Auto-Finalization Fix

• Fixed an issue where an officer who disconnected during a raid could later log back in and automatically finalize a stale local copy after the scheduled raid end time.
• Automatic scheduled finalization is now scoped to the officer session that actually started the raid.
• Raid-tracker ownership is intentionally not persisted between WoW sessions.

If an officer reconnects later with a stale active raid:

• The addon does not manufacture a new raid-end event.
• The stale raid remains pending.
• It waits for an authoritative Raid End update from another officer or a manually requested Sync.

Disconnect Safety

• Disconnecting does not delete or reset the active raid record.
• Existing attendance, transactions, loot history, and raid state remain intact.
• If the original tracking officer reconnects and is present at the end of raid, they can manually press End Raid to finalize the same existing raid.

Authoritative Raid-End Reconciliation

• Manual delta Sync now correctly clears a stale local active-raid pointer when the authoritative donor reports that the raid has already ended.
• A stale officer client will adopt the authoritative completed raid state rather than locally generating its own substitute end state.

Reduced World-Entry Processing

• Removed unnecessary guild-roster requests and broad UI refreshes from routine world transitions.
• Graveyard releases and zone transitions no longer trigger heavyweight ledger or raid-state reconstruction.
• Guild/member state is refreshed through normal guild events, explicit Sync, and relevant UI interactions instead.

Existing Ledger Safety

Version 2.5.20 does not modify the persistent DKP database structure.

Database.lua remains byte-for-byte identical to version 2.5.19.

There is:

• No database migration.
• No transaction rewrite.
• No transaction-ID migration.
• No raid-history migration.
• No DKP balance rebuild.
• No approval migration.
• No main/alt mapping migration.
• No reset-generation change.

Existing EOAQuartermasterDB SavedVariables remain valid and are loaded directly.

Do not delete SavedVariables or run /dkp reset when upgrading.

Compatibility

Addon Version: 2.5.20 Synchronization Protocol: 20 / DKPLedger20 Database Schema: 14

The communication protocol was intentionally bumped so older clients using the previous stale raid auto-finalization behavior cannot synchronize with 2.5.20 clients.

All addon users who participate in synchronization should update to version 2.5.20.