03 04 Config jzintv_flags

03 04 Config jzintv_flags

This page explains how to set emulator flags through Sprint Boost config.

Why this section matters

jzintv_flags lets you define standard jzintv command line options in the config.

A common pattern is:

• Set shared flags at folder level
• Let all games in that folder inherit them
• Override or cancel specific flags for a game when needed

Folder-level default for many games

If you put this in a folder-level boost.toml, all games in that folder tree adopt these flags.

[jzintv.flags]
z = 3
gfx-palette = "{usb_mount}/.kbdAndPalettes/sva2_palette.txt"
kbdhackfile = "{usb_mount}/.kbdAndPalettes/Quit_Reset_Pause.kbd"

This is great for consistent behavior across a game collection.

Where jzintv_flags can be used

jzintv_flags are available in config processing for:

• boost_mode = "basic"
• boost_mode = "enhanced"

They are not relevant in pure passthrough behavior (boost_mode = "off").

Game-level override and cancel

A game-specific *_boost.toml can change or remove inherited flags.

[jzintv.flags]
z = 2
kbdhackfile = false

What this does:

• z = 2 overrides the inherited z value for that game
• kbdhackfile = false cancels/removes that inherited flag for that game

Syntax note (different from command-line style)

This is the part that can feel unfamiliar at first.

In command line usage, people are used to writing flags like:

• -z3
• --gfx-palette='/media/usb0/.kbdAndPalettes/sva2_palette.txt'
• --kbdhackfile='/media/usb0/.kbdAndPalettes/Quit_Reset_Pause.kbd'

In Sprint Boost TOML, flags are key/value entries under [jzintv.flags].

For readability, these guides prefer the friendly key style (without leading -/--) in examples. CLI-style keys are still supported.

Examples:

• z = 3
• gfx-palette = "{usb_mount}/.kbdAndPalettes/sva2_palette.txt"
• kbdhackfile = "{usb_mount}/.kbdAndPalettes/Quit_Reset_Pause.kbd"

So you are describing flags as config values, not typing a shell command.

Important TOML quoting rule

If you choose CLI-style keys with a leading - or --, those keys must be quoted.

✅ Valid:

[jzintv.flags]
"-z" = 3
"--kbdhackfile" = "{usb_mount}/.kbdAndPalettes/Quit_Reset_Pause.kbd"

❌ Invalid TOML:

[jzintv.flags]
-z = 3

If TOML is invalid, Sprint Boost may ignore that config file.

Using paths in flag values

You can build path values with built-in tokens and global_variables references.

[jzintv.flags]
kbdhackfile = "{usb_mount}/.kbdAndPalettes/Quit_Reset_Pause.kbd"

Useful built-ins include {usb_mount}, {game_folder}, and {game_file}. You can also use {gv.<key>} values from [global_variables].

Interaction with Sprint game JSON (jzintv_extra)

Sprint Boost still honors Sprint's game JSON jzintv_extra settings when they are present.

Important precedence behavior:

• If jzintv_extra and [jzintv.flags] set the same emulator option, the JSON jzintv_extra takes precedence.
• Your folder/game jzintv_flags are still applied, but overlapping options can be replaced by the game JSON values.

Practical takeaway:

• If a flag in boost.toml seems ignored for one title, check that game's JSON for jzintv_extra.

Override behavior summary

• Folder-level [jzintv.flags] = shared defaults
• Game-level [jzintv.flags] = per-game changes
• More specific config wins
• false is the normal way to cancel an inherited flag

Practical tips

• Start with one or two shared flags at folder level.
• Add game-level overrides only when needed.
• If a flag does not seem to apply, check for a game-level override.

Next step

Continue to:

• 03 05 Config display