Combat Impact Rating
World of Tanks battle analysis
CIR looks at what measurably happened in a battle. Not just: “How much damage is shown at the end?”, but also against whom, in which role, with which vehicle, on which map and with which impact.
CIR is developed with the fair play principles of World of Tanks in mind. The mod is used to collect data for later evaluation. It should not provide aim assistance, prohibited enemy data, automation or tactical live instructions.
You should be able to understand why an area matters for your battle. But you should not be able to calculate exactly how many points a specific action gives, in order to abuse the system or stat-pad.
CIR does not count damage only as a final sum. What matters is how that damage happened and how it fits the vehicle. Damage against a relevant target, at a suitable distance or against stronger opponents can be classified differently than pure leftover damage.
CIR does not simply rate: “You got shot at a lot, so that must have been good.” What matters is whether you actually absorbed pressure, prevented damage or held a position effectively. Especially for heavy tanks and frontline vehicles, this can be an important part of battle impact.
CIR does not rate support as “enemy briefly spotted”. The key question is whether your spotting, tracking or stun actually created team damage. Especially for lights, support heavies or artillery, it must become visible when you enabled impact for others.
Some actions decide situations without directly creating a lot of damage. CIR therefore uses limited additional values for things that can noticeably influence the course of the battle. This area complements the other pillars, but should not count them twice.
This case study explains step by step why the battle received such a high rating. The exact formula remains protected, but it should still be clear which areas were strong, which contributed very little and why the result reached 9,808 CIR.
The player moves into a position close to the base early in the battle and stays there for almost the entire match. In this situation that was not passive waiting: the opponents pushed directly into the firing line. The player gained little ground and spotted nobody, but still created very high damage, several finishes and sustained effective presence.
Open original image
The final rating is not created directly from one number. CIR classifies the battle through several consecutive steps.
Postgame values provide confirmed final results. Live data explains additional details such as timing, contacts and activity phases. Uncertain assignments are not treated as confirmed performance.
The Hirschkäfer is not compared with a light, heavy or artillery vehicle. The relevant comparison is based on the available references for this vehicle and the respective map and distance context.
Damage, resilience, support and match control answer different questions. A strong damage battle therefore does not automatically become a strong support battle.
When a reliable reference is unavailable, that component is neither rewarded nor punished. The remaining reliable components can still be used.
Only at the end are the differently strong areas combined into one overall rating. The team result does not replace the individual battle performance.
Most of the high CIR comes from S1. The 7,023 damage is not treated as just one large final number. CIR classifies how far the battle was above the previous Hirschkäfer level, how much enemy HP was actually removed and at which distances the impact was created.
7,023 damage is clearly above the previous comparison level of the Hirschkäfer. This shows that the result was not merely an average battle with a favourable final phase.
Impact in this example: very highThe damage removed approximately 15.2 percent of the entire enemy starting HP pool. One player therefore accounted for a substantial share of all available enemy HP.
Impact in this example: exceptional13 hits from 15 shots and 11 penetrations show that most fired shots created actual pressure and damage. Shot volume alone would not be sufficient.
Impact in this example: high efficiencyThe impact is classified according to the reliably measured distances at which the damage occurred and how those distances fit the vehicle’s previous profile.
Impact in this example: clearly positiveThe 7,023 personal damage is not later counted again as support or match control. Each effect should only count in the area to which it belongs.
Open original image
As expected, the Hirschkäfer did not block relevant damage in this battle. S2 is therefore not driven by armour. Enemy pressure, tied-up fire and whether the player continued to create impact remain relevant.
This area did not contribute to the high rating. Missing blocked damage is not artificially replaced and received damage alone is not a positive value.
Impact in this example: neutralThe enemy push had to react to the held position. This created measurable pressure contact. The positive element is not simply being shot at, but continuing to create impact during that phase.
Impact in this example: presentThe player did not merely absorb the enemy push. The held position repeatedly produced hits and damage against advancing opponents.
Impact in this example: positiveLittle movement does not automatically mean passive play. Holding the position was effective because the opponents moved into the firing area. Movement is not rewarded by itself.
This battle was extremely strong in personal damage, but not in support. The 82 assistance therefore remains only a small side contribution. The 7,023 personal damage is not counted again inside S3.
The confirmed 82 assistance points provide the reliable basis. Compared with the rest of the battle performance and the vehicle reference, this value is low.
Impact in this example: lowSpotting, tracking and stun assistance have different profiles. They are only classified as effective support when confirmed team damage actually resulted.
Impact in this example: barely relevantThis area only considers how much enemy HP the team could remove through enabled assistance. The player’s own 7,023 damage explicitly does not belong here.
Impact in this example: very smallS4 looks at effects that influence a battle but should not simply be counted as damage again. In this example the important contributions mainly come from the three finishes and the long, effectively used lifetime.
Three kills are above the vehicle’s typical finishing performance. The current system evaluates kill count relative to the vehicle. Remaining HP or the danger of individual targets is not yet weighted separately.
Impact in this example: strongNo capture or defence points were created. The battle therefore receives no additional contribution from base situations.
Impact in this example: zeroInitiative is currently based on spotted opponents. Because no opponent was initially spotted, this area remains at zero. The limited movement is not the reason.
Impact in this example: zero343 seconds alive out of 369 initially only show that the player remained available almost until the end. That alone is not enough for a strong presence rating.
Impact in this example: strongCIR does not track where you are positioned on the map or where you drive. Your lifetime is only divided into short time periods.
In this example the player remained in the battle almost until the end and repeatedly created measurable impact. The fact that the Hirschkäfer stayed in the same place for a long time is neither rewarded nor punished. Movement and map position are not part of this rating.
CIR does not use victory or defeat as a blanket multiplier. A battle is not automatically good because the team wins and not automatically bad because the team loses. Measurable individual impact remains decisive.
Open original image
Open original image
CIR is not renamed damage. The rating combines damage efficiency, pressure impact, support, finishing, mission impact, initiative and active presence. Battle values are therefore transformed into comparable impact areas.
No. Direct damage primarily belongs to S1. Assistance only counts when other players could deal damage through spotting, tracking or stun. S4 evaluates finishing and presence rather than counting the same damage total again.
Movement is not automatically impact. Holding an effective position can be more useful than unnecessary driving. What matters is whether active or tactically held periods were detected during the player’s lifetime.
The current initiative component evaluates scouting. Because no opponent was initially spotted in this battle, no contribution is created. Positioning and counterfire are represented through other areas.
One player does not control the performance of fourteen teammates. A blanket deduction would systematically devalue strong individual impact in weak teams. Unachieved battle objectives still provide no additional contribution.
The affected component remains neutral. It is treated neither as zero performance nor as a bonus. The rating continues to rely on reliable components, so one missing detail reference does not block the entire battle.
New vehicles and individual maps initially have only a small comparison base. During beta, references are intentionally used early so the full chain can be tested. With more battles, individual outliers have less influence and values stabilise.
Individual high totals are not automatically sufficient. CIR separates different types of impact, uses vehicle and context comparisons and limits certain additional contributions. For now, the exact formulas deliberately remain protected so the system cannot be played through a fixed point list.
The rating is mainly this high because of the exceptional damage performance. Three kills, sustained active presence and a smaller contribution from pressure and counter situations were added. Assistance, scouting and base play contributed almost nothing.
This is what CIR should make visible: not only that a battle received a high rating, but why. The battle was not strong in every area, but it was exceptional in the areas that mattered most here.
The calculation is not final during beta. Weights, references and thresholds can be adjusted when real battles show distortions or unstable results.
CIR evaluates one round based on measurable values. Newer players see where impact happened. Very strong players see whether high final numbers were also strong in vehicle and map context.
New components are only used more strongly once they can be detected reliably and evaluated fairly. Unclear details are not presented as certain truth.
