Log in
PUBG Mobile on GameLoop Beta: All Issues FixedThe latest EmuDesk Smart Tool update fixes all compatibility issues with GameLoop Beta including camera stuttering and delivers fully functional keymaps, including at 1080p and 2K.Get EmuDesk Smart Tool

CODM character stops taking damage after few minutes (TAC + Smart Tool) — known anomaly

HighTenstore Android ConnectCall of Duty: Mobile4 solutions

You launch CODM via the Smart Tool, queue into a match, play normally for a few minutes — and suddenly you stop receiving damage from enemies. Bullets visibly hit your character, kill cam shows enemy shots connecting, but your HP doesn't drop. Reported framing:

"I started playing CODM through GameLoopHUB because CODM simply won't launch through the regular GameLoop. After playing CODM through GameLoopHUB for a few minutes, the damage my character takes stops. What should I do about this?" — GlobalisTik

This is a confirmed anomaly with two possible interpretations:

  1. TAC physics / state desync bug — the emulator's networked state desyncs from CODM's server after the AMD time-drift kicks in, causing damage events to register on the server but not in the local client. (Same root cause as the AMD bullet-registration drift, but inverse — you don't take damage instead of not dealing it.)
  2. Anti-cheat detection trigger — Tencent's anti-cheat may be deliberately ignoring damage to flag your account as cheating, creating a fake "invincibility" before issuing a ban.

Both interpretations have the same fix sequence — and one of them (interpretation 2) makes this a genuine ban-risk situation requiring immediate action.

Last updated 8 weeks ago0 users reported this issue11
Sign in to interact

Solutions

Solution 1

⚠️ STOP playing immediately if you see this. Do not continue the match.

  1. Quit the current match (Esc → Exit). Do NOT use the in-game "Surrender" button — that creates a "leaver" record on top of the suspicious behavior.
  2. Close CODM completely.
  3. Close TAC via Task Manager (kill all TAC/AndrowsConnect processes).
  4. Don't relaunch for at least 4-6 hours. The damage-stop bug compounds in subsequent sessions if you play through it.

The reason for caution: even if interpretation 1 (TAC state bug) is correct, the server still sees damage events that don't register locally — to the server, you appear to be invincible, which matches "godmode hack" behavior in Tencent's anti-cheat heuristics. Even an innocent TAC bug can result in a temporary ban.

Jun 4, 2026
Was this helpful?0

Solution 2

Prevent the underlying clock drift via Hyper-V. Per the same fix as the bullet-registration drift issue:

  1. Win+R → optionalfeatures → enable Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform.
  2. Reboot.
  3. Hyper-V provides a clock reference TAC uses to stay synced with the host, eliminating the drift that causes both damage-stop and bullet-stop bugs.
Jun 4, 2026
Was this helpful?0

Solution 3

Report to the EmuDesk team in Discord. If this happens to you, ping #en-support-cod-mobile with:

  • Your TAC version (from Diagnostics log — see how to find it).
  • Your CPU model.
  • Whether Hyper-V is enabled or not.
  • How long you played before damage stopped.
  • Whether you got a ban (and how long) afterwards.

The EmuDesk team is collecting data on this anomaly to determine if it's TAC-side or anti-cheat-side. Your data point helps.

Jun 4, 2026
Was this helpful?0

Solution 4

Until the root cause is confirmed: limit sessions to 30 minutes max. The damage-stop bug doesn't appear in short sessions. If you must play, treat 30 minutes as a hard cap, then close TAC + Smart Tool entirely (not just CODM) before another session.

Jun 4, 2026
Was this helpful?0
Experiencing a different problem?Report a new issue to help the community find solutions.

Comments (0)

No other comments yet. Be the first to share your thoughts.

Sign in to_leave_comment

On This Page