Skip to content
DP-ADDONReviewed · 2026-11-19Desktop 1.8 · Companion 1.1.1Lire en français

Companion architecture ​

Modules and lifecycle ​

Core.lua initializes the character, orchestrates events and defers updates blocked by combat. Adapter.lua reads TSM and inventory. Engine.lua decides on owned items. Journal.lua observes auctions; Session.lua tracks tasks. Transfer.lua validates imports and prepares TSM groups. Presentation and translations are separate from rules.

At login, the Companion loads saved TSM history. Some reads depend on internal SavedVariables structures as well as public TSM APIs: this requires compatibility tests whenever TSM changes. After mail collection, changed inventory may require a reload to reconcile history. The desktop cannot force SavedVariables to be written.

Owned-item decisions ​

Protection order matters: bound/quest or manually kept; paused; unknown item; zero stock; uncertain history; repeated expirations; reload required; variant evidence; valid price and fee; vendor comparison; quantity and minimum benefit. Benefit here is net surplus over vendor value, not crafting margin.

Desktop-imported prices have a two-hour limit. TSM API prices do not always expose a usable timestamp: a cached state does not guarantee that freshness. The Companion recipe view has simpler independent filters; the desktop plan adds observed demand, a budget, reserve and detailed restocking constraints.

Native journal ​

The journal is scoped by character, realm, faction and region. It retains up to 2,000 auctions per character, for 90 days since last observation; pending creations expire after one day. Explicit outcomes are retained. Absence from a complete list becomes unknown, never automatically sold.

The desktop reader checks journal version, profile and exact identities. It bounds merging to 10,000 observations and keeps last-good data when a save regresses. Its region reader currently recognizes EU, US, KR and TW; the export format also accepts CN, which does not establish full CN validation.

Validation boundary ​

Lua replays verify events, combat, imports, isolation and idempotence without a WoW client. Event signatures, auction reconciliation and real TSM imports still need confirmation in the exact game version. Follow the in-game smoke procedure before qualifying a stable release.

A local-first advisor. Estimates stay visible.