Loom: The Adventure with No Inventory

By 1990, LucasArts had a design rulebook that most of the adventure genre was starting to imitate: no dead ends, no deaths that punished a player for something they couldn’t have known, verbs enough to cover any reasonable action. Loom, designed by Brian Moriarty, took that rulebook and threw half of it away on purpose. There is no inventory in Loom. There is no verb list. There’s a distaff, a spellbook of four-note musical patterns, and a world that responds to them. It remains the strangest interface decision LucasArts ever shipped, and one of the most interesting.

Moriarty had come from Infocom, where he’d written text adventures including Trinity and Wishbringer, and Loom carries some of that pedigree in its restraint. The premise: Bobbin Threadbare, the last member of a guild of weavers called the Loom, is cast out into a world governed by other guilds — Shepherds, Glassmakers, Blacksmiths — each with its own magical vocation. Bobbin’s only tool is his distaff, an instrument that can play short musical phrases, and every spell in the game is one of these four-note “drafts”: Opening, Dyeing, Sharpening, and so on, learned by observing them cast around the world and then replayed at will.

A verb list made of notes

The mechanical trick is elegant. Instead of clicking “use key on door,” you play the four-note draft for Opening at a locked door, or a chest, or an eye that needs to see. The same draft applies broadly across contexts, and the game’s puzzles come from figuring out which draft applies to a given situation and where to aim it, not from hunting an inventory for the one object that unlocks a specific scripted event. Notably, several drafts can be played backwards for an inverted effect — Opening reversed becomes Closing, Dyeing reversed strips colour rather than adding it — which turns the small set of core drafts into roughly double their number of practical tools without the game ever needing to teach you a new interface.

This is a genuinely different kind of puzzle-solving from anything LucasArts’ SCUMM-driven contemporaries offered. Monkey Island’s puzzles are about correctly identifying an item and its target. Loom’s puzzles are about correctly identifying a transformation and where to apply it — closer to a small, learnable grammar than to an ever-growing pile of collected objects. Moriarty was explicit, in interviews around the game’s release, that he wanted to build an adventure a genuinely new player could pick up without the genre’s usual baggage of exhaustive item-combining and dead inventory clutter.

Difficulty as a dial, not a wall

Loom shipped with a difficulty option baked directly into the format: the CD-ROM “Talkie” release let players skip past required draft-guessing sequences by simply consulting the manual’s list of known drafts, effectively letting a player choose how much of the game’s difficulty they wanted to opt into. That’s an unusual thing to build in 1990, when most adventures treated their exact solution as the entire point and offered no accommodation for a player who wanted the story more than the friction. Moriarty’s own stated position was that a good story shouldn’t be gated behind a puzzle a player couldn’t solve, and Loom’s design is one of the earliest serious attempts in the genre to treat accessibility as a design axis rather than an afterthought.

The game is also unusually short and unusually gentle by the standards of its era — there is essentially no way to permanently fail, no inventory item that can be lost or wasted, and the handful of dangerous encounters resolve through the same draft system rather than through combat or timed reflexes. Where King’s Quest built genuine tension out of a player’s fear of an unwinnable state, Loom removed that fear almost entirely, betting that a shorter, kinder experience with a genuinely novel interface would be memorable in its own right rather than through difficulty.

The look of a world without an inventory bar

Removing the inventory changed more than the interface — it changed how the game had to be shot and staged. Adventures built around item-collecting typically reserve screen space for a persistent inventory strip, a constant reminder of what you’re carrying and, implicitly, what you still need to find a use for. Loom has no such strip. The full screen belongs to the world, and Bobbin’s distaff appears only when a draft is being played, which gives every location a cleaner, more painterly composition than the genre’s norm. The game’s soft, painterly backgrounds — deliberately closer to a storybook illustration than to the busier, prop-cluttered rooms LucasArts built for Monkey Island — read as intentional once you notice how little clutter the interface itself demands. A game about weaving and threads earns a visual identity built on texture and colour rather than on a shelf of collectible objects, and the absent inventory bar is a large part of why that identity holds together.

Why the systems idea still matters

The lasting value of Loom is its proof that an adventure game’s core verb — the thing you do over and over to interact with the world — need not be “click item on target,” a lesson that outlasts nostalgia for any one puzzle chain. A four-note musical phrase, learned by ear and by observation, carries just as much of a puzzle-solving grammar as an inventory does, provided the world is built consistently enough around it. That’s the same design lesson later systems-driven games would rediscover in different clothes — a small rule set, applied broadly and combined cleverly, doing more work than a large pile of bespoke one-off interactions ever could.

It’s worth setting Loom against Ron Gilbert’s puzzle grammar for Monkey Island, written at the same studio in the same period: Gilbert’s essay on puzzle fairness assumes an inventory as the basic unit of adventure design, the thing a puzzle is built around. Loom is the one LucasArts game from that era that questioned whether the inventory needed to exist at all, and the fact that it still produces coherent, satisfying puzzle chains without one is the strongest evidence Moriarty’s bet actually paid off.

The audio problem nobody else had to solve

Loom’s central mechanic created an engineering headache none of its contemporaries faced: the game needed players to reliably distinguish musical notes, which meant it needed a sound system precise enough that a four-note phrase read as unmistakably itself rather than as an approximation. On the era’s PC sound hardware — a landscape of competing standards, from the internal PC speaker’s beeps up through early Sound Blaster and Roland MT-32 cards — that was a genuinely hard problem. LucasArts built the game around its own iMUSE audio system, developed specifically to keep music responsive to game state, and Loom became one of its first serious showcases: a title where the score wasn’t backing music but the interface itself, meaning any latency or mistracked note wasn’t just an atmosphere problem, it broke the puzzle.

That technical investment paid off in ways that shaped LucasArts’ later, more famous games. iMUSE went on to underpin the dynamic scoring in Monkey Island 2 and beyond, adjusting musical themes on the fly as players moved between rooms and triggered events, and the studio’s reputation for interactive music arguably starts with the specific problem Loom forced its engineers to solve. An experiment built around a distaff full of four-note phrases ended up leaving a permanent mark on how the whole studio scored every subsequent adventure it shipped.

The commercial afterlife of an experiment

Loom didn’t spawn a franchise. There was talk of a trilogy — Moriarty has spoken since about planned sequels that never materialised as LucasArts’ priorities shifted toward the more broadly commercial Monkey Island line — and the single game that exists reads, in hindsight, like the first act of something bigger that got left unfinished. That makes it something rarer than a classic: an experiment the studio ran once, judged interesting rather than commercially essential, and moved on from without ever quite repeating it elsewhere in its catalogue.

The result is a game that still gets cited whenever the conversation turns to interface design in adventures, precisely because so few other studios ever tried anything as structurally different. Sierra kept building around typed and later point-and-click inventories. LucasArts itself went back to a conventional verb-and-inventory system for every subsequent release. Loom’s four-note spellbook remains a genuine dead end in the genre’s evolutionary tree, and the reason is availability rather than quality: nobody else picked up the thread it left dangling.

Spoilers below

The plot resolves with Bobbin discovering that the Age of Great Guilds is ending and that his own transformation — set up through a running thread about swans, feathers and the Weavers’ guild motif of transmutation — is the mechanism by which he ultimately confronts the game’s antagonist, the sorceress Hetchel’s rival within the Loom guild itself. The final sequence has Bobbin using a specific combination of drafts, including a Transcendence-style spell built from the game’s core vocabulary, to resolve the guild conflict rather than through any conventional combat encounter.

Consistent with the game’s tone throughout, the ending is quiet rather than triumphant — there’s no boss fight, no last-minute reveal designed to shock, just the same careful application of the draft system that’s carried every puzzle before it. That restraint at the climax is the clearest evidence of how disciplined Moriarty’s design was: he built one small toolset and trusted it to resolve the entire story, right through to the credits, without ever reaching for a mechanic outside the game’s own established grammar.

If the four-note draft system is what hooked you, the clearest next step in the same design lineage — a puzzle grammar built on rules rather than object-hoarding — is Day of the Tentacle, which took the opposite approach to solving the same fairness problem and made it work through three simultaneous, interlocking timelines instead.