Transaction Ledger & Anti-Dupe

Transaction Ledger & Anti-Dupe

Applies to: Nord Inventory v2.0.0

Ledger

The Operations Ledger searches nord_inventory_transactions. Filters can target transaction ID, identifier, item, inventory, UID, weapon serial and container UID. Identity fields are preserved in transaction payloads to make investigations possible without mutating item state.

Config.Operations.MaxLedgerRows bounds the result size.

Clear records

Admins with the forensics permission can clear the transaction ledger through the Operations toolbar. The action:

• requires confirmation in NUI;
• deletes transaction rows only;
• does not reset the table primary key;
• does not touch live/persisted inventories;
• writes an entry to the separate Admin Studio audit log containing the deleted-row count.

New movements continue to be recorded immediately after cleanup.

Anti-Dupe Center

The scan is diagnostic and never deletes items automatically. It checks these identities independently:

• unique item UID;
• weapon serial;
• container UID.

A supposedly unique identity appearing in a stack with count > 1 is also suspicious. The scanner overlays live cached inventories over persisted storage so the same online player is not counted twice from stale SQL + live runtime state.

Alerts are persisted in nord_inventory_forensics_alerts until resolved. Resolving an alert changes its status; it does not modify the underlying item automatically.

Safe use

Run scans on demand rather than polling them continuously. Review the matching inventories and item identity before deciding whether an alert represents a real duplication, a legacy malformed item or a legitimate historic record.