Weapons affect both loadout choice and wanted-state risk in San Diego Border Roleplay. The official experience says teams receive different loadouts and gear. The official Armed and Suspicious badge specifically says that equipping a weapon near a federal agent can make a player wanted. That is the most important confirmed weapon rule: where and when you equip matters. A complete weapon catalog, damage table, and tier list are not published officially.
Confirm the weapon identity
Use the exact name shown in the current loadout, shop, inventory, pass page, or team interface. Record its source, team, rank or pass requirement, currency, displayed cost, and server date. A weapon seen in another player’s hand does not prove that it belongs to your role or remains obtainable.
If a name comes from a community guide, label it Community reported until the live interface matches. Do not turn a visual resemblance into a model name. Updates can change access or replace an item while old videos remain searchable.
Understand wanted-state risk
The Armed and Suspicious badge connects equipping a weapon near a federal agent with becoming wanted. It does not state a fixed distance, list exempt teams, or guarantee the same result in every context. Before carrying or drawing a weapon near the checkpoint, observe the current warning, status display, role, and server rules.
If wanted status appears, record the action and location. Holstering may not immediately clear it, and this guide does not assume a timer. Avoid repeatedly drawing the weapon to test the boundary around unsuspecting players.
Match weapons to roles
Federal and enforcement teams may receive role-specific loadouts, while Civilian access can have different legal or wanted consequences. Read the team inventory every time you switch roles. A Police tool should not be described as a Border Patrol standard unless both current loadouts show it.
The First Catch badge confirms Police can kill or arrest a wanted criminal for a progression goal. It does not define every acceptable use of force. Visible wanted status, current tools, live prompts, and server rules still determine the interaction.
Test handling without inventing stats
In a permitted controlled setting, verify equip and holster behavior, aim presentation, firing or activation, reload or cooldown indication, ammunition display, and how the item returns to inventory. Use the same device and conditions for comparisons. Never test damage on an uninvolved player.
Record only values exposed by the current interface or reproduced through a clearly described current test. One elimination does not establish damage because range, health, armor, server latency, or another player can affect it. Leave damage, recoil, accuracy, range, and time-to-eliminate unranked without repeatable evidence.
Weapon use at the checkpoint
Keep a weapon holstered unless the current roleplay situation and rules require it. Drawing near federal staff can change wanted status, disrupt inspection, and turn a normal crossing into an enforcement event. Travelers should wait for the actual inspection interaction instead of trying to intimidate or bait officers.
Federal players should confirm the player, item, wanted display, and valid response before escalating. The checkpoint is also a traffic system; unnecessary weapon use can block lanes and involve players who are not part of the incident.
Access through shops or gamepasses
When a weapon is associated with a pass, open the current official Roblox product page and confirm title, creator, price, and description. A community catalog can help discover a name, but it cannot guarantee the current benefit. Do not assume a combat-themed pass grants a particular weapon, damage bonus, or permission.
When the source is in-game cash, record the live currency and cost before buying. Keep purchase access separate from role access: owning an item does not prove every team can equip it in every zone.
Troubleshoot equip and firing problems
If an item will not equip, check role, spawn protection, team inventory, purchase state, current menu, cooldown, and input device. If it equips but does not activate, read the visible ammo, target, range, and mode indicators. Test once in a quiet permitted location.
If behavior differs between servers, record each server date and interface. A rolling update or server issue is more plausible than a universal hidden rule. Never use an injector, macro, or exploit to bypass a loadout restriction; the official description warns that cheats and automated farming can lead to bans.
Build a safe loadout note
For each verified item, keep name, team, source, access, equip behavior, displayed ammunition or cooldown, wanted-state observation, and tested date. Add performance only after a repeatable legal test. Recheck after updates.
Use Equipment for scanners and job tools, Police for enforcement boundaries, and Civilian for carrying risk. The Updates hub explains how to recheck unstable details.
Evidence notes
- Official experience and badge descriptions: Official for team-specific loadouts, weapon-related wanted status, and the Police wanted-criminal goal.
- Current loadout, inventory, shop, and official Roblox product pages: Required for live weapon names and access.
- Complete catalog, damage, recoil, range, ammunition, rankings, and role permissions: Needs in-game testing.