Skip to content
Dust Front RTS Guide
Menu

Updated demo records: Deployment

Checked: — build 26104922

Use the current settings below when comparing this entity. The earlier text and its tactical conclusions remain historical; their values are not assigned to this build.

The object expands into a static object. In static mode, it folds back into a mobile object.

Activation / Reload, seconds
3.7
Carriers / 1
MCV
Carriers / 2
Vehicle "Buksir"

Some parameters and links remain uncertain. A missing value here does not establish absence of a game mechanic.

Compare the relevant cost, defence or support settings before applying an older recommendation. File settings do not establish battle results or a guaranteed counter.

Unreadable objects and an unresolved ability link prevent treating this as a complete measurement of every mechanic.

The previous comparison is retained below — build 26004785. The following dates and values belong to their own source.

Revision for the installed demo: Deployment

Current records — build 26004785

The current records below replace the older values for the same entity. The earlier text is retained separately as a historical version; its numbers and tactical conclusions are not claims about this version.

The object expands into a static object. In static mode, it folds back into a mobile object.

Ability activation settings

Reload, seconds: 3.7

Linked carriers

1. MCV

2. Vehicle "Buksir"

When choosing or using this entity, compare the current settings shown here with the situation in your demo. File values alone do not measure battle results, simultaneous ability activity or a guaranteed counter. Earlier advice that depends on changed values remains historical until checked again.

The historical edition is retained below — build 23882143. Its earlier values must not be carried into the current version.

The historical edition is retained below — build 23882143

This Deployment entry uses the description “The object expands into a static object. In static mode, it folds back into a mobile object.” from build 23882143. It is linked to both the MCV and TRM Silach, so its internal name should not be read as an exclusive assignment to a single vehicle. The linked placement components record the static and mobile states and the ground required by the objects. This supports relocation, but does not establish identical production behaviour during the transition. Compare the MCV and TRM pages before treating their roles or deployment choices as interchangeable.

The MCV costs 1 000 minerals and has 1 900 base hit points with 15 armour in build 23882143. Its entry describes base construction and links to production as well as a security call. The same armour value, 15, appears on the Combine, whose price is 100 minerals, but this comparison does not rank their strategic value. The MCV’s role comes from its construction functions, not from being the sole producer in the files. Read its full page for the buildings it can create and its additional resources.

Relocating the MCV changes where you can organise base construction. Its 1 000-mineral price and 15 armour make the route worth checking before moving into danger. The deployment description allows folding back, while the linked components contain placement checks; neither establishes a safe transformation time. The vehicle also has a security call in its data, so a missing ordinary weapon entry does not mean it has no means of support. Compare the MCV’s construction and security pages when deciding how to protect the move.

An exposed MCV can be a useful target because of its construction role, but it is not automatically helpless. It has 15 armour and costs 1 000 minerals; the linked security call must also be considered. Its area-resistance coefficient is 0.2, which does not establish how much artillery damage it receives. The files inspected here do not define a vulnerability window during deployment or prove that every production function stops while moving. Check the MCV page and the defenders present before committing an attack.

Deployment — Updated demo records as it appears in the Dust Front RTS demo, from the game files of build 23882143

Deployment — Updated demo records

Confirmed Established — fromdocs/sources/demo/raw/AbilitiesRTS.AbilityConfig.json / McvDeploy, build 23882143

What it is

This Deployment entry uses the description “The object expands into a static object. In static mode, it folds back into a mobile object.” from build 23882143. It is linked to both the MCV and TRM Silach, so its internal name should not be read as an exclusive assignment to a single vehicle. The linked placement components record the static and mobile states and the ground required by the objects. This supports relocation, but does not establish identical production behaviour during the transition. Compare the MCV and TRM pages before treating their roles or deployment choices as interchangeable.

Where it comes from

The MCV costs 1 000 minerals and has 1 900 base hit points with 15 armour in build 23882143. Its entry describes base construction and links to production as well as a security call. The same armour value, 15, appears on the Combine, whose price is 100 minerals, but this comparison does not rank their strategic value. The MCV’s role comes from its construction functions, not from being the sole producer in the files. Read its full page for the buildings it can create and its additional resources.

How it is actually used

Relocating the MCV changes where you can organise base construction. Its 1 000-mineral price and 15 armour make the route worth checking before moving into danger. The deployment description allows folding back, while the linked components contain placement checks; neither establishes a safe transformation time. The vehicle also has a security call in its data, so a missing ordinary weapon entry does not mean it has no means of support. Compare the MCV’s construction and security pages when deciding how to protect the move.

How to beat it

An exposed MCV can be a useful target because of its construction role, but it is not automatically helpless. It has 15 armour and costs 1 000 minerals; the linked security call must also be considered. Its area-resistance coefficient is 0.2, which does not establish how much artillery damage it receives. The files inspected here do not define a vulnerability window during deployment or prove that every production function stops while moving. Check the MCV page and the defenders present before committing an attack.

Values read from game files · version 23882143

← All abilities