A Players Guide to Bug Reporting for War Thunder

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 my advice 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

  • My advice is that 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) in the report for efficiency
    A report where metric was stated to be the used number for HP

  • 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. Report where it happened

  • 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. WT Wiki page as source

  • Reports must not be based on any assumptions and are mostly required to have fixed figures or similar to pass.

  • My advice is to ensure any armour reports are tested in game via custom game or another game mode before posting a report

  • My advice is to ensure armour test are performed at the correct angle, some use 90 degrees as flat, some use 0 degrees as flat before posting a report.

  • 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
    These were calculated via experimentation with Jacob De Marre and may not be 100% accurate for all shells

  • SAPBC uses a 0.65x Multiplier of Jacob De Marre
    These were calculated via experimentation with Jacob De Marre and may not be 100% accurate for all shells

  • HE, HEAT, HEATFS and HESH penetrations are reportable with real figures.
    HEAT Report HE report

  • Advice for when reporting errors in a vehicle model, ensure that each error is itemized and well-documented with your photo evidence. Generally, the source of the photos is also required. (Direct quote from Kleinerpanzer, a normal player as of writing this)

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. Report where it happened

  • My advice when testing engine power is to 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. A report where this happened

  • 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. A report where it was accepted

  • 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. Major Update "Line of Contact" - Rumor Round-Up & Discussion (Part 2) - #555

  • Flight model reports reliant on external data, including local host, are forbidden and some types of reports will be refused outright Smin stating it is planned to change in the future as the mechanics are added to display it in game

Ground Specific Rules:

Spoiler

Some rules are there for specific parts of a ground vehicle:

Naval Specific Rules:

Spoiler

Some rules are there for specific parts of a naval vehicle:

  • My advice is that 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 → Rolled Cemented Armour Report that confirms this

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

  • My advice is 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. Next Major Update - Rumor Round-Up & Discussion (Part 1) - #314

  • My advice is 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 A report that was denied for such

  • 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.

  • My advice is if it was reported on the old forum and no new one has been created on the cbr since as it brings it up to modern standards

  • 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.

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 source or it will have to just be advice

If there are better sources for the rules or advice without proof of rule please send anything that could prove it as such

Community Bug Reporting (CBR) Site

Last updated:
13/02/2026

14 Likes

*included

which part is that in lmao

in the ground part

FHA is RHA for ground vehicles in game (See Pz III/IV)

1 Like

I like the compiling you have done here :)

Few notes (personal ones, i have no behind the scenes info):

Don’t start with seniors unless the regular Technical Moderators can’t help you, in that case they will add the Seniors themselves or you can ask for a Senior to be added. (My yellow highlight below)

image

( Source: Who is who and Reporting Procedure)

I would perhaps also add that even if a report is marked as “accepted” then there is a difference between a report being forwarded as a suggestion or forwarded for review or forwarded in general as stated by the bug reporting manager (i’m not entirely certain about the exact differences but i’m 99% sure there is a difference in the way a report is forwarded).

Yeah but the Pz IIIL has HHRA for some reason

(ive got a suggestion pending on that for differentiation, please suggestion mods)

image
image
image

6 Likes

in general anyway, FHA is RHA for ground vehicles

added, cheers

1 Like

Pro tip: The dev server period is the most critical window for bug reporting. Reports submitted during this period are usually treated as high priority and have a much greater chance of being reviewed and actioned quickly.

So, if you want a new vehicle to be completely modeled as accurately as possible, don’t wait or postpone your findings. Try to submit bug reports and collaborate with others while the dev server is still open.

New bug reports on older vehicles are far less likely to receive immediate attention unless they gain significant visibility, high upvotes, or broader community support.

2 Likes

Unfortunately, that use to be true, but i dont think it is anymore.

Plenty of things have been reported during the dev server for new vehicles and still not fixed months/years later.

Most recent of this that comes to mind and is totally unexcusable will be the Hawk 209 missing its radar fairly certain that report was submitted during the dev server

its true if its added in that update lol

I can think of plenty of reports that were reported during the dev server and have yet to be fixed, even if the vehicle was brand new. Like I dont think a single report for the Ajax has been fixed yet and many were reported during the dev server

same happened to the CV90 Mk IV but bc they do very little prior research they get flooded with reports

a few did, few didn’t

Dev server reports are taken more seriously but don’t guaruntee a fix (Just look at F-18E flight model reports lmao)

1 Like

Plenty of recent dev bug reports have been accepted and implemented, so yeah, unfortunately, some cases are not like this for several factors. That’s why I said “greater chance of being reviewed…” and never said “it’s guaranteed.”

This post was flagged by the community and is temporarily hidden.

There is an exception, no? Gear ratios via datamines can be bug-reported according to this Revision of gear ratio for 2s3m bug report.

I have opinions.

1 Like

Datamines are generally not permitted, Gear ratios are one of the VERY few exceptions

1 Like