Quick answer: Persist current stock and gate restock on an elapsed game-time interval, so opening the menu shows the remaining inventory rather than a fresh refill.

If a vendor's rare item comes back every time you reopen the shop, stock is being rebuilt on open. Persist it and restock on a timer. Here is how.

How to fix it

1. Persist remaining stock

Store the shop's current quantities in saved or world state and load them on open, so buying an item reduces stock that stays reduced across visits.

2. Restock on a time interval

Track the last restock time and only refill when enough game time has passed, rather than refilling in the open handler that runs on every visit.

3. Separate init from open

Initialize a shop's base stock once when it is first created, and keep the open routine purely for displaying current state, never for resetting it.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Unreal Engine error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.