This is to clear up any confusion on any current ruling or confusion you may have with Gaijins enforced rules on bug reports.
I also have 0 affiliation with Gaijin but would like this all to be known to others due to the amount of hidden or largely unknown rules.
Bug Report Layout
Spoiler
You can lay your report out however you want but for efficiency and a speedy acceptance it it best to lay it out in the following,
-
Issue:
Describe briefly and very literally what the issue is, how to recreate the bug and what the expected outcome is. Include as much detail as possible however as it gives the devs more idea of what’s causing the issue. -
Vehicles affected:
Its important to list every vehicle in the game, including event or hidden, vehicles that are affected by said issue.
Its also important to list the file name of the vehicles, this is acquired by using the war thunder wiki, the file name is found in the URL. You can also find it through the data mines -
Source:
List each source included through full title, author, year of publication and ISBN numbers where applicable
Sources must be attached with full page images that are:
Not cropped
Legible
Not translated
Legal to share outside your own country
You must also either attach the full source (such as an entire manual) or the front cover of the source
- Fix:
This isn’t as important but it is recommended to include. Include a little line that states what the fix should be
Example image of a report:
Ensure to include game replays, Clog files and other relevant data when reporting an actual bug within the game. Historical issues rarely need this
Include the current game version (found in the top right of the hangar)
Generalised rules:
Spoiler
ENSURE THE SOURCE IS LEGAL
Official Statement on source material classifications
What is appropriate source material for historical issues?
- OEM Manuals (primary source): User manuals, repair manuals, factory manuals, operating manuals, technical manuals etc. Single source is required (preferred source).
- Authored works (secondary source): Reference books on collections of vehicles/aircraft/ships (‘coffee table books’), biographies, specialist books, “expert” opinion publications, industry magazines etc. At least two unrelated sources required.
Please be reminded that Wikipedia or other private websites are not considered reliable sources.
You need to provide the following information about the source:
- Title and if applicable: publication date, document number, ISBN.
- Author or organisation
- Image of the cover
- Images of all the referenced pages and their page numbers
- References for photographs
If you have found an actual bug within the game then please read the wiki article on bug reporting as it includes steps to ensure it is a bug and includes data on how to obtain certain files or bypass anti cheats
-
All Measurements are to be in METRIC with the standard for horsepower being Use Metric Horsepower (PS/ЛС/MHP) 1PS = 735.5 Watts (0.7355 kW)
-
3rd Party information such as WTRI, Datamines or statshark are forbidden to be used as sources and will have your report denied outright without a second thought.
-
The report website is only there for issues within the games code, if you are missing GE, your issues are to be directed towards the support tickets on the website. Any gripes you may have with the game, we all have them, are to be voiced on the forum without being rude to others. Apparently the devs do read the forum.
-
Reports must not be based on any assumptions and are mostly required to have fixed figures or similar to pass.
-
Ensure any armour reports are tested in game via custom game or another game mode
-
Ensure armour test are performed at the correct angle, some use 90 degrees as flat, some use 0 degrees as flat.
-
AP, APC, APBC, APCBC and APCR are all calculated Via the wiki Jacob De Marre
-
APFSDS is calculated via Lanz Odermatt, unless it is a composite apfsds (Most USSR apfsds are composite) in which the real pen figures are hard coded into the game as lanz odermatt cannot calculate the composite shell.
-
APDS is calculated via gaijins magic, we have no access to it so individual parts should be reported as one report if possible.
-
SAP uses a 0.46x multiplier of Jacob De Marre
-
SAPBC uses a 0.65x Multiplier of Jacob De Marre
-
HE, HEAT, HEATFS and HESH penetrations are reportable with real figures.
Aircraft specific rules:
Spoiler
Some rules are there for specific parts of an aircraft:
-
Jet Engine thrust sources must state that the figures given are for an engine installed inside of the aircraft. This is due to the airflow lost when installed and will therefore change the ratings of the engine.
-
When testing engine power ensure you are testing at the correct altitude and that you are reading the measurement at the speed given in your source, if no speed is given in your source then ensure that the plane does not reach that power at any speed at that altitude.
If the source states the engine is static but it is installed then proceed to gently press the nose of your aircraft into a building and test from there as you will not move. -
The maximum speed of an aircraft is given in IAS, in game there is a multiplier compared to official figures. For example the MiG-21Bis can only reach 1300kmh according to the manual but in game the number is multiplied by 1.05x and can now reach 1365kmh at sea level. Occasionally however Gaijin do a multiplier of 1.10 but that is up to dev discretion. This does not apply to components such as flaps or gear.
-
The maximum G limit of an aircraft is also multiplied in game, if a plane in a manual is stated to only reach 7Gs safely then it is multiplied by 1.5 to 10.5Gs.
-
Currently weight reports for aircraft are forbidden
-
Any weapon may be reported and passed as a suggestion for an aircraft as long as you can prove it is compatible with it within its current configuration.
Ground Specific Rules:
Spoiler
Some rules are there for specific parts of a ground vehicle:
-
Horsepower reports are to be based on Gross, DIN70020 / SAE outputs from the driveshaft itself
-
Autoloaders, as of 25/12/2025, are based on their “technical maximum reload speed” and are no longer sustained reload speeds
-
Gunners sight FOV Cannot be used for bug reporting, only Zoom
-
Unity (1x) sights are not modelled for the gunners, but are for Commanders
-
1.9-3.5x sight is the default sight for low tier vehicles with AWFUL sights or those with unknown sights
-
3 degrees/s is the placeholder elevation speed (when it isn’t known)
-
Shoulder Stabilisers are added for vehicles that are elevated and depressed via the gunner’s physical movements (no gearing / elevation drive)
-
Digital Zoom IS NOT used for ground
-
Some armour types are not included, such as FHA, and will require a suggestion on the forum.
-
Any reports for HHRA or similar must be proven not to be brittle. If it is then its modelled as RHA
-
Hull MGs are not modelled unless there are no other options for MGs or if the devs just decide to do it by themselves.
-
NVDs are not modelled below roughly 9.0, even if your vehicle had them
-
These are currently what excluded armour types are modelled as (Not in game → In game):
FHA → RHA
Naval Specific Rules:
Spoiler
Some rules are there for specific parts of a naval vehicle:
-
Most ships are based off plans and blueprints whether they made it out of that or not and so should be reported as such.
-
These are currently what excluded armour types are modelled as (Not in game → In game):
FHA → HHRA
Some issues you may come across:
Spoiler
-
Although you may disagree with the outcome of a report, the only solution is to message another technical moderator or above about it, do start with the lowest level first, any level jumping or ignoring the escalation procedure will result in delay in resolving your problem, however do be polite as they are just volunteers. Who is who and Reporting Procedure
-
If you disagree with the end result then all you can do is talk on the forums about it and see if you can garner enough attention for it to be changed, though extremely unlikely and once again please be polite about it.
-
A response from a tech mod or above does not mean that it is their opinion on the matter in all cases, they are simply told by the dev team what is and isn’t allowed and how things work
-
If you report one day gets implemented but its not what you had hoped it to be, it is usually because the source given states “at least” or “minimum” which the dev team will always go for as it is the only fixed number given
-
If your report is marked as fixed but isn’t, your only solution is to make another report.
-
If you make several reports with 0 difference in sources or text then you will just be banned or suspended given enough time.
-
Sometimes a report is denied for “balance reasons” your only solution is the forums, especially when the BR changes come around
-
You report may sit on accepted for a long time, we are coming up to nearly 10 years since the Centurion Mk V AVRE ERA report was accepted without fix.
-
If it was reported on the old forum and no new one has been created on the cbr since then the report is no longer considered and needs to be remade.
-
There are also different types of acceptance via the report team, a suggestion is not a guarantee it will ever be acted on as it is entirely down to balance. A small but not drastic change will likely be accepted and eventually added but no time can be given.
-
If a new vehicle of the class or type you have reported is being added then usually your report will be acted on, but mention it around to ensure its remembered.
-
A report can also be denied if the change is insignificant so ensure that you have done the metric conversions beforehand as the devs may miss it
If I have missed any rule then please let me know and I will add it ASAP, please also provide a pretty picture of someone within gaijin saying such and with a link preferably
Community Bug Reporting (CBR) Site
Last updated:
13/02/2026
