Differences

This shows you the differences between two versions of the page.

--- batocera_conf_syntax [2022/02/18 21:07] – note about conflict atari
+++ batocera_conf_syntax [2022/09/06 11:28] (current) – SSH command too atari
@@ Line 13: / Line 13: @@
 ===== batocera.conf option keys and values =====
-''/userdata/system/batocera.conf'' is the main user-configuration file in Batocera. This will contain all the settings you may have set in **GAME SETTINGS**, **ADVANCED PER SYSTEM OPTIONS** and a few other places.
+''/userdata/system/batocera.conf'' is the main user-configuration file in Batocera, it can be [[:add_games_bios#while_batocera_is_running|accessed from the network share or the file manager]] or [[:access_the_batocera_via_ssh|via SSH]] with the following:
+<code bash>
+nano /userdata/system/batocera.conf
+</code>
+This will contain all the settings you may have set in **GAME SETTINGS**, **ADVANCED PER SYSTEM OPTIONS** and a few other places.
 <WRAP center round info>
@@ Line 65: / Line 71: @@
 This will change the **EXTERNAL PALETTE** option for the [[systems:c64|Commodore 64]] game "Arkanoid - Revenge of Doh" to use the "vice" palette. Here, the system is "c64", the ROM filename and extension is "Arkanoid - Revenge of Doh (USA, Europe).zip", the key name is "external_palette" and the value is "vice". No ''<subkey # name>'' is used.
-**Folder-specific option**
+**Folder-specific option** (introduced in **v34**)
 Here's an example of setting an option for games launched from a certain folder:
@@ Line 107: / Line 113: @@
 However, if you'd like to find the keys manually, you have to change your approach depending on which keys you are after:
-  * To find the global keys (ones that can be applied to //most// systems) manually, look through the code and figure out its logic in the launcher script (in the ''/usr/lib/python3.9/site-packages/configgen/'' folder).
+  * To find the global keys (ones that can be applied to //most// systems) manually, look through the code and figure out its logic in the launcher script (in the ''/usr/lib/python#.#/site-packages/configgen/'' folder).
-  * To find the emulator keys (of which apply to all systems that emulator supports, usually) manually, look through the code and figure out its logic in its [[modify_the_system_while_it_s_running#editing_system_files|configuration generator]] (most of which are in ''/usr/lib/python3.9/site-packages/configgen/generators/'').
+  * To find the emulator keys (of which apply to all systems that emulator supports, usually) manually, look through the code and figure out its logic in its [[modify_the_system_while_it_s_running#editing_system_files|configuration generator]] (most of which are in ''/usr/lib/python#.#/site-packages/configgen/generators/'').
   * To see system-specific keys, look at the ''/usr/share/emulationstation/es_features.cfg'' file. The ''features'' tag shows which "global" keys can be applied to your system, while the rest of the system-specific keys are specified in their own core option section.