The administrator’s build model
VVV is a campaign framework and convenience family. It is not a requirement for every STW feature. Start with the feature you want, install its provider, and add only the integrations that have both sides present.
Example: a server wanting sniper teams and transport helicopters can install STWSnipers + STW Transport Helipads and the selected aircraft sources. It does not need STWVeniVidiVici, VVV Bases, VVV Reinforcements or Full Edition.
Direct-install catalog
| Package | Classification | Works without VVV? | Administrator meaning |
|---|---|---|---|
| STWSnipers | Independent optional gameplay mod | Yes | Owns sniper/spotter loadouts, automatic pairs and intelligence reports. VVV is not needed for its standalone feature. |
| STW Transport Helipads | Independent helicopter provider | Yes | Owns transport pads, route validation, autonomous flights and its own configuration. VVV does not supply its basic transport behavior. |
| STW Combat Helipads / Light | Independent helicopter providers | Yes | Own their combat-support behaviors. Add aircraft sources only when selecting their prefabs. |
| STW Helo Spawner | Independent helicopter population | Yes | Owns its own automatic helicopter population. It does not automatically become a VVV reinforcement system. |
| STW Bases Generator | Independent base provider | Yes | Can create bases without D&C. STWBasesDACIntegration is optional and adds D&C-aware placement. |
| STW Armored Spawner, Boats, Civilians, Zombies, Weapons, Clothes, etc. | Independent optional providers | Generally yes | Install their provider and declared dependencies. Do not install VVV merely because a scenario also uses VVV elsewhere. |
| VVV core and VVV extensions | Campaign family | Core is the base of the family; extensions target it | Use when you want the D&C campaign, VVV-specific objectives, reinforcement flow, aviation extension or bundled content. |
| Bridges and adapters | Connectors | Only with their contracts | They add a relationship; they do not replace either provider and are not a reason to install the whole VVV family. |
Helicopter mods and soft dependencies
A helicopter provider and a helicopter content source are different things. The provider owns the pad, route, sortie or spawn behavior. A content source contributes an aircraft prefab. The source is a soft dependency when the provider can run with other aircraft or with none selected.
- Transport Helipads soft aircraft sources: vanilla UH-1H and Mi-8MT Transport are available without an optional helicopter mod. Optional aircraft profiles appear only when their prefabs and dependencies are available.
- VVV Helicopters: is a VVV extension for campaign-specific aviation content. It is not a prerequisite for independent Transport Helipads or Combat Helipads.
- Multiplayer: the server and every client need the source mod for any selected aircraft. Missing soft content should remove only that choice, not invalidate the provider.
- Configuration: selecting a class name in a JSON file does not download or load its source mod. The mod list must supply it first.
STWSnipers is optional
STWSnipers is an independent optional provider, not a required part of the VVV foundation. An administrator can run it beside a VVV campaign, or run it in a completely separate scenario.
Without VVV
Sniper/spotter loadouts, automatic pair creation and intelligence reports remain STWSnipers features. Configure and test them through the STWSnipers manual.
Beside VVV
It can enrich the same battlefield with long-range teams, but “beside” does not automatically mean “campaign-controlled.” A specific bridge or integration is required for a cross-system contract.
With a missing content source
Optional weapon or faction content should be treated as a catalog choice. If its prefab is unavailable, use the provider’s fallback or omit that choice.
Safe administrator workflow
- Write down the desired capability, not the desired bundle.
- Install the provider and its declared hard dependencies.
- Run a small test scenario with only that provider.
- Add optional content sources one at a time; confirm server and client availability.
- Add a bridge or adapter only after both provider systems work independently.
- Publish a manifest with three columns: provider, optional content, connector.
- When removing a feature, remove its connector first, then its optional content, then its provider.
Return to the ecosystem overview
For the complete package map, bridge matrix and VVV extension explanation, return to the STW Veni Vidi Vici Ecosystem manual.