STW Online Manuals · Start here

STW Quick Reference Guide

A short, friendly guide to the systems that make an STW scenario feel alive—and to what administrators should expect the first time they run one.

24/7 server friendlyFirst-run generationLow-end defaultsAdministrator reference

Combat Zone integration

STWCombatZone is an independent Combat Zone provider. STWCombatZoneCKnowledgeAdapter adds Combat Zone capabilities to STWCombatKnowledge, allowing Combat Knowledge perception and automated support decisions to issue Combat Zone support orders.

FPV drone modules

STWFPVDrone is the standalone server-authoritative drone system. STWSpecialForces assigns drones to Special Forces teams. The optional STWFPVDroneDACAdapter publishes player detections to DAC surveillance, while STWFPVDroneEnvironmentAdapter validates routes around forests and buildings.

STW FPV drone module dependency diagram

Dependency flow: STWFPVDrone → STWSpecialForces; STWFPVDrone → STWFPVDroneDACAdapter → STWDivideAndConquer, STWDACSurveillanceBridge and STWCombatKnowledge; STWFPVDrone → STWFPVDroneEnvironmentAdapter → STWDivideAndConquer and STWBuildingKnowledge.

Optional integrations and bridge mods

STWDivideAndConquer is fully usable on its own, but the complete STW campaign experience comes from combining it with the optional systems that populate the strategic map, create varied encounters, improve AI reactions, and connect battlefield support to territory ownership. Install the compatible projects on both the server and clients when you want these features.

Diagram of optional STW integrations and bridge mods

Recommended campaign companions

Optional reinforcement and battlefield providers

When bridge mods are needed

Bridge mods are only required when connecting an optional provider to the specific system named by the bridge. Use STWDACHeavyWeaponBridge when STWDivideAndConquer and STWHeavyWeapons should share territory-aware mortar management. Use STWStrongholdHWeaponsBridge when STWStronghold and STWHeavyWeapons should work together for Heavy Weapons checkpoint or support integration. Use STWDACSurveillanceBridge when STWDivideAndConquer and the compatible surveillance provider should share DAC territory or surveillance integration. Do not install a bridge when its two endpoint systems are not installed together.

None of these optional projects is required for the core campaign to start. However, installing the complete compatible set makes the strategic layer feel more alive: territory can influence encounters, reinforcements, defensive systems, artillery, surveillance, and AI reactions instead of existing as isolated features.

STW Mod Directory

Find each STW mod’s Workshop page and online manual here. STW Divide&Conquer Enhanced is documented in this guide because it is an add-on to the original STW Divide And Conquer.

STW modWorkshopManual
STW Divide And ConquerWorkshopManual
STW Divide&Conquer EnhancedWorkshopThis guide
STW Anti-Air TeamWorkshopManual
STW Air DropsWorkshopManual
STW Armored SpawnerWorkshopManual
STW Bases GeneratorWorkshopManual
STWBasesDACIntegrationWorkshopThis guide
STW Boats SpawnerWorkshopManual
STW ChoppersWorkshopManual
STW Civilians SpawnerWorkshopManual
STW Close Quarters BattleWorkshopManual
STW Combat Helipads LightWorkshopManual
STW Combat KnowledgeWorkshopManual
STW Combat Support APIWorkshopManual
STW CratesWorkshopManual
STW ExperienceWorkshopManual
STW Garbage SystemWorkshopManual
STW Heavy WeaponsWorkshopManual
STW Light Vehicle SpawnerWorkshopManual
STW Mine FieldsWorkshopManual
STW Parachute Spawn PointWorkshopManual
STW Snipers & SpottersWorkshopManual
STW StrongholdWorkshopManual
STW Tanks SpawnerWorkshopManual
STW Task CommanderWorkshopManual
STW Transport HelipadsWorkshopManual
STW Zombies SpawnerWorkshopManual

STW Bases, Crates and Divide and Conquer

STWBasesGenerator creates and persists faction bases, spawn points, arsenals and related base entities. STW Crates is a standalone crate system, while STW Bases-Crates Integration optionally creates or reuses a faction crate for each generated base.

STWBasesDACIntegration is a separate optional compatibility mod. It connects STWBasesGenerator to STWDivideAndConquer without making either core project depend on the other. It can restrict generated-base placement to D&C-owned or frontline cells, optionally use D&C shoreline cells in shoreline mode, remove a base and its associated entities when its cell is captured, and notify the Bases-Crates integration so the associated crate is removed too.

The Bases and Crates systems remain usable without D&C. The DAC integration is only needed when base placement and base lifetime should follow D&C territory ownership. Its profile configuration is stored at $profile/STW/DivideAndConquer/STWBasesDivideAndConquerConfiguration.json. Custom Bases factions, including RHS factions, can be mapped explicitly to D&C RED or BLUE in that file.

The STW Mods Complete Experience

STW Divide And Conquer is the foundation: it provides the strategic campaign and the front line that the other systems can build upon. STW Divide&Conquer Enhanced makes that experience better by adding optional strategic reinforcements and integrations with compatible STW addons. STW Combat Knowledge makes the experience complete by giving the battlefield a deeper sense of awareness, reaction and combat support.

Important installation note: STW Divide&Conquer Enhanced is an ADD ON. It does not replace STW Divide And Conquer. The original STW Divide And Conquer mod must still be installed and enabled on the server, together with the Enhanced addon.

Dependency diagram

1. STW Divide And Conquer

Required foundation for the strategic campaign.

2. STW Divide&Conquer Enhanced

ADD ON that enhances the original campaign. It requires the foundation above; it is not a substitute for it.

3. STW Combat Knowledge

Recommended companion that completes the tactical experience.

↓   Complete STW campaign experience   ↓

Optional compatible addons, such as STW Snipers & Spotters and STW Anti-Air Team, can provide additional battlefield activity when installed.

Recommended server setup

  1. Install and enable STW Divide And Conquer.
  2. Install and enable STW Divide&Conquer Enhanced.
  3. Install and enable STW Combat Knowledge.
  4. Add compatible optional addons when desired.

In one sentence

Divide And Conquer is the foundation, Divide&Conquer Enhanced improves it, and Combat Knowledge completes the experience.

STW Divide And Conquer workshop page

Working STW Servers Configuration

The STW Divide And Conquer and STW Combat Knowledge profile configuration is a complete working configuration for STW Servers. Use it as a guideline when configuring your own server and adapt the settings to your scenario, map, mod list and hardware.

Download the working configuration ZIP

To use it, download the ZIP and decompress it directly under the main profile folder. Its contents are arranged so the included files are placed in the expected profile structure, including $profile/STW.

Configuration reminder: treat this package as a known-working starting point, then review and tune the files for your own server.

What to expect the first time

First generation can take a long time. STW is designed for 24/7 systems and builds a strategical database for the scenario. On huge maps, generating those database files can take more than an hour—but this is normally needed only the first time for that scenario.

Let the server finish. Once the strategical database files exist, the system can restart quite quickly on later launches. The first run is the heavy one because STW is preparing the information it needs instead of repeatedly rebuilding it every time the server starts.

While those files are not present, the system may respond very slowly. That can look like a problem during the first run, but it is usually the expected cost of preparing the scenario. Avoid repeatedly restarting the server during generation, because each interrupted run can delay the point at which the files are ready.

Practical advice: generate the files during a maintenance window, keep the server running until the process has completed, and then use the normal 24/7 restart schedule.

Configuration for administrators

The mods arrive preconfigured with settings intended to be friendly to low-end systems and with no RHS presence assumed. This gives a sensible starting point for a broad range of servers; it does not mean every map, mod collection or player count will need identical settings.

Make configuration changes in the corresponding files under $profile/STW. Each system has its own folder and configuration file. Stop the server before editing, make one deliberate change at a time, and restart it so the new values are loaded cleanly.

Good starting point

  • Use the shipped defaults first.
  • Confirm the scenario works without RHS before adding more faction or asset dependencies.
  • Give first-run database generation enough uninterrupted time.

When tuning

  • Increase activity gradually on low-end hardware.
  • Use the specific system manual to identify its configuration file.
  • Keep a copy of working files before making larger changes.
Remember: configuration belongs in $profile/STW, not in the addon files. Profile settings are the administrator’s safe place to tune the installed systems for a particular server and scenario.

Performance tuning

For a smoother server, activate -aiPartialSim on the server. This lets the server use partial AI simulation and is especially useful when a scenario has many active AI groups. Apply the launch option to the authoritative server rather than relying on individual clients.

It is also advised to use a cleanup system such as STW Garbage System. Removing eligible wrecks, bodies, inventory items and other accumulated clutter helps keep long-running 24/7 sessions healthy. Tune cleanup carefully for your scenario so deliberately placed or distant encounters are not removed unexpectedly.

Vanilla persistence: set vanilla persistence to a high number, or disable it completely. A short persistence lifetime can repeatedly save and restore large amounts of world state, adding unnecessary work and potentially working against the cleanup strategy chosen by the administrator.

Make these choices alongside the STW settings under $profile/STW, then test them on the actual map and mod list used by the server. Large maps, high player counts and heavily populated scenarios may need more conservative spawn and cleanup settings even when the shipped defaults run well on a smaller test.

If the system seems slow

  1. Check whether this is the first run for the scenario and whether the strategical database files have been generated yet.
  2. If it is the first run, allow the server to continue running. Huge maps can take over an hour.
  3. After generation, restart the server and compare startup and response time.
  4. If the problem remains, review the relevant file under $profile/STW, reduce activity using that system’s manual, and check the server log for errors.

For detailed behaviour and settings, open the manual for STW Combat Knowledge, STW CQB, STW Stronghold, STW Civilians or STW Zombies.

Captain Sprocket patch

More STW help

Use this page as the starting point, then open the relevant system manual when you are ready to tune behaviour.

Return to all STW manuals