How to read the catalog
Provider
Owns a complete gameplay loop: it can start and operate without VVV. Examples: STWSnipers, STW Anti-Air Team, STW Combat Zone and STW Bases.
Shared API
Defines a neutral contract. It does not create the gameplay by itself. STW Combat Support API is the shared request/provider contract used by support features.
Soft companion
Optional source content or behavior. The provider detects it and adds the capability when available; the base provider continues safely without it.
Bridge / adapter
Connects two providers. It must be installed deliberately because it is useful only when both sides of its contract are present.
Support and awareness graph
This is the important relationship behind Combat Zone and Anti-Air Team. Combat Knowledge can observe eligible AI reports, decide whether support is appropriate, and submit a request through the shared API. The support provider still owns the final validation and execution.
Key distinction: Combat Knowledge decides from information it genuinely received; Combat Zone creates and manages a zone; the adapter is what connects those two. None of this requires the VVV campaign.
Expanded capability catalog
| Provider / connector | Classification | Standalone? | Important companions or integrations |
|---|---|---|---|
| STW Anti-Air Team | Independent provider | Yes | Creates manual or automatic AA gunner/assistant pairs. Optional RHS Status Quo, RHS Content Packs 01/02 and Nasty Glock 18C add equipment or faction-aware candidates; absent content falls back or is skipped. |
| STW Combat Zone | Independent provider | Yes, for manual/Game Master zones; automated integration uses the listed companions | STW Combat Support API + STW Combat Knowledge + STW CombatZoneCKnowledgeAdapter are the documented automated stack. Combat Zone itself is independent of STWCQB and STWDAC. |
| STW Combat Knowledge | Independent awareness/policy service | Yes, but it needs support providers for visible effects | STW Transport Helipads is required for automated Helicopter Assault. STWSnipers is optional and changes sniper/spotter contact policy when present. |
| STW Combat Support API | Shared contract | No visible gameplay alone | Used by integrating providers such as Combat Zone, Armored Spawner, Heavy Weapons and helicopter support. |
| STW Snipers & Spotters | Independent optional provider | Yes | Combat Knowledge optionally recognizes its managed roles and applies shorter contact memory/lower automatic-support priority. |
| STW Transport Helipads | Independent provider | Yes | Vanilla UH-1H and Mi-8MT Transport are baseline aircraft; optional aircraft sources appear only when prefabs and their dependencies load. Required by Combat Knowledge automated Helicopter Assault. |
| STW Armored Spawner | Independent provider | Yes | Combat Support API is the shared contract for Armored Support. Vehicle-content mods are soft dependencies. |
| STW Heavy Weapons | Independent provider | Yes | Can expose mortar support through Combat Support API. D&C and Stronghold bridges are optional. |
| STW Bases Generator | Independent provider | Yes | STWBasesDACIntegration optionally translates D&C ownership/frontline data. STWBasesCratesIntegration optionally connects base lifecycle to Crates. |
| STW Divide and Conquer | Independent campaign provider | Yes | Combat Knowledge is recommended, not hard-required. VVV is the packaged ecosystem around this campaign core. |
| STW Combat Zone CKnowledge Adapter | Adapter | No | Requires Combat Zone + Combat Knowledge and translates accepted knowledge decisions into Combat Zone requests. |
| STW DAC Surveillance / Heavy Weapon bridges | Bridges | No | Require the relevant D&C and source provider contracts; they add cross-system behavior only. |
STW Anti-Air Team: administrator view
Anti-Air Team does not need VVV, Combat Zone or Combat Knowledge to create pairs. Its automatic system discovers terrain, deploys pairs, replaces casualties and can relocate survivors. Optional content is detected through available prefabs; missing RHS or Glock content affects only those loadout choices. Its declared required core content must still be installed as documented by the Anti-Air manual.
STW Combat Zone: administrator view
Combat Zone is also independent of STWCQB and STWDAC. It represents an active area, maintains a moving bubble around players, spawns groups outside the bubble, dispatches them toward it, and cleans up after the player group leaves.
- Standalone/manual: load STW Combat Zone and use its Game Master placement.
- Automated support: load STW Combat Support API, STW Combat Knowledge and STW CombatZoneCKnowledgeAdapter on server and clients.
- Decision flow: Combat Knowledge evaluates a real sighting; the adapter submits a capability request; Combat Zone validates faction, duplicate zones and provider limits; the server creates or updates the zone.
- VVV relationship: none is required. VVV/D&C can coexist, but Combat Zone is not the same thing as strategic CQB.
Example direct-install manifests
| Goal | Provider list | Optional connector/content |
|---|---|---|
| AA defense only | STW Anti-Air Team + its declared required dependencies | RHS content / Nasty Glock only if desired |
| Automated Combat Zones | STW Combat Zone + STW Combat Support API + STW Combat Knowledge | STW CombatZoneCKnowledgeAdapter |
| Snipers with support awareness | STWSnipers + STW Combat Knowledge + STW Combat Support API | Transport Helipads if automated Helicopter Assault is enabled |
| VVV-style campaign | STWVeniVidiVici / D&C + selected VVV extensions | Combat Knowledge recommended; bridges/adapters only for external systems |
Return to the administrator assembly guide or the VVV ecosystem overview.