Roanoke’s official description lists robbing ATMs as an activity. That confirms the mechanic at a high level, but it does not publish ATM locations, requirements, tools, controls, payout, cooldown, alert behavior, police response timing, or penalties. Treat all of those as live checks. Do not invent an efficient farming route or guaranteed reward from the sentence on the game page.
Verify the current interaction
Find an ATM through normal exploration or a current in-game marker. Confirm that the object exposes an interaction on your device. Read every live prompt before beginning and record any role, item, level, cooldown, or other requirement the interface shows.
If the interaction does not appear, do not assume every decorative ATM works. Check that you are at an interactive object, that the activity is currently enabled, and that your server has loaded correctly. A location from an older video may have changed.
Scene setup card
Location
Choose one confirmed interactive ATM and give responders a recognizable nearby landmark.
Participants
Assign the initiating player, observer or witness, responding officer, and optional dispatcher.
Response rule
Agree when police can learn about the incident and how much time the interaction receives.
Ending
Set an escape boundary, voluntary stop, arrest scene, or reset condition before a pursuit starts.
Use a private or quiet setting for a controlled event. In a public server, ask the players involved and avoid blocking roads used by deliveries or casual drivers. An ATM scene should not automatically pull every nearby player into a chase.
Run the robbery step by step
First, stage the getaway vehicle without blocking the interactive object or roadway. Confirm that the driver knows the route and the agreed boundaries. Second, begin only through the current game prompt; do not describe an unsupported tool or button as required. Third, give the observer or alert system the agreed opportunity to create a response.
When responders arrive, make their signals readable. Decide whether the scene becomes dialogue, a short pursuit, or a stop. If it becomes a chase, follow the route, reset, ramming, and damage rules established before the event. Finish at the agreed boundary rather than extending it until someone disconnects.
Separate payout testing from roleplay
If you are measuring the mechanic, use a simple record: date, server type, player state, interactive location, displayed requirement, start and completion state, displayed Cash before and after, cooldown message, and any alert. Repeat only when the game allows it. Keep roleplay transfers or unrelated job income out of the balance comparison.
Do not publish a guaranteed payout from one attempt. Updates, access states, bonuses, or server conditions may change it. If the interface does not identify the source of a balance change, mark the result uncertain.
If you are running a story scene, the dramatic result does not need to match a measured payout. Make it clear that fictional dialogue and community rules are not official economy data.
Police response
Responders should learn the location through the agreed mechanic, witness, or dispatcher instead of reading out-of-scene chat and appearing instantly. Stage safely, keep traffic moving, and assign one person to lead contact. The Police guide provides a full traffic-stop and pursuit sequence.
Do not assume the Emergency Services pass includes every police role or tool. It officially unlocks the dealership category, while vehicles remain Cash purchases. Team and equipment access need separate verification.
Getaway vehicle choices
Choose reliability and control for the agreed route rather than an unsupported fastest-car ranking. A highly tuned vehicle may make the matchup unfair or become difficult to brake. Tell participants whether passes, engine swaps, drag chutes, or limited wheels are allowed.
Walk the route once at normal speed. Identify busy intersections, narrow property entrances, job pickup areas, and a safe ending point. Leave enough shutdown room after any high-speed section and never depend on a drag chute you have not tested.
Troubleshooting
If the ATM interaction stops, record the exact screen message. It may indicate a cooldown, missing requirement, unavailable object, or server issue. Change one condition at a time and rejoin once only after preserving the context. Do not turn a loading failure into a claim about permanent removal.
If no police response occurs, the mechanic may not generate one automatically, or no participating player may be available. The official description does not specify an automated dispatch contract. Agree on a witness or dispatcher for planned scenes.
If players disagree about the outcome, return to the brief: response timing, pursuit boundaries, collision rules, and ending. Stop the scene if consent is withdrawn. A mechanic that permits an action does not require another player to continue roleplay.
What still needs live testing
Interactive ATM locations, access requirements, tools, prompts, completion steps, payout, cooldown, alert behavior, police response mechanics, penalties, reset behavior, and private-server differences all require current in-game verification. Keep screenshots and dates with any result, and leave fields blank when the game does not show them.