The config file

Location#

$ .minecraft/config/inputbooster.properties

The directory is resolved from the inputbooster.configDir system property when it is set, and config relative to the game directory otherwise. The system property exists so the automated tests can use a throwaway folder.

Format#

A standard Java properties file: key=value, one per line, # starts a comment.

#InputBooster 4.1.2-alpha configuration - by Ahaduzzaman Khan
poll_rate_hz=200
poll_rate_auto=true
burst_mode=true
combo_keys=true
sprint_fix=true
auto_sprint=true
wtap_assist=true
anti_idle=true
auto_strafe=true
cps_limiter=true
max_cps=20
cps_mode=FIXED
click_sounds=false
click_sound_pitch=1.35
click_sound_volume=0.35
replay_enabled=true
safe_mode=true
event_log=true
key_conflict_warn=true
per_server_profiles=true
custom_keyboard_handler=false
show_f3_info=true
show_keystrokes=true
overlay_position=0
overlay_scale=1.0
overlay_opacity=0.8
show_action_bar=true
fps_check_interval=20
debug_mode=false
engine_mode=0
keyboard_repeat_guard=true
mouse_scroll_debounce_ms=0
mouse_click_dedupe_ms=0
compat_fallback=true
overlay_mode=0
overlay_show_engine=true
overlay_show_events=true
overlay_show_overhead=true
config_version=305

That is all 39 persisted keys with their default values. The full table with ranges and readers is in the key reference.

How it is written#

The save is synchronous and atomic:

1. The parent directory is created if it does not exist.
2. A temporary file is created in the same directory.
3. Every key is written to it.
4. The temporary file is moved over the real file, atomically where the filesystem supports it.

Path temp = Files.createTempFile(parent, "inputbooster", ".tmp");
try (OutputStream out = Files.newOutputStream(temp)) {
    props.store(out, "InputBooster " + MOD_VERSION + " configuration - by Ahaduzzaman Khan");
}
try {
    Files.move(temp, CONFIG_PATH, StandardCopyOption.REPLACE_EXISTING,
        StandardCopyOption.ATOMIC_MOVE);
} catch (AtomicMoveNotSupportedException e) {
    Files.move(temp, CONFIG_PATH, StandardCopyOption.REPLACE_EXISTING);
}

How it is read#

load() starts from the documented defaults every time and then applies the file. That ordering matters: an earlier version only assigned the keys that were present, so any key missing from the file kept whatever value it had in memory — importing a partial config leaked the previous session's settings.

Accepted boolean spellings#

Anything else falls back to the default, and the key is named in the warning line described in validation.

Ranges#

Numeric values are clamped, not rejected, when they are read and when they are set:

The schema version#

config_version is the on-disk schema version. The current value is 305.

When the mod loads a file with a lower version it logs a migration line and renames three legacy keys:

The version is written back on the next save, so a migrated file stops migrating.

The three files#

Only the first is created automatically. The profile file appears when you save a profile; the bindings file appears when a binding is written.

Related pages#

• Key reference — every key, its default, its range and what reads it.
• Validation — what happens to a bad value.
• Profile format — the JSON schema.