Easy Anti-Cheat does not detect AlphaRes, and using AlphaRes will not result in a Fortnite account ban. The tool operates entirely outside the runtime memory space that EAC monitors, performs no process injection, modifies no game files, and writes only to a single configuration file in %LocalAppData% before Fortnite is launched. From the anti-cheat’s perspective, an AlphaRes-applied resolution is indistinguishable from a value typed into Fortnite’s own video settings panel.
Across more than six years of public availability (the original tool reached the community in 2019), zero verified AlphaRes-related Fortnite ban incidents have surfaced on Reddit, GitHub, the Fortnite Competitive Discord, or any pro-player communication channel. Several professional players (Clix, members of the NRG and Liquid rosters, and Tfue in his early career) have publicly used stretched configurations during ranked, Cash Cup, and FNCS competition without consequence.
This article exists because every Fortnite chapter rollover and every quarterly EAC update produces the same recurring question in r/FortniteCompetitive and on community Discords: “did the new patch break AlphaRes” and “is it safe this season”. The short answer has not changed since 2019. The long answer, which covers exactly what EAC inspects, exactly what AlphaRes touches, and exactly why the two never intersect, is what follows.
TL;DR Ban-Risk Verdict
- Zero documented ban incidents attributable to AlphaRes since the public release in 2019.
- Easy Anti-Cheat does not detect or flag AlphaRes, because the tool exits before Fortnite launches and never touches the running process.
- Custom resolutions are an officially supported feature of Fortnite, exposed in the in-game video settings panel. AlphaRes simply automates writing the same configuration values.
- Pro players have publicly used stretched resolution across competitive seasons (Clix, Bugha at points, NRG roster members, FaZe historically, Tfue early in his career) without incident.
- What AlphaRes is not: not a cheat, not a memory editor, not an injection tool, not a DLL hook. It is a configuration writer.
What Easy Anti-Cheat Actually Monitors
Easy Anti-Cheat (EAC) is a kernel-level anti-cheat solution maintained by Epic Games (acquired through Kamu in 2018) and integrated into Fortnite, Apex Legends, Rust, and dozens of other competitive titles. Its detection model is well-documented through reverse-engineering write-ups on UnknownCheats, Guided Hacking, and academic papers on anti-cheat architecture. The detection vectors that matter for Fortnite fall into six broad categories.
| EAC Detection Vector | What It Looks For |
|---|---|
| Process injection | External processes attempting to load DLLs into the FortniteClient-Win64-Shipping.exe address space, hook system calls, or open process handles with write-memory privileges. |
| Memory tampering | Real-time scanning for unauthorized writes to game memory regions: player coordinates, view matrices, ammo counts, or any mutable state EAC has flagged as protected. |
| Modified game files | Hash-based integrity verification of pak files, executable binaries, and configuration directories Epic considers part of the trusted client surface. |
| Hooked rendering / API calls | Detection of overlays, ESP wallhacks, or aimbots that intercept DirectX 11/12 rendering pipelines, OpenGL, or Vulkan calls. |
| Kernel exploits and rootkits | Signature scanning of loaded kernel drivers, suspicious driver behavior, and known cheat-driver patterns at ring 0. |
| Process enumeration | Scanning the system process list for known cheat-tool signatures and blacklisted executable names that have appeared in past cheating cases. |
Technical aside: when EAC actually runs
EAC initializes only after Fortnite begins launching. The EasyAntiCheat service starts, the kernel driver is verified, and the EAC user-mode component attaches to the FortniteClient process. Anything that ran (and exited) on the system before that handshake is invisible to EAC. This single architectural fact is why pre-launch configuration utilities, including AlphaRes, sit entirely outside the anti-cheat’s scope.
What AlphaRes Actually Does
AlphaRes is a small portable executable (under 200 KB at typical builds) that performs exactly one operation: it writes resolution values into %LocalAppData%\FortniteGame\Saved\Config\WindowsClient\GameUserSettings.ini. That is the file. There is nothing else.
The full sequence when a user opens AlphaRes, types 1440x1080, and clicks Apply:
- AlphaRes opens
GameUserSettings.iniwith standard Win32 file I/O (CreateFilewithGENERIC_READ | GENERIC_WRITE). - It locates the
ResolutionSizeX,ResolutionSizeY,LastUserConfirmedResolutionSizeX, andLastUserConfirmedResolutionSizeYkeys. - It overwrites the values with the requested resolution.
- It saves the file and exits.
That entire operation completes in under 50 milliseconds, occurs before Fortnite is launched, and is functionally equivalent to opening the file in Notepad and editing the same lines manually. The only thing AlphaRes adds over manual editing is convenience (a UI, validation, and pre-set common resolutions).
The vector-by-vector mapping
| EAC Vector | Does AlphaRes Touch It? |
|---|---|
| Process injection into Fortnite | No. AlphaRes never opens a handle to FortniteClient. It exits before Fortnite is even launched. |
| Memory tampering on the running game | No. No memory writes, no WriteProcessMemory, no debug attaches. AlphaRes is a file editor. |
| Modified game files (pak, exe) | No. AlphaRes does not write to the Fortnite install directory. GameUserSettings.ini in %LocalAppData% is per-user configuration, not part of the integrity-verified game surface. |
| Hooked rendering / DirectX intercepts | No. No DLLs, no overlay layer, no rendering hooks. AlphaRes does not load into any graphics process. |
| Kernel drivers / rootkits | No. AlphaRes is a user-mode executable that runs without administrator privileges and installs no drivers. |
| Process enumeration signatures | Irrelevant. AlphaRes is no longer running by the time EAC initializes. Even if EAC scanned for the process name, the process is already gone. |
The mapping reaches the same conclusion across every vector: AlphaRes performs none of the operations EAC monitors. The two systems do not overlap in behavior, in process space, or in time.
The Technical Reason AlphaRes Is Safe
The reason ban-risk is effectively zero comes down to a single observation: EAC never sees AlphaRes do anything. By the time Easy Anti-Cheat is loaded and active inside Fortnite’s process, AlphaRes has been closed for several seconds at minimum (and typically several minutes, since users configure their resolution and then launch the game from the Epic Games Launcher).
From the anti-cheat’s point of view, the chain of events looks like this:
- The user launches Fortnite.
- The Epic Games Launcher starts the FortniteClient process.
- FortniteClient reads
GameUserSettings.inias part of its normal initialization to determine resolution, key bindings, mouse sensitivity, and dozens of other user preferences. - EAC initializes alongside Fortnite and attaches.
- EAC observes a Fortnite process running at the resolution specified in the configuration file.
The configuration file might have been edited by Fortnite’s own settings menu, by Notepad, by a PowerShell script, or by AlphaRes. EAC has no way to distinguish (and no reason to care). The resolution value is not a signal of cheating, not a runtime memory state, and not part of the trusted-binary surface. It is user data, treated as such by every component of the anti-cheat stack.
Custom Resolution Is an Officially Supported Feature
Fortnite exposes custom resolution as a first-class configuration option. Inside the game, Settings → Video → Display Resolution presents a dropdown of resolutions detected from the connected display, plus the option to use 3D Resolution scaling for non-native rendering. The resolution dropdown is populated from values the operating system reports as supported by the GPU and monitor combination, and Fortnite writes the user’s selection to the same GameUserSettings.ini entries that AlphaRes targets.
Epic Games has issued no policy statement, no community update, no Trello item, and no patch note since the introduction of FNCS in 2019 indicating that custom or stretched resolutions are against any rule. Tournament rulebooks for Cash Cups, FNCS, and the Fortnite World Cup have addressed input devices, software prohibitions (specifically named cheats and scripting tools), and account-sharing rules, but not display resolution. Resolution is, and has been, treated as a hardware-and-display configuration choice belonging to the player.
Easy Anti-Cheat similarly treats configuration values as user data. The EAC code that initializes inside Fortnite has access to the resolution Fortnite is rendering at, but it does not flag, log, or report unusual resolutions. The runtime resolution is irrelevant to cheat detection: a player using 1920×1080 native, 1600×1080 stretched, 1024×768 black bars, or 4K downsampled is functionally identical from an anti-cheat perspective.
Pro-Player Adoption History
The single strongest practical evidence that AlphaRes (and stretched resolution generally) is ban-safe is the long, public, and uninterrupted history of professional Fortnite players using it across every major competitive era. The configurations below are drawn from publicly reported tournament setups, streamed gameplay, and player-disclosed config posts. Configurations change over patches and chapters, so these should be read as historically reported rather than current loadouts.
| Player | Org / Era | Reported Resolution | Context |
|---|---|---|---|
| Clix | NRG (Chapter 2 onward) | 1600×1080 stretched | Publicly disclosed across stream config overlays and FNCS competition. |
| Bugha | Sentinels (post World Cup) | Native and stretched at different points | World Cup winner; switched between native 1920×1080 and stretched configurations across chapters. |
| Tfue | FaZe (early career) | 1680×1050 stretched | One of the earliest high-profile adopters; widely credited with popularizing stretched among NA pros. |
| NRG roster | Chapter 3 to Chapter 5 | Multiple stretched configurations | Edward, Ronaldo, and Unknown publicly streamed with non-native resolutions during competitive sessions. |
| Liquid roster | Various FNCS seasons | 1440×1080 and 1600×1080 commonly | EU competitive players including Stompy and Th0masHD reported similar configurations. |
| FaZe historical | Chapter 1 and 2 era | Stretched standard for snipes | FaZe’s competitive Fortnite roster ran stretched configurations at multiple points; common across the org’s competitive arm. |
The professional scene’s continued and unconcealed use of stretched resolution across more than six years of competitive Fortnite is the clearest available signal. Pros operate on accounts worth hundreds of thousands of dollars in prize-pool eligibility, sponsorship value, and tournament invitations. If AlphaRes (or any stretched-resolution tool) carried meaningful ban risk, the competitive scene would be the first place that risk would manifest, and it has not.
Documented Ban Incidents (Or the Absence of Them)
A focused search across the channels where Fortnite ban reports surface returns no AlphaRes-attributable incidents:
- r/FortniteCompetitive and r/FortNiteBR ban-appeal threads: The standard “I got banned and I don’t know why” thread pattern, examined across several years of submissions, contains no thread where AlphaRes is identified by Epic Support, by the player, or by the community as a contributing factor.
- GitHub issue trackers for related tools: Issue trackers on community resolution and FOV utility repositories contain no closed or open issues reporting an EAC ban tied to AlphaRes-style configuration writers.
- Fortnite Competitive Discord: Long-running channels covering competitive integrity, ban appeals, and tool compatibility have produced no consensus thread identifying AlphaRes as a ban vector.
- EpicGames Player Support tickets (publicly shared): Players sometimes share Epic Support transcripts when appealing bans. None of the publicly circulated transcripts cite AlphaRes, stretched resolution, or configuration tools as the reason for action.
Distinguishing real signals from anecdote
“I once used AlphaRes and later got banned, therefore AlphaRes” is not a signal, it is a correlation in a population that includes most stretched-resolution Fortnite players. A real signal would be: an Epic Support response identifying AlphaRes specifically; a publicly issued anti-cheat update changelog naming the tool; or a clustered wave of bans uniquely affecting AlphaRes users in a short window. None of these have occurred.
Could a Future EAC Update Change This?
Honesty matters here. Anti-cheat systems are updated routinely, and the kernel-level posture of EAC means Epic could, in principle, expand the scope of what the anti-cheat watches. The realistic answer about whether AlphaRes is at risk in a future update has two parts.
What is technically possible: EAC could begin tracking and reporting the source process responsible for the most recent edit of GameUserSettings.ini. EAC could maintain a heuristic blacklist of configuration-writing utility names and refuse to launch Fortnite when one is present. EAC could fingerprint the AlphaRes binary and flag its execution history through an extended monitoring window before the Fortnite launch.
Anti-cheat updates are possible
None of the above scenarios have happened, but it would be inaccurate to claim future EAC updates can never affect AlphaRes. Any third-party Fortnite utility carries a non-zero theoretical risk that future anti-cheat scope expansion will reach it. The practical risk in 2026 is essentially zero, but readers should understand the difference between “currently safe” and “guaranteed safe forever”.
What is practically likely: EAC updates target cheats and exploits, not configuration utilities. Anti-cheat development resources are scarce and prioritized against active threats: aimbot vendors, ESP frameworks, kernel cheat drivers, and account-sharing exploitation. A configuration writer that does not interact with the running game presents no signature anti-cheat developers would prioritize, because there is nothing for them to “block” that affects gameplay fairness. Fortnite itself supports custom resolutions, and any blanket attempt to detect-and-block configuration-writers would also flag legitimate user activity (running Notepad, running a registry editor, running a system utility that touches AppData).
What CAN Get You Banned in Fortnite
Distinguishing AlphaRes from things that actually do carry ban risk is useful for context. The following categories of Fortnite tools are routinely associated with bans, ranging from suspensions to permanent hardware bans depending on severity.
- Aimbots: Automatic targeting tools that read player positions from memory and snap the crosshair. Detected by EAC’s memory-tampering and behavioral-detection systems. Permanent ban almost universally.
- ESP / wallhacks: Visual overlays that draw player skeletons or boxes through walls, typically implemented through DirectX hooking or memory reading. Detected by EAC’s rendering-hook and memory-scan vectors.
- Model replacements: Replacing player or weapon models inside Fortnite’s pak files. Triggers EAC’s file-integrity verification.
- Exploit injectors and DLL loaders: Any tool whose function is to inject code into FortniteClient. Detected as soon as the injection attempt occurs.
- Macro and scripting tools that automate inputs: Tools that simulate inputs to automate building, editing, or aim flicks. Risk depends on detection method and the specific tool, but tournament rules also explicitly prohibit input automation.
- Account sharing and boosting: Not a software-detection vector but a policy violation that can result in account action.
AlphaRes performs none of these operations. It does not interact with Fortnite’s runtime state, does not modify any installed game file, does not inject anywhere, and does not automate any input. The category difference matters: AlphaRes belongs to the same class as a custom .ini editor, a config backup tool, or a wallpaper changer, not the class of game modifications.
Risk-Mitigation Best Practices for the Ultra-Cautious
For players who want to apply additional caution beyond the technical baseline (typically professional or semi-pro players whose accounts represent significant value, or players returning from prior account flags who want zero perceived risk), the following practices reduce already-minimal exposure further.
- Use AlphaRes as a portable executable and close it after each apply. AlphaRes does not require installation. After applying a resolution, close the application. There is no need for it to remain in memory.
- Apply resolution between Fortnite sessions, not during. Run AlphaRes when Fortnite is closed and the Epic Games Launcher is also closed. Apply the change, then launch Fortnite normally.
- Do not pair AlphaRes with any other third-party tool that touches Fortnite. If a player runs AlphaRes alongside an unrelated tool that interferes with Fortnite, and that other tool triggers anti-cheat action, the simultaneous presence of AlphaRes will be irrelevant to the cause but easy to misattribute.
- Store the executable in a clear, unambiguous location such as
C:\Tools\AlphaRes\. This is purely organizational, not security-relevant. - Verify download integrity from the official site before each new version. SHA-256 checksums are published on the download page.
- Keep Fortnite’s video settings consistent. If a resolution is applied via AlphaRes and then the user opens Fortnite’s in-game video settings and saves a different resolution, the in-game change will overwrite the AlphaRes value. This is configuration behavior, not anti-cheat behavior, but worth understanding.
FAQ
Will AlphaRes get me banned in Fortnite?
No. AlphaRes does not perform any operation that Easy Anti-Cheat monitors. It writes to a single configuration file (GameUserSettings.ini in %LocalAppData%) before Fortnite is launched, and it exits before EAC initializes. From the anti-cheat’s perspective, the resulting resolution change is identical to a value adjusted through Fortnite’s own video settings menu. There is no DLL injection, no memory tampering, no driver, no overlay, no hook, and no modified game file. Across more than six years of public use since 2019, no documented Fortnite ban has been attributed to AlphaRes by Epic Support, by community investigation, or by any credible third-party report. The tool sits firmly in the same category as a configuration utility or a wallpaper changer, not in the category of game modifications.
Has anyone actually been banned for using AlphaRes?
No documented ban incident attributable to AlphaRes has surfaced across the public channels where ban reports normally appear: Reddit’s r/FortniteCompetitive and r/FortNiteBR ban-appeal threads, the Fortnite Competitive Discord, GitHub trackers on related community tools, or shared Epic Support transcripts. Anecdotal “I got banned and I once used AlphaRes” reports are noise, not signal: most stretched-resolution players have used some kind of resolution utility, and a ban cause attributed by Epic Support to a different reason (charge-back disputes, account-sharing, suspected aimbot use detected separately) has nothing to do with AlphaRes. A real signal would require Epic Support naming the tool, a clustered wave of bans uniquely affecting AlphaRes users, or an anti-cheat changelog entry. None of these have occurred.
Does Easy Anti-Cheat detect AlphaRes when it scans my system?
Easy Anti-Cheat initializes only after Fortnite begins launching. AlphaRes is no longer running by that point: the user opens AlphaRes, applies a resolution, the application exits, and only then does Fortnite get launched. There is nothing for EAC to detect because the AlphaRes process is already gone. Even in scenarios where a user leaves AlphaRes running in the background, EAC’s process-enumeration scanning is focused on known cheat-tool signatures (aimbot loaders, injection frameworks, kernel cheat drivers); a small portable utility that does nothing while idle is not a signature category EAC tracks. Test runs over the years have confirmed that EAC does not flag, log, or interfere with AlphaRes binaries either before or during a Fortnite session.
Is custom resolution actually allowed by Epic Games?
Yes. Custom resolution is a first-class supported feature inside Fortnite. The Settings → Video panel exposes a Display Resolution dropdown, populated with resolutions reported as supported by the GPU and monitor. Fortnite writes the user’s selection to the same GameUserSettings.ini entries that AlphaRes targets. Epic Games has issued no policy statement, no Trello item, no patch note, and no community update against custom or stretched resolutions in the years since the FNCS launch in 2019. Tournament rulebooks for Cash Cups, FNCS, and the World Cup address prohibited cheats, scripting tools, and account-sharing, but not resolution. Resolution is treated by Epic, by tournament administrators, and by Easy Anti-Cheat as a hardware-and-display configuration choice belonging to the player.
Do professional Fortnite players actually use stretched resolution?
Yes, and they have done so publicly across every chapter since the competitive scene formed. Notable historical examples include Tfue (one of the earliest high-profile adopters with 1680×1050 reported during his FaZe period), Clix on NRG with 1600×1080 stretched, members of the NRG, Liquid, and FaZe rosters across multiple seasons, and many EU competitive players in FNCS finals. Configurations change between patches and chapters, so any specific number cited here should be read as historically reported rather than a current setup. The point is that professional players, whose accounts represent significant prize-pool eligibility and sponsorship value, have used stretched resolution and AlphaRes-like configuration tools openly during streamed competitive play for years without consequence.
What if a future EAC update breaks AlphaRes?
It is technically possible for a future Easy Anti-Cheat update to expand its scope, but practically very unlikely to affect AlphaRes. EAC development resources are prioritized against active cheating threats: aimbot vendors, ESP frameworks, kernel cheat drivers, and exploit injectors. A configuration utility that does not interact with the running game presents no actionable signature. Even if a hypothetical EAC update tracked the source process responsible for editing GameUserSettings.ini, blocking such activity would also block legitimate operations (Notepad edits, system administration scripts, the user’s own backups). The realistic ongoing risk is best characterized as: AlphaRes is currently safe, and the maintainers monitor each EAC update for compatibility. If a future update changes the situation, it will be communicated publicly.
Can I use AlphaRes on my main Fortnite account?
Yes. The whole point of the safety analysis above is that AlphaRes does not differentiate between accounts because it does not interact with accounts at all. AlphaRes does not authenticate to Epic Games, does not communicate with Fortnite servers, does not exchange any data with Fortnite-related services, and does not handle account credentials. It writes to a local configuration file. Professional players, who treat their main accounts as significant assets due to prize pool eligibility, ranked progression, and sponsorship visibility, have used AlphaRes-style stretched configurations on their main accounts across every season since 2019. There is no recorded benefit to using a secondary account when configuring resolution.
If my account gets permanently banned, could AlphaRes be the cause?
No, in the practical sense. Permanent Fortnite bans are issued for cheating (aimbot, ESP, exploit use), severe Terms of Service violations, charge-back disputes, account-sharing in competitive contexts, and similar high-severity actions. Resolution-tool use is not on this list. If a permanent ban has been issued, the cause is something else: Epic Support transcripts, when shared by appealing players, consistently identify the actual triggering action. A player who has previously used AlphaRes and then later receives a permanent ban for an unrelated reason should appeal through Epic’s standard channels with the actual context of their account, not assume AlphaRes is involved. Misattributing bans to unrelated software is one of the most common patterns in ban-appeal communities and is rarely correct.
Is AlphaRes detected by other anti-cheats like Vanguard or BattlEye?
AlphaRes is designed and used for Fortnite, which uses Easy Anti-Cheat. The tool has no relevance to other titles’ anti-cheat systems. Riot Vanguard (Valorant) and BattlEye (PUBG, Rainbow Six Siege, others) operate on different games with different configuration files; AlphaRes does not write to or interact with those games at all. Running AlphaRes on a system that also has Vanguard installed for Valorant, for example, has no relevance to either system: AlphaRes does not touch Valorant’s configuration, and Vanguard does not monitor non-Valorant utilities. The same applies to BattlEye-protected titles. AlphaRes is, by design, a Fortnite-specific configuration writer, and ban-risk analysis is specifically scoped to Fortnite’s anti-cheat (Easy Anti-Cheat).
Should I tell Epic Games Support that I use AlphaRes?
There is no requirement to disclose AlphaRes use to Epic Support, and there is no benefit to volunteering the information unsolicited. AlphaRes is functionally equivalent to manually editing a configuration file or adjusting a setting through Fortnite’s video panel; users do not typically inform support of routine configuration choices. If a support agent asks specifically about resolution utilities or third-party tools during a ticket investigation, an honest factual answer is appropriate (“I use a small utility called AlphaRes to apply a stretched resolution, which writes to the same GameUserSettings.ini that the in-game settings menu writes to”). Epic Support agents, when this has come up in shared transcripts, have not flagged or escalated such disclosures, consistent with the tool’s status as a standard configuration utility.
What if Epic later disallows custom resolutions in tournaments?
If Epic Games changes its tournament policy to disallow custom resolutions, the requirement would apply to any method of applying that resolution: AlphaRes, a Notepad edit, the in-game settings menu, a third-party utility, or any other path. The tool used to apply the resolution is irrelevant; the resolution itself is the regulated property. As of this article’s verification date in 2026, no such tournament rule exists for FNCS, Cash Cups, or any other Epic-sanctioned competition. Tournament rule changes are typically announced months in advance through Fortnite’s competitive blog and the official rulebook, so any future change would be visible to the community well before it took effect. Players should monitor official tournament announcements for the most current rules.
Does AlphaRes work in tournament play?
Yes. AlphaRes-applied resolutions persist across Fortnite sessions until either the user changes the resolution again (through AlphaRes, the in-game settings, or a manual file edit) or Fortnite itself overwrites the values during a settings save. Tournament play, including FNCS and Cash Cups, uses the same Fortnite client, the same Easy Anti-Cheat, and the same configuration system as casual matchmaking. Resolution applies identically across game modes. Pro players have used stretched resolution in FNCS finals, on the World Cup stage, and on the Cash Cup leaderboard for years, with the configuration applied through utilities or manual edits. Tournament-mode lobbies do not apply additional configuration validation against resolution; they validate against account eligibility, region, and the standard anti-cheat checks that are unaffected by resolution choice.
Where to Go Next
For the deeper safety analysis covering binary integrity, source verification, and the full security audit, see the dedicated Is AlphaRes Safe guide. For step-by-step setup, see Install AlphaRes on Windows. To configure a competitive stretched resolution end-to-end after confirming it is safe, see Apply Stretched Resolution in Fortnite with AlphaRes. For the broader pillar guide and quick downloads, return to the AlphaRes homepage.