valmojr/armatak
1
0
Fork 0
mirror of https://github.com/valmojr/armatak.git synced 2026-06-13 13:13:29 +00:00
Code Issues Packages Projects Releases Wiki Activity
Page: Arma 3 Mission Maker Guide
Pages
Arma 3 Mission Maker Guide Arma 3 Players Guide Home Mission Maker Function Reference UAS Tools Guide Video Streaming Guide
Clone
14
Arma 3 Mission Maker Guide
Valmo Trindade edited this page 2026-05-25 03:15:56 -03:00
Table of Contents

Mission Maker Guide

This guide covers the current server-side ARMATAK workflow for 3DEN and Zeus, you don't need to setup a full TAK Server in order to play Arma 3 with ARMATAK, but connecting the Arma Server to a TAK Server allows you to stream more game data than the player's location itself. This guide won't get deep into a TAK Server configuration, you may have many options, the simplest one is paying a group at IronTAK

Before You Start

You need:

  • an Arma 3 mission with ARMATAK loaded
  • a TAK-compatible backend such as TAK Server, IronTAK or OpenTAKServer.
  • at least one TAK client already connected, so you can verify the feed

ARMATAK can publish through two transport modes:

  • CoT Router (TCP)
  • CoT Router (Authenticated)

Use the authenticated mode unless you intentionally want a legacy unauthenticated TCP feed.

Which Module Should You Use

CoT Router (TCP)

Use this only if your server exposes unauthenticated TCP ingress.

Fields:

  • TAK Server Address
  • TAK Server TCP Port

Typical port:

  • 8088

CoT Router (Authenticated)

This is the recommended mode.

Fields:

  • TAK Server Address
  • Enrollment HTTPS Port
  • Enrollment Username
  • Enrollment Password

Typical port:

  • 8446 for enrollment

3DEN Setup

  1. Open your mission in the 3DEN editor.
  2. Go to the modules list.
  3. Place either CoT Router (TCP) or CoT Router (Authenticated).
  4. Fill only the fields required by that module.
  5. Sync the module to the entities you want to export.

Notes:

  • Sync units and vehicles, not groups.
  • The module position on the map does not change behavior.
  • The Arma server must be able to reach the TAK server address you configure.

Zeus Setup

The same router modes are available in Zeus:

  • CoT Router (TCP, Zeus)
  • CoT Router (Authenticated, Zeus)

After opening the dialog:

  1. Fill the required fields.
  2. Confirm the connection.
  3. Use Mark Entity on the units or vehicles you want to publish.

Notes:

  • Mark Entity is entity-based, not group-based.
  • Units, vehicles and relevant world objects can be exported depending on the available CoT conversion path.

What Gets Published

The server-side router currently emits CoT for:

  • infantry units
  • vehicles
  • autonomous vehicles and drones
  • digital pointers
  • selected custom markers and draw data exposed by the addon

The router runs continuously while the mission is active and republishes the synced entities on a timed loop.

Routed vehicles may also publish sensor-detected contacts from getSensorTargets. For mission-specific entities where that would create noisy duplicate TAK markers, such as a convoy target that should appear only as Enemy Convoy, disable sensor contact publishing on that entity:

_vehicle setVariable ["armatak_disable_sensor_data", true, true];

Scripted Mission Functions

Mission scripts can also publish reports, drawings, routes, UAS CoTs and cleanup messages directly through ARMATAK functions.

See the Mission Maker Function Reference for function signatures and SQF examples.

Recommended IronTAK Setup

If you use IronTAK:

  • create a technical user for the session or server
  • assign that user only to the groups that should receive the feed
  • use CoT Router (Authenticated)

That gives the session a real authenticated identity and lets IronTAK apply normal group scope and ACL logic.

Troubleshooting

If nothing appears in TAK:

  • confirm the TAK client itself is connected and healthy
  • confirm the Arma server can resolve and reach the configured host
  • if you are using CoT Router (TCP), confirm unauthenticated TCP is actually enabled on the server
  • if you are using CoT Router (Authenticated), confirm enrollment credentials are valid
  • check armatak.log on the Arma side for transport errors

If the feed worked but later stopped:

  • restart the router module through Zeus
  • verify the TAK backend is still accepting the target transport
  • inspect armatak.log and server logs together

If you need help, join the Discord.

ARMATAK

Arma 3 addon for streaming game data into the TAK ecosystem.

ARMATAK