Cheats are fine until they quietly disable something you cared about, which is why the consequences matter.

Short answer

Most are toggles: entering the same code again turns the effect off.

  • Expect achievements to lock for that save file.
  • Save manually before using anything irreversible.
  • Write down what you changed, so you can undo exactly one thing if it goes sideways.

War Thunder models more of the vehicle than it tells you about, and the grind punishes guessing. A code that softlocks a mission is a known risk in more than one of these games. Codes typically do not persist through a reload, which surprises people who use them for convenience.

Codes that no longer work

None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. Achievement locking is usually per-save rather than per-account, but not always. Anything that requires downloading a program is not a cheat code. Treat anything stated without a version number as provisional.

Some effects stack in ways the developers did not intend and the game does not handle gracefully. Case and spacing matter more than the lists suggest. There is no hidden trick here that the game is keeping from you.

Anything promising online effects

Console entry uses button sequences with tight timing, and mistiming reads as a broken code. If your result differs from what is described here, note what is different first rather than starting over. Most of the disagreement you will find online is two people describing different builds.

  • Never enter anything into an online mode.
  • Enter codes exactly, including spacing.
  • Give a method one honest attempt before deciding it does not work.
  • Re-enter the same code to toggle an effect off.

How to enter them

Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts. If you are coming to this after a long break, the terminology has probably moved on. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing. Everything below is framed around the current state of War Thunder rather than a launch-week impression.

The community wisdom on this is roughly half right, and the half that is wrong costs the most time. The short version is near the top on purpose; the reasoning is there if you want to know why. Anything that behaves differently on console than on PC is flagged where it matters.

What each one actually does

Where two approaches both work, the one with fewer moving parts is the one to keep. Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. The developers have changed their mind about this at least once, which explains the older advice.

Where something depends on your platform or region, that is called out rather than glossed over. Do the cheap check before the expensive one — that ordering alone saves most of the frustration. What follows assumes you are on a current install and have not modified it.

What you give up

It helps to understand why a step exists, because then you can adapt it when your situation is slightly different. Screenshots age faster than text, which is why this describes rather than shows. A single check up front replaces a lot of guessing later.

Where people go wrong

  • Changing five things at once and then not knowing which one helped.
  • Treating a rare edge case as the normal behaviour and planning around it.
  • Grinding a method that was patched months ago because a thread still ranks well.

War Thunder FAQ

Do I need any mods or third-party tools for this?

No. Everything described here works with the base game on any supported platform.

How long does this take?

Minutes if it goes cleanly, an evening if you hit the edge case in the caveats list. Neither is unusual.

Why is a code not working?

Either it belongs to an older version, or the entry method differs on your platform. Both are common.

Why do other guides describe this differently?

Most were written for an earlier version and never revisited. Compare the steps against what your build actually shows.

Bookmark it if you like, but honestly, once you have done it once you will not need to come back.