The checkpoint is the core San Diego Border Roleplay interaction. Drivers approach in a vehicle, Border Patrol decides whether to approve or inspect them, and some vehicles move to secondary inspection or scanning. Official badge descriptions confirm approval, secondary inspection, scanner operation, legal crossing, and processing 25 Civilians, giving both sides a reliable task order.
Civilian approach and queue
Spawn an available vehicle and follow the main road toward the checkpoint. Slow down before the booth area, stay in the active lane, and leave enough space for the vehicle ahead to finish. Do not switch lanes suddenly or block a secondary turn. If the current server displays a signal, barrier, or instruction, follow it rather than a screenshot from another build.
Keep weapons holstered. The official Armed and Suspicious badge says equipping a weapon near a federal agent can make you wanted. A legal crossing is the best way to learn the route because it removes unnecessary risk from the first inspection.
Approval and inspection outcomes
At the decision point, wait for approval or an inspection instruction. Approval should lead to the border exit and the official Legal Border Crossing goal. An inspection may ask you to remain, expose inventory, move, or follow another prompt. Exact questions and UI buttons are not public, so respond to what the current player or system shows.
If sent to secondary inspection, move only when the path is clear. The Secondary Inspection badge confirms that Border Patrol can send a Civilian there. The Scanner Operator badge confirms a scanner interaction. Neither description publishes the scan algorithm, detection chance, or exact bay controls.
Border Patrol first shift
Join Border Patrol through the current team menu and inspect the tools you actually receive. Identify the lane, approval control, secondary action, scanner, and communication method before processing traffic. If a tool is rank- or pass-locked, do not claim it as standard team gear.
Process one vehicle slowly. Receive it, inspect the live prompts, choose a valid outcome, and confirm that the vehicle exits or reaches secondary. Then return the lane to a clear state. Speed should come only after the complete flow is repeatable.
The Stamp of Approval badge gives a clear early goal: grant a Civilian entry into the United States. Border Veteran requires processing 25 Civilians. That number proves an official volume milestone, but not the XP paid for each vehicle.
Secondary inspection and scanner use
Secondary inspection keeps longer checks away from the main queue. Send a vehicle only through the current action and server rules. Do not invent suspicion criteria or use the area to trap players. Communicate which vehicle is moving and whether the main lane should continue.
At the scanner, follow the displayed interaction. The official badge says “Scan a Civilian using the Scanner,” but it does not define every object, result, or false-positive rule. Record the prompt and outcome if you are documenting the current build. Do not publish a guaranteed detection percentage without repeated evidence.
Smuggling and detection boundaries
The official experience teases carrying something suspicious and hoping agents do not look closely. Current beginner guides describe goods with detection behavior and a seller across the border. Those sources support the broad risk loop, not a permanent item table.
For Civilians, read the live item panel before buying and accept that inspection can fail. For Border Patrol, use the current scanner and rules rather than recognizing contraband from an old list. The Smuggling guide covers purchase and seller decisions; this page stays focused on checkpoint handling.
Police and wanted response
Police may respond after a criminal crossing or wanted event, but Police should not replace the Border Patrol decision workflow without a current server reason. The official First Catch and wanted badges confirm enforcement goals. They do not publish pursuit jurisdiction, force-entry rules, or arrest payouts.
Communicate location, vehicle, direction, and visible wanted state. Avoid random escalation in the inspection queue. The Police guide covers the enforcement route and its evidence limits.
Common checkpoint failures
If the line stops, check whether a vehicle is still active, a barrier awaits an interaction, or secondary is full. If the wrong vehicle receives an action, slow down and clear selection before repeating. If scanner prompts do not appear, confirm team, rank, equipped tool, distance, and input device.
If driver and agent disagree, follow the current interface and server moderation. A guide cannot override a live rule. Move to a quieter server when chaos prevents learning; repeated random outcomes do not teach the actual flow.
Checkpoint etiquette
Drivers should stay in line, avoid horn spam, and wait for a clear outcome. Agents should process in order, explain a secondary move briefly, and avoid holding a vehicle without a reason. Everyone should keep the crossing usable for other players.
Do not use exploits to cross barriers, automate approvals, or farm processing counts. The official description warns that cheating and auto-farming can lead to bans. A legitimate Border Veteran run comes from real interactions.
Record the current layout separately
Use the Checkpoint Map for lane, booth, bay, and exit landmarks. Keep this guide for procedure. After an update, the spaces may move while the core approval-inspection-secondary sequence remains recognizable.
Record server date, team, lane, prompt labels, outcome, and any rank restriction. That makes a future correction precise without turning one player’s experience into a universal scan rule.
Evidence notes
- Official experience and Roblox badges: Official for the checkpoint loop and named badge actions.
- Current beginner guides: Community corroborated for the broad driving, inspection, and smuggling interaction.
- Exact UI, scan logic, detection values, lane layout, authority rules, payouts, and XP: Needs in-game testing.