Hey everyone, we’d like to jump in regarding reports from the dev.
This situation is effectively a miscommunication on our part — a lot of reports have been marked ‘Not a Bug’ on our report site, this is not strictly the case and we’d like to clarify the process and situation.
The ‘Not a Bug’ tag is used when a report can’t generally be forwarded, this is especially the case for vehicles on the dev server. Vehicles that are on the dev server often have preliminary attributes which will be changed by the time the vehicle releases. The dev server is there for testing purposes of course, and we appreciate all of your reports on currently incorrect elements, but it’s often the case that values that’re incorrect on the dev server are already in the process of being fixed before any reports come in, in these cases the report is given the same label.
This doesn’t mean the issue reported is not considered as a general bug though despite the tag, we can absolutely understand the confusion and frustration here, we’ll be improving our tags and our communication on the site in general to reflect this.
Our team have to process a huge number of reports especially during busy times like this. In order to forward all of the reports that are able to be forwarded, the reports that can’t be forwarded need to be filtered out quickly. This has led to a large number of reports being marked as ‘Not a Bug’ with no explanation given, this is a consequence of having to deal with a huge amount of reports in a very short time frame, but nevertheless is something we will be clarifying more effectively going forward.
As a final note, we understand the issues that can arise from ambiguity in this case, but please don’t use that ambiguity as a drive to harass members of our team, or in the community as a whole. Our moderators are not gatekeepers, they are just trying to filter usable reports as quickly as possible.
Going forward we’ll be improving clarity on our community bug report site in all respects, as always thank you for your attention here and helping us improve the game.
Furthermore, a comment from our developers about the armour protection of modern tanks and reports regarding this issue
We’ve seen a lot of your comments on the T-90M and spall lining — we plan to add anti-fragmentation lining to other tanks as well, for those we have enough information on. At the moment we have reliable data about the lining on the later versions of the Leopard 2 (and the Swedish versions), M3A3 and M1128. We’re currently working on the spall liners for these other vehicles, those that aren’t ready for the major update will be introduced a little later, likely in one of our weekly updates.
Also, the current parameters of the lining is not final, we plan on making it destructible, so after a successful penetration it’s considered destroyed and won’t offer any protection.
As for processing reports regarding the protection of modern tanks, our current approach is described in detail here: [Development] Reports concerning the protection of post-war combat vehicles - News - War Thunder
In the near future (before the release of the major update) we will update the tank protection tables linked in the article above and add all of the tanks from the major update to it. This way you can compare the current armour values with the expected values.
