Jet Force Gemini Trivia & Easter Eggs

Rare’s Most Ambitious N64 Shooter Hiding in Plain Sight

Jet Force Gemini arrived in October 1999 during one of the most extraordinary runs in Rare’s history, sandwiched between Donkey Kong 64 and the looming end of the Nintendo 64 era. Though it sold well and earned strong reviews, the game has always lived in the shadow of stablemates like GoldenEye 007 and Banjo-Kazooie — a fate that obscures just how technically daring and narratively unusual it actually was. Digging into its development reveals a project full of creative ambition, last-minute compromises, and a few decisions that continue to frustrate players to this day.

Rare Was Running Multiple Juggernauts Simultaneously

By 1999, Rare had become Nintendo’s most important second-party studio, and the internal pressure was enormous. GoldenEye 007 had shipped in 1997 and redefined console first-person shooters. Banjo-Kazooie launched in mid-1998. Donkey Kong 64 and Jet Force Gemini were both deep in development at the same time, racing toward holiday windows just weeks apart. Rare’s Twycross facility was effectively running several AAA productions in parallel with teams that would seem impossibly lean by modern standards. The Jet Force Gemini team was small even by late-1990s benchmarks, which makes the scope of what they delivered — dozens of distinct environments, three playable characters with unique mechanics, a full multiplayer suite — all the more remarkable. That parallel development crunch almost certainly influenced some of the design compromises that defined the final product.

Three Characters, Three Problems

The decision to build the game around three distinct protagonists — Juno, his twin sister Vela, and their dog Lupus — was one of the earliest and most consequential creative choices. Each character controls differently: Juno is the balanced ground operative, Vela can hover briefly using her jetpack boots, and Lupus moves on all fours and can equip a turret. The intent was to give players a reason to revisit levels, since certain areas are only accessible by specific characters. In practice, this created a structural problem that wouldn’t become fully apparent until players neared the end of the game. The three-character conceit also forced the art and design team to essentially triple certain animation and ability sets, a significant cost on a project already stretched thin. Rare leaned into it anyway, and the result is a game with genuine mechanical variety that few N64 titles matched.

The Tribal Rescue Mechanic Became the Game’s Most Divisive Choice

Of all the design decisions in Jet Force Gemini, none generated more backlash than the requirement to rescue Tribals — small, woolly civilians scattered across every level — as a prerequisite for the true ending. The total number scattered throughout the game runs into the thousands, hidden in corners, behind destructible walls, and in zones requiring specific character abilities. Players who powered through the main storyline and then attempted to reach the final confrontation with Mizar discovered they were locked out without completing this exhaustive collectathon. Many reviewers docked the game specifically on this point. The Tribals themselves were deliberately fragile — enemy fire could kill them, forcing restarts of encounter sequences — adding a layer of frustration on top of the sheer volume of searching required. Rare had used collectibles effectively in Banjo-Kazooie, but the Tribal system pushed that philosophy into punishing territory.

Some Tribals Required a Second Human Player

Perhaps the most criticized aspect of the Tribal requirement was only discovered after many players had already committed significant time to the game: a portion of Tribals were located in areas of the multiplayer maps that were not accessible during the single-player campaign. To collect them legitimately, players needed a second controller and a cooperative partner to enter those zones. This effectively made 100% completion a multiplayer requirement in a game that was primarily a single-player experience. In an era before online gaming on consoles, this meant players without a sibling or nearby friend were simply blocked from the complete ending. Rare later acknowledged the frustration this caused. The issue was eventually addressed in subsequent patches in some regions, and workarounds were documented by the community, but the original retail version shipped with this requirement intact.

Graeme Norgate’s Score Defied Genre Expectations

The soundtrack, composed primarily by Graeme Norgate — one of Rare’s most prolific composers during the N64 era — is one of the most underappreciated scores of the platform. Where many action games of the period defaulted to relentless high-tempo percussion, Norgate took Jet Force Gemini’s science-fiction setting as license to experiment. The result mixes orchestral arrangements, ambient electronic textures, and occasionally jazz-inflected passages that create an atmosphere closer to a prestige animated film than a weekend action game. The Mizar’s Palace tracks in particular carry a sense of genuinely alien menace. Norgate had previously worked on Killer Instinct and contributed to GoldenEye, but Jet Force Gemini gave him the broadest canvas of his N64 work. The score remains a touchstone for fans of late-1990s game music and has been performed at several video game music concert series in the years since.

The Engine Pushed N64 Hardware to Its Edge

From a technical standpoint, Jet Force Gemini made demands of the Nintendo 64 that few other titles attempted. The game rendered large outdoor environments with real-time lighting and populated them with enough enemies on screen simultaneously to create genuine battlefield chaos — the ant-soldier hordes that serve as Mizar’s army were a deliberate visual statement about what the hardware could handle. Rare’s programmers had refined their N64 engine through multiple releases by this point and had a sophisticated understanding of the console’s MIPS-based processor and Reality Coprocessor. The game ran at a locked 30 frames per second in most scenarios, a standard that many competing titles couldn’t maintain. Certain heavy combat sequences did produce slowdown, but the baseline performance was notable for how much was happening simultaneously. The draw distances, particularly on exterior levels, were among the most ambitious on the platform.

Easter Eggs Wired Rare’s Universe Together

Rare embedded several cross-game references throughout Jet Force Gemini, a habit the studio had developed across their N64 library. Players who explored thoroughly could find nods to Banjo-Kazooie and other Rare properties hidden in level geometry and background details. The game also contained internal developer jokes that only made sense to the team — a tradition at Rare stretching back to their earlier Nintendo work. More visibly, the game’s multiplayer mode featured a Banjo head as a selectable character option, one of the more overt winks the studio included. Rare during this period operated with a degree of creative autonomy that allowed these small personal touches to survive into final builds, which is part of why their games from this era reward close inspection in ways that heavily focus-tested titles typically do not.

Microsoft’s Acquisition Ended Any Sequel Ambitions

Jet Force Gemini concluded on terms that clearly anticipated a continuation: Mizar is defeated but the broader threat from his insectoid empire is left narratively open, and the characters were established with enough backstory to sustain follow-up stories. Those sequels never came. Microsoft acquired Rare in September 2002 for approximately $375 million, redirecting the studio toward Xbox and later Kinect projects. The Jet Force Gemini intellectual property became part of Microsoft’s portfolio, where it has remained dormant ever since. A Rare Replay compilation released in 2015 for Xbox One included Jet Force Gemini, giving the game renewed visibility, but no new installment has been announced across the decades since the original. The game’s cult following has grown steadily in the years since, driven partly by nostalgia and partly by the genuine recognition that its flaws were the product of ambition rather than carelessness — the mark of a team swinging hard at a difficult target at the peak of a remarkable era.