Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:SCUMM resource files

From ReverseEngineering.wiki
Format
Developer LucasArts
Extensions .000 .001 .LA0 .LA1 .lfl .SOU .BUN
Endianness little in v3-v5 file structure; tags big-endian block names in later versions
On this wiki Facts · Code · Notes · Topics

Resource files of LucasArts' SCUMM adventure engine (index .000/.LA0 and data .001/.LA1 files, or per-room .lfl files in v3): tagged blocks (LECF, LFLF, ROOM, DOBJ...) in the data files, wrapped in a single-byte XOR in most games (0xFF in v1-3, 0x69 from v5).

Overview

SCUMM games keep their data in an index file (object/room/script/costume/sound directories) and one or more data files. Everything ScummVM (GPL) knows about the layout is in engines/scumm (resource.cpp, file.cpp). This page records the parts confirmed in ScummVM at commit 98d8fda.

XOR obfuscation

The files are XORed byte by byte with a constant key, so no tag is visible in a hex dump until you XOR the whole file. ScummEngine::getEncByte (resource.cpp) returns 0xFF for version <= 3, 0x69 for version 5 and later (feature GF_USE_KEY), and 0 for version 4 when the room is 0 or >= 900 (the index/boot files); games without the feature use 0. Sound files use a separate key (_sfxFileEncByte).

Index blocks

The index file is a series of tagged blocks; ScummVM's readIndexBlock (resource.cpp) recognises, among others, DOBJ (object owner/class table), DROO/DIRR (room directory), DSCR/DIRS (scripts), DCOS/DIRC (costumes), DSOU/DIRN (sounds), DCHR/DIRF (charsets), RNAM (room names), MAXS (maximum counts), AARY (arrays), and for Humongous Entertainment v7 DLFL, DISK, SVER, INIB; ANAM (The Dig, The Full Throttle) and DRSC (Curse of Monkey Island) also appear. Room data uses the tag ROOM; costumes COST, or AKOS when the game has the new-costume feature.

Block layout and the outer containers

Unverified (from memory of the SCUMM documentation, not checked in the source read here): a block is a 4-byte tag followed by a 4-byte big-endian size that includes the 8 header bytes (v5+; older versions use a 2-byte size). Data files start with LECF containing LOFF (room offsets) and one LFLF per room, each holding ROOM and its scripts, sounds and costumes. Test by XORing with 0x69 and looking for LECF at offset 0 of the .001 file.

Tools

ScummVM (reader for every version), ScummVM tools (descumm, extraction).

Code & repositories

  • https://github.com/scummvm/scummvm @ 98d8fda924f4d469d1281a0747dc4385462a78c6 · license: GPL-3.0
    ScummVM (GPL-3.0): engines/scumm and engines/sci/resource readers for SCUMM and SCI resources
    Tested on: source read, not run: source reading only · checked 2026-10-18; last activity 2026-10-18

Pitfalls

  • Wrong key on a v4 game: the boot room files use no XOR, the others do.
  • Humongous Entertainment games (HE) use different tags and an index of their own.