Shows where JoyPro finds the binds of the original IL-2 Sturmovik: Cliffs of Dover on this PC:
%USERPROFILE%\Documents\1C SoftClub\il-2 sturmovik cliffs of dover\confUser.ini. Detect in the import wizard's
Expert import section runs it.
engine il2cod paths --text
Advanced
No options. Listed: your own config location of engine games config set first, then confUser.ini and the one of
the pre-Blitz mod folder ...\il-2 sturmovik cliffs of dover - MOD\confUser.ini, each when it exists.
Read-only; also works when the game is not installed or switched off.
Technical internals
Output: JSON (Game, DisplayName, ConfigPaths, Warnings), or with --textIL-2 Sturmovik: Cliffs of Dover Config Paths, Paths: <n> and the files. Exit code 0; an unknown option fails with Unknown IL2CoD 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 Cliffs of Dover commands JoyPro knows: the game's command names per section (pilotMove.aileron, ...), with
axis or button and category.
engine il2cod catalog --text
Advanced
No options; read-only, also when the game is not installed.
Same sections and categories as Blitz (Axes, Aircraft, Common, Gunner, Views, Time, Orders, Game, Vehicle), in a
list of its own.
A fresh install has no list yet; the first scan, import, export or engine il2cod refresh-db builds it. Until then
the command lists no action and warns IL-2 Sturmovik: Cliffs of Dover 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.
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 binds of the original Cliffs of Dover in confUser.ini, joystick and keyboard, with chords as modifiers,
without changing your profile or the game. Look first in the import wizard runs it.
engine il2cod scan --text
Advanced
Reads the [HotKey <section>] lines of the first file engine il2cod paths lists, or of the file given (positional
or --path).
The original names devices Joystick, Joystick1, Joystick2 ... in DirectInput order: each name is shown on the
connected device at that position.
Keys are listed without --include-keyboard; axis settings are read but not listed; a command that is not in the
list yet gets a warning naming engine il2cod refresh-db.
--ignore-device <name> / --ignore-devices <a;b> leave the binds of those devices out.
Safety: reads only, also while the game runs; a fresh install first builds and saves the 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.
Exit code 0; 1 on an error (no config file found). Unknown options fail with Unknown IL2CoD 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'.
--ignore-device(s): the binds of these devices are left out
For beginners
Reads the binds of the original IL-2 Sturmovik: Cliffs of Dover from confUser.ini into your JoyPro profile, with
chords as modifiers and the axis settings of each command. Nothing in the game changes. The GUI runs it with
Import on the Cliffs of Dover card of the Start page.
It reads %USERPROFILE%\Documents\1C SoftClub\il-2 sturmovik cliffs of dover\confUser.ini; the pre-Blitz mod
folder ...\il-2 sturmovik cliffs of dover - MOD\confUser.ini is listed too.
Default: adds to the open profile (--merge means the same); --replace replaces every relation of the profile by
what the file has.
--include-keyboard also reads the keys; chords become JoyPro modifiers.
The original names devices Joystick, Joystick1, Joystick2 ... in DirectInput order (up to 8): JoyPro maps each
name to the connected device at that position.
Safety: reads only, not refused while the game runs; the profile is kept as "Before import from IL-2 Sturmovik:
Cliffs of Dover" 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 config file found).
Without a path it reads the first file of engine il2cod paths; a fresh install builds the command list first.
With --profile the profile is saved afterwards. The imported inputs are recorded as JoyPro's in
confUser.ini.joypro.json, and 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 IL-2 Sturmovik: Cliffs of Dover'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. IL-2 Sturmovik: Cliffs of Dover 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 the flight sections of confUser.ini of the original IL-2 Sturmovik: Cliffs of Dover. Close
the game first. The GUI's Export now on the Cliffs of Dover card runs it.
It edits Documents\1C SoftClub\il-2 sturmovik cliffs of dover\confUser.ini with the original's device names
(Joystick, Joystick1 ...); Blitz uses the same file with its own names (engine il2codblitz export).
--mode
In the game
add
nothing is removed; a bind on a taken input is listed, not written
merge
your binds go in; a game bind on an input you give another command is removed, the rest stays
merge-overwrite (engine default)
as merge, and every command you bind loses its other inputs (keyboard only with --include-keyboard)
clean (GUI default)
the devices you write keep only your binds in the managed sections
--nuke-untouched-devices: the other connected devices lose their lines in the managed sections (not with add).
The original reads the first 8 game controllers; a device further down is refused.
Never touched: [HotKey vehicle], mouse lines, keyboard lines without --include-keyboard, devices that are not
connected, unknown sections, --ignore-device(s), the --vjoy-tunnel device.
Safety: refused while the game's own Launcher runs (another program with that name does not count); backed up
first (undo: engine backups list); the profile is kept as "Before export to IL-2 Sturmovik: Cliffs of Dover".
--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 IL-2 Sturmovik: Cliffs of Dover'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: Documents\1C SoftClub\il-2 sturmovik cliffs of dover\confUser.ini (ini; devices Joystick, Joystick1 ...). IL-2 Sturmovik: Cliffs of Dover 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
Adds new Cliffs of Dover commands to JoyPro's command list: JoyPro's own list of the game's commands, then every
command found in your confUser.ini and the game's default binds. Update on the Cliffs of Dover card of the Start
page runs it.
engine il2cod refresh-db --text
Advanced
Rows the list already has stay; nothing is removed. Read without a path: the files of engine il2cod paths (the mod
folder's too) and confUser.ini in the installation folder.
A path (positional or --path) reads only that file, or confUser.ini in that folder.
Command names with blanks are skipped. --dry-run writes nothing; otherwise the list is written only when it
changed.
Refused when the game is not installed or switched off in Settings > Games; the game may run.
Technical internals
Output: JSON of the refresh (DryRun, FilesWritten, Steps with the new commands per file and Actions: <old> -> <new>, Warnings), or a text report with --text.
Exit code 0; 1 only for a refusal or an unknown option.
Writes %LOCALAPPDATA%\JoyPro2\GameData\DB\IL2CoD\actions.tsv and records the game's Steam build for
engine db check-updates.