Arc Raiders recently flagged and banned some players who were using accessibility peripherals. One affected gamer, who is quadriplegic and uses a specialized controller, had their account suspended but has since had it restored after community attention and direct contact with the developer.

What happened

In January a player known in-game as ClootyBapper received a temporary suspension that lasted until late February. The player says they never used exploits or cheats. Attempts to reach the studio through normal support channels did not produce results at first.

Timeline

  • January: Temporary suspension issued.
  • Late February: Suspension end date, but the account owner still sought clarification.
  • March 17, 2026: The developer publicly acknowledged the issue and said they were working on it.
  • After that: The player was reinstated and thanked the community for helping.

What Embark Studios said

Embark posted that certain players using accessibility peripherals were being banned and that the team is working to resolve the problem as soon as possible. The company added that support is reviewing appeals and that anyone affected should continue to reach out to the studio.

How the player responded

The affected player described feeling low and frustrated, noting the situation was particularly painful given their physical disability. After the developer responded and support reviewed the case, the player reported the account is active again and expressed gratitude to those who raised the issue.

What this means for other players

  • If you use an accessibility peripheral and you were banned or suspended, contact Embark support and file an appeal. The studio says it is reviewing appeals.
  • Keep records of your case and any communication you have with support. That can help speed up review.
  • Community visibility helped in this case. If more affected players make themselves known, it may push the issue higher on the priority list.

This looks like a case where automated systems flagged valid hardware as a rule violation. The developer has acknowledged the error and is working to correct it. That does not undo the stress caused, but it is the step needed to prevent further incidents.