In Company of Heroes 3 (CoH3), a "maphack" is a type of cheat that removes the fog of war, giving a player full vision of the entire battlefield, including all enemy units and hidden structures. As of 2026, the community continues to report these as a persistent issue in competitive multiplayer. Common Features of CoH3 Maphacks
Fog of War (FoW) Removal: The primary function, allowing cheaters to see every unit movement from the start of the match.
Zoom Hacks: These often accompany maphacks, allowing players to zoom out much further than normally permitted to see larger portions of the map at once.
Hidden Unit Tracking: Cheaters can see camouflaged units, such as Snipers or commandos, and even "ghost" structures (buildings that have been placed but not yet constructed).
Automatic Counters: Hackers often react with "pixel-perfect" movement to avoid Anti-Tank (AT) guns or mines they should not be able to see. How to Spot a Maphacker in Replays
Players often use the in-game replay system to verify suspicions. Key signs include:
Camera Tracking: In a replay, if you lock the camera to the player's perspective, they may be seen staring at your units through the fog or tracking their movement across the map.
Blind Artillery/Mortars: A common "tell" is when a player consistently uses "attack ground" or mortar barrages on stationary or mobile units deep in the fog of war without any recon units (like flares or scouts) nearby.
Odd Maneuvers: Moving units to the exact spot that avoids a hidden minefield or flanking an MG-42 in a building without ever having spotted it first. The State of Anti-Cheat (2026)
Relic Entertainment uses an in-game report system to handle these cases. While players frequently express frustration over the speed of bans, the developer has issued "ban waves" and recently adjusted the system to be more aggressive.
Reporting: You can report players directly through their profile banner in-game or via the results screen.
Developer Feedback: Some users have reported receiving notifications from Relic confirming that an account they reported for maphacking was successfully banned. Community Counter-Arguments
It is important to distinguish between hacking and high-level play. Some "hacks" are actually legitimate game mechanics:
The Controversial World of Company of Heroes 3 (CoH3) Maphacks: What You Need to Know coh3 maphack
In the competitive landscape of Company of Heroes 3 (CoH3), information is the most valuable resource. Knowing where your opponent is positioning their anti-tank guns or where a flanking maneuver is starting can decide the match. This strategic "Fog of War" is a core pillar of the franchise. However, a shadow looms over the multiplayer community: the rise of the CoH3 maphack. What is a CoH3 Maphack?
A maphack is a type of third-party software or script that removes the "Fog of War" from the game's mini-map and tactical map. In a standard match, players can only see enemy units within the line of sight of their own troops. A maphack bypasses this restriction, granting the user "God-view" over the entire battlefield. In CoH3, this provides several game-breaking advantages:
Perfect Counters: Seeing exactly what tech path an opponent is taking (e.g., rushing a Panzer IV) allows the cheater to prepare counters perfectly.
Avoiding Ambushes: Stealth units or hidden MG teams become useless.
Artillery Precision: Calling in off-map strikes or mortar fire on units that should be hidden. The Impact on the Multiplayer Community
The presence of maphacks undermines the integrity of the Elo ranking system. For many players, the frustration of losing to someone who seems to have "psychic" knowledge of their movements leads to burnout and a declining player base.
Relic Entertainment, the developers of CoH3, has integrated Easy Anti-Cheat (EAC) to combat these tools. While EAC is effective at catching many public "trainers" and "scripts," private or more sophisticated maphacks often play a cat-and-mouse game with developers, leading to occasional "waves" of cheaters. How to Spot a Potential Maphacker
If you suspect someone is using a maphack in your lobby, look for these "red flags" in your replays:
Unnatural Reactions: They move their units to counter yours before your units are ever spotted by their scouts.
Blind Fire: They consistently use artillery or abilities on "unrevealed" areas where your units happen to be sitting.
Lack of Scouting: A player who never uses scouts or flares but still manages to have a perfect response to every flank is highly suspicious. The Risks of Using Maphacks
For those tempted to gain an edge, the risks far outweigh the temporary "glory" of a win:
Permanent Bans: Relic has a zero-tolerance policy for cheating in multiplayer. A detected maphack will result in a permanent ban from online services. In Company of Heroes 3 (CoH3), a "maphack"
Security Threats: Many sites offering "free CoH3 maphacks" are fronts for malware, keyloggers, and ransomware that can compromise your entire PC.
Community Blacklisting: The CoH3 community is tight-knit. High-level players often share lists of suspected cheaters, making it impossible to find matches in private leagues or tournaments. Conclusion: Protecting the Game
The best way to enjoy Company of Heroes 3 is through skill, strategy, and fair play. While maphacks are a persistent issue in the RTS genre, reporting suspicious players through official channels and supporting developer efforts to strengthen anti-cheat software is the only way to keep the battlefield level.
Telemetry doesn't just scan for known cheat signatures. It looks for anomalies:
Every unit, building, and capture point in COH3 has a binary state: Visible or Hidden. In a clean game, your client only renders "Hidden" objects as black voids. However, to sync the game state between two players (Peer-to-Peer with a relay server for COH3 1v1/2v2), your computer technically knows where the enemy tank is; it just refuses to draw it on your screen.
A maphack injects a Dynamic Link Library (DLL) into the COH3 process. This DLL scans the game’s memory for the specific hexadecimal values controlling the "Visibility Flag" and flips them. To the cheat, it’s a simple line of code: if (unit.isEnemy) setVisibility(True);
The honest answer is no. As long as client-side authority exists (your computer needs to know where the enemy tank is to render the terrain), a kernel-level cheat or a hardware spoof can bypass it.
However, Relic could take inspiration from League of Legends (which uses a similar RTS engine for fog) and implement Server-Side Fog of War.
This would mean the server only sends you the location of enemy units if you have a valid scout unit with line of sight. The downside? It requires massive server processing power. For a game with 8 players and hundreds of units (the "late game blob"), server costs would explode.
What Relic Should Do (and soon):
Command & Conquer: Heroes 3, or more accurately, Command & Conquer: Renegade and its relation to the Heroes series might cause confusion. The actual "Heroes" series from EA is primarily known for Command & Conquer: Tiberian Dawn, Command & Conquer: Red Storm, and expansions, rather than a directly titled "Heroes 3". That said, there seems to be some confusion or mix-up here.
If you're talking about Command & Conquer: Heroes (which might be a misnomer), you might actually be referring to:
Assuming you're referring to Company of Heroes (CoH) and similar games: How Telemetry Works Telemetry doesn't just scan for
The problem is that COH3 maphacks are predominantly "External." Because Relic opted for a deterministic lockstep model (to reduce server costs), the client holds too much authority. Hackers operate on a "Loop" model:
As of the Hammer & Shield and Nightfighters patches, Relic has shifted to Server-Sided Validation for ranked matches. This means the server double-checks if a player should have line-of-sight to a unit before confirming a hit. However, this increases server lag and doesn't fully prevent movement-based cheating.
You just lost a 45-minute 1v1 game. The opponent had perfect timing on every dive. They retreated their mortar just before your artillery landed. They hunted your sniper across the map without ever sending a scout.
Are they cheating, or are they a top 50 player smurfing?
Here are the behavioral "red flags" that differentiate a skilled player from a maphacker.
Red Flag 1: The Unscouted Flank Counter You send three units around the extreme edge of the map—a path that no player would normally patrol because it offers no resources. Within 10 seconds, the enemy pivots their entire army to that specific tree line. When you watch the replay, they never moved their camera to that area, and they had zero units providing vision.
Red Flag 2: Artillery Sniping on the Move A legitimate player barrages a known garrison or a capture point. A maphacker barrages your retreating squad that is hidden behind a shot-blocker. Watch the replay: if their artillery lands exactly on a moving unit that they had no line of sight to, and they didn't use a scout ability (like a Kettenkrad or Pathfinder), it's a hack.
Red Flag 3: Perfect Mine Avoidance Mines win games in CoH3. A single teller mine can cripple a Pz.IV. A maphacker never drives over a mine. Ever. They will micro their vehicles around a minefield they have "never seen." If you lay mines in the fog of war and they drive a perfect slalom around them, you are facing a cheater.
Red Flag 4: The "Sniffer" Army The hacker knows where you are, but they pretend not to. They will send a single scout squad directly toward the exact location of your anti-tank gun—not because they are probing, but because they need a "legitimate" reason to attack there. This is called "Sniffing." It is the art of pretending to scout.
In COH3, a well-positioned Marder tank destroyer hiding in the treeline can destroy a Sherman that costs 50% more fuel. A maphacker never drives into an ambush. They will always magically "decide to go the other way" or pop smoke for no apparent reason. This renders the defender’s tactical setup utterly worthless.
Unlike traditional memory-reading cheats (which are often caught by Easy Anti-Cheat), the CoH3 maphack is reportedly a shader or rendering exploit. Because CoH3 uses the Essence Engine (the same engine as Age of Empires IV), hackers have found ways to disable the "fog" layer client-side.
Crucially: The server still knows the hacker cannot see the units, but the hacker’s screen renders them anyway. This makes the cheat very difficult for automated anti-cheat to detect, as it looks like a graphical glitch rather than a memory manipulation.