WoT Marks Tracker: Battle Logs, Drills, and Session Planning

A battle log for Marks of Excellence is primarily a way to find repeated losses: an unproductive early trade, an empty sector, or a shot with no realistic penetration chance. The percentage tells you where the attempt is heading, but not which decision needs to change.

A useful tracker separates personal damage and assistance categories, records the vehicle configuration, and keeps a short note about the turning point. This lets you distinguish a poor position from poor execution instead of rebuilding your equipment after every defeat.

This method supports independent practice in Random Battles in Wargaming's PC World of Tanks. It helps organize attempts at one, two, or three marks without promising a result within a fixed match count.

What the mark tracks and what your log tracks

One, two, and three marks require a result higher than that of 65%, 85%, and 95% of players in the same vehicle. The system compares performance with the recent 14-day period and updates after a Random Battle. Marks cover Tiers V-XI; an earned mark stays with the tank if the percentage later falls.

Fifty battles in your table are a chosen training sample rather than a separate award rule. Official support describes personal performance through the last 100 battles. An average over ten, twenty, or fifty matches helps analysis, but should not be presented as the game's exact internal value.

For a mark result, personal damage is combined with the maximum assistance: spotting, immobilization, or stunning. Adding the three categories overstates your calculation. Keep them separate in the log even when one source normally dominates in your vehicle.

Columns to record after a battle

A small table is enough to start. Retain date and region so different benchmarks do not get mixed, and give the configuration a short, clear label. If you change gun, crew, or equipment loadout, begin a separate comparison.

The calculation for each row is straightforward: personal damage plus the maximum of the three assistance categories. With 1,800 personal damage, 900 spotting, 400 tracking, and zero stun assistance, record 2,700. A value of 3,100 incorrectly adds two assistance categories together. These are teaching figures, not a target for any particular tank.

After a block of 10-20 battles, add the correct results and divide by match count. For example, 27,000 over ten battles gives an average of 2,700. Do not average already averaged blocks of unequal length without weighting their match counts. Separately count how often you lost the ability to continue before taking your first useful action.

Compare decisions within your role

With a TD, closely review gun use: was there a firing line, room to turn, or a missed rotation? For a scout, examine allied gun support and preserved observation. Assess a medium or heavy according to its actual task rather than requiring equal personal damage and assistance.

Even identical averages can come from different behavior. Waiting for a losing flank may produce several convenient shots while depriving the team of timely support. Beside the number, record the decision point, its effect on the battle, and an available alternative rather than just “good” or “bad.”

Preparing a session and its budget

Choose one vehicle and one testable task. An hour to an hour and a half may suit you while attention holds, but do not make 60-90 minutes an obligation to continue through fatigue. Finishing earlier is more useful than trying to recover a lost percentage immediately through frustrated peeks.

Before starting, check suitable ammunition reserves. A special shell should address particular armor and angles rather than serve as a mandatory good-statistics button. Food is an option with a considered consumable setup and sustainable budget. First establish the cost of your normal play, then choose a loadout you can maintain.

Do not switch vehicles solely because two awkward maps appeared. Record why the opening failed instead. Change the task or end the session when decisions stop being attentive. Replace the claim that “night is always worse” with observations of your own fatigue and play quality.

Equipment, crew, and modifications

For a conventional-loading vehicle with a closed cabin and an available Stabilizer, a starting option is Rammer, Ventilation, and Stabilizer. A medium needing more independent view range can compare Ventilation with Optics. These are compatible-vehicle options rather than a universal triple for every TD and heavy.

A scouting option for a Tier VIII+ light or medium is Optics, Commander's Vision System, and Low Noise Exhaust System. Compare it with a firing loadout according to the task. Do not mount a Rammer on an autoloader or autoreloader, assume every vehicle has a Stabilizer, or ignore Ventilation restrictions.

Do not copy a perk order without considering roles and qualifications. In Field Modification, compare the benefit with its penalty, especially when trading accuracy, aiming, and other properties. An alternate loadout helps separate firing and scouting tasks in advance when available. Tier XI has its own Upgrades system, so a Tier X tree is not a ready-made answer for it.

Three maps as exercises rather than guarantees

Redshire. For a TD, choose a firing line with understood allied observation and an escape route. Record whether the target was actually visible and whether you could cause damage without exposing yourself to another sector. Do not assume every distant bush is automatically correct. Terrain, cover, and map events require checking in the current client.

Official illustration for the 2.4.1 map changes: check routes in the current client before repeating an old opening. This collage is not a recommended-position diagram.

Prokhorovka. If practicing central participation, first assess enemy scouting, allied support, and cover after detection. Record which sector you could spot or fire into and why you had to leave. “Take the middle” without an escape plan is not a mandatory opening for every tank.

Himmelsdorf. On a heavy-tank route, study a peek relative to allied and enemy guns: how many enemies can reply and who covers you? Do not repeat an old route solely from memory: released Update 2.4.1 adds a position and route for the southern team at H2, offering opportunities comparable to C3. This is a reason to inspect the western area rather than a promise of easy damage.

Use the first three minutes as a consistent replay checkpoint. Targets such as “1,000” or “2,000 by the third minute” can be personal training references rather than mark-system requirements. Retain cases with no useful firing line: they help identify when to reject a familiar opening.

Coordinate exposure with allied readiness: if the neighboring tank is reloading, it may not support your immobilization of an enemy. Choose an accessible penetrable area rather than relying on a random outcome. When frontal armor offers no reasonable shot, assess another angle or lane instead of repeatedly spending hit points on the same unsuccessful firing line.

Three drills for your next block

A ten-shot sequence

In a suitable practice setting, repeat shots at a selected accessible area from the same distance and angle. Record hits, penetrations, and your movement before firing. Then repeat with one controlled change. Ten shots are an attention and execution drill rather than sufficient evidence for an exact hit probability.

Tracking with a purpose

Practice suspension shots when penetrable armor lies behind the track and allies can use the stop. In the replay, check what happened: was the track broken, did you cause personal damage, and did allies hit in time? Tracking assistance does not automatically raise the mark total when another assistance category is already higher that battle.

A peek and a fallback position

Before the first trade, name the cover you will retreat to. After the battle, check which event should have triggered relocation: lost support, an open flank, or an approaching opponent. Leave early enough to retain further firing opportunities without abandoning a sector before assessing the consequences for allies.

A short review before the next attempt

• Did the opening provide observation or a shot, and which conditions helped?

• What was achieved during the first three minutes with assistance counted correctly?

• Which damage was genuinely available, and which required unjustified risk?

• When should you have rotated, and did saved hit points help in the finish?

• Which single adjustment will you test in the next block?

The client remains the place to check your actual percentage; the external table explains your decisions. If using a third-party tracker, retain its region and data date. Repeatedly fixing a lost firing opportunity is more useful than rewriting your target every battle to match the latest number you saw.