Direct answer: Use tanks as a durable frontline and pressure tool, not as a complete army. The public description confirms vehicles, but current tank names, statistics and counters must be verified in the current build.
What the sources support
Dust Front RTS is described as including vehicles and military equipment produced through industrial systems. That supports a tank-focused role guide, but not an invented unit database. Treat any exact armor, range, cost or damage value as pending until a dated build shows it.
The strategic question is therefore where armored presence changes the mission. Tanks may hold a route, protect production, punish exposed positions or create time for infantry and other forces to work.
Position before commitment
Armor is most valuable when the route and objective are clear. Use terrain, sightlines and support routes where the current build provides them, and avoid sending the entire armored group into unexplored space. A tank force that loses information loses the advantage of durability.
Keep a retreat or replacement path. If the first engagement goes poorly, a damaged force that can return to support is more useful than a force trapped beyond the economy's reach.
Combine roles
Do not treat tanks as a replacement for information, screening or flexible response. Official material names infantry, vehicles and aviation as broad categories. Compose around the mission: a frontline element, a way to learn what is ahead and enough support to keep the force supplied or replace losses.
The best composition is scenario-based. A force for holding a resource route may differ from one for a mobile strike or base defense.
Production and economy
Vehicle production draws on the same industrial chain that supports structures and other military equipment. Before committing to armor, confirm the extraction and processing stages can sustain replacement. A successful attack that leaves the factory idle is a strategic loss delayed by a few minutes.
Use a short initial queue and observe input demand. Add capacity only after the first queue demonstrates a repeatable flow in the current version.
When armor fails
Review the cause, not only the outcome. Was the force surprised? Did it lack support? Was the route too narrow? Did production fail to replace losses? Did the objective require mobility or information rather than durability? Each answer points to a different correction.
Avoid translating a single video result into a universal counter chart. Version, map and mission conditions can change the value of the same unit.
Tank test notes
For a useful tank page, record the build, unit name, cost, production time, movement, engagement behavior and a comparison against at least one other role. Add screenshots or clips that show the interface and context. Until those observations are available, keep advice role-based.