Gribbly's Day Out: Braybrook's Game About Being Fussed Over

Andrew Braybrook is remembered on this desk mostly for the precision of Paradroid and the confident swagger of Uridium, games built around a single player-controlled unit doing exactly what it is told with no margin for the game to complicate that relationship. Gribbly’s Day Out, published by Hewson in 1985 and developed through Braybrook’s own studio Graftgold, is the odd one out in that run, because its central character, Gribbly Grobbler, is not really the point. The Gribblets are.

Gribbly can jump and float, using bubbles defensively against the primitive creatures roaming the hills of the planet Blagbor, and a dangerous entity called Seon lurks behind a barrier known as the psi net, which the player can switch on and off at fixed points to manage the threat it poses. None of that ability set is what the game is actually testing. Across sixteen caves, the job is to collect eight Gribblets in each one before the local creatures kidnap them, and to get them back to a safe cave before that happens. Gribbly is capable. The Gribblets are not. The entire design tension of the game lives in that gap.

Escort logic, a decade before the genre had a bad reputation

Modern players tend to associate escort mechanics with frustration, thanks to a long run of games that bolted a fragile companion onto an otherwise competent action game and let the companion’s poor pathing sabotage an otherwise well-designed level. Gribbly’s Day Out predates that entire reputation by years, and it avoids the genre’s worst trap by design rather than luck: the Gribblets are being collected, actively, by a player who has to go and find each one and physically bring it back, which puts the burden of navigation on Gribbly rather than on an AI companion’s pathfinding. There is no broken escort AI to blame here, because there is no escort AI at all in the sense later games would popularise. There is only the question of whether the player can reach a Gribblet before a local creature does.

That distinction matters more than it might sound. An escort mission fails when the player is competent and the companion is not, creating a mismatch the player cannot correct. Gribbly’s Day Out never creates that mismatch, because the fragile party in the equation has no agency to fail with. The only variable is the player’s own speed, route-planning and willingness to risk the more dangerous corners of a cave to retrieve a Gribblet before it is lost. When the mission goes wrong, it is legibly the player’s fault, which is precisely the property that later, more resented escort mechanics failed to preserve.

The psi net as a resource, not a wall

None of this is explained to the player through any onboarding sequence. Home-computer games of this vintage rarely offered one, and Gribbly’s Day Out is typical of the period in expecting a player to learn the psi net’s function through direct experimentation, likely at the cost of an early Gribblet or two lost to Seon while the mechanic’s actual behaviour is being worked out. That trial-and-error onboarding reads as unforgiving by contemporary standards, but it also means the psi net’s importance is learned the way most of the game’s real lessons are learned: through a specific, memorable loss rather than through a paragraph of instruction that a player might skim past without absorbing.

The psi net constraining Gribbly’s movement, switchable on and off at fixed points scattered through each cave, is doing more mechanical work than a simple obstacle would. Left on, it protects against Seon, the black beast whose threat is serious enough that most caves cannot be safely completed with the net left off for long. Switched off, it presumably opens up movement or access the net otherwise restricts, at the cost of exposing Gribbly to a threat the net exists specifically to hold back. That trade-off, protection against freedom, recurs constantly across the sixteen caves, and it means the psi net functions less like scenery and more like a resource a player has to manage moment to moment, not unlike choosing when to spend a limited defensive tool in a game with a more conventional combat system.

Sixteen caves, only two of them fixed

The caves themselves vary considerably in colour palette and terrain layout from one to the next, which was itself a deliberate response to the C64’s technical ceiling rather than pure decoration. Braybrook and the rest of the small Graftgold team understood the machine’s constraints well enough by 1985 to know that a visually distinct cave, even built from a similar tile vocabulary underneath, reads to a player as meaningfully different territory, which matters a great deal in a game whose branching structure depends on caves feeling worth returning to rather than interchangeable. A player revisiting Blagbor across several sessions is meant to recognise specific caves by sight, which is only possible because the sprite and colour work behind each one was treated as a genuine design decision rather than an afterthought bolted onto a functionally identical layout.

The structural detail that separates Gribbly’s Day Out from a simple sequence of levels is that only the first and last of its sixteen caves are set in stone. Which caves a player visits in between, and in what order, depends on how many Gribblets were actually saved in each one, which means the specific run of caves a player experiences varies from playthrough to playthrough based on performance rather than following a single fixed path. That is an unusually adaptive structure for a home-computer platformer from 1985, and it means two players who both call the game finished may have experienced meaningfully different sequences of caves to get there, shaped entirely by how well each one managed the Gribblet-collection problem along the way.

That variability also raises the stakes on every individual cave in a way a fixed, linear sequence would not. A poor showing does not simply mean a harder version of the next scripted level. It can mean an entirely different, and by implication less forgiving, set of caves waiting afterward, which gives the collection mechanic a consequence that reaches beyond the immediate cave a player happens to be standing in.

Braybrook’s real subject

It is worth being specific about why the difficulty of Gribbly’s Day Out earned it a reputation, at the time and since, as one of the more demanding platformers in the C64’s early library. The combination of a strict time pressure created by kidnapping creatures, a movement set limited to jumping and floating rather than running at speed, and a psi net that has to be actively managed rather than ignored, stacks several sources of pressure on top of one another simultaneously rather than testing them one at a time. Most platformers of the period isolate their challenges: a jumping section here, an enemy-avoidance section there. Gribbly’s Day Out runs all of its systems concurrently in every cave, which is a large part of why contemporary players and later retrospectives alike single it out as a genuinely difficult game rather than merely a fiddly one.

Braybrook’s other Graftgold-era games are often read, correctly, as studies in elegant systems: Paradroid’s transfer mechanic, Uridium’s pure precision flying. Gribbly’s Day Out sits alongside them as a study in a different kind of system, one built around vulnerability rather than capability. The player character in Braybrook’s other games is usually the most capable thing on screen, a droid absorbing enemy units or a ship outflying everything in its path. Gribbly is capable too, in the narrow sense of being able to jump and float competently, but the actual object of the player’s attention throughout is a population of Gribblets who can do neither, and the entire game is organised around the discomfort of being responsible for something you cannot fully protect. That is a more melancholy design proposition than Braybrook’s catalogue usually gets credit for, buried inside a brightly coloured platformer that reads, on the surface, like a straightforward collect-em-up.

Reading Gribbly’s Day Out against Andrew Braybrook: The Programmer as Author is the clearest way to see this thread running through his catalogue: a consistent interest in what a single, well-defined system can teach a player about a relationship, whether that relationship is a droid absorbing a corridor of enemies or a small creature failing to save all eight of its charges in a cave it thought it had cleared in time.

Approached today, Gribbly’s Day Out reads less like a curiosity in Braybrook’s back catalogue and more like a necessary counterweight to it. A career built entirely on the confident, capable systems of Paradroid and Uridium would tell only half the story of what Graftgold was actually interested in during the mid-1980s. The other half is here, in a game about failing to save all eight of something you were responsible for, dressed in bright Blagborian colours and a jaunty premise that undersells how much genuine tension the Gribblet-rescue loop generates once a player has been playing long enough to actually care whether a given Gribblet makes it home.

Where to play it now

Gribbly’s Day Out runs cleanly in VICE and other mainstream C64 emulators, and it rewards patience with its controls more than most Braybrook titles, since the jump-and-float movement set takes a session or two to feel confident with before the Gribblet-rescue timing starts to click into place.

Spoilers below

The later caves in a well-played run, the ones reached only by saving enough Gribblets earlier to unlock the harder branch of the sixteen-cave structure, introduce creature placements dense enough that saving all eight Gribblets in a single pass is rarely realistic on a first attempt. The honest approach the design rewards is triage: identifying which Gribblets are reachable before local creatures can intercept them, and accepting that some caves are built to be only partially cleared rather than fully solved. Players chasing a perfect eight-for-eight result on every cave will find the later stages punishing in a way that reads as unfair on a first encounter, when the more accurate read is that the branching cave structure was already grading performance from the very first level onward, long before the difficulty became obvious.