Best Practices

• Execute mutations on authority through a validated project integration. Use queries and replicated snapshots for UI.
• Keep ItemIDs unique across all configured databases. Use unique identity tags within each Pawn/PlayerState lookup context.
• Set MaxStackSize to at least 1 and to 1 for nonstacking items. Use positive weights for weight-limited paths and validate asset values before shipping.
• Handle OutAddedAmount rather than treating success as a full-quantity guarantee. Preserve pickup and reward remainders.
• Use SlotID for runtime entry identity. Do not hold array indices or pointers across operations that add/remove entries.
• Keep shared Data Assets immutable during gameplay. Store durability, weapon build identity and other instance state in a separate project model.
• Implement consumption, equipment, permissions, trades and persistence explicitly; item tags do not implement those systems.
• Bind UI events and read an initial snapshot. Handle possession changes, failed soft loads and RPC rejection.
• Verify Implementation Limits before integrating transfers or calling low-level component interfaces.

Use Debug and Testing as a practical acceptance checklist for your configured inventory.

---