How to Count Training and Battle Requirements Across Digimon Growth Stages
On a Digimon Original (Ver.20th), track training and evolution battles separately for the current stage: training advances effort, while battles toward a stage requirement must be completed before that stage’s evolution timer expires. The exact rules depend on the device. For example, the original Version 3 guide says training and care counters reset when a Digimon evolves, but battle counting works differently. Check the guide for your specific model, then keep a fresh count after each evolution.
Start by identifying the device and the next evolution
“Digimon virtual pet” covers devices with different evolution rules. The steps here focus on two documented examples: the Digimon Original (Ver.20th), using its manual and evolution guide, and the older Version 3 virtual pet. They illustrate why a single rule cannot safely be applied across the series. If you have a Pendulum, Digital Monster Color, or another model, use that model’s own manual and evolution chart instead.
First, identify the device name and version. Then find the current Digimon on its evolution chart and read the requirements for its next stage. Record each condition separately: training sessions, battles, wins, care mistakes, or other requirements. A number shown for one evolution route may not apply to a different Digimon, even at the same stage. The Ver.20th guide, for instance, lists 15 battles and 12–15 victories for many Stage IV-to-V routes, while its earlier-stage routes can depend on training and other conditions. Ver.20th Evolution Guide
Know which counters are being measured
Training is not the same as battles. On the Ver.20th, each training session adds a quarter of an effort heart, whether the session succeeds or fails, so four sessions make one effort heart. Training also serves other purposes, such as adding strength when successful. The evolution chart may call for a specific number of training sessions, so effort hearts are a useful cross-check but not always an exact substitute for counting sessions. Ver.20th User Manual
Battles have their own record. For the Ver.20th, the manual describes a battle record based on wins compared with losses, and says a high win percentage and at least 15 battles are needed for Stage V. Many routes in the evolution guide express that as 15 battles with 12–15 victories. Count the battles and wins separately; reaching 15 total does not by itself satisfy a route that also requires enough wins.
Use an evolution as your counting checkpoint
For a practical rule, treat each evolution as a new checkpoint unless your model’s guide says otherwise. On the Ver.20th, the evolution guide gives a time to the next stage—24 hours from Stage III and 36 hours from Stage IV, for example—and its routes state the conditions for the next evolution. That makes it useful to begin tracking the route’s requirements as soon as the Digimon reaches a new stage, rather than assuming earlier training or battles automatically carry forward. Confirm the timer and conditions against the entry for your Digimon. Ver.20th Evolution Guide
The older Version 3 guide states the reset rule explicitly: counters other than battles reset when the Digimon evolves. It also gives a stage-specific battle rule for Perfect evolution: at least 15 battles at either the Child or Adult stage as a minimum, with 15 at both stages described as improving the chance. This is a clear example of why “start over after every evolution” is not a universal battle rule. Follow the stated counting window for your model and route. FileIsland: V-Pet Version 3
Keep a simple stage-by-stage ledger
Write down the stage, the evolution target, and the exact requirements before you begin counting. A paper note or phone note works; the device may show some status values but may not expose a complete training-session tally. Use one line per stage, and do not add unverified actions to the totals.
| Stage | Training sessions | Battles | Wins | Next requirement / check |
|---|---|---|---|---|
| Current stage | tally each session | tally each completed battle | tally wins separately | Copy from this Digimon’s chart entry |
| After evolution | start a new tally when the rule resets | continue only if the model’s rule says battles carry across stages | update with eligible wins | Recheck timer and next route |
This layout prevents three common errors: treating effort hearts as a perfect training counter, confusing training with battle totals, and carrying a counter forward without evidence. For the Ver.20th, make a mark for every training session even if it fails, because unsuccessful sessions still add effort. For a battle requirement, record a completed battle and its outcome, rather than counting training or a battle attempt that did not finish.
Plan battles around both total and win requirements
If the route calls for 15 battles and at least 12 wins, stop to check both figures as you go. After 15 battles, 12 wins meets that listed condition; 11 wins does not. The Ver.20th chart commonly shows 12–15 victories alongside 15 battles for Stage V routes. If you have fewer than 15 battles, the win percentage alone is not enough. Ver.20th Evolution Guide
Before battling, check the device manual for prerequisites such as available stamina or strength. The Ver.20th manual says battles require DP and describes strength as a factor in battle performance. These affect whether and how effectively you can battle, but they do not replace the route’s required number of battles or wins. If a device’s records are unclear, note each completed result yourself and compare it with the chart’s stated requirement.
Check the rule when a counter seems wrong
If an evolution does not happen, first verify that the correct route and device version are selected. Then check whether the timer has elapsed, whether the required count belongs to the current stage or a specified earlier stage, and whether a separate win threshold applies. Finally, confirm what qualifies as a counted training or battle on that model. The Version 3 reference, for example, distinguishes training counts by version: on Versions 2–5 only successful training counts toward evolution, whereas its Version 1 notes that even a failed or cancelled session counts. Do not transfer that rule to another device. FileIsland: V-Pet Version 3
A reliable routine is straightforward: identify the model, copy the next-stage requirements, start a ledger at the counting point stated by that model’s guide, and check totals before the evolution window closes. Keep training, battles, and wins in separate columns. That small habit makes it much easier to tell whether a requirement is complete—and avoids mistaking one device’s stage rules for another’s.