Boatventure: Getting Bloggy

Boatventure! Basic movement implementation!

[Re-post from acpcproductions.com] Hello everyone, it's Ryan Huggins, a game designer here at ACPC Productions and I'll be running the Boatventure blog. We've just *really* gotten into working on the game after finally settling on Unity after having built several prototypes in Game Maker. I'm currently busy working on the first iteration of the game and am taking a break to set up this blog. To begin this blog, I'm just going to throw up a few pictures, but I'll be updating periodically every time I make visual progress on the game; and sooner or later, I'll actually talk about the gameplay... The .gif at the top of the list is an example of the basic movement implementation and the current (rudimentary) system for cycling through your boat modes.

Some Boatventure and some Railwar! Two games being developed by ACPC Productions crossing over. Art by Meghan.

Screenshot Mock-ups

A mock-up by our artist, Meghan. Boatventure has gone through a ton of artistic revisions these last few months. This is an example of being at the surface of the water.

Another mock-up; Meghan and I have been doing a bunch of work trying to figure out the style for Boatventure. We've got a lot of work to do, but the style's finally getting to a place that we like. This is an example of underwater exploration.

Character Art

This is the original concept art for Wynona. A main character (but not THE main character) of Boatventure.

This is a grandma. She is also a pirate.

Tears and blood. We're not sure why she's crying, but Meghan felt compelled to draw it. Classic Ghibli-style tears.

Student Developer: Microsoft Surface Pro - Log 3 + Boatventure 2013

WHO IS SHE? She is the co-lead of BOATVENTURE 2013!
Boatventure 2013 Dev Log located below the Surface Pro: Wrap Up.

The Surface Pro: Wrap Up

It's been roughly 2 weeks since I decided to use the Microsoft Surface Pro as a tool for game development and in these two weeks I've decided that the Surface Pro is a great tool for developers on the go, but not yet a perfect replacement for a desktop development environment. Most of the problems stem not from the internal hardware or the power of the system itself, but in the available software and the size of the screen (which surprised me in how much it could hinder productivity). The Surface Pro did a lot of great things for me--it ran pretty much everything, let me draw and sketch ideas like I was using paper, connectivity was solid and the type cover made it comfortable to program for hours--but there were a few issues that slowed me down and helped me determine that, for a software/game developer, the Surface Pro is a stellar secondary device, but only a decent primary one.

For a primary device, the screen size was much too small for me to easily multitask, especially when it came to managing 8+ code windows at once. That was probably my biggest issue and it ended up inhibiting me more than I would like to admit. A few other smaller issues, like the length of the charger and the quirks of Windows 8 also, upset me, but it was definitely the screen size that convinced me to return to my desktop for big projects.

However, where the Surface Pro truly shines is in its ability to be an amazing portable device. If I was to go out for a few hours--an example would be a class--where I needed a light device that could power through all of my college activities, let me sketch ideas, and make code edits (or even create full programs in a reasonable amount of time), the Surface Pro would absolutely be the device I would choose. It's just when you ask it to become a primary device that it may fall short for heavy developers.

Do I recommend it? Yes. And I already have to several people. It's just important to ask what you want the device to do before you purchase it.

Boatventure 2013: Development Log 1

A great example of prototyping in action.
These five silhouettes are no longer part of the game.

Today marks the beginning of the weekly (or occasionally bi-monthly) development log of Boatventure 2013 (20XX)! I was working on the first draft design/prototype of the game during my two week test of the Surface Pro as a development device, but sadly (or wonderfully), that prototype bombed and helped us to determine that our core mechanic just wasn't fun! First, here's a bit of background

After many years of global warming, the majority of planet Earth has found itself submerged beneath a torrent of rising sea levels while much of mankind has been wiped out by the resulting influx of superstorms. In recent years however, with humanity at the brink of extinction, the Earth has finally begun to stabilize itself. The majority of those who survived this global warming-related apocalypse have taken refuge on what little dry land remains, while others have taken to the seas themselves, searching valiantly, for any remains of civilization until the depths claim their lives as well. Thrown into the fray without any hesitation for adventure, you play as a boat scouring the ocean world, searching for a way to kickstart a new civilization, and somehow resurface the world that now lies beneath the tides.

If you take a look at the images above, you'll see five ships and a submarine. In the first design of the game, the player would be able to unlock new, larger ships and then cycle through them at will during the gameplay in order to solve puzzles or just lay down the law to other ships. The system was based around a mobility-power dynamic, where the smaller ships were more mobile, but the larger ships were more powerful. Luckily, it became apparent during prototyping (and prior to that, in some arguments with the musician, Jack Yeates) that the system might not be fun, or at least be terribly difficult to balance. (On that note, check out one of our MANY concept songs and maybe let us know what you think!)



In a true designer fashion, I don't like really like scrapping cool conceptual systems without testing, so I insisted that we prototype it out; and for a few days, I thought it would work out, but it quickly become more and more apparent to me that cycling through different boats was a fun mechanic, but that the power vs mobility dynamic was not. At all.

In the end, we got rid of the different sized boats, but kept the idea of cycling through multiple specializations of ship. This means that you can unlock new ships with a new type of weapon (like how Megaman unlocks new weapons) and cycle through them in real time. In addition to this, we're considering a Cave Story-esque mechanic where each ship can "tier up" by doing well, obtaining a more powerful weapon in the process. Like Cave Story, however, they can also level back down.

It's important to note, that unlike both of the mentioned games, we plan to make sure that every type of weapon has some sort of gameplay purpose (akin to The Legend of Zelda's items) to aid in the exploration! So cannons might be able to break down certain walls, torpedoes can destroy underwater rocks, and battering rams could maybe let the player push objects that would normally damage them. Each different weapon corresponds to a different specialization. (We're still coming up with more like an anchor grappling hook.)

A bit of a very basic platforming scenario. TAKING PLACE AS A BOAT!!! :D

In addition to the combat, it's important to remember that the game is an exploration-adventure game where the player is literally a boat. We've spent a lot of time thinking about how the player can get around (and we have a lot of ideas!) Though, one of the tested mechanics that was really positively received, was the submarine mode. Since your boat has the special ability to change into different ships, it can, naturally change into a sub to explore the deep-sea depths! In addition to this, the player can unlock a lot of other cool tools for exploring and getting past obstacles that they couldn't otherwise get past.

Submarine mode is my personal favorite though. It literally and figuratively adds depth to the game and will let us design some really cool areas to fight in, explore, or solve puzzles in, whereas the other ideas are more combat orientated with the added bonus of increasing mobility (Castlevania-style).

So, hopefully, you like the idea of Boatventure! It's really shaping up to be an amazing, beautiful, stylistic adventure game that we can be proud of; and our secondary protagonist at the top of the page, is shaping up to be a great character. More on the main character in the coming updates. :)

More sketches of our super cool co-lead! 

Student Developer: Microsoft Surface Pro - Log 2

Windows 8 metro/desktop multi-tasking can be good and bad.

It's been three days since I started using the Microsoft Surface Pro (in conjunction with Game Maker: Studio) as a tool for developing games. At the same time, it's been roughly two days since I've begun using Game Maker: Studio as an engine for game development (the first day was spent setting up my Surface for development). This mix of new experiences doesn't quite make for the perfect experiment, but it has given me insight into how a student (read: inexperienced) developer may fare using the Surface Pro as a portable solution to any number of problems.

The Surface Pro has many advantages over traditional laptops and tablets such as being portable (vs laptops) and blazing fast (vs tablets), but at the same time, it also has a long list of software and hardware bugs common to first generation hardware that don't exactly make it the perfect tool for everyone. Having known about these issues prior to purchasing it, these past few days with the Pro, have been a mixed bag of feelings as I adjust to the new work environment.

What Went RIGHT

Speed:

The Surface Pro is more than fast enough to handle the development of traditional 2D games in pretty much any situation. Outside of Game Maker: Studio, I've not had any problems in particular with any tool I've had to use to get things done. Photoshop, Paint Tool SAI, Visual Studios 2012, Steam, Chrome--pretty much everything runs smoothly. Game Maker: Studio seems to be slightly glitchy, though I'll chalk that one up to Windows 8; and it doesn't impede my progress much at all.

Art:

Making 2D art is CHILD'S PLAY on this thing. Open up Photoshop, break out the Wacom digitizer pen, and you're set to make game art at blazing speeds. Considering I'm not one of ACPC Production's artists, I don't actually make the art for Boatventure 2013, but since I originally bought the Surface for use as a drawing tablet, I've done extensive research and testing in this category. With the new WinTab drivers finally out (get them here), this thing is great for your artistic needs.

Programming:

Programmers with larger hands might want to get a nice Bluetooth keyboard (Logitech k810 or better) for long hours of programming, otherwise the type cover (not the touch) is actually pretty good for programming once you get used to the strange placing of some keys and disable the function lock (press Fn and caps lock together). Overall, without investing in an external keyboard, I've been able to reach my normal typing speeds without any perceivable discomfort at all.

What Went WRONG

DPI Scaling:

The DPI scaling is awful. This is a Windows issue primarily, but I almost wish they went for a lower resolution because of it. At 125% scaling (which I recommend to avoid the bitmap stretching), using non-Metro apps is pretty much impossible (sans mouse) without closing something by mistake. Text is super crisp though; and with a Bluetooth keyboard, I could TOTALLY see myself using the Surface in portrait mode for some portable epic programming marathons.

Track pad:

Pretty much, the standard track pad on the type cover is awful for development purposes. Coupled with the small size of things on the screen due to the DPI scaling, it's pretty much unusable. Absolutely necessary to purchase a wireless (Bluetooth) mouse if you want to get anything done in a reasonable time outside of minor tasks.

Battery Life:

This is an issue everyone knows about, but the battery life on the Surface Pro is not good at all. You could, if you wanted, plug it in when you're working, but isn't the point to do work away from home and the convenience of unlimited electricity? A Haswell upgrade or a battery pack keyboard could make this a non-issue, but I find myself stopping work to let the Pro charge, which could be a deal breaker for a ton of people. I personally use this time to workout, calm down and figure out how to fix programming bugs, but being forced to leave and come back (with fresh eyes, might I add), is not necessarily a good "feature".

Misc.

Other things to talk about might be 10.1" either not being enough room to work for some people, or the perfect size for others; or to perhaps gush more about how great the pen is, but I'll talk more about those things in coming logs.

Next time, though, I plan to talk a bit more about the actual project and how the Surface is influencing it's development.

Expect Greatness~

Ryan Huggins.

Design Process: Project Voyage (Day 1)

Voyage Concept Art.

DESIGN PROCESS: This is where I will be choosing a project and discussing it's design decisions over a period of time. Expect frequent updates.

So, I'm currently on break from the college life and my goals are very specific. First and foremost, I want to complete the alpha version of Dolphin Squadron, implementing the last of the gameplay features, adding a reasonable tutorial and getting some music done for the game. Secondarily however, I've had this new idea floating around in my head and I want to mess around with it.

Design Process: Day 1

So, I got home from college yesterday for my semester break. It turns out, that being in a car/on a bus for eleven hours really kills my desire to work on anything productive and I almost did nothing for an entire day! Bummer. I've been in that mood before though; that mood where you don't want to do anything, but know that you should be doing something productive. Usually, I lose and don't do anything, but this time I did something a little different. I decided not to fucking waste any time. So here I am, writing this Design Process entry. I will be spending about an hour every day for the next few weeks updating this design journal with what I've been doing pertaining to game design and development. Today, that focus will be on Project Voyage. 

Project Voyage is simply a side-project. Moreso than Project Fall or Dolphin Squadron where I've actively developed the games for a few weeks, I'm just messing around and designing the shit out of Voyage. It's going to be a pretty transparent design process and the goal is to end up with a pretty comprehensive guide/discussion of how a game is conceptualized. Granted, I'm still a student of game design and I'll probably do a lot of things wrong, but I think that just being able to see the process will be a good thing for anyone who is new to game design and just wants to see how it's done.

Project Voyage

Open skies, open water, open shore. What do? Explore!

Voyage is an artistic game where you play as a 40-something year-old man/woman who gives up life in society to explore the seven seas as a sailor. The core of the game would take place primarily on the surface of the ocean and be seen from either a side or angled frame of view. Throughout the course of the game, the player will explore the world, discovering a variety of different methods of “play”. These methods of play--things such as fishing, exploring, finding treasure and shipmates, discovering new things about the world and sea battling--will all be core to the gameplay and progress the metagame. The game will begin at a deliberately slow, relaxing pace and ultimately speed up as time goes on. Ultimately, your goal is simply to discover everything the world has to offer to you. I don't want to pressure the player and I don't want to have them feel a constant tinge of terror. I want them to relax and enjoy nature. Through it all, the player character (PC) will become more and more like a seafarer who gains control over the seven seas. Whether or not you’re a good or a bad person is both up to you, and determined by the rules that you set for the seas and for yourself.

So, the idea for Voyage came up while I was thinking of what kind of mood I wanted to evoke from my next projects. I liked the colors and oceanic atmosphere of Dolphin Squadron, but wanted to capture it on a different front; a deliberately slow-paced game was what I wanted. One where I would create my atmosphere primarily through music and animation. A stark contrast to what I'm doing with Dolphin Squadron (which is a fast-paced retro action arcade game). 

Just something artsy I put together to find some more of the "feels".

The "feels" as I like to call them, are core to any art game. They're the emotions evoked through play. You get them through a mix of music, pacing, graphics and gameplay. In a game like this, gameplay is very important, but it can't be overly complicated or frustrating. I'm not trying to break the trend or anything, but I'm trying to create a fun, relaxing game concept. Not a micromanagement survival simulator. Something that's parts Superbrothers: Swords & Sworcery EP, a little bit of TAG (Treasure Adventure Game) and maybe a little bit LoZ: Phantom Hourglass or Spirit Tracks. In discussing it with Jacques Yeates (the composer), he described a game where you're not pressured to be good. We agreed that a survival game Voyage was not.

Survival games are too micromanagement-y; and there are just too many things to worry about. We definitely don't want a game where the player is too scared to try and go somewhere because they'll die, lose all of their stuff, and suddenly be back to square one right after discovering something new and cool (like a sexy hat). At the same time, you never want a game that feels like there is no weight to your actions, so we're still determining how to give weight to character actions.

Art and music are pretty straightforward when you're doing shitty concept art and linear musical scores, but what happens when you have to give real life to them. I don't even know what the game itself is going to look like yet. I wonder if I should take a straight up 2D approach to the game (ala Another World [land] and Castle Crashers [sea]?) or do something 3D, which I'm completely unfamiliar with. We had considered a Zelda-style perspective, but then I made the concepts and they just felt "right". Now we know we need a horizon, so we're still working out the perspective kinks. I'll draw out something tonight, probably.

Musically, Jacques has made some stuff that I'll start showing in the next Design Process entries (maybe a new song every entry for a few days?). It's really good and definitely captures the atmosphere, but we're also looking at how we're going to implement it. Dynamic music? Oh boy, I can code, but I'm still a newbie with anything musical. 3D? What's that? 2D is my home. And don't even get me started on what I'll be doing with the art. Hopefully someone from ACPC Productions (a college "studio", to which I design, program and produce for) will help out. Otherwise this will take forever!

Anyway. As usual...

Expect Greatness (and daily updates).

Ryan Huggins~

Current Project: Dolphin Squadron

DOLPHIN SQUADRON

So, Dolphin Squadron has been in development for about a month now. Originally, it was supposed to be an arcade-inspired game for Steam's Greenlight program. Sometime during the beginning of development we realized that we liked the game beyond it just being a school project and it went from a shitty school project to a shitty personal one. 

In Dolphin Squadron, you are a dolphin hired by the US Marine Corps to intercept dangerous underwater mines that are being used to covertly destroy coastal cities around the world. The core game is a vertical scrolling shooter where you play as a weaponized dolphin fired out of a deep-sea submarine. Starting at the bottom of a trench and traveling up towards the surface, the goal of the game is to destroy a mine before it reaches the surface by first, catching up with and destroying a mechanized escort fish that's carrying it to the surface, and then destroying the mine with your dolphin's body. The hook is exploding dolphins. To destroy the mines, you have to destroy the mecha with your dolphin lasers and then slam your dolphin into the mine.

There's more than just dolphin lasers now, but this pitch was what sold the game to my class and teacher and from there we began development on a game that was pretty much about blowing up marine wildlife. Ironically, only one person was concerned about the potential for people to become offended by the game's core theme of kamikaze dolphins, but we ignored them and continued to work on the game.

These kind of things still make me happy. Haha

Presently, the game is on a smooth development course (with an February-April release window), but there are a few issues with the core design and some mechanical issues that I'll need to iron out before a release. Of these, one is establishing a clear method of level progression and another is the difficulty of creating "procedural" (read : random) obstacle generation that doesn't fuck up and create impossible gameplay at higher difficulties. I haven't heard any complaints about the enemy/obstacle locations being "dickish" (direct quotes) from the most recent versions of the game, but reaching a happy balance for difficulty (as far as concentration of obstacles goes) is getting very difficult.

Currently, the spawning of enemies and obstacles is pretty random--and that works fine for now--, but I'm wondering if there should be a more dynamic system for spawning enemies and obstacles. I figure that once I reach a middle ground for obstacle concentration, I can tone up the difficulty through other means such as providing the level boss (the mecha) with weapons and introducing mid-bosses in some levels. Weapons balance was a minor issue for awhile, but at this point, the weapons seem to be suitably balanced, though they'll definitely change a little bit before the end of development.

Our goals for the game aren't terribly crazy, but we do plan on polishing the game for at least a month or three before releasing it. Figuring that we can implement all aspects of the levels, get all of the art done and add a fun number of gameplay secrets before sometime in late January/early February, we could have the game ready for a release sometime in April. Eventually, I'll release a video or two of the gameplay and how it's progressed. :D

Expect Greatness,
Ryan Huggins~

Welcome Back, Me

Well, it's certainly been awhile since I've last updated. For the last few weeks (months?) I've just been acquainting myself with the college life. I'm now attending Champlain College for game design and so far it's been a pretty fun time. ...But no one cares about my college experience. What's important is that I've been improving my skills as a game developer and designer for the time I've been gone and here I am, returning prepared to make some games. So, let's talk about those.

Project Fall :

My previous project, Project Fall, hasn't been updated too much, though I'll potentially be releasing the prototype to the wild soon. Currently, I'm working on developing an artistic style for the game before I dive head-first back into development and turning it into either an arcade-style platformer (a murderbox as I like to call it) or a full-fledged platformer. Who knows. Maybe I'll do both! The design is solid, the testers like/love it, the controls are sexy--it's a good prototype...now to just make something with it.

Concept Art for Project Fall

Dolphin Squadron :

Here is the project that I'm currently working on. Dolphin Squadron! Dolphin Squadron is an arcade-inspired scrolling shooter where you play as a dolphin employed by the Marines/SEALS to intercept and destroy deadly, coastal-city-destroying, mines...with your flimsy dolphin body. I like to call the game Exploding Sea Battles sometimes since there are a lot of explosions, many of which are friendly sea creatures simply getting in your way.

I designed the game for my Game History and Development class here at Champlain College, but it was an idea that I had previously come up with while I was showering. Figuring that a radical game about exploding sea creatures and a weaponized dolphin would garner at least a little attention, I decided to use the concept for the game. Right now, the game is a little more than a prototype and I plan to throw up some updates and videos here to show progress as the game develops.

A friend of mine actually turned his monitor to play the game...

Dolphin Squadron was developed over 4 weeks (for class), though arguably, I coded pretty much the entire current version of the game in less than a week (the last week :P) before the game was due. We plan to finish the game and add some more crazy shit to make it sexier and overall more fun to play. Current issues include difficulty, a minor lack of understanding the goal (for new players), and a shitty tutorial.

Hanriot :

Hanriot was our (ACPC Production's) first game jam game. We formed at the game jam and have decided to stay a loose group pretty much during our time at college. Hanriot was a game designed for the theme of disavantage and our lead designer (I programmed), James Shasha, decided on an Italian Pilot who crash-lands in the Alps, behind enemy lines, during WWI. The goal of the game is to get through the Alps and reach the city at the end of the game.

We didn't manage to complete the game because of mapping bottleneck issues with Game Maker 8.1, but we did create a visually pleasing game (even though it wasn't perfect) in 48 hours, with a bunch of freshman game developers. We were very pleased with ourselves.

YOU CAN DOWNLOAD THE GAME HERE.

WELL, ACTUALLY HERE.


Project Clusterfuck :

So, I wanted to make an RPG/Adventure game and thus, Project Clusterfuck was born. Generally, I develop games under the Siifour Studios name, but this game is currently being developed under "my" side-studio ACPC Productions (you don't want to know what it stands for) and the final game will probably fall under the ACPCP and Siifour Studios production houses (Siifour's designer and musician and ACPCP's artists, testers, co-designer).

The game is literally a clusterfuck of five different RPG stories because we thought it would be cool to have the player transverse through a series of different RPG stories. Whether or not the idea will hold up is up for speculation, but based on our current designs, we're more than ready for the hurdle. I'm producing, coding, and designing the game, but with five people writing five different stories for the game, I figure that I'll be more of a mediator and balance maintainer than a full-fledged designer. :P

Project Clusterfuck is my current large-scale side-project. While I work on Clusterfuck, I'll probably develop at least 5 or 6 games of a Project Fall or Dolphin Squadron scale and hopefully they'll be just as fun as those two games are shaping up to be.

We will also have a fuck-ton of art and concept assets.

Now here are the artists:


Brook (Revocare) :

Some of Brook's OCs.

A mecha and it's rider (WIP)

Brook is our key artist. 

Megahn (Nanrie) :

Two Clusterfuck characters together. 

One of Megahn's OCs.

She can drawn with pencils too. Who does that anymore? ;D

Hunter (Totalblatherskite) :

They got infatuated by a cat in a movie. He drew a cat.

OCs from Hunter's story. 

Matt (Pseudosutra  I don't currently have any of his art, but here are his character designs) :

One of Matt's characters drawn by Brook.

An ACPCP fan favorite. Gungie (I think that's how they spell it...)

MOTH CHARACTER! :D

Ryan  (Project Duo) :

The main character of Project Duo.

I'm not a colorist. Haha

The above character's brother.

Note : All of this art (sans Hunter's) is for Project Clusterfuck. ;D

Expect Greatness.
Ryan Huggins~

Working With Flash

A great environment.

After working in Game Maker 8.1x for a pretty long time to build games, I figured it was about time I started learning another environment for designing and developing games in. Game Maker 8.1 is a good program, and is very capable of doing what I wanted it to do with my 2D projects, though I felt limited only knowing one or two programs for game creation. Enter FlashDevelop + FlashPunk. (To be honest however, I may end up using Game Maker (Studio) to make a lot of my older game ideas because I know it best.)

It's been a blast messing around in a new engine/language...so finding myself reading code snippets on my phone in the middle of the night to learn the language pretty much sealed the deal for me and Flash (at least for Project Fall). Moving over from Game Maker 8.1 to FlashDevelop + FlashPunk has been a fairly smooth transition and the object orientation of FlashPunk has been very helpful in allowing me to learn AS3 quickly. Still though, I'm kind of a noob, so I have a bit of practice before I can actually make anything worthwhile with the program!

I've been using the FlashPunk official website and official forums to learn the language and build games and Zachary Lewis's tutorials have taught me pretty much everything I need to know to get my hands dirty with the program even if I'll have some trouble for awhile.

To be honest though, the only real issue I'm having right now is that I'm having trouble referencing variables from other classes and I figure that it's only my newbie-ness preventing me from doing something so basic. I figure that I've learned enough about the engine to begin porting the Fall prototype over into Flash and I can only hope that the performance issues that plague Flash as a game development platform doesn't become a serious issue for me! -.- Wish me luck!

Expect greatness. Ryan Huggins~

Current Project: Fall

You're the horizontal thing (he's flipping).

Today is the last day that I've dedicated to official prototyping of Project Fall. Which essentially means, that I will continue to prototype the game until it feels like I want it to feel, then move on to learning Unity so I can port it to that platform (if 2D is actually feasible there). It also means that I can like, release screenshots and concepts of the prototype because it's actually pretty fun now.

Obviously, the screenshot that you have become privy to in this post represents more of my legendary placeholder artwork, but it handles the job of emulating gameplay, and it does that job extremely well.

The Early Story

So far, a few things are different with how I approached this project as compared to City Across the Sky, and yet the game followed a pretty standard stream of changes and iteration. At first, I had an idea of a game where you would have a bunch of weapons (the prototype only has 10), murder enemies, and avoid falling objects from the sky. It was going to focus on paths of motion and tight controls but be executed around the notion of avoiding this falling objects. I started on the prototype, got wall-jumping the way I wanted it, added a weapon or two, created some enemies and everything was fine and dandy. I thought the game would work out exactly as I planned it. Then I added the falling objects and the game suddenly was some shit. I realized that my original vision just wouldn't work with what I had coded (motion of objects and controls) and with that, the vision in my head fell apart. However, I liked what I had created a lot, so I kept the enemies, weapons, and movement and later moved towards and idea which I called the "murder box".

The Fall

After the idea of "Fall" had failed me, I decided to keep the name (since I have another project called Spring [more on that later]) and work on the concept of a murder box arcade game. But, for awhile, I thought the idea was much too simple and reminded me a lot of Super Crate Box, a game by Vlambeer, a studio that I really like and would ideally, like to emulate, but not copy. I was at a complete loss for what to do with the game, and let it sit for about 5 or 6 days. I hadn't abandoned it, but I didn't have an idea for what to do with the game. The simplicity of the gameplay is inspired somewhat by Super Crate Box and to a lesser extent Super Meat Boy, but I'm working hard to make it feel like a different game entirely.

I believe that it's very important to come up with your own ideas, but at the same time, I don't think that borrowing ideas that work from other games to supplement your own individual visions is necessarily a bad thing. As long as you're not ripping off another game, I feel like similarities between games should only serve to honor the original inventor of the idea.

The Inspiration

For awhile, I had trouble finding something that could work as a goal for the gamer; one that didn't tread too closely to Super Crate Box or the notion of solely trying to acquire a higher score (but that would ultimately be the goal of course). In SCB, getting the crates and finding new weapons was the major goal. It served the purpose of randomizing gameplay and acted as the scoring mechanism which was a great design choice because it fostered simplicity. For a while, I wondered what I could use as my scoring mechanism. For a while, I couldn't think of anything.

But, I asked my girlfriend (who is by no means a gamer of any kind) to make a list of things she thought I could put into the game to make it better. She made a list of ten things, and initially, I thought the list was a pile of crap, so I was frustrated by her naivety within the discipline of game design. I was serious, and her suggestions were...well they were not serious. So at first I disregarded the list and stopped development for a day or two. But eventually I came back and looked at the list and something clicked with two entries on the list.

1. Triangles that spin and cut you.
2. Squares that shoot you.
3. Keep the basic shape thing you have.
4. If there is something good falling from the sky, give it a rainbow trail or something.
5. Zooming cars.
6. Raining guns that you have to avoid.
7. Mermaids.
8. Catch the gun and it kills everything on the screen. Call it the "Silver Star Gun".
9. Bubbles. Toxic bubbles or happy bubbles.
10. Sound effects.

Raining guns and the "Silver Star Gun". From these ideas, I created the Gunstar. 

The GUN STARRR.

A weapon that, if the player is doing very well for a certain period of time, will fall from the sky and offer you ultimate power for a short time span and allow you to murder the crap out of everything on the map (if you're skilled). This idea, spawned from a list of what I considered terrible ideas at first, inspired me to work on the game as a murder box and helped me move away from the idea that the game was too inspired by Super Crate Box.

What you should take from this is, ideas can come from ANYWHERE, not just yourself. Outside ideas are extremely important and even if you don't think that whoever is giving you the ideas is qualified to give you ideas (probably because you don't think they know about games or fun and you do because you're a "game designer" and they're a regular person). You have to remember--and I have learned to remember--that game designers aren't usually your target audience, just because they MIGHT be the most vocal audience or offer the most criticisms, you don't tailor your game to them, you tailor it to the people you want to play your game. In the case of Fall, it was casual gamers and the indie hardcore.

The Murder Box

So, by mixing ideas from other games and adding a few of my own, I've managed to make Fall feel more like an action-arcade game inspired by the elemets of Super Crate Box (spawning weapons to keep you on your toes), rather than a copy. By adding elements from Team Fortress 2 (rocket jumping), Cave Story (where certain weapons affect how you move), Galaga (power-ups which are not implemented into the prototype yet), Super Meat Boy (simple motion, but with my own arcade "feel") and my own design elements (usually inspired by friends and family) such as the Gunstar (a power-up) and the leveling (leading to bosses), difficulty (based on a tier system) and scoring mechanics (which encourage the player to beat their own high scores to encourage player improvement), I managed to make Fall a completely different game and in the end I hope others think so as well.

Concept Artwork

By Jacques Yeates. He thinks it's too cutesy. You can see how the Gunstar
 has influenced the theme of the game.

By Ryan Huggins. I thought the shades (reference to Gurren Lagann) made this
one of the greatest things ever.

Early Prototype Videos

Expect greatness. Ryan Huggins~