On the anniversary of one launch, the announcement of another


36 years ago today, the space probe Voyager 2 lifted off from Cape Canaveral atop a Titan IIIE rocket, beginning its vast and unparalleled Grand Tour of the Solar System. Just over two short weeks later, Voyager 1 launched from the exact same pad, on a trajectory that would fire it faster and further than – not just its sibling – but anything else created by human hands.

Next week, nestled snugly between those two amazing milestones, we will be commemorating the occasion with our own launch celebration – finally, owners of Android devices will be able to play Voyager: Grand Tour!

The game will be available on both the Google Play store and the Amazon Appstore, with support for Google Play Game Services and GameCircle (including a brand-new feature: achievements!).

All systems GO for launch!

Voyager 1.0.1

Our first update has just been approved for release on the App Store!

What’s included? Mostly UI and UX improvements: stuff to improve the overall play experience. First up, mission sets now display completion percent with a new progress meter. Earn gold with two stars on every mission for a perfect score!


We got rid of the need to visit a sub-menu to select an alternative probe – now you can just swipe side-to-side on the title menu to switch. There’s also a brand new bonus probe: Mariner 2, the first successful planetary flyby and great-grandfather of the Voyager missions, is free for anyone who rates (or re-rates) the game!


On the title menu, there are links to our Facebook and Twitter profiles (please like and/or follow Rumor Games!). Finally, swipe sensitivity has been bumped up in all menus, and the touch target are bigger for small buttons – basically, a bunch of stuff to make the UI feel better and more responsive.

Check it out today, and let us know what you think!

Fast Scene Switching in the Unity Editor

One of the many powerful features of Unity is the ability to write extensions for the editor. As I worked on Voyager: Grand Tour, I found myself doing a number of repetitive tasks – not terribly time-consuming individually, but frustrating enough in aggregate to get me curious about optimizing my workflow with software. Still, I put it off, figuring I didn’t have time to divert toward extraneous development to save a few seconds here and there.

Well, a few months ago, a friend of mine by the name of Zach Aikman gave a talk on Unity Editor extensions at the local Unity user group meetup. His detailed overview provided more than enough information to get me started, and the first thing I did when I got home was to whip up a solution to a problem that, while small, had nagged me frequently while developing Voyager: quickly switching between scenes.

In my game, I split my content and menus up into a lot of scenes that I frequently had to switch between, which in the default Unity editor meant a lot of pointlessly scrolling around in the project view. This simple editor window grabs a list of scenes from the Build Settings and presents them as buttons for fast switching. It’s dead simple, but it genuinely saves me time and frustration every day, and I’m happy to share it with anyone who’s interested!

// --------------------------------
// <copyright file="SceneSwitchWindow.cs" company="Rumor Games">
//     Copyright (C) Rumor Games, LLC.  All rights reserved.
// </copyright>
// --------------------------------

using System.IO;
using UnityEditor;
using UnityEngine;

/// <summary>
/// SceneSwitchWindow class.
/// </summary>
public class SceneSwitchWindow : EditorWindow
    /// <summary>
    /// Tracks scroll position.
    /// </summary>
    private Vector2 scrollPos;

    /// <summary>
    /// Initialize window state.
    /// </summary>
	[MenuItem("Tools/Scene Switch Window")]
    internal static void Init()
        // EditorWindow.GetWindow() will return the open instance of the specified window or create a new
        // instance if it can't find one. The second parameter is a flag for creating the window as a
        // Utility window; Utility windows cannot be docked like the Scene and Game view windows.
        var window = (SceneSwitchWindow)GetWindow(typeof(SceneSwitchWindow), false, "Scene Switch");
        window.position = new Rect(window.position.xMin + 100f, window.position.yMin + 100f, 200f, 400f);

    /// <summary>
    /// Called on GUI events.
    /// </summary>
    internal void OnGUI()
        this.scrollPos = EditorGUILayout.BeginScrollView(this.scrollPos, false, false);

        GUILayout.Label("Scenes In Build", EditorStyles.boldLabel);
        for (var i = 0; i < EditorBuildSettings.scenes.Length; i++)
            var scene = EditorBuildSettings.scenes[i];
            if (scene.enabled)
                var sceneName = Path.GetFileNameWithoutExtension(scene.path);
                var pressed = GUILayout.Button(i + ": " + sceneName, new GUIStyle(GUI.skin.GetStyle("Button")) { alignment = TextAnchor.MiddleLeft });
                if (pressed)
                    if (EditorApplication.SaveCurrentSceneIfUserWantsTo())


Now also available on the Unify Community Wiki.

Voyager Level Design

I’d like to share a bit of my process of creating levels for Voyager.

Most of the time, a level starts as an idea for a technique I’d like the player to learn, or a cool experience I want them to have. For instance, a gravitational slingshot is a core mechanic in the game, but at some point I’d like players to figure out how to chain multiple slingshots together to get past several obstacles. I also like the idea of weaving between planets – sort of a space slalom. So, there should be a level between learning how to do a slingshot maneuver and being expected to string them together to win where the chaining concept is introduced and presented in a fun way.

The “Gas Giants” level does just that. It features an arrangement of planets that suggests (but does not require) a winding, between-the-gates sort of trajectory. Jupiter blocks a direct route to the target Uranus, and Saturn gets in the way of a simple slingshot around Jupiter on the right-hand side. Once I’ve got the general arrangement of planets figured out, it’s time to run the Path Predictor.

Path Predictor is one of the more important tools in my design arsenal. It simulates the trajectory for a launch, given an angle and power level (and delay, for levels with a timing element). After running it, I end up with a visualization like this.

Though it’s usually more helpful to filter out angles that result in crashes and misses and just focus on successful paths.

This view makes it clear that there are a few viable slalom trajectories, but it’s also quite easy to just bypass that experience and slingshot straight to the target. I need another way to reinforce the weaving path as something worth attempting. That’s where star placements come in.

In this level, there are a few points where the slalom trajectories intersect, providing natural, ideal locations for stars. This ensures there are multiple viable solutions. And of course, players will experiment with different power levels (or, with the “expert” controls enabled, fractional angles) that could surprise even me.

Of course, at this point the level is still far from done. It needs to be playtested for fun and difficulty before making the cut in the finished product!

Announcing Voyager: Grand Tour

It’s about time I start talking about what I’ve been working on these last few months.



Voyager: Grand Tour is more than a sequel or remake. It’s a re-imagining.

Dramatically improved graphics (before/after):

VoyagerVoyager: Grand Tour

New multiple-target levels:


Stunning first-person replays of each successful flyby:


More planets, more missions, more everything!

Completely rewritten from the ground up using the powerful, cross-platform Unity game engine, I hope to eventually target many devices and markets. But the inaugural release will be next month on the App Store, for iPhone, iPad, and iPod Touch!

Stay tuned to Facebook, Twitter, or right here for updates.

Dark Side of the Jam

Last weekend, I organized and participated in Seattle’s satellite “Dark Side of the Jam,” a space-themed game jam which the Academy of Interactive Entertainment graciously agreed to host. Our mission was to build a game (using at least one NASA asset) in just 48 hours.

Our satellite jam started at 6pm on Friday, with participants filing in until around 7:30. We kicked off the event with some inspirational words by Dan Dixon, the creator of Universe Sandbox, and then started brainstorming ideas. As more people arrived, we decided to split into two teams, but to let everyone collaborate between the two projects (especially our artists and sound designer!).

We tossed around a number of exciting and ambitious ideas, from a game about discovering exoplanets with real-world problem solving elements (along the lines of Foldit) to one about engineering your own rockets (think Kerbal Space Program).

Two projects gathered the most attention and excitement, though. One was a game about driving the Lunar Rover around to pick up your astronaut bros. The other, and the one I worked on, is called Seven Minutes to Heaven. The game is about the time delay involved in communicating with a rover on Mars. While that delay can range from a couple of minutes to nearly half an hour, the name is an allusion to Curiosity’s Seven Minutes of Terror.

The game is played by selecting commands from the control panel’s arrows to drive the rover, a camera to get a better view of the surrounding area, and the drill to take a sample from the surface. The objective is to search for elements of interest (Hydrogen, Helium, Carbon, and Oxygen) within the time limit. The amount of each element in a square is communicated through an emission spectrum. The player can cross-reference this against known spectra to make decisions about where the most productive areas to drill are. It’s a little like Minesweeper, if you had to wait a while for your moves to take effect, the numbers were in code, and you only had until the sun goes down to finish playing. Also it’s on Mars.

Because we only had 48 hours to build the entire game, some features did not make it into the finished product before the end of the jam. With more time, we would have given players specific objectives (for example, find at least 6 units of Carbon and 2 of Helium) and better explained the controls and emission spectra in-game. We also didn’t get in all the art and sound effects produced by our teammates, or have much time for testing and play balance.

Even so, I’m really proud of how complete and polished the game ended up. More than that, I had a great time getting to know and work with a bunch of awesome people.