Criminal items are useful only when the current activity recognizes them. A tool’s presence in a dealer or smuggler interface does not prove that it opens every bank, container, safe, register, or vending target. Identify the robbery first, then verify the exact live requirement and net risk.
Source and item index
Find a legitimate source
Use normal in-game contacts and interfaces. The dealer and smuggler can have server-variable positions. Confirm the NPC identity and current shop title before buying.
Do not download an item generator, install an extension, run a script, or give another player account credentials. Those are security risks, not item sources.
Match an item to a robbery
Fixed building
Bank or jeweler
Check the current building prompt and full objective before buying an access item.
Search target
Container or safe
Confirm a valid available target first so tool cost is not followed by an endless search.
Small target
Register or vending machine
Verify that the specific object supports a live robbery and the item is actually requested.
Open the matching page under Robberies for preparation, interaction, and result checks. Do not apply one target’s tool or timing to another.
Calculate net value
Record the balance before buying, the item price, search time, success or failure, actual reward, wanted state, and police outcome. A successful reward greater than the tool price does not guarantee a good loop after failed attempts or arrest.
Unknown fields stay unknown
Leave durability, use count, exact timing, probability, and hidden effects blank unless the current game exposes or a reproducible source supports them. Label the check date and server context for stock and price.
The maintained Items reference and robbery pages help establish categories. The live contact, inventory, and target prompt determine current availability and behavior.
Item-to-target worksheet
Before purchase, write the chosen robbery, current target location, contact, exact item name, displayed cost, and evidence that the live prompt accepts it. After use, add the interaction result, whether the item remained, the reward category, wanted state, and police outcome. This prevents one tool from being described as universal because it worked once.
If the target is unavailable, do not test the item on unrelated scenery. Preserve the item according to ordinary game rules or choose an activity that explicitly supports it.
Dynamic contact and stock checks
Dealer and smuggler positions can vary by server, and their visible stock can change separately. Record location and stock as two observations. If a contact moves, the item may still exist; if an item disappears from stock, the contact can still be valid. Rejoin once before reporting removal.
Net-risk review
Include the search for the contact, item cost, target search, failed attempts, cooldown, arrest, and lost time. Do not compare only the successful loot with the purchase price. A legal job can provide a steadier route even when a single robbery result is larger.
Update maintenance
After a release, recheck the live contact interface and one intended target prompt. Update source, name, cost, compatibility, and observed effect independently. Leave exact use count, hidden success chance, activation time, and other unexposed fields unknown. This creates a durable item guide without converting a dated observation into a permanent mechanic.
When the target rejects an item, preserve the exact message and stop. That negative result is more useful than retrying until server state becomes ambiguous.
Keep the observation date with that message.