10 min read

Sierra Parser Commands Guide

Last updated: February 7, 2026

Overview

The text parser was Sierra On-Line’s primary interface for adventure games from 1984 to 1991, requiring players to type commands to interact with game worlds. This system powered the AGI engine era (1984-1989) and continued into the early SCI era (1988-1991) before being replaced by point-and-click interfaces.

Understanding the parser is essential for playing classic Sierra adventures—from King’s Quest through Leisure Suit Larry III—and can mean the difference between frustration and enjoyment.

What is a Text Parser?

A text parser is an input system that interprets typed commands and translates them into game actions. Sierra’s parser understood approximately 1,000 words per game12, though this varied by title—with responses ranging “from helpful to humorously sarcastic.”2

The parser worked through verb-noun combinations:

  • LOOK TREE
  • GET SWORD
  • TALK MAN
  • OPEN DOOR

Players typed commands into a text input line while controlling their character with arrow keys or joystick. This hybrid approach—keyboard movement plus typed commands—was revolutionary for 198434.

How It Worked

  1. Player positions character near an object or person
  2. Player types a command (e.g., LOOK AT STATUE)
  3. Parser analyzes the text for recognized verbs and nouns
  4. If understood, the game executes the action
  5. If not understood: “I don’t understand” or similar response

The parser responses ranged from “helpful to humorously sarcastic”1, and discovering witty rejection messages became part of the entertainment.

Common Verbs and Commands

Essential Verbs

These verbs work across virtually all Sierra parser games:

VerbFunctionExample
LOOKExamine objects/environmentLOOK AT PAINTING
GET/TAKEPick up itemsGET KEY
OPENOpen doors, containersOPEN CHEST
CLOSEClose doors, containersCLOSE DOOR
TALK/ASKSpeak to charactersTALK TO MAN
GIVEGive inventory itemsGIVE BREAD TO BEGGAR
USEGeneral interactionUSE ROPE
DROP/PUTPlace itemsPUT ROCK IN HOLE
READRead signs, books, notesREAD SIGN
PUSH/PULLMove objectsPUSH BOULDER
CLIMBAscend surfacesCLIMB LADDER
SWIMWater navigationSWIM

Game-Specific Commands

Different series required specialized vocabulary:

Police Quest56:

  • RADIO - Use police radio
  • CUFF - Handcuff suspects
  • SEARCH - Pat down suspects
  • CITE - Issue citations
  • BOOK - Process prisoners

Space Quest78:

  • SCAN - Use scanner equipment
  • PRESS BUTTON - Operate controls
  • HIDE - Take cover

King’s Quest III spell-casting910:

  • Commands followed exact manual wording
  • Required precise punctuation
  • Single typos caused death

Parser Tips and Tricks

Phrasing Matters

The parser was notoriously literal. If one phrasing doesn’t work, try alternatives:

❌ PUT BAG BOTTLE (fails due to parser bug in LSL21112) ✅ PUT THE BAG IN BOTTLE

As Al Lowe explained: “The day before the game shipped, the system programmer in charge of ‘the parser’ fixed a bug that I’d been complaining about for days. He assured me he changed nothing else. I foolishly added the new code to the game.”12 The bug causes commands like “PUT BAG BOTTLE” to fail because the parser incorrectly treats “bag” as a verb rather than a noun. “16 years later, I’m still answering emails about a bug I swear I didn’t create!”12

❌ TAKE ITEM ✅ GET ITEM or PICK UP ITEM

Positioning is Critical

“The parser system, while functional, could be frustratingly rigid, requiring precise positioning and phrasing to execute commands successfully”1314.

  • Walk directly next to objects before interacting
  • Some commands only work from specific screen positions
  • If a command fails, try moving closer

Common Frustrations

“I don’t understand” The parser didn’t recognize your wording. Try:

  • Simpler phrasing
  • Different synonyms
  • Removing articles (THE, A, AN)

“You can’t do that” The parser understood but the action isn’t possible. Either:

  • Wrong location/timing
  • Inventory item required
  • Different approach needed

“I see no _____ here” The object isn’t in this screen or isn’t visible. Check:

  • Are you on the right screen?
  • Is the object hidden?
  • Have you examined the area with LOOK AROUND?

The Speed Problem

In Gold Rush!, “the text parser doesn’t pause while typing commands”1516, meaning the game continued running while you typed. This required fast typing during time-sensitive sequences.

Spell-Casting Nightmare

King’s Quest III featured the most demanding parser use in Sierra history. Players had to:

  1. Follow spell recipes from the physical manual exactly
  2. Type every word, comma, and period precisely
  3. Complete entire spell sequences without errors

“A single misspelling when casting spells, even when just preparing ingredients, results in spell backfiring with fatal results”1718. Players often needed 10-15 attempts to complete spells correctly919. The parser was described as “stubborn” by reviewers, requiring precise phrasing to accomplish tasks.20

Humorous Parser Responses

Sierra designers filled their games with witty responses to unusual commands:

Leisure Suit Larry Series

Typing inappropriate commands in Leisure Suit Larry yielded memorable responses2122:

  • MASTURBATE → “Larry, the whole idea was to stop doing that!”
  • LOOK AT PUSSY → “Obviously, restraint is no problem for you, Larry”

The second game’s parser responses were praised as “the only parts of the game that have aged gracefully”2324.

King’s Quest III

When players used profanity: “Obviously, you were raised by a naughty wizard”2526.

Typing EAT CHICKENS produced: “Sorry, Colonel; they’re not even dead yet!”—referencing KFC founder Colonel Sanders2526.

Space Quest Series

The Space Quest games rewarded experimentation with the parser. Hidden easter eggs included2728:

  • Typing KEN made Ken Williams walk onscreen complaining the game was behind schedule
  • A specific dialogue with a Sarien guard about owning King’s Quest II awarded 6 bonus points29

The Transition to Point-and-Click

Why the Parser Disappeared

By 1990-1991, Sierra phased out the parser for several reasons:

  1. Accessibility: “People solved the game much faster because they didn’t have to guess which words we wanted them to type”—Al Lowe on LSL53031

  2. Competition: LucasArts’ SCUMM interface proved more accessible2

  3. Technical Progress: Mouse-driven interfaces became standard

The SCI1 Icon Bar

SCI1 games (1990-1991) introduced the iconic interface replacing the parser3233:

  • Walk - Navigate character
  • Look - Examine objects
  • Hand - Interact/manipulate
  • Talk - Converse with characters
  • Inventory - Access collected items

Hybrid Approaches

Some later games offered both options:

Gold Rush! Anniversary lets players “switch between a traditional text parser interface and a modern point-and-click system at any time”3435. However, “certain puzzles require switching to typed commands to complete”34.

Leisure Suit Larry 7 features “a unique hybrid interface that combines point-and-click mechanics with an optional text parser”3637. The parser remembered previously used commands, allowing players to reuse actions like “fart” throughout the game38.

Parser Era Games

AGI Era (Text Parser Required)

YearGameNotable Parser Feature
1984King’s Quest IFirst graphical adventure parser4
1985King’s Quest IIPull-down menus added (1987 re-release)39
1986King’s Quest IIIComplex spell-casting system10
1986Space Quest ISci-fi vocabulary, witty responses40
1987Space Quest IILast major AGI release
1987Police Quest IPolice procedure vocabulary6
1987Leisure Suit Larry IAdult humor responses22
1988Gold Rush!Real-time parser (no pause while typing)16

SCI0 Era (Parser with Mouse Movement)

YearGameNotable Parser Feature
1988King’s Quest IVDual AGI/SCI release
1988Leisure Suit Larry IIFamous parser bug (“PUT BAG”)12
1989Leisure Suit Larry IIILast Larry parser game14
1989Space Quest IIIParser with SCI graphics
1989Quest for Glory IRPG elements with parser

Simplified/No Parser (Children’s Games)

Mixed-Up Mother Goose was “deliberately designed to be simple enough that ‘even young children can play it when adults are out of the room’“41. The AGI implementation was “notably simplified, removing the text parser that was standard in other AGI titles to accommodate non-reading players”41.

Playing Parser Games Today

Tips for Modern Players

  1. Keep notes on parser vocabulary that works1
  2. Save frequently—Sierra games are unforgiving
  3. Be patient with phrasing—try multiple approaches
  4. Read the manual—essential for copy protection puzzles and spell systems26
  5. Use walkthroughs sparingly—“half the fun is experimentation”1

ScummVM Enhancement

ScummVM offers features that ease parser frustration42:

  • Save states
  • Text input history
  • Consistent speed across systems

All AGI and SCI parser games are fully supported142.

See Also

Internal References

External References

Footnotes

  1. Adventure Game Interpreter – Parser vocabulary, interface details, ScummVM support ↩ ↩2 ↩3 ↩4 ↩5

  2. Hardcore Gaming 101 – Space Quest – Retrospective on parser mechanics, series analysis ↩ ↩2 ↩3

  3. 1984 - King’s Quest - Quest for the Crown – Hybrid keyboard/parser interface, parser commands ↩

  4. Sierra Fandom Wiki – Space Quest: The Sarien Encounter – Parser input interface, AGI engine details ↩ ↩2

  5. 1987 - Police Quest - In Pursuit of the Death Angel – Police procedure commands, protocol requirements ↩

  6. MobyGames – Police Quest I – Police procedure commands, game mechanics ↩ ↩2

  7. 1986 - Space Quest - The Sarien Encounter – Parser input, sci-fi commands ↩

  8. Sierra Fandom Wiki – Space Quest I – Parser commands, pseudo-3D environment ↩

  9. 1986 - King’s Quest III - To Heir Is Human – Spell-casting system, parser criticism, 10-15 spell attempts ↩ ↩2

  10. Wikipedia – King’s Quest III – Release dates, spell-casting system, technical firsts ↩ ↩2

  11. 1988 - Leisure Suit Larry Goes Looking for Love (in Several Wrong Places) – Parser bug (“PUT BAG”) ↩

  12. Al Lowe Official Site – Clues and Cheats – LSL2 parser bug explanation, development anecdote ↩ ↩2 ↩3 ↩4

  13. 1989 - Leisure Suit Larry III - Passionate Patti in Pursuit of the Pulsating Pectorals – Precise positioning requirements ↩

  14. Adventure Classic Gaming – LSL3 Review – Positioning requirements, interface rigidity ↩ ↩2

  15. 1988 - Gold Rush – Real-time parser without pause ↩

  16. Abandonware DOS – Gold Rush! – Real-time parser mechanic ↩ ↩2

  17. 1986 - King’s Quest III - To Heir Is Human – GameFAQs review on spell-casting deaths ↩

  18. GameFAQs – King’s Quest III User Review – Spell mechanic criticism, death on typos ↩

  19. Diary of a Part Time Writer – King’s Quest III – Spell attempt counts, magic map mechanic ↩

  20. Just Games Retro – King’s Quest III – Parser stubbornness, version differences ↩

  21. 1987 - Leisure Suit Larry in the Land of the Lounge Lizards – Parser responses, humor ↩

  22. MobyGames – Leisure Suit Larry I – Parser responses, adult humor ↩ ↩2

  23. 1988 - Leisure Suit Larry Goes Looking for Love (in Several Wrong Places) – IGN on parser responses ↩

  24. IGN – Revisiting Leisure Suit Larry – Parser responses praised as aging gracefully ↩

  25. 1986 - King’s Quest III - To Heir Is Human – Easter egg responses (Colonel Sanders, wizard quote) ↩ ↩2

  26. King’s Quest Omnipedia – King’s Quest III – Easter eggs, copy protection, manual requirements ↩ ↩2 ↩3

  27. 1986 - Space Quest - The Sarien Encounter – Ken Williams easter egg, KQ2 bonus points ↩

  28. The Cutting Room Floor – Space Quest I – Ken Williams easter egg, hidden content ↩

  29. Space Quest Historian – 11 Things You Didn’t Know About Space Quest – Ken Williams easter egg programming anecdote ↩

  30. 1991 - Leisure Suit Larry 5 - Passionate Patti Does a Little Undercover Work – Al Lowe on faster gameplay without parser ↩

  31. IGN – Talking Leisure Suit Larry with Al Lowe – Al Lowe on parser vs point-and-click accessibility ↩

  32. Sierra Creative Interpreter – Icon bar interface, SCI evolution ↩

  33. ScummVM Wiki – SCI – SCI engine support, interface evolution ↩

  34. 2014 - Gold Rush Anniversary – Dual interface system, puzzle limitations ↩ ↩2

  35. Steam – Gold Rush! Anniversary – Dual interface system description ↩

  36. 1996 - Leisure Suit Larry 7 - Love for Sail – Hybrid point-and-click/parser system ↩

  37. MobyGames – Leisure Suit Larry 7 – Hybrid interface, parser memory feature ↩

  38. 1996 - Leisure Suit Larry 7 - Love for Sail – Parser memory feature, “fart” command ↩

  39. Sierra Fandom Wiki – King’s Quest II – 1987 re-release with pull-down menus ↩

  40. MobyGames – Space Quest I – Technical specifications, credits ↩

  41. 1987 - Mixed-Up Mother Goose – Simplified interface for children, no parser ↩ ↩2

  42. ScummVM Wiki – Space Quest – AGI support, platform compatibility ↩ ↩2

Graph View

Backlinks