The smuggler is another contact whose useful position can vary by server. Treat every location claim as a dated observation. Your goal is to identify the current NPC through its supported interaction, not to stand on an old coordinate and assume the game is broken.
Prepare the search
Collect current clues from the game or maintained reference, identify accessible candidate zones, and plan a loop. Note the server and check date. Use a vehicle that can turn and park in confined areas without drawing avoidable attention.
Do not buy a supposed location from another player or enter account details on an external tracker. A valid guide can explain a search method without requesting private credentials.
Search and verify
If the contact is not present after the planned loop, stop and change server once or try later. Do not turn absence into a guessed position.
Evaluate items before buying
Purpose
Match the live activity
Confirm that a current robbery or roleplay system actually uses the item.
Cost
Use the displayed price
Record today's interface rather than copying an old price into a permanent route.
Risk
Include search and failure
An item is not profitable merely because a successful reward can exceed its price.
Open the criminal items guide for source and purpose categories, then the specific robbery guide for the target flow. Unknown durability, success rates, or numeric effects should stay unclaimed.
Record a useful location report
Include the check date, server context, nearest fixed landmark, route from that landmark, NPC interaction title, and whether the stock interface opened. Avoid publishing private player information. Make it explicit that the contact may move.
The maintained Smuggler reference supports the dynamic-location model. The current server decides position, access, and stock.
Smuggler observation card
Record the date, server type, nearest fixed landmark, road used, accessible entrance, NPC name or interaction title, and the categories visible in stock. Do not include another player’s private information. A screenshot can support the landmark description, but the text should still explain how to reach the area through normal play.
If the contact is visible but an interface does not open, allow the server to load, move into the intended interaction range, and try once. Do not use camera or character clipping. Classify the result as unverified rather than announcing an active location.
Compare multiple server observations
Two reports are useful when they show whether the contact repeats a candidate zone or moves between zones. They do not establish a permanent spawn unless the current game or maintained documentation says so. Keep each observation with its own server and date rather than combining them into a false universal coordinate.
Stock and robbery compatibility
Read the exact item name and displayed cost before purchasing. Then open the target robbery guide and check that the live objective requests or accepts that item. A smuggler sale is not evidence that an item works on every criminal target. Record unknown durability, timing, and effect fields as unknown.
If the intended target is unavailable, keep the item only according to normal game rules and do not assume an old reward will repay the cost. Search time, purchase cost, failed interaction, and police outcome all belong to the method’s net result.
Before leaving the contact, verify that the purchased item entered the expected inventory and keep the exact current name. This prevents a later target failure from being blamed on the wrong location.