COMMANDNET S3

Plan. Coordinate. Execute.

Operations staff usually work across several completely different tools.

Mission files are stored in one place.

Briefings live somewhere else.

SOPs are buried in documents.

Server information is tracked manually.

Mission feedback arrives through Discord.

Mod lists are passed around through exported launcher presets.

CommandNet S3 is designed to bring those workflows together.

CommandNet S3 expands CommandNet with tools specifically for:

S3 Operations Staff

Mission Developers

Zeus / Game Masters

Server Administrators

Mission Briefings

Operations can have structured briefings containing:

• Mission name
• Task and purpose
• Objectives
• Briefing status

Briefings can remain internal while being prepared and then become available to authorized participants once they are ready.

SOP & Doctrine Library

CommandNet S3 includes a versioned SOP system.

When leadership publishes a new version of a document, members can be required to acknowledge that specific version.

That makes it possible to see who has reviewed current doctrine instead of simply assuming everyone read a Discord announcement.

Mission Development

Mission developers can maintain versioned mission files directly through the S3 system.

Supported workflows include:

• Mission versions
• Mission file storage
• Mod lists
• DLC requirements
• Launcher preset generation
• Playtest feedback
• Feedback resolution

The goal is to preserve the exact mission build being worked on while providing a structured place for testing feedback.

Loadout & Equipment Validation

Because CommandNet Core already understands units, positions, equipment, and Arma class names, S3 can use that information for operation-specific equipment checks.

Paste a loadout list and identify equipment as:

Approved

Not Authorized

Not Found

Live Operation Notes

Game Masters can maintain timestamped notes during an operation.

Those notes can later be used to help build an After-Action Report rather than relying completely on memory after the mission ends.

Server & Mod Tracking

CommandNet S3 can also provide visibility into game infrastructure.

Server status can include information such as:

Online state

Server name

Current map

Mission

Player count

Ping

Tracked server mods can also be compared against expected versions to identify outdated installations.

Operation Information Pages

CommandNet S3 can create live operational information pages combining data such as:

• Operation information
• Briefing objectives
• OPORD content
• Server status
• Mod information
• Timeline
• Task organization
• Communications plan
• Rules of engagement
• Pre-operation checklist
• Quick links

Instead of distributing operational information across five different Discord channels, your members can have one place to look.

COMMANDNET S3

Better planning.

Better information.

Better operations.