War Thunder corrects aircraft ratings—but the battle mode matters
The October 30 server patch adjusts specific aircraft and modes, plus one F-102A weapons combination.
War Thunder’s October 30 server update corrects several Battle Ratings that did not match the final table of planned changes. The important detail is the game mode: the same aircraft does not receive an identical adjustment everywhere.
Gaijin’s official server-update notice identifies three groups of corrections and a separate weapons-loadout restriction. It is a targeted maintenance update, not a new vehicle release or a comprehensive rebalance of every aircraft.
Read the mode beside the number
The Chinese F-16A MLU moves from 14.0 to 13.7 in Air Simulator Battles. The Hawk T Mk 1A and its FRP version move from 7.7 to 7.3 across Air Battles modes. The N1K2-J, N1K2-Ja, Spitfire F Mk XVIIIe and Yak-3U move from 6.7 to 6.3 specifically in Ground Realistic Battles.
| Aircraft | Mode named in the notice | Correction |
|---|---|---|
| F-16A MLU, China | Air Simulator | 14.0 → 13.7 |
| Hawk T Mk 1A, including FRP | All Air Battles modes | 7.7 → 7.3 |
| N1K2-J, N1K2-Ja, Spitfire F Mk XVIIIe, Yak-3U | Ground Realistic | 6.7 → 6.3 |
The table is useful precisely because “this plane went down” is incomplete information. Someone preparing an Air Realistic lineup should not apply a Ground Realistic correction to it. The notice describes alignment with the already finalized table, rather than announcing a new rationale for each aircraft’s rating.
A loadout change is separate from matchmaking
Gaijin also adds a restriction on using AIM-26B and FFAR concurrently on all F-102A variants. That concerns the weapons combination, not a Battle Rating change listed for the aircraft. A remembered loadout and a remembered matchmaking value are different things to recheck after this update.
The developer notes that server-side changes may not require a client download and that the published list covers key changes rather than every improvement. An absent large download therefore does not establish that nothing changed.
For this patch, the useful check is small and specific: inspect the affected aircraft in the mode you actually play, then verify the loadout separately. The corrected number only becomes meaningful once it is attached to the right battle.
