Importing and Managing ScummVM Games

Import ScummVM game folders through LaunchBox’s current ROM workflow, configure standalone or RetroArch launching, manage saves and variants, and migrate legacy entries safely.

Written By launchbox

Last updated 6 days ago

ScummVM runs supported adventure games and other classics from their original game-data files. In current LaunchBox releases, ScummVM is configured as a normal emulator and games are imported through the regular ROM import workflow. LaunchBox passes each game folder to ScummVM, which detects and starts the supported game in that folder.

Before you begin

  • Use game files you legally own. LaunchBox and ScummVM do not supply commercial game data.

  • Check the ScummVM compatibility list and the supported-game notes for your title.

  • Copy all required files from the original discs or installed game. Requirements vary by title, release, language, and original platform.

  • Extract installers and archives first. ScummVM normally needs access to the actual data files.

Organize the game folders

Use one permanent folder per game beneath a parent folder, for example:

D:\Games\ScummVM\  
            Beneath a Steel Sky\  
            Day of the Tentacle\  
            The Dig\

Preserve required subfolders, speech, video, music, fonts, and other supporting files. Do not remove unfamiliar files simply because they do not look executable. ScummVM usually runs the data through its own engine instead of launching the original DOS or Windows executable.

If a game has multiple discs, follow that game's ScummVM data-file instructions. Required files from all discs are commonly combined into one game folder, but duplicate filenames must be handled exactly as the title's documentation specifies. Do not overwrite files blindly, and do not build a console-style M3U unless the instructions for your chosen ScummVM setup explicitly call for one.

Import games with standalone ScummVM

  1. In LaunchBox, open Tools > Import > ROM Files.... You can also drag the parent folder into LaunchBox and choose the ROM import workflow.

  2. Add the parent folder that contains your individual game folders. When asked whether to include subfolders, allow LaunchBox to scan the library rather than treating every data file as a separate game.

  3. Choose or create a local platform such as ScummVM. If you use another platform name, set Scrape As to ScummVM so the importer applies its ScummVM folder-detection behavior.

  4. Select ScummVM as the emulator. If it is not configured, the wizard can download and configure it for you.

  5. Choose the metadata and media options you want.

  6. Review the final import list carefully. Each row should represent a game folder, not every file inside it.

  7. Finish the import, then test several games from LaunchBox.

The LaunchBox-managed ScummVM setup uses a command equivalent to -p %romfile% --auto-detect --fullscreen. For this setup, a game's Application Path is its data folder. ScummVM examines that folder at launch, so you do not need to add the game to the ScummVM Launcher or enter a target ID first.

Install, repair, or update ScummVM

You can also add ScummVM from Tools > Manage > Emulators.... Point a manually configured entry to scummvm.exe, or use LaunchBox's download option. LaunchBox installs a managed copy beneath LaunchBox\Emulators\ScummVM and creates scummvm.ini beside the executable. In current ScummVM releases, that file enables portable mode, keeping configuration and application data with the emulator.

When LaunchBox recognizes an emulator whose executable is named scummvm.exe, its emulator editor can also offer supported update or repair actions. Back up the ScummVM folder and important saves before updating, then test a few representative games. New releases can add engines and detection signatures, but a new build can also change behavior for a particular title.

Add or repair one game manually

For a modern standalone-ScummVM entry:

  1. Add a game or edit the existing game.

  2. On Launching, set Application Path to the folder containing that game's data files.

  3. On Launching > Emulation, enable emulation and choose the ScummVM emulator entry.

  4. Confirm the game's platform is associated with ScummVM under Tools > Manage > Emulators....

  5. Save and test the game.

The Root Folder field is not a substitute for the game's Application Path. With the standard standalone configuration, the folder supplied as the ROM path is what ScummVM scans.

Game IDs, configured targets, and automatic detection

ScummVM distinguishes between a supported game ID and a configured target. A target is an entry saved in ScummVM's configuration and can have its own settings. The modern LaunchBox default instead supplies the game-data folder with --auto-detect, so neither value normally needs to be stored in the LaunchBox game.

If you replace the default command line with a target-based custom setup, add and test the game in the ScummVM Launcher first, then use the exact configured target. A LaunchBox title, folder name, game ID, and target can all be different. See ScummVM's command-line documentation before changing the default parameters.

What about .scummvm files and RetroArch?

LaunchBox also supports importing .scummvm launcher files when the ScummVM platform is being run through RetroArch. That is a different launch arrangement from the standalone ScummVM folder workflow. A .scummvm file normally identifies the game for the RetroArch ScummVM core, whereas standalone ScummVM can receive the game folder directly and use automatic detection.

Choose one method deliberately. Do not mix folder entries, .scummvm files, the standalone executable, and the RetroArch core unless you understand which emulator and command line each entry uses.

Variants, languages, and uncertain detection

The same title can have DOS, Windows, Macintosh, Amiga, FM-Towns, console, demo, or language-specific data. If ScummVM reports multiple matches or LaunchBox starts the wrong variant:

  1. Open scummvm.exe directly.

  2. Select Add Game and choose the exact game-data folder.

  3. Review the variants ScummVM detects and compare them with the files you own.

  4. Test the correct variant directly in ScummVM.

  5. If automatic detection remains ambiguous, use a tested target-based custom command only for that game or create a separate emulator configuration.

If ScummVM cannot detect or run the folder directly, changing LaunchBox metadata will not fix the underlying data problem.

Settings, configuration, and saves

With automatic detection, command-line options such as fullscreen can override applicable ScummVM defaults. Open ScummVM directly to configure graphics, audio, input, extra paths, and save locations. Settings saved for a configured target are not necessarily applied when the game is launched through --auto-detect; add only the command-line overrides you actually need.

A LaunchBox-managed ScummVM installation is portable because its installer creates scummvm.ini beside the executable. ScummVM therefore keeps portable application data—including saves—under its emulator folder unless you change its Paths settings. A manually installed non-portable copy typically uses ScummVM's Windows user-data locations. Check Global Options > Paths in ScummVM rather than assuming where saves are stored.

Back up both the location shown as ScummVM's save path and its configuration before updating, moving, or replacing the emulator. LaunchBox metadata is not a backup of ScummVM saves or configuration.

Controllers and Additional Apps

Many supported games were designed for a mouse and keyboard. Configure global or engine-specific keymaps in ScummVM, and test pointer movement, clicks, menus, and any virtual-keyboard requirement. Check that LaunchBox or Big Box exit and Pause controls do not conflict with essential game inputs.

Use LaunchBox Additional Apps for manuals, setup utilities, bonus programs, or an original executable you want available beside the ScummVM launch. An Additional App does not automatically become part of the ScummVM game-data folder. Avoid setting an app to run before or after the game unless that automation is intentional and tested.

Moving a ScummVM library

Moving game folders does not automatically rewrite every LaunchBox entry. Update the affected games' Application Paths to their new folders, then test them. Moving the emulator also requires updating its scummvm.exe path. If you use configured ScummVM targets or custom extra/save paths, update those inside ScummVM as well.

Before a bulk path change, create a LaunchBox data backup and keep the old folders until the new paths have been verified. Changing a path in LaunchBox does not itself move, copy, or delete the underlying game files.

Legacy LaunchBox ScummVM entries

Older LaunchBox libraries may contain games that use the retired built-in ScummVM integration. For those existing entries, Edit Game > Launching > ScummVM can still appear and contains Use ScummVM, Game Data Folder Path, What Game Is It?, Fullscreen, and Aspect Correction. This legacy mode launches the old copy expected at LaunchBox\ThirdParty\ScummVM\ScummVM.exe; it is not the workflow LaunchBox now creates for new imports.

The legacy ScummVM, DOSBox, and normal Emulation modes are mutually exclusive for the main launch. Do not enable or disable them casually: turning off the legacy ScummVM option clears its stored game-data folder and selected game type. To modernize a legacy entry, first configure the current ScummVM emulator, record the old data folder, then change the game to use that folder as its Application Path and select ScummVM under Emulation. Test the migrated entry before removing any old files.

Troubleshooting

  • The import creates many entries for one game: make sure the platform or Scrape As value is ScummVM and import the parent folder with standalone ScummVM selected.

  • No games appear in the final list: verify that each child folder actually contains files, that the platform maps to ScummVM, and that the selected locations are accessible.

  • The game is not detected: the files may be incomplete, unsupported, inside an archive or installer, or from an unrecognized release. Test the same folder with ScummVM's Add Game or detection tools.

  • Several games or variants are detected: separate unrelated games into different folders and identify the correct language, platform, and release.

  • ScummVM opens to its Launcher: verify the game's Application Path is the data folder and that the emulator still includes -p %romfile% --auto-detect.

  • ScummVM says the path is missing: correct the LaunchBox Application Path; changing Root Folder alone is insufficient.

  • Music, speech, or video is missing: consult the title-specific ScummVM data-file notes for required disc audio, speech, video, or extra files.

  • The game works in ScummVM but not LaunchBox: compare the executable, folder, command line, and whether your direct test used a configured target whose settings automatic detection does not use.

  • Saves seem to have disappeared: confirm which ScummVM executable is launching and check its configured save path. Managed portable and manually installed copies may use different locations.

  • A .scummvm file does not launch: confirm the game is intentionally configured for the RetroArch ScummVM core and that the file contains the correct identifier.

Recommended beginner setup

Keep one complete folder per game, import the parent folder through Tools > Import > ROM Files..., let LaunchBox download standalone ScummVM, and keep the default automatic-detection command line. Test uncertain data directly in ScummVM, preserve the managed emulator folder and saves, and consult the official game notes for title-specific disc and media requirements.