Reading Time: 9 minutes

The Hugo series on this blog: Part 1: Hugo's House of Horrors (1990) · Part 2: Hugo II, Whodunit? (1991) · Part 3: Hugo III, Jungle of Doom! (1992) (you are here) · Part 4: Nitemare-3D (1994)

By 1992 David P. Gray had a hit, a sequel that was too big and too hard, and a new idea: hire a real artist. Hugo III, Jungle of Doom! is the result. It's the prettiest game in the trilogy, the shortest, and the only one where Hugo cannot die. It also has an Indiana Jones hat, a Tarzan swing, a witch doctor, an exorcism, and an elephant that has no business being in South America.

As in part 2, we've taken the game apart through its data (265 scripts and 685 commands), the vendor notes Gray sent to shareware distributors, ScummVM's engine code and Gray's own interviews.

Spoilers ahead. Hugo III is short, about 20–30 minutes by one reviewer's count, so if you plan to play it, do that first.

A note on the pictures. There are no screenshots in this post. Every image was drawn from the game's own data (the database ScummVM uses to run it) or by our own code. The real thing is still on sale, and MobyGames and Wikipedia have screenshots if you want to see Gary Sirois's jungle.

The case file

Hugo III, Jungle of Doom!
ReleasedShareware v1.0, 20 February 1992 (548 KB download); 1.1 April 1992, 2.0 September 1992, 2.1 May 1994
Designer and programmerDavid P. Gray
ArtistGary Sirois, a computer artist from a neighbouring town
NeedsEGA or VGA, 400 KB of memory, about 1 MB of hard disk
MediaTwo floppy disks: H3_PART1.EXE and H3_PART2.EXE, with an installer
Price to register$20, or $40 for the trilogy
Re-released1995 for Windows as Hugo's Amazon Adventure
TodayGOG's The Hugo Trilogy; ScummVM since version 1.3.0 (2011)

Gray's vendor letter, dated February 1992, lists what's new in four lines: graphics by a professional artist, easier puzzles with hints, a "turbo" button for fast exploration, and, with an exclamation mark, that the hero cannot be killed. It also includes a DEMO.BAT for trade shows, which plays the automatic story at the start of the game over and over.

How a jungle got chosen

Each Hugo game is a different genre, and Gray has explained why with disarming honesty. Episode one alliterated (Hugo, House, Horrors). Episode two rhymed (Hugo, whodunit). For episode three he ran out of rhyming ideas, and a friend recommended a local artist, Gary Sirois, who was good at drawing trees. Hence: a jungle.

Gray also owned up to his geography. The game is meant to be in South America, but it drifted towards Africa in his head, and Sirois pointed out there are no wild elephants in South America. The elephant stayed because the plot needs it. Gray's official explanation: "If anyone asks, it escaped from a zoo." As for Hugo's new Indiana Jones look, Gray allows that the film might have had a subconscious influence, but says Tarzan mattered more.

Paying a professional had a cost. Gray's one regret is that the game was far too short: professional art pushed the budget up, which meant fewer screens and so fewer puzzles.

The crash, as 36 pairs of numbers

The DOS intro is the cleverest thing in the game for the least data. Over a map screen, the engine plots one white pixel per tick from a list of 36 coordinates, and at ticks 4, 9 and 35 it stops for a text box. That's it. Here it is, rebuilt from the coordinates and text in the database:

Animation: a white dotted line is drawn across a dark green field while three text boxes explain the flight home, the magnetic storm and the crash
Hugo III's intro, rebuilt. Path and text are from the data. The map picture isn't in our data, so the background is a plain field.
The 36 intro coordinates plotted and joined, with the three text moments labelled
Ten points in a straight line, six pixels per tick, then the compass goes haywire.

The story it tells: Hugo and Penelope are flying home from Great Uncle Horace's cottage when a freak magnetic storm sends the compass spinning. Lost over the jungle and nearly out of fuel, Hugo spots a clearing. "Hold on Penelope, we're going down...!"

The story (spoilers)

Hugo fiddles with the wrecked plane, and Penelope wanders off and is bitten by a tree spider. The 1992 catalogue blurb gives Hugo 48 hours to find the antidote, though the game never puts a clock on it. He needs water from a magic lagoon (the Pool of Life in Gray's own blurb), but a waterfall is in the way.

Along the way he trades with a village of natives, escapes a witch doctor, borrows a blowpipe with sleeping darts, and puts an elephant to sleep. It drops into the stream, dams it, and the waterfall dries up. He swings on vines and gets past a ghost by exorcising it, and the old man from the first two games turns up once more. Hugo collects the water, saves Penelope, and they fly off into the sunset.

Network diagram of Hugo III's 24 places coloured by area: crash site, river and waterfall, village, and jungle, cliffs and caves
The whole of Hugo III, from its exit scripts. Compare Hugo II's sprawl in part 2.

A kinder jungle, in numbers

"Hero cannot be killed" isn't just marketing. You can see it in the script data:

Bar charts: scripts that end the game (4, 6, 0), timed text boxes (0, 0, 48), yes/no questions (0, 0, 4) and palette changes (0, 2, 10) for the three Hugo games
Counted across each game's scripts. Hugo III has no GAMEOVER command at all, and dozens of timed messages.
  • Zero game-over scripts, after four in Hugo 1 and six in Hugo II. The ghost, the witch doctor and the natives can stop you, but they can't end the game.
  • 48 timed message boxes (the new WARN command) carry the cutscenes and the story. The four yes/no boxes are the old man's questions (more on those below), and the hints come from a separate system.
  • A "story mode" (INIT_STORY_MODE) that hides the prompt during cutscenes, used to open and close the cinematic parts.
  • Ten palette swaps (REMAPPAL), several of which flick one colour on and off a tick at a time for flashes and flicker.

Dead ends haven't disappeared entirely. Adventure Classic Gaming noted one early action that you have to do straight away or you'll be stuck later. But this is a game designed to be finished.

The 'perspective' is two drawings of Hugo

Contemporary write-ups praised a new feature: Hugo gets smaller as he walks away from the camera. RGB Classic Games noticed an awkward flash when he changes size. In the data, the database holds two complete hero objects, hero and whero, and Hugo III swaps their sprite sets with the same SWAP_IMAGES command that turned Hugo into Penelope in Hugo II. There's no scaling code in the engine. Gray drew Hugo at a second size, and the flash is the swap.

The village screen drawn as five coloured hotspot rectangles: two exits at the sides, two walk-up zones and a remark zone
The village's invisible zones. Every way in or out of this screen swaps between the two Hugo drawings.

The database has a third Hugo, hero_old, and a swinger sprite set for swinging on a vine across the stream. Gray's Tarzan influence is right there in the object names.

Bell, book and candle

The ghost in the cave is the best example of Hugo III's sense of humour. In the data, the verb exorcise on the ghost needs three objects: the bell, the book and the candle, the traditional bell, book and candle of an excommunication.

A DOS-style text box saying three things are needed for an exorcism
Try it before you're ready. Text from the data; screen recreated by us.

The game also rewards poking around. A scroll carries a little poem signed by the old man, who says he lost his crystal ball near a mighty boulder. If you look behind the rock, the parser has its own verb, behind, and a reply that teases you for being so thorough:

Animation: typing 'look behind the rock', then a text box teasing the player and handing over a crystal ball
Hugo III's parser knows 171 verb words, more than either earlier game.
Bar charts of Hugo III's object values and bonus awards
128 points: 53 from objects and 75 from 16 bonuses. The book (10) and crystal ball (9) are the prizes.

Under the bonnet

Two disks, two scenery files

Hugo III was too big for one floppy disk. Gray's vendor letter warns distributors that they'll need two. The engine shows how that was handled: Hugo II's single scenery database is split in two, and ScummVM's FileManager_v3d chooses between them with one test, if (screenIndex < 20).

Diagram showing disk 1 and disk 2, and SCENERY1.DAT holding screens 0-19 and SCENERY2.DAT holding screens 20-25
Screens 0–19 in one file, 20–25 in the other.

Small things that changed

  • A slightly faster clock. ScummVM runs Hugo III's DOS version at 9 ticks a second, against 8 for the first two DOS games. The Windows versions all use 9.
  • The parser. Hugo III gets its own parser class. In it, "verb-only" objects in the room can react to a verb with no noun, and a bare LOOK also lists the things you could pick up.
  • Its own glitches. ScummVM removes a stray wall in the crash-site screen that blocked its click-to-walk route finder, and special-cases Hugo III's inventory box text.
  • Scripted transitions. A new command, INIT_JUMPEXIT, lets a mouse click on an exit take effect immediately while the hero is invisible, as during the plane crash.

Over the trilogy, the number of different script commands actually used went from 28 in Hugo 1 to 37 in Hugo II and 36 in Hugo III. Hugo III dropped the maze and bit-flag commands and added hints and story mode:

Table of script command types used by each Hugo game
The script language across the trilogy. Yellow = never used by the first game.

Secrets from the source code

ScummVM's data generator, create_hugo, keeps Gray's original identifiers and comments, so all of Hugo III's scripts have names. Here's what they reveal.

  • How the hint system works. Nine scripts, kALac2 to kALac9, form a chain. Each asks whether you've earned one particular bonus. The first one you're missing triggers its tip: planetip, modeltip, sticktip, mousetip, cubestip, dammedtip, magictip, oldmantip, and finally remedytip. The hints follow the order of the puzzles.
  • A voodoo doll. kALmakeclay turns the clay into a model of the witch doctor, but only inside his hut. kALstickpin then makes him leap 20 pixels in a single tick and collapse, for 5 points.
  • The elephant is two bits. A sleeping dart sets bit 1 and the mouse from the cage (kALscare) sets bit 2. Only when both are set (mask 3) does the stream get dammed.
  • The old man's quiz was changed for ScummVM. The data has a comment marked HACK. The original asked typed questions (PROMPT), but ScummVM replaced them with yes/no boxes because its prompt box wasn't implemented, so that it could test whether the game could be finished. Get one wrong and kALwrong sends you back to the cave.
  • The crash site's 'horizon'. In the Windows data a two-tick loop, kALhorizon, swaps between the near and far drawings of Hugo whenever he crosses y = 151. ScummVM copied it into the DOS data to make mouse play work.
  • Seven dead scripts. kALcrashNoStory (a start without the intro story), kALmap0 and kALmap1 (palette tweaks inherited from Hugo II), kALsong3, kALgotit, kALempty2 and kALnopurps are never called. Hugo 1 and Hugo II have none.
  • Other details. The old man's screen runs kALflash, which reschedules itself every 10 ticks to flicker one colour. The garden is commented as "The secret garden". Three of the 265 scripts (the horizon loop) were added by ScummVM, not Gray.

The music

Hugo III's DOS sound is still the PC speaker. Adventure Classic Gaming summed it up as bleeps, bloops and short melodies. There are thirteen songs in its table, but only seven are ever played. The other six are leftovers from earlier games, including the dog and mummy tunes from Hugo's House of Horrors.

The theme: it plays over the intro map and again on the sunset at the end (10 seconds).
Piano roll of Hugo III's theme
The theme as notes over time.
By the stream.
The spider strikes.

One technical note for anyone reimplementing it. Hugo III uses a note length of zero (L0), which the first two games never do. In the original player that leaves the timer at −1, so the next note starts on the very next tick, the same as L1. Our part-1 renderer didn't expect it and crashed, which is how we found out.

Was it any good?

Adventure Classic Gaming gave it 3 out of 5, loving Sirois's art (lush shrubs, rippling water, the animated village fire) and the humour, but calling it a pit stop rather than an adventure. PC Gamer's Richard Cobbett liked the art but not the game. RGB Classic Games liked the hint system and the perspective, awkward flash and all. Everyone mentions the length.

For the series, it's a happy ending: Hugo and Penelope fly into the sunset with nobody dead. Hugo III had no sequel in the same style, and when Hugo came back two years later, he was carrying a plasma gun. That's part 4.

What we learned

  1. Art changes everything, including the budget. A professional artist made the game beautiful and short at the same time, and Gray said so himself.
  2. Difficulty is a design choice you can see in data. Zero GAMEOVER commands, 48 timed messages and four yes/no hint prompts are a philosophy, not an accident.
  3. Old tricks get new jobs. The sprite swap that made Penelope playable became the perspective system.
  4. Floppies shape code. One if statement exists because the game didn't fit on one disk.
  5. Data outlives intentions. Six unused songs and an extra Hugo sprite set ride along in the database 34 years later.

Sources


The Hugo series on this blog: Part 1: Hugo's House of Horrors (1990) · Part 2: Hugo II, Whodunit? (1991) · Part 3: Hugo III, Jungle of Doom! (1992) (you are here) · Part 4: Nitemare-3D (1994)

← All articles

Related articles