Game Error ARC Raiders

Attachments Sellin' Bug - ARC Raiders Item Loss Fix Guide

📅 Published: 2026-02-05 🔄 Updated: 2026-02-05 👥 Reports: 0 ⚡ Severity: 🟢 Low

🎯 Quick Answer

When selling a weapon, manually select each attached component before confirming the sale; unattached components are not returned to inventory and their value is not included in the total.

SECTION 1: OVERVIEW

The Attachments Sellin' Bug is a user interface and inventory management error in ARC Raiders. The error manifests when a player initiates a bulk sell operation from their inventory or a vendor screen. When a weapon with attached components (e.g., scopes, magazines, grips) is selected for sale via a "Select All" or similar bulk function, the game's transaction logic fails to automatically include the monetary value of the attached mods in the total sale price. Furthermore, these unselected attachments are not returned to the player's stash upon transaction completion, resulting in permanent item loss and reduced currency acquisition. This error affects the Windows PC version of ARC Raiders. Analysis indicates the error occurs in all current game versions as of the initial Early Access release. The error frequency is classified as common when bulk selling mechanics are utilized. The severity impact is moderate, categorized as a progression-hindering resource loss bug rather than a game-breaking crash. No specific error codes or system messages are generated; the failure is silent.

SECTION 2: SYMPTOMS

The primary symptom is a discrepancy between the expected and actual currency received after selling a modified weapon. The transaction interface displays a total sale price that reflects only the base weapon's value, not the cumulative value of the weapon and its attachments. A secondary, confirmatory symptom is the subsequent absence of the unattached mods from the player's personal stash inventory. The error triggers during the specific gameplay action of confirming a sale at a vendor after using a multi-select function. The user experiences no error messages, crashes, or UI warnings; the sale completes normally from a system feedback perspective, masking the underlying resource loss.

SECTION 3: COMMON CAUSES

Category: Game Bug Specific technical explanation: Flawed item linkage logic in the bulk transaction system. The game client treats a weapon and its attached mods as a single entity for gameplay but as separate inventory entities during vendor transactions. The bulk selection function fails to traverse the attachment hierarchy. Why this causes the problem: This causes the system to only process the root item (the weapon) for sale, ignoring linked child items (attachments). Category: Game Bug Specific technical explanation: Inconsistent state management between the inventory module and the vendor UI module. The "selected" state of a parent item is not propagated to its dependent components when selected via a global command. Why this causes the problem: This results in the vendor transaction engine receiving an incomplete item list for the sale calculation and processing. Category: Configuration Error Specific technical explanation: Local game settings or cached UI data that corrupts the item selection payload sent to the game server during a vendor interaction. Why this causes the problem: Corrupted payload leads to server-side misinterpretation, causing it to accept the sale but only register the explicitly selected items. Category: Network Problem Specific technical explanation: Packet loss or desynchronization between the client and game server at the moment the sell command is issued. The server may receive an incomplete item list. Why this causes the problem: The server's authoritative state is updated based on the incomplete data, finalizing the sale and deleting items not listed in the received packet. Category: Software Conflict Specific technical explanation: Overlay software (e.g., Discord, NVIDIA GeForce Experience, MSI Afterburner) hooking into the game's DirectX rendering pipeline may interfere with the UI element detection responsible for highlighting all sellable items. Why this causes the problem: This interference can prevent the game from correctly registering all selected graphical elements, leading to an incomplete internal item list.

SECTION 4: SOLUTIONS

Solution 1: Manual Attachment Selection Prior to Sale

Difficulty: Easy Time Required: 1 minute per transaction Success Rate: High Prerequisites: None Steps:

Navigate to a vendor and access the sell menu.
Locate the weapon you intend to sell from your inventory list.
Do not use any "Select All" or bulk selection shortcuts.
Manually select the check box or highlight the base weapon.
Expand the weapon's attachment sub-menu if necessary.
Manually select the check box for each attached component (Optic, Magazine, Muzzle, etc.) individually.
Confirm the total sale price reflects the combined value of all selected items.
Execute the sell command.

Technical Explanation: This method bypasses the faulty bulk selection logic by providing the transaction system with an explicit, complete list of every item ID to be processed, ensuring the server receives correct data for both currency calculation and inventory removal. Verification: The currency received matches the sum of the individual sell values shown for the weapon and each attachment. The attachments are removed from the inventory post-sale, as intended.

Solution 2: Clear UI and Inventory Cache

Difficulty: Medium Time Required: 5 minutes Success Rate: Medium Prerequisites: File explorer access Steps:

Exit ARC Raiders completely.
Navigate to C:\Users\[YourUsername]\AppData\Local\ARC Raiders\Saved.
Locate and delete the following folders: Config, Cache, SavedData.
Open the Windows Run dialog (Win + R), type %localappdata%, and press Enter.
Find the ARC Raiders folder, right-click it, and select Delete.
Restart your computer.
Launch ARC Raiders. The game will regenerate fresh configuration and cache files.

Technical Explanation: Corrupted local cache files can cause UI state inconsistencies. Deleting them forces the game to rebuild these files from scratch, potentially resolving selection state propagation errors. Verification: After cache regeneration, test the bulk sell function with a common weapon. The bug may be temporarily resolved, though manual selection (Solution 1) remains the definitive fix.

Solution 3: Verify Game File Integrity

Difficulty: Easy Time Required: 10 minutes Success Rate: Medium Prerequisites: Launcher access (Steam/Epic Games Store) Steps:

Open your game launcher (Steam or Epic Games Store).
Navigate to your Library.
Right-click on ARC Raiders and select Properties.
In Steam, go to the Installed Files tab and click Verify integrity of game files. In the Epic Games Store, find the Verify option under the game's settings.
Allow the process to complete. This will scan all game files and redownload any that are missing or corrupted.
Launch the game after the verification is complete.

Technical Explanation: This process replaces any corrupted or altered game client scripts responsible for inventory management and UI interactions with clean, official versions, eliminating client-side code as the cause. Verification: The verification tool will report if files were replaced. Post-verification, the game client is in a known-good state, though the core bug may persist until patched.

Solution 4: Disable Third-Party Overlays

Difficulty: Easy Time Required: 3 minutes Success Rate: Low Prerequisites: Knowledge of running background applications Steps:

Close ARC Raiders.
Exit any application that may draw an in-game overlay. This includes:

* Discord (disable in-game overlay in Discord Settings > Activity Privacy) * NVIDIA GeForce Experience (open GeForce Experience > Settings > disable In-Game Overlay) * Xbox Game Bar (Windows Settings > Gaming > Xbox Game Bar > disable it) * MSI Afterburner/RivaTuner Statistics Server * Overwolf applications

Launch ARC Raiders directly from its desktop shortcut or game directory executable.
Test the vendor sell interaction.

Technical Explanation: Overlay software injects code into the game's rendering process, which can interfere with input handling and UI element state management, potentially exacerbating selection bugs. Verification: With overlays disabled, test the bulk sell function. While unlikely to resolve the core bug, this eliminates potential interference, providing a cleaner testing environment.

Solution 5: Perform a Clean Graphics Driver Installation

Difficulty: Advanced Time Required: 15 minutes Success Rate: Low Prerequisites: Administrator access, internet connection Steps:

Download the latest graphics driver for your GPU (NVIDIA or AMD) from the manufacturer's website.
Download and run the Display Driver Uninstaller (DDU) utility from https://www.guru3d.com/download/display-driver-uninstaller-download/.
Boot Windows into Safe Mode.
Run DDU and select "Clean and restart" for your graphics driver.
After the restart, install the freshly downloaded graphics driver using the "Custom" installation option.
Select "Perform a clean installation" during the setup process.
Restart your system normally and launch ARC Raiders.

Technical Explanation: A clean driver install removes all previous driver files and registry entries, ensuring no GPU-level rendering or DirectX handling conflicts are affecting the game's UI rendering pipeline. Verification: Graphical performance should be stable. This solution addresses systemic graphical conflicts but is a broad-spectrum fix for a specific UI bug.

SECTION 5: PREVENTION

To prevent recurrence of resource loss, adopt the manual selection protocol as a standard operating procedure for all vendor sales. Configure your inventory sorting to group weapons with their attachments for clearer visibility before transactions. Maintain a regular schedule for verifying game file integrity through your launcher, particularly after major game updates. Monitor the total sale price displayed in the vendor UI before confirming every transaction; this value must equal the sum of all components being sold. Adherence to this explicit verification step is the primary preventative measure against the bug.

SECTION 6: WHEN TO CONTACT SUPPORT

Contact official ARC Raiders support only if the bug manifests even when following Solution 1 (manual selection), indicating a potentially different, escalated inventory corruption issue. Before contacting, gather the following diagnostic information: system specifications (CPU, GPU, RAM), game version number, and the exact time/date of the transaction with loss. Locate and be prepared to provide game log files, typically found in C:\Users\[YourUsername]\AppData\Local\ARC Raiders\Saved\Logs. Official support channels are accessed through the ARC Raiders website or the game's official Discord server's designated support section.