I have lost count of how many team fights in Overwatch 2 have crumbled because my Baptiste immortality field simply decided not to exist. One second I toss the drone against a wall, anticipating a clutch save; the next, I’m staring at a 25‑second cooldown and a kill feed full of eliminated teammates. It is 2026, the game has evolved through dozens of seasons and a steady stream of balance patches, yet this infuriating bug refuses to die. As a support main who leans heavily on Baptiste, I keep asking myself: why is an ability that can swing entire matches still being swallowed by geometry?

The problem, extensively documented by players for years now, rears its head mostly on certain maps and in cluttered environments. Throw your immortality field at a Push robot and it might fall right through the floor. Aim for a wall in Busan’s Meka Base and the device can phase straight into the void. Over on the forums, veteran Baptiste mains have compiled entire lists of cursed spots—forklifts on Junkertown, specific corners on Dorado, even the payload’s rear flank on Midtown. None of these surfaces are safe. The field is supposed to bounce off surfaces and deploy a protective halo, but when the collision detection fails, the projectile either vanishes entirely or clips through the geometry without triggering. The result is not just a wasted cooldown; it is a fight suddenly lost before it even began.

Reddit user Analyzor first brought widespread attention to this glitch way back in 2022, and I naively assumed a fix would roll out within weeks. Yet here I am, four years later, able to replicate the bug effortlessly in a custom lobby. I loaded up Busan’s downtown section yesterday and tossed the drone against a wall near the capture point. Nothing. I tried it on the moving platform in Antarctica Peninsula—same silent disappearance. The most soul‑crushing test happened on Esperança when the Push robot was inches from the finish line: I lobbed my field onto the robot’s side to protect my frontline, only to see the cooldown start ticking with no field on the ground. My Ana, who was waiting for that save, died immediately. How have these collision oversights survived every major engine update the game has received since launch?

Perhaps the silence from Blizzard is the strangest part. Over the years, the team has reacted swiftly to game‑breaking hero issues—think of the two‑week removal of Mei, Torbjörn, or Bastion when their abilities broke in critical ways. Baptiste mains are not asking for him to be ripped from the roster, of course; we just want his signature ability to function on every map tile. The Immortality Field already demands careful aim and predictive timing. Having to pre‑screening each surface for a known black hole is not a reasonable skill check. In competitive play, where every second matters, losing a fight to geometry randomness feels cheap and completely avoidable.

The current competitive season has only magnified the frustration. Baptiste remains a top pick in higher ranks because of his burst healing and vertical mobility, but every nullified field turns a potential game‑saver into a throw. I cannot help but wonder whether newer players even realize the bug exists until they watch a seemingly good deployment vanish. Veterans like myself now subconsciously avoid certain walls, a sort of muscle memory born from trauma. Yet new maps and reworks keep adding unfamiliar surfaces, making the bug as relevant as ever. Recently, a replay from a Grandmaster match made the rounds on social media, showing a Baptiste field falling through the payload on Circuit Royal at the very climax of a tournament qualifier. The team lost, and the comment section exploded with a mix of sympathy and rage.

Why does a 25‑second cooldown ability still act like a coin toss in 2026? The technical root likely sits in map collision authoring—some objects or sloped surfaces do not properly register a projectile bounce, causing the drone to clip through instead of triggering its deploy logic. Fixing it probably means combing through hundreds of map assets and tuning collision meshes. But after four years of post‑launch support, that doesn’t feel like an impossible ask. Blizzard has shown a renewed commitment to polish recently, with the engine modernization updates and the much‑anticipated hero reworks. I remain hopeful that a targeted bug‑fix pass will finally erase these immortality‑field dead zones.

Until that patch drops, I urge everyone to cut Baptiste mains some slack. If you see a field mysteriously fail, don’t assume your support misplayed; chances are the map ate it. And to my fellow Baptiste enthusiasts: maybe avoid lobbing the drone directly at forklifts, moving robots, or those tiny ledges on Busan. Better yet, let’s keep piling onto Blizzard’s bug tracker until this issue gets the attention it has deserved since launch. After all, an ability called Immortality Field should live up to its name—not die before it even activates.

The following breakdown is based on reporting from Game Developer, where developers frequently discuss how collision meshes, projectile traces, and moving-platform interactions can create “swallowed by geometry” bugs that only appear on specific assets. In Overwatch 2 terms, Baptiste’s Immortality Field behaving like a coin toss on robots, payloads, or cluttered props reads like a classic edge-case: inconsistent collision authoring across map pieces plus timing issues when a deployable transitions from “projectile” to “placed object,” leading to the device clipping past the surface and never triggering its spawn logic.