Lists where JoyPro finds the joystick preset of Arma Reforger on this PC. The first one is what engine reforger scan,
engine reforger import and engine reforger export use when you give no path. Detect in the Other Games panel
(Start page, Expert import) runs it and puts the first one into File / Folder.
engine reforger paths --text
Advanced
%USERPROFILE%\Documents\My Games\ArmaReforger\profile\.save\settings\customInputConfigs\JoyPro.conf, listed as
soon as the game's settings folder exists. The file itself is JoyPro's preset: the first export writes it.
No options. Reads only; it also works while the game runs or when it is not installed.
Technical internals
Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or text with --text ("Arma Reforger Config
Paths", "Paths: " and one line per location). Exit code 0, also when nothing was found (empty list).
engine reforger without an action runs paths.
Before the first export the listed file does not exist yet; a scan or import then reports Reforger input config not found: <path>.
What it does Lists where JoyPro looks for this game's controls on this machine: files, folders or registry keys (your config location from games config set first). A file the game has not written yet can be listed (e.g. Arma Reforger's JoyPro.conf, Project Wingman's Input.ini).
Lists the Arma Reforger actions JoyPro manages (its command list): id, axis or button, category and title. An export
writes only these actions, and the relation editor and the search list them.
engine reforger catalog --text
Advanced
The list is %LOCALAPPDATA%\JoyPro2\GameData\DB\ArmaReforger\actions.tsv (when that folder does not exist, the
DB\ArmaReforger folder next to the engine).
It is built from the game's archives by engine reforger refresh-db, or by the first scan, import or export.
catalog only shows the list; it never builds it. Titles that look like ids are shown readable.
No options. Reads only; works without the game installed.
Technical internals
Output: JSON (Game, Source, Actions with Id, Title, IsAxis, Category, Warnings), or text with
--text ("Arma Reforger Action Catalog", "Source:", "Actions: ", then ` | axis|button | |` per action).
Without a list: the warning Arma Reforger action catalog not found: <path> and an empty list, exit code 0.
What it does Lists every action of JoyPro's command list of this game with its kind and category: <data>\GameData\DB\<Game>\actions.tsv, else the program folder's DB\<Game>.
Shows the joystick binds Arma Reforger has now, without changing your profile or the game. Use it to look before an
import. Look first on the game's card of the Start page and Scan in the Other Games panel run it.
engine reforger scan --text
Advanced
It reads the helicopter flight Action blocks of JoyPro.conf with multiplier and invert, and maps the game's
joystick0 to joystick3 back to your devices through the device order of the game's engine settings.
Path (positional or --path): another preset file.
--ignore-device <name> / --ignore-devices <a;b> (separated by | or ;, --ignore-devices also by commas) leave the binds of those devices out
(a name without {GUID} means every device of that name); a step line names them and counts the binds.
Keyboard binds are not read in this game.
Safety: reads only and is not refused while the game runs. It is refused when the game is not installed (set its
folder: engine games install set) or switched off in Settings > Games.
A fresh install has no command list yet: the first scan builds it from the installed game and saves it (a step line
says so).
Technical internals
Output: JSON (ConfigPath, BindingsRead, Bindings with ActionId, Device, Input, IsAxis, Reformers,
Inverted, then Steps, Warnings, Errors), or text with --text ("Arma Reforger Scan", "Config:", "Bindings
Read:" and the list).
Exit code 0; 1 when the result has errors, for example No Arma Reforger config file found. Pass the path explicitly., or Reforger input config not found: <path> before the first export.
Unknown options fail with Unknown ArmaReforger scan argument(s): ...; MSFS options (--game-profile,
--include-disconnected, --include-sim-defaults) are refused.
Binds of the vJoy device JoyPro forwards into (--vjoy-tunnel) are left out.
What it does Reads the game's controls (its control file or folder, or registry values for Nuclear Option and Tiny Combat Arena; Ace Combat 8 stores none) and shows the joystick binds, without changing the profile. Without a command list yet (fresh install) it first builds the list from the game and saves it.
Option
Values
Meaning
--path
<config-path>
Optional explicit path override. Use when you prefer option form over positional path.
--ignore-device
<name>
Leave the binds of this device out (one per flag; a name without {GUID} means every device of that name). Example: --ignore-device 'vJoy Device'.
--ignore-devices
<csv>
Leave the binds of these devices out (separated by commas, | or ;). Example: --ignore-devices 'vJoy Device,Old Pedals'.
In the game Reads Arma Reforger's files only; nothing changes in the game. A scan only shows what an import would bring and does not change the profile. Arma Reforger details · what each mode changes
Example
engine reforger scan --text
How the options interact
--ignore-device / --ignore-devices leave the binds of those devices out of the scan or import (the result names how many).
--ignore-device(s): the binds of these devices are left out
For beginners
Reads the helicopter binds of JoyPro's joystick preset for Arma Reforger into your JoyPro profile, with multiplier and
invert. Nothing in the game changes. The GUI runs it with Import on the Arma Reforger card of the Start page.
It reads %USERPROFILE%\Documents\My Games\ArmaReforger\profile\.save\settings\customInputConfigs\JoyPro.conf and maps
the game's joystick0 to joystick3 back to your devices through the device order rules of the game's engine
settings.
Default: adds to the open profile (--merge means the same); --replace replaces every relation of the profile by
what the preset has.
Keyboard binds and modifiers are not read; --include-keyboard changes nothing.
Safety: reads only, not refused while the game runs; the profile is kept as "Before import from Arma Reforger"
first.
--ignore-device <name> / --ignore-devices <a;b> leave the binds of those devices out (a name without
{GUID} means every device of that name); a step line says how many binds were left out.
Technical internals
Output: JSON of the import result or a text report with --text; exit code 1 on an error (No Arma Reforger config file found. Pass the path explicitly.).
Without a path it reads the file engine reforger paths lists first; a fresh install builds the command list from
the game's archives first.
With --profile the profile is saved afterwards; a game JoyPro never exported to is watched from now on.
What it does Imports the game's joystick binds into the loaded profile (merged by default; --replace starts from an empty relation list). Without a command list yet it first builds the list from the game.
Option
Values
Meaning
--path
<config-path>
Optional explicit path override. Use when you prefer option form over positional path.
--replace
switch (no value)
For game import: start from an empty relation list instead of merging into the loaded profile.
--include-keyboard
switch (no value)
--ignore-device
<name>
Leave the binds of this device out (one per flag; a name without {GUID} means every device of that name). Example: --ignore-device 'vJoy Device'.
--ignore-devices
<csv>
Leave the binds of these devices out (separated by commas, | or ;). Example: --ignore-devices 'vJoy Device,Old Pedals'.
In the game Reads Arma Reforger's files only; nothing changes in the game. The binds come into the profile as relations; JoyPro's own data next to the game file brings back names, groups, modifiers and curves. Arma Reforger details · what each mode changes
Only aircraft/helicopter actions: clean and nuke release those on the written / unused devices; --ignore-device(s) and --vjoy-tunnel devices are never cleared
For beginners
Writes JoyPro's joystick preset JoyPro.conf for Arma Reforger with your helicopter flight binds, and sorts your
devices into the game's four joystick slots. Close the game first; then pick JoyPro once under Settings >
Controllers > Joystick preset and restart the game. The GUI's Export now on the Arma Reforger card runs it.
Only the flight Action blocks of the preset change; a block left without sources is removed.
--mode
In JoyPro.conf
add
every source stays; a bind whose joystick input another flight action uses gets a mark "Not written to the game"
merge
your sources go in; another flight action's source on the same input is removed
merge-overwrite (engine default)
as merge, and an action you bind loses its other joystick sources of connected devices
clean (GUI default)
the flight sources of the devices you write are replaced by yours
--nuke-untouched-devices: the same for connected devices without binds in your profile (not with add).
Device order: JoyPro edits the JoystickOrderRule entries of ReforgerEngineSettings.conf (slots 0 to 3, a slot you
chose with joystickSlot first) in every settings folder it finds; without a saved settings file it warns. More than
four devices get a warning.
Per bind a multiplier and invert; no dead zones or curves. Game settings you stored (HOTAS collective mode, force
feedback intensity) go into ReforgerGameSettings.conf, also from a profile without Reforger binds.
Never touched: InputUserSettings.conf, your other presets, infantry, vehicle and menu actions, keyboard, mouse and
pad sources, joysticks that are not connected, --ignore-device(s), the --vjoy-tunnel device, other lines of the
settings files.
Safety: refused while ArmaReforgerSteam, ArmaReforger_BE or ArmaReforger runs; backed up first (undo:
engine backups list); the profile is kept as "Before export to Arma Reforger". --dry-run writes nothing.
Technical internals
Output: JSON of the export result or a text report with --text; exit code 1 on an error (the game runs, an
invalid --mode, no file found).
What it does Writes the profile's binds for this game. Only the flight actions JoyPro manages are changed, the game must be closed, and the game's files are backed up first (engine backups). Without a command list yet it first builds the list from the game.
Option
Values
Meaning
--path
<config-path>
Optional explicit path override. Use when you prefer option form over positional path.
--mode
cleanaddmergemerge-overwrite
Export mode for DCS/IL2 export commands: clean, add, merge, merge-overwrite.
--dry-run
switch (no value)
Report what the export would write; the game's files are not changed.
In the game Writes into Arma Reforger's control files while the game is closed (refused while it runs), after a backup. Infantry sims with aircraft and helicopters: JoyPro writes only the cataloged aircraft and helicopter actions. Bind file: JoyPro's own preset ...\customInputConfigs\JoyPro.conf (Enfusion text) + device order in ReforgerEngineSettings.conf. Arma Reforger details · what each mode changes
Reads the installed game or <source-path> and adds its new actions to the catalog, the known ones stay; writes it only when it changes
For beginners
Builds JoyPro's Arma Reforger command list from the installed game's archives, or adds the actions that are new. Run
it after a game update, or when JoyPro says the list is missing. Refresh DB in the Other Games panel (its DB
Source box is the path) and the Start page's notice "Command lists to build or update" run it.
engine reforger refresh-db --dry-run --text
Advanced
Without a path it reads the game folder's .pak archives under addons: Configs/System/chimeraInputCommon.conf
(the flight contexts of its action manager), the key binding menu and Language/localization.en_us.conf for the
titles.
Path: the game folder, one .pak file, a folder with the extracted files, or chimeraInputCommon.conf itself.
Then your own input configs (the *.conf presets of customInputConfigs and InputUserSettings.conf) are read for
flight actions mods add.
Known actions keep their entry.
--dry-run reads everything and writes nothing (step "Dry run: nothing was written."). Without it the list is
written only when it changed.
Safety: only JoyPro's list changes, never a game file; it is refused when the game is not installed or switched off
in Settings > Games. The GUI can cancel it while the game's files are read; nothing is written then.
Technical internals
Output: JSON of the refresh (DryRun, FilesWritten, Steps with Actions: <old> -> <new>, Warnings,
Errors), or text with --text.
Exit code 0; 1 when nothing could be read: Arma Reforger was not found. Set its folder (engine games install set reforger <folder>) or pass the game folder, a .pak file or the extracted Configs\System\chimeraInputCommon.conf.; the list stays unchanged.
Writes %LOCALAPPDATA%\JoyPro2\GameData\DB\ArmaReforger\actions.tsv (with a header line that has the date). After a
real run the game's build is recorded for engine db check-updates.