By Christopher Livingston on July 7th, 2014 at 9:00 pm.
Each Monday, Chris Livingston visits an early access game and reports back with stories about whatever he finds inside. This week, speaking with robots, and the resulting loss of his sanity, in Bot Colony.
Science-fiction writers love driving robots crazy, from Speedy in Asimov’s “Runaround” to Ash attempting a magazine-murder in Alien. Is it time for a robot to drive a human crazy instead? Considering that talking to a robot in Bot Colony for a couple hours reduced me to wailing “BLOOP! BLOOP! BLOOP!” into my headset, it just might be. There’s video evidence below: I’ll let you be the judge. Bloop.
Bot Colony is an adventure game that involves talking to robots, and while it can be played entirely with typed text commands, the real appeal is in literally speaking with the game’s robots through a microphone. The game supports Windows Speech Recognition, which I’ve never used before, so I began with about ten minutes of reading text into my microphone. Cleverly, though, the game uses this text to explain how the bots of Bot Colony work, the best ways to ask (and answer) questions, and how to avoid confusing them.
The game recommends doing the calibration exercise multiple times from start to finish, but I only went through once, which might explain some of the difficulties (bloop!) I encounter later. Once calibrated, I’m given an introductory mission, which begins with one robot teaching me how to speak to another robot.
I recorded some of this training mission in the videos below, but first, an apology: Um… sorry. Sorry about the audio quality, the inept transitions, the inconsistent titles, my cruddy mic, my irritating voice, and my big dumb stupid head. Sorry!
Also, profanity warning! I drop at least two f-bombs and use a handful of other, lesser swears. Let’s watch!
Okay, talking to robots seems simple enough! Let’s see if I can make it do things. The mission is, look around the various rooms of the house through hacked security cameras, and compare each room’s current state to photos taken earlier. My job: spot what has changed (objects not in their original positions) and direct the house robot, using voice commands, to put things back in their proper places.
We begin in a kid’s rec room, where a toy giraffe, originally placed on the top of the cabinet, has been knocked onto the floor. No worries, Jimmy and I will sort it out. Eventually.
So, that took a little doing. As you can see, it helps to ask Jimmy what objects are called to make sure you’re giving him the proper instructions.
We then went on to the master bedroom, where an alarm clock needed to be placed on a… well, Jimmy and I disagreed about the name of the thing the clock needed to be placed on. Also, surprisingly, Jimmy started asking me questions, hoping to learn more about alarm clocks. Spoiler alert: he did not learn more about alarm clocks. We ended our work in the bedroom by closing a drawer (while learning a lot about drawers!) and attempting a seemingly insurmountable task: moving a weird statuette from one shelf to another. How did it go?
Clearly, Jimmy and I were hitting our stride and really starting to communicate like a chore-robot and a camera-spy who had known each other since childhood. Next, we flew through the bathroom, replacing a couple of items without a hitch. I tried to make Jimmy use the toilet, but he wasn’t impressed with my immature attempts at potty humor. Also, I forgot to record it.
We were getting better and better. Our next challenge, rotating a pot on a stove so the handle stuck out in a different direction, was a breeze:
With the smashing success of the kitchen pot behind us, Jimmy and I forged ahead into another bedroom for our next task. The photo showed three board games sitting in a stack on a coffee table: a purple game at the bottom, a blue one in the middle, and a yellow one on top. Now, however, while the purple game was still on table, the yellow and blue games were on the floor. The way Jimmy and I were rolling, this would be a snap!
Actually, it caused me to snap. In other words: bloop. Afterwards, I went into the living room, hoping for a fresh start. Jimmy, unfortunately, insisted on dwelling in the past. Check it out:
Keep in mind, all of what you just watched is only the training simulator to prepare you for, like, the actual game, which has a story and characters and different locations and a whole bunch of robots. I played through a bit of Episode 1 (of the two playable episodes available as of this writing), which took me to the titular Bot Colony. There were robots everywhere: one was running a check-in desk, two soldier-bots were guarding a door, two more were running the baggage claim, and yet another was in charge of a taxi stand.
I’m on the island to investigate some corporate espionage, though most of my time in Episode 1 was spent in the luggage room, first trying to retrieve my briefcase, which is a bit of a puzzle involving codes, colors, dates, and, of course, giving the proper instructions to Mike, the baggage retrieval bot, and Mary, the x-ray technician bot. Then, I have to retrieve another briefcase, for reasons that are spoilers and winds up being a much more complicated task.
In fact, I’m still in the luggage room, due to failing that mission twice and running into a glitch on my third try. Despite that glitch, and my occasional exasperation with Jimmy, it turns out I enjoy the hell out of telling robots to do things and then watching them do things. When it works, it’s oddly satisfying. When it doesn’t work, it’s generally amusing.
This experience was based on Alpha 7 of Bot Colony. If you plan to buy it, make sure you read all the requirements very carefully. You must have 64-bit Windows 7, and if you use Dragon for speech recognition, it sounds like it won’t work with a Steam copy.