Dad Gaming

Turn Batocera Into a Family Console: Kids Mode, Game Lists

A retro console that works is not the same as a retro console the family can use. The installation post left a machine that boots. It did not leave a machine that a seven-year-old can start without help, and it certainly did not leave one that stays inside a set of limits.

This guide takes a working Batocera installation and makes it a living-room console: controllers that respond the first time, a library organised so the right games are visible, and the restricted interface modes that keep the front-end navigable for younger players.

Everything here uses Batocera’s own supported configuration. The official UI mode documentation is the reference for the restricted modes, and the official controller documentation is the reference for pairing and mapping.

KI-Hinweis (KI-Assistenz): Dieser Beitrag wurde von DadChecks Editorial KI-gestützt erstellt und von den automatisierten Prüfagenten der Redaktion geprüft. Keine Person hat den Beitrag selbst geschrieben oder getestet. Es ist eine Recherche, kein Praxistest: Es gab keine eigene Testhardware, keine eigenen Messungen und keine eigene Kaufentscheidung.

Before you start

Requirements

  • A working Batocera installation. If it does not boot yet, do that first: install Batocera on a second SSD.
  • At least one controller, connected over USB or Bluetooth.
  • A keyboard, for the configuration steps. The configuration menus are navigable with a controller, but a keyboard is faster and you will want one for recovery.
  • A USB stick or a spare partition for the configuration backup described below.

Applicable versions. The UI modes and the settings that control them are part of Batocera’s current release. The official documentation is the authority for the exact wording of each menu.

Prerequisites — one rule that matters. Make the changes in this order: controllers first, then the library, then the restrictions. The restricted modes make the configuration menus harder to reach, so configuring the restricted mode first and the controllers afterwards is how people end up locked out of the settings they need.

Step 1: first-time controller setup

The official controller documentation states that Batocera detects most common gamepads automatically and configures them without further input. The practical sequence for a first-time setup:

  1. Connect the controller before you open the settings. Plug it into a USB port, wait a moment, and the front-end will announce it.
  2. Let the automatic configuration stand for the first controller. The automatic mapping is the one the documentation describes for the common Xbox, PlayStation and 8BitDo layouts. Mapping everything from scratch before you know what the automatic mapping does is work you may have to redo.
  3. Test it. Open the front-end, move the pointer with the stick or the D-pad, and confirm the on-screen response. A controller that is paired but not moving is a different problem from one that is not paired at all.

Wired first. For a console that lives under a television, a wired controller removes a whole category of problem. Bluetooth pairing can drop, can re-pair to a different device, and can pair to the console from a different room. If you are buying one controller for a living-room machine, USB is the better bet. Bluetooth is worth it for the second player who is moving around.

Controller mapping

Mapping is where the front-end tells you what each button does. The official documentation covers the controls available while the mapping screen is open.

The mapping that matters most for a family machine is the Start button, because it is the way back out of a menu. Before you finish, confirm that:

  • Start opens the main menu from the front-end.
  • Select opens the per-game options.
  • Back or the equivalent returns from a submenu.

If the Start button does not work, a child can still get into a menu they cannot leave. That is the one mapping failure worth spending five minutes on.

Two controllers, one layout. If two people are going to play, buy both controllers with the same layout. Mixing a D-pad pad with a stick-based pad means one player has a layout that does not match the on-screen prompts, and you have to map the second one to match. This is the advice from the hardware guide, and it holds.

Step 2: organising the library

A console with five thousand games in it is not a console. The configuration work in this step is what turns a disk of files into something usable.

Game organisation

Batocera’s library is organised by system, and each system’s games live in a directory. The configuration is done from the interface rather than from the filesystem for most things, and the official documentation is the reference.

What is worth knowing:

  • A game appears when the front-end can read its file and identify the system. A file in the wrong directory does not appear at all, which is the single most common “my game is missing” cause.
  • Metadata is fetched by the scraper. The front-end can download descriptions, box art and release information for games it recognises. This is covered in the front-end documentation; the point for this guide is that a game with metadata is a game a child can pick from a picture rather than a filename.
  • Scraping takes time and needs a network. On a first run over a large library, this is the step that takes the longest.

Game metadata

Metadata is what makes a game list usable rather than a directory listing. The practical points:

  • Let the scraper run before you build the collections. A collection built from unscraped entries shows raw filenames, which defeats the purpose.
  • Metadata is cached locally. Once fetched, it stays available when the network does not.
  • Game names and descriptions come from a database. Some titles come back with an odd year or an odd description. That is a database entry, not a fault in your install.

Hiding unwanted systems

You do not have to show every system the front-end can emulate. The system visibility settings let you restrict which systems appear in the menu.

For a family machine, this is the highest-value single setting, because it removes the entire category of “how do I get to the game with the weapons I am not allowed”. The settings are under the front-end’s system configuration, and the official documentation covers the per-system and global options.

The rule for choosing what to hide: hide what you do not want a mistake around, not what you find inconvenient. A system with a controller-locking or full-motion mechanic is a good candidate; a system nobody will ask for is just clutter, and clutter is harmless.

Creating curated game collections

Collections are the front-end’s grouping mechanism: a named list of games that appears as its own entry, separate from the per-system lists.

For a family machine, collections are usually the better primary structure than the raw system lists, because a collection can be built around what is actually appropriate rather than around which emulator a game happens to use.

Three points from the official documentation that matter in practice:

  • A game can appear in more than one collection and in its system list at the same time. Hiding the system does not hide the game, and adding it to a collection does not remove it from the system list.
  • Collections are configured through the front-end, which means the changes are stored in the configuration the front-end manages — and can be backed up with it.
  • A collection with one game is still a collection. Useful for a “Saturday morning” set.

Step 3: the restricted UI modes

This is the section the official documentation exists for, and it is where the previous version of this article went wrong. An earlier published version tried to force Kids Mode by editing the configuration file with sed commands in a boot script. That approach is not used here, for two reasons: the commands it used were a substitution that could not work, and editing the configuration file behind the front-end’s back is the wrong layer entirely.

Kiosk Mode versus Kids Mode

The official UI mode documentation describes both modes. The difference in one line each:

Kiosk Mode Kids Mode
What it is for A console that is always in the front-end, with no way to fall out of it A console for younger players, with the library restricted to what has been permitted
Who it is for The owner, or a guest using the machine A child using the machine
Game list The full library, unchanged Only the games that have been explicitly permitted
What the player can change Nothing — that is the point Nothing within the permitted set
What it protects against Accidental changes to the configuration Exposure to the full library, and accidental changes

Both are configured from the front-end’s own settings, and both are stored in the configuration the front-end manages. Neither requires editing a file.

The mode to choose depends on what you are defending against:

  • Kids Mode is the one for a child. The game list is restricted to what you permitted. This is the difference that matters.
  • Kiosk Mode is for the console itself. It prevents accidental changes to a machine that anyone can reach, without restricting what is on it.

A family machine often wants both in sequence: configure everything with the full interface, enable Kids Mode for the children to use, and disable it again when you want to add something.

Selecting the permitted games

The permitted games are selected in the front-end. The procedure is:

  1. Enable Kids Mode from the UI mode settings.
  2. Go to the game list. The games not yet permitted are shown in a separate area of the library — the official documentation describes this as the games being shown but not available, or the list being filtered.
  3. Mark the games to permit. Each permitted game then appears in the normal library.
  4. Check the result by leaving the front-end and coming back, and then by looking at the library as the restricted user would see it.

The important detail is the last one: verify the restriction by using the console as the restricted user will, not by reading the settings screen. A game that is still visible in the menu is visible, whatever the toggle says.

UI restrictions

Beyond Kids Mode’s game list, the front-end offers settings that restrict what the interface itself does — whether the system list is shown, whether the scraper is available, whether the front-end can be exited. These are covered in the same official documentation.

Two warnings that apply to all of them:

  • These settings are easier to lock yourself out of than they look. If the restricted interface hides the settings menu, you need the recovery route below to get back.
  • A restricted mode is a convenience, not a security control. It keeps a seven-year-old out of a settings menu. It does not stop a determined adult, and it should not be treated as a parental control system with the expectations that implies.

Safe recovery from restrictive settings

This is the part that has to work before you need it, not after. If you enable a restrictive mode and the way back into the settings is inside the restricted interface, you have locked yourself out.

The recovery routes, in the order you should try them:

  1. The front-end’s own reset. The official documentation describes a reset to factory settings from the settings menu. If you can still reach the settings menu, this is the route.
  2. Boot the system with the settings menu forced. The official documentation describes a way to access the settings even when the interface is restricted.
  3. The configuration backup. If you made the backup described below, you can restore the configuration from it.
  4. Reinstall the system partition. The last resort: re-image the Batocera drive from the official image. This is why the two-drive layout in the installation guide is worth having — the first disk, with your old system, is unaffected by any of this.

Read the recovery section of the official documentation before you enable the restricted modes, not after.

Backing up the configuration

Before any of the changes in step 3, copy the configuration. The official storage manager documentation describes where Batocera keeps its configuration and how to back it up.

What the backup covers: the front-end settings, the UI mode, the permitted game list, the controller mappings, and the collection definitions. What it does not cover: the game files themselves.

Back it up to a USB stick or to the other drive in the two-drive layout. A backup on the same disk that fails is not a backup.

Avoiding accidental changes

The settings that restrict the console are, by design, difficult to change casually. Which means the opposite risk — the person who set them up cannot change them back without the recovery route. A few habits prevent the common cases:

  • Make the configuration changes in one sitting, then leave the console alone. The settings menu is where the accidents happen.
  • Back up before each group of changes, not just once at the start. The controller mapping, the library and the UI mode are separate changes and each can be its own rollback point.
  • Write down which mode is enabled. In a restricted interface the mode name may not be visible, and “which mode did I set this to” is the first question when something looks wrong.
  • Keep the keyboard. Every recovery route in this article assumes you can type.

Testing startup behaviour

The last step is the one that decides whether the console is actually ready: power it off and turn it back on, without touching anything.

Test in this order:

  1. Cold boot to the front-end. Does it reach the library without a keyboard, without a menu selection?
  2. Controller first. Is the controller connected and responding before you touch anything else? A controller that has to be re-paired after every power cycle is not a family console.
  3. Start button. Can you open the main menu?
  4. A permitted game. Does it launch, and does the controller control it?
  5. A non-permitted game. Is it absent from the library in Kids Mode?
  6. Exit and re-enter. Can you get out of the game and back to the library?
  7. Second controller, if you have one: does it appear and work after a cold boot?
  8. The restricted view. Look at the library as the restricted user would see it, not as the administrator sees it.

If any of these fails, the console is not finished. Work the troubleshooting table before handing it over.

Troubleshooting common controller problems

Symptom Likely cause What to do
The controller is not detected at all Not connected, or a pairing that did not complete Reconnect the USB cable, or remove and re-pair the Bluetooth device
Detected, but the pointer does not move The axis mapping is wrong or the stick needs calibration Re-run the controller configuration for that pad
Buttons do the wrong thing The mapping does not match the on-screen prompts Re-map the buttons; confirm the Start button first
Works in the front-end, not in a game Per-emulator input configuration differs Configure the input in the emulator that failed, not only in the front-end
Only one of two controllers works The second pad was not configured Configure the second controller explicitly
Works, then stops after a power cycle Bluetooth pairing was not persistent Use the USB port for that controller, or re-pair and save the pairing
The console ignores the controller entirely The restricted mode is still enabled from a previous setup Follow the recovery route above

A final living-room console checklist

Everything below is a thing you can check in a minute.

Hardware

  • [ ] The console boots on its own, from a cold start.
  • [ ] The display output is the one the television expects, at a resolution the television accepts.
  • [ ] The first controller is wired and permanently connected.
  • [ ] A keyboard is within reach for recovery.
  • [ ] The machine is on the wired network, or the wireless one is saved.

Library

  • [ ] The games that should be there are there.
  • [ ] The games that should not be there are not.
  • [ ] The library is scrolled, so every entry has a name and an image rather than a filename.
  • [ ] The collections reflect what you want on the front page.

Restriction

  • [ ] The UI mode is set deliberately, and you know which one it is.
  • [ ] The permitted game list is correct, checked from the restricted view.
  • [ ] You have read the recovery route for the mode you enabled.
  • [ ] You have a configuration backup on a drive that is not the one that failed.

Testing

  • [ ] Cold boot reaches the library with no input other than the controller.
  • [ ] Start button opens the menu, and back returns from it.
  • [ ] A permitted game launches and plays.
  • [ ] A non-permitted game is absent.
  • [ ] Both controllers work after a cold boot.

Limitations

  • Not tested with a child. No child tested this console, and this article does not claim otherwise.
  • The procedure was not executed on the reference hardware. The configuration steps are documented from the official sources, not recorded from a session on the machine described in the hardware guide.
  • Menu wording follows the official documentation. Batocera renames things; your version’s documentation is the authority.
  • Kids Mode is a front-end restriction, not a security control. It keeps a young player inside a set of games. It is not a parental control.

References