Shows where JoyPro finds Tiny Combat Arena's binds on this PC: the game's registry key HKCU\Software\TinyCombat\Arena,
which exists once you started the game. Scan, import and export use it when you give no path; Detect in the import
wizard's Expert import section runs it.
engine tinycombatarena paths --text
Advanced
No options. Listed: your own config location of engine games config set first, then the registry key when it
exists. An empty list means the game has not saved any settings yet.
Read-only; also works when the game is not installed or switched off.
Technical internals
Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or with --textTiny Combat Arena Config Paths,
Paths: <n> and the locations. Exit code 0; an unknown option fails with Unknown TinyCombatArena paths argument(s): ....
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 Tiny Combat Arena actions JoyPro knows, with axis or button and category (Flight Control, Weapon Control,
View Control, Camera Control, Map Control, System ...): the actions you can bind for the game.
engine tinycombatarena catalog --text
Advanced
No options; read-only, also when the game is not installed.
Only actions the player can assign in the game are in the list; each axis action also has the button rows
<action>.Positive and <action>.Negative.
A fresh install has no list yet; the first scan, import, export or engine tinycombatarena refresh-db builds it.
Until then the command lists no action and warns Tiny Combat Arena action catalog not found: <path>.
Technical internals
Output: JSON (Game, Source, Actions with Id, Title, IsAxis, Category, Warnings), or with --text
one line per action <id> | axis|button | <category> | <title>. Exit code 0.
File: %LOCALAPPDATA%\JoyPro2\GameData\DB\TinyCombatArena\actions.tsv (fifth column: the game's numeric action id).
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 Tiny Combat Arena has for your connected devices, on every tab of its Control Mapper, without
changing your profile or the game. Look first in the import wizard runs it.
engine tinycombatarena scan --text
Advanced
Reads what engine tinycombatarena import reads: the player's ControllerMap values under
HKCU\Software\TinyCombat\Arena (axes with invert, buttons, the four main hat directions, buttons on an axis). A path
(positional or --path) may name that key.
--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 counts them.
Not read, with a warning: half-axis binds, maps of two devices of one model, devices that are not connected. No
keyboard binds, and not the curves of Controls.cfg.
Safety: reads the game only, also while it runs; a fresh install first builds and saves JoyPro's command list.
Refused when the game is not installed or switched off in Settings > Games.
Technical internals
Output: JSON (Game, Actionscan, ConfigPath, BindingsRead, Bindings, Steps, Warnings, Errors), or
a text report with --text (<action> <- <device> <input> per bind).
Exit code 0; 1 on an error (No Tiny Combat Arena config file found. Pass the path explicitly., Tiny Combat Arena has no settings yet (HKCU\Software\TinyCombat\Arena is missing): start the game once., a list without action
ids). Unknown options fail with Unknown TinyCombatArena scan argument(s): ....
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 Tiny Combat Arena's files only; nothing changes in the game. A scan only shows what an import would bring and does not change the profile. Tiny Combat Arena details · what each mode changes
Example
engine tinycombatarena 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 joystick maps of your connected devices from Tiny Combat Arena into your JoyPro profile, from every tab of
the game's Control Mapper: axes with their invert, buttons, hat directions and buttons on an axis. Nothing in the game
changes. The GUI runs it with Import on the Tiny Combat Arena card of the Start page.
It reads the game's settings in the registry, HKCU\Software\TinyCombat\Arena: one ControllerMap value per device
and tab (Flight, Weapons, Camera, View Select, Map UI, System) for the player Player.
Default: adds to the open profile (--merge means the same); --replace replaces every relation of the profile by
what the game has.
Keyboard binds and modifiers are not read; --include-keyboard changes nothing. The game's curves in Controls.cfg
are not read.
Two or more devices of one model cannot be told apart and are left out (warning).
Safety: reads only, not refused while the game runs; the profile is kept as "Before import from Tiny Combat Arena"
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 Tiny Combat Arena config file found. Pass the path explicitly.).
The path may be the registry key itself; without one it reads the key engine tinycombatarena paths lists. A fresh
install builds the command list from Arena_Data\sharedassets*.assets 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 Tiny Combat Arena'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. Tiny Combat Arena details · what each mode changes
Flight only: clean takes over the devices it writes, nuke clears unused devices; --ignore-device(s) and --vjoy-tunnel devices are never cleared
For beginners
Writes your binds into Tiny Combat Arena's joystick maps, each into the tab of its action (pitch into Flight, a gun into
Weapons, a view into View Select); the rest of each map stays. Close the game first. The GUI's Export now on the
Tiny Combat Arena card runs it.
It edits the player's ControllerMap values under HKCU\Software\TinyCombat\Arena. Tiny Combat Arena is a flight-only
game: every assignable action counts as JoyPro's.
--mode
In the maps of your devices
add
nothing of the game changes; a bind whose input drives another action (or the other pole of an axis) is listed
merge
an action on an input you give another action loses it; the action keeps its other inputs
merge-overwrite (engine default)
as merge, and every action you bind leaves its other inputs on the connected devices JoyPro can read
clean (GUI default)
every other assignable action of the written devices is released, on every tab
--nuke-untouched-devices: the other connected devices (one of a model) lose those actions; a device without saved
maps gets empty ones (not with add).
No curves, keyboard binds or modifiers are written.
Never touched: actions the player cannot assign, keyboard and mouse maps, calibration maps, controller assignments,
Controls.cfg, devices that are not connected, two devices of one model, --ignore-device(s), the --vjoy-tunnel
device.
Safety: refused while Arena runs; the player's controller-map values go into the backup store first (undo:
engine backups list); the profile is kept as "Before export to Tiny Combat Arena". --dry-run writes nothing.
Technical internals
Output: JSON of the export result or a text report with --text; exit code 1 on an error (Tiny Combat Arena is running (Arena). Close the game first; it overwrites its config on exit., an invalid --mode, no key 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 Tiny Combat Arena's control files while the game is closed (refused while it runs), after a backup. Combat flight sims and combat flight games that read several joysticks. Bind file: registry HKCU\Software\TinyCombat\Arena (Unity PlayerPrefs, Rewired maps per mapper tab). Tiny Combat Arena details · what each mode changes
Rebuilds the catalog from the installed game or <source-path>: actions the game no longer has are dropped; writes it only when it changes
For beginners
Builds JoyPro's Tiny Combat Arena command list from the installed game's own action list. Run it after a game update;
Update on the Tiny Combat Arena card of the Start page runs it.
engine tinycombatarena refresh-db --text
Advanced
Reads the action list from the game's data folder Arena_Data: the sharedassets*.assets files first, then
resources.assets and globalgamemanagers.assets; the first that holds the list wins. A path (positional or
--path) may be the game folder, the data folder or one .assets file (DB Source with Refresh DB in the
import wizard's Expert import section).
Actions the player cannot assign are left out (a step line counts them). The list is rebuilt from the game; an
action the game no longer has drops out with a warning.
--dry-run writes nothing. Otherwise the list is written only when it changed.
Refused when Tiny Combat Arena is not installed or switched off in Settings > Games; the game may run.
Technical internals
Output: JSON of the refresh (DryRun, FilesWritten, Steps with Actions: <old> -> <new>, Warnings,
Errors), or a text report with --text.
Exit code 0; 1 when the list was not found (Tiny Combat Arena's Rewired InputManager was not found. Pass --path with the game folder, its data folder or the .assets file.); the list stays unchanged.
Writes %LOCALAPPDATA%\JoyPro2\GameData\DB\TinyCombatArena\actions.tsv and records the game's Steam build for
engine db check-updates.
What it does Rebuilds the catalog from the installed game or <source-path>: actions the game no longer has are dropped; writes it only when it changes.
Option
Values
Meaning
--path
<source-path>
Same as <source-path>: the game's installation or a file of the game to read the actions from.
--dry-run
switch (no value)
Report what the command would do; nothing is written or changed.