Players often call every promotion resource “XP,” but San Diego Border Roleplay may show a bar, count, rank progress, completed objective, or another label in the current interface. The official badges confirm team objectives and maximum-rank goals, not XP values. This guide uses “XP” as the search term while requiring you to preserve the exact live label before measuring anything.
Find the real progress display
Join one team and locate its current rank, progress, objective, or statistics interface. Record the exact label, starting value, current rank, next displayed goal, and server date. If no numeric value appears, do not convert a visual bar into a precise number.
Switching teams may expose a different track. Save Border Patrol, Police, US Army, FBI, and any other role separately. Account cash, badge count, role rank, and player-level indicators are different systems unless the live interface explicitly links them.
Use official actions as test candidates
Official badges establish several Border Patrol actions: grant a Civilian entry, send one to secondary inspection, and scan one with the Scanner. Police has a recognized goal for killing or arresting a wanted criminal. These are strong candidates for progression tests because they are verified gameplay events.
The badges do not say how much progress each action gives or whether every completion affects rank. The test must compare the progress display before and after the action. Badge completion itself may be one-time while the gameplay action repeats.
Test one variable at a time
Capture the starting display, complete exactly one valid action, wait for normal feedback, and capture the ending display. Repeat the same action several times before comparing a different action. Keep failures in the record; they reveal whether completion or attempt matters.
Do not mix an approval, secondary referral, scan, arrest, and time played into one result. A promotion during that session cannot identify its cause. If only a visual bar exists, report directional movement rather than a guessed number.
Border Patrol progress session
Begin with normal approvals because the interaction is central to the checkpoint and confirmed by an official badge. Then create a separate session for secondary referrals and another for successful scans. Follow the current roleplay rules and process real traffic rather than coordinating artificial spam.
Record valid completions, not clicks. A referral is distinct from a vehicle merely entering a side area, and a successful scan is distinct from equipping a scanner. The live result or badge wording should guide the completion boundary.
Police progress session
Record one valid wanted-player event at a time. Separate arrest from elimination because the First Catch badge permits either but the rank system may treat them differently. Record whether the wanted status was visible and whether the current enforcement interaction completed.
Current community guides discuss apartment printer investigations. Until the live progress display changes after a confiscation, do not include printer activity in a Police XP formula. Community agreement about the loop is not official proof of rank credit.
Calculate only supported rates
If the interface shows numeric progress, the observed change is ending value minus starting value. For a session rate, divide confirmed progress by completed valid actions or active measured time. State server date and sample size. Do not generalize a single result into a universal fastest method.
Include travel, queue, failed interactions, and recovery when comparing practical efficiency. A rare action with a large change may produce slower progress per session than a reliable checkpoint task. Keep “per action” and “per minute” separate.
Avoid invalid farming methods
The official experience warns that cheats and automated farming can lead to bans. Do not use macros, AFK loops, exploit clients, collision abuse, or arranged account feeding. Besides the account risk, artificial repetitions produce results that do not represent normal play.
The safest fast-progress strategy is mastering a legitimate repeatable team loop: clear checkpoint decisions for Border Patrol or accurate wanted responses for Police. Speed comes from fewer mistakes and less downtime, not bypassing the game.
Troubleshoot no visible progress
Check the exact team, whether the event completed, whether the target was valid, whether a progress panel must be reopened, and whether a delay is visible. Compare the badge or outcome message with the rank display. Then reproduce once in a fresh server.
Do not invent a daily cap, hidden cooldown, or level requirement because one attempt failed. Record the message and conditions. If two servers disagree, label a possible rollout and check again after an update.
Turn observations into a route
Choose the legitimate action with the clearest completion and most consistent progress in your dated tests. Build a route around reaching, completing, and resetting that action. Recheck after promotions because access, objectives, or requirements may change.
The Ranks guide records verified team endpoints. Use Badges for official objective wording and Updates before carrying a value into a new version.
Evidence notes
- Official badge descriptions: Official for checkpoint approval, secondary inspection, scanner use, Police wanted-criminal actions, and four team maximum-rank endpoints.
- Official experience description: Official for continued development and the warning against cheats or automated farming.
- XP label, numeric awards, formulas, thresholds, multipliers, caps, and fastest rates: Needs in-game testing.