Re: How to get help with Apex Legends account bans and suspensions
Hello EA Community Managers,
I have just submitted a third appeal (#253676878)
I am writing here to bring your attention to a critical issue with my account. I received a permanent ban for "Gameplay Enhancement," which happened strictly while I was playing the official Bot Royale mode. My official EA Data Export Log, which includes the exact date, time, and the specific anti-cheat trigger for my ban, looks like this: {"time":"2026-08-29T17:14:24.291455Z","type":"ban"}],"antiCheatReportsHeaders":["message"],"antiCheatReports":[{"message":"#REPORT_PLAYER_REASON_AIMSNAP"}].
I can say with absolute confidence that I have never used cheats, macros, third-party software, or any other utilities to gain an advantage over other players. I have always respected the game and its community.First, let me present a logical argument in my defense: I have over 3,000 hours of legitimate playtime in Apex Legends, and I have invested a lot of effort and significant financial resources into my account. I would never risk all of this progress—especially in Bot Royale, a training mode where winning grants absolutely nothing but basic XP and Battle Pass challenges. I am 100% sure that the ban was triggered in Bot Royale because it is the only game mode I have been playing for the past 2–3 months.
On August 29, the day of my ban, I played exactly 27 matches, and all of them were in Bot Royale. This data is clearly visible in my official connection logs.When I saw the permanent ban notification, my surprise was beyond limits. I immediately started analyzing what could have triggered such a decision. At first, I thought that my high-statistic games with 25+ kills and 6000+ damage might have raised red flags on my account profile. Then, I wondered if earning up to 7000 XP per match in Bot Royale was flagged as abnormal account level farming.But then, I remembered a very specific, strange moment that occurred during one of my last matches. Below, I will provide a detailed description of a game physics bug during that session which caused the anti-cheat to false-trigger. I am 100% confident this is the exact reason, as nothing like this had ever happened prior to this session.
The map was Storm Point. I prefer playing solo, so I landed alone at the Storm Catcher POI. Usually, 1 or 2 bot squads drop there. This match was no exception. While I was fighting those 2 squads, Ring 1 started closing. Since Storm Catcher was inside the next safe zone, another bot squad spawned dynamically right at my location.As most players know, AI squads in Bot Royale sometimes spawn directly near the player—especially during Ring closures, to prevent them from dying out in the storm. But while they usually appear nearby on the ground, this time I heard footsteps instantly appearing on the roof. I took high ground on the roof where the Survey Beacon usually spawns. I could hear running and stepping sounds, but no enemies were visible. Out of pure curiosity, I searched for them for a long time.It turned out they had spawned completely inside the geometry/texture of a large metal box-like structure on the roof, located near the solar panels (or something that looked like solar panels). The bots were trying to run, but they were perfectly static, clipped into each other inside the wall. There was a narrow open gap at the very bottom of this metal structure where their legs were exposed. Without thinking twice, I started shooting into that gap. It turned out that a whole squad was stacked in that single pixel coordinate, which I only realized after knocking down the first one. I am 100% sure the anti-cheat triggered exactly at this moment. There are several reasons for this that I am aware of (though a technical specialist will likely see even more).
Reason 1: The squad spawned in a location where it is physically impossible for a team to be in any other game mode. In Ranked or Public matches, it is impossible to access that spot, let alone fit an entire squad inside it. Therefore, the anti-cheat system likely flagged my actions as a "wallshot" or shooting through map geometry.
Reason 2: Because the entire squad was stacked within a single pixel coordinate—meaning their character models and hitboxes were completely overlapping—my bullets hit multiple targets simultaneously. This is mathematically impossible in standard PvP modes where real players do not spawn dynamically. When I fired into that gap, the anti-cheat system likely misinterpreted the instant, frame-by-frame damage registration between the overlapping targets as an unnatural aimbot lock. This perfectly explains the exact trigger phrase found in my log: "message":"#REPORT_PLAYER_REASON_AIMSNAP".
Once again, there could be more underlying technical reasons, but these are the ones apparent to me. While researching my issue, I encountered numerous complaints from other players who received permanent bans specifically while playing the Bot Royale mode around August 27–30. I cannot speak for what happened in their individual matches, but I have described my own case in full detail and attached the official telemetry logs as proof.
I kindly ask EA_Mako, or any available Terms of Service specialist to review this thread and escalate it directly to the Respawn Anti-Cheat team so they can inspect the Storm Catcher environment logs. I just want to recover the account I deeply value.
Thank you.
