My Mechanical Romance : Mac and PC builds
So, the 48 hour game competition is now done with, and the level of entries was fantastic. I was especially impressed with the efforts of some of the amateur teams – amazing work from people outside the games industry, in crazy timelines, and with a surprising amount of polish. They also tended to sleep way less than us, who for the most part actually got some sleep in the middle there – we’re old men (well, some of us are) we can’t stay up for 48 hours straight making games!
On the nice side, our game “My Mechanical Romance” won the pro team competition. We used the three seed words (Giant, Storm, and Love) to tell a tale of Giant Robots who, after fighting oppression for many years, have finally been allowed to be wed. You control the forces of the wind in order to blow the clouds around Central Park, keeping them away from the Giant Robot Weddings and (once you get to Level 2) into the various groups of protesters who arrive.
It’s a simple piece, but I find the mechanic really interesting, and I’m fascinated with where we can take it. There’s a build below for people who’d like to play it on PC – I’d provide the Mac and Webplay builds, but for some reason they’re huge – I’m going to take a look at that tomorrow and see if I can’t get them smaller.
Edit : Large Intel Mac build now available for your delight!
So, enjoy our little piece of 48 hour pro-Giant-Robot-Wedding touch controlled fun : My Mechanical Romance!
My Mechanical Romance, a literal screenshot
Some quick instructions – hold down the mouse and drag the cursor to blow a breeze across the clouds. Keep the mouse held down for longer breezes. Keep clouds away from weddings, and over protesters. Enjoy having a play!
PC Build : My Mechanical Romance
Intel OSX Build : My Mechanical Romance (40 odd MB)
Comments
Leave a Reply
Benno Rice on 10.11.2009
The Mac build might be larger due to the fact that it appears to include Mono. The Windows build might be leveraging the .NET framework installed on the system. Not sure why the web build might be so large.