https://github.com/jonpas/armaqdl
Quick Development Launcher for Arma 3
https://github.com/jonpas/armaqdl
arma arma3 developer-tools hacktoberfest hemtt launcher
Last synced: 2 months ago
JSON representation
Quick Development Launcher for Arma 3
- Host: GitHub
- URL: https://github.com/jonpas/armaqdl
- Owner: jonpas
- License: mit
- Created: 2019-08-05T19:00:49.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2024-08-20T13:05:42.000Z (almost 2 years ago)
- Last Synced: 2025-08-27T17:09:09.313Z (10 months ago)
- Topics: arma, arma3, developer-tools, hacktoberfest, hemtt, launcher
- Language: Python
- Homepage:
- Size: 86.9 KB
- Stars: 10
- Watchers: 2
- Forks: 1
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# ArmaQDL
[](https://github.com/jonpas/ArmaQDL/actions/workflows/test.yml)
[](https://pypi.org/project/ArmaQDL)
[](https://pypi.org/project/ArmaQDL)
[](https://winstall.app/apps/jonpas.ArmaQDL)
Quick launching various mod development configurations for Arma through a simple CLI.
Through easily-identifiable preset locations, this program can provide a fast and developer-friendly CLI with some additional optional features, such as building mods and opening the last log file. It is designed around easily modifiable location groups and build tools.
## Features
- Easy **mod launching** from different **preset locations**
- **Load mission** via mission name only or specifying profile name
- **Build** development **mods**
- Open the last log file
- Select the profile to start with
- Toggle file patching, script errors, signature check and windowed mode
- Mod location wildcards (`glob` pattern matching)
- Easy **dedicated server and headless client launching**
- Load mission on dedicated server (by manipulating `server.cfg`)
- Join server
## Installation
ArmaQDL is distributed on [PyPI](https://pypi.org/) as well as a Standalone executable (Windows only).
- Use [WinGet (recommended)](#winget-(recommended)) or [Standalone](#standalone) if you are on Windows and don't have Python installed.
- Use [PyPI](#pypi) if you have Python installed or are not using Windows.
PyPI provides easier updating of ArmaQDL, while Standalone requires manual updates.
#### WinGet (recommended)
Open Command Prompt, PowerShell or any other terminal application and install ArmaQDL.
```sh
$ winget install armaqdl
```
#### Standalone
Download `armaqdl.exe` from [latest release](https://github.com/jonpas/ArmaQDL/releases/latest) and place it in a convenient location.
_Note: Add location directory to `PATH` environmental variable to use it directly._
#### PyPI
Installation as a user is recommended to avoid permission issues with CLI script installation.
```
$ pip install --user ArmaQDL
```
_Note: Add pip installation directory to `PATH` environmental variable to use it directly._
## Setup
Open Command Prompt, PowerShell or any other terminal application, and run ArmaQDL once to generate the configuration files (this will not launch Arma).
```sh
# WinGet / CMD / PyPI if in PATH
$ armaqdl
# PyPI as a Python module
$ python -m armaqdl
```
_Note: Add `.exe` if `armaqdl` is not enough to find the executable._
You should modify the [default settings](https://github.com/jonpas/ArmaQDL/blob/master/config/settings.toml) to your needs. Launching without setup may create a new profile and result in failed launches.
Settings file can be found in your operating system's standard configuration directory, usually:
- Windows: `%AppData%\ArmaQDL\settings.toml`
- Linux: `~/.config/ArmaQDL/settings.toml`
Settings are in [TOML](https://toml.io/en/) format and can be edited with any text editor.
### Dedicated Server
Loading a mission on dedicated server automatically requires `server.cfg` to be present next to `arma3_x64.exe` with at least the following mission and Headless Client entries.
```cpp
// Automatically load the first mission in rotation
class Missions {
class Test {
template = "mission.vr";
};
};
// Allow Headless Clients from local machine
headlessClients[] = {"127.0.0.1"};
localClient[] = {"127.0.0.1"};
// Allow multiple connections, unsigned mods and file patching (as needed)
kickDuplicate = 0;
verifySignatures = 0;
allowedFilePatching = 2;
```
ArmaQDL copies the mission from used profile's missions folder and updates the mission name in `server.cfg` to make the server automatically load it.
## Usage
ArmaQDL is a CLI script, view all the options with the `--help` flag.
```sh
$ armaqdl -h
```
_Note: All examples use `armaqdl` to launch ArmaQDL, replace it appropriately depending on your install._
**Example 1:** _(launching and building mods)_
Launches Arma with CBA from main location, ACE3 from Workshop install and ACRE2 from local development folder. Additionally builds ACRE2 mod and opens the latest log file. Loads Arma directly into the editor using the specified mission from the "Soldier" profile.
```sh
$ armaqdl main:cba workshop:@ace dev:acre2:b -m Soldier:test.vr
```
Specific build tool can also be specified, such as HEMTT.
```sh
$ armaqdl main:cba workshop:@ace dev:acre2:bhemtt -m Soldier:test.vr
```
**Example 2:** _(server and mission handling)_
Launches Arma Server with CBA from local development folder and loads specified mission from default profile's missions folder, copying it to the server in the process.
```sh
$ armaqdl dev:cba -m test.vr -s
```
Launches Arma with CBA from local development folder and connects to the given server with the given password (`-j` defaults to the settings file).
```sh
$ armaqdl dev:cba -j 192.168.1.1:2302:test
```
**Example 3:** _(glob and skipping)_
Launches Arma with all mods in a folder `modpack` from main location, skipping ACE3 in the same folder and instead loading ACE3 from a local development folder. This is useful for replacing a subset of mods from a bigger modpack.
```sh
$ armaqdl main:modpack\* main:modpack\ace:s dev:ace
```
**Example 4:** _(launch types)_
Launches Arma with mods from local development folder, CBA using HEMTT release build, ACE3 using automatic launch type determination and ACRE2 using non-HEMTT build. Available launch types are `dev`, `build`, `release` for HEMTT or none for non-HEMTT `addons/`. Automatic determination uses HEMTT if `.hemttout` folder exists with launch type as specified in settings file, or `dev` if not specified.
```sh
$ armaqdl dev:cba:trelease dev:ace dev:acre2:t
```
Build type for HEMTT can also be specified using the same flag in addition to build flag.
```sh
$ armaqdl dev:cba:bhemtt:trelease dev:ace:b:tbuild
```
**Example 5:** _(optionals)_
_Note: Only optionals inside `optionals` folder in a full `@mod` folder structure (such as HEMTT produces) are supported._
Launches Arma with Theseus Services from local development folder and its MELB Variants optional skipping the prefix using glob pattern matching. `@` must still be used for each optional (or pattern) specified.
```sh
$ armaqdl dev:TheseusServices:o@*variants_melb
```
Glob pattern matching may also be used to match multiple optionals.
```sh
$ armaqdl dev:TheseusServices:o@*variants*
```
## Development
ArmaQDL uses [Hatchling](https://hatch.pypa.io/latest/) as a build backend and [flake8](https://flake8.pycqa.org/en/latest/) as a style guide.
```sh
$ pip install --user -e .
```
[Hatch](https://hatch.pypa.io/latest/) is the primary project manager of choice, but any project adhering to PEP 621 (`pyproject.toml` specification) can be used.
```sh
# Run development build
$ hatch run armaqdl
# Lint with flake8
$ hatch run lint
# Test with pytest
$ hatch run test
# Bundle with PyInstaller
$ hatch run static:bundle
```
Limited Linux support exists for testing purposes, but launching Arma or opening the last log file is not supported. Contributions are welcome!