Project allo – Entry 9

This week we focused on improving our game experience based on the feedback and observations from our playtest last weekend. We have another playtest scheduled for this Saturday so that we can test out the mechanical changes that we made. Our semester is approaching its end so we have accelerated production to reach our goal of a complete game experience by our soft opening.

We conducted a playtest last weekend to assess our current game design. The playtest showed us that players liked the team shooting experience we offered them. They really liked the visual theming. With regard to the 3 control interfaces we had them try, the majority of players liked being able to independently rotate their cannons around the entire ship as opposed to being dependent on the captain for positioning (as was the case in the other 2 control schemes). They really liked the surprise of the special ‘danger’ event that happened at the end of the test level. Criticism centered around the insufficient responsiveness of the controls. We had incorporated friction and inertia into the movement of the captain’s shield and crew’s cannons in order to give the cannons more weight and make the game a bit more challenging; however, we observed that we set those parameters too high so we will be reducing them for our next playtest, in addition to the other mechanics changes.

Our challenge this week was for our design team to lock down the intended game experience. So far we have been creating an experience intended to be cooperative; however, the shooting mechanics and current enemy designs do not require or encourage the players to work together. In the playtest, we observed that each player’s role is so intuitive that they don’t need to communicate more than once or twice during the game. We had a long discussion on whether we wanted to continue with this shooting gallery approach or stick to our original intention of tower defense. We chose to stick with the simple basic shooting mechanics; however, we will be adding unique special abilities to each player role, as well as enemies that can only be damaged by specific players in order to increase the cooperation requirements of the game. We believe this will make gameplay have more meaningful choices on strategy and we will test the theory in our playtest this week.


Project allo – Entry 8

So far we have been working to design the roles of captain, navigator of the ship, and crew, players who man the cannons of the ship. We have iterated on mechanics that allow the captain to move the ship up and down, as well as crew mates to move their cannons around the ship in order to aim. We are anticipating our second playtest and wish to lock down these two roles in order to consider a third role to provide more variety and selection for the players.

Our designers came up with a third interaction scheme for the game based on feedback we received from clients and faculty. The captain can move the ship up and down onscreen, as well as rotate a barrier that can protect parts of the ship from enemy impacts. The gunners are able to rotate the cannons around the ship’s entire 360-degree range (though they cannot occupy the same space/overlap). We wanted to try a version with these mechanics in order to give the shooters more independence from the navigator, as well as to give the navigator a more clear and meaningful interaction.

Captain and Crew

Project allo – Entry 7

In the time since we decided on moving forward with our fourth prototype idea, we have been designing and building elements to turn it into a comprehensive experience that appeals to both children and their parents. We have designed and are building a cooperative, space-themed, tower defense/shooter hybrid game that drops players into the role of space pirates trying to survive perilous locations in search of treasure.

We have been building our final product design for the last few weeks leading up to our halfway milestone. This is a short peak at our progress.

Project allo – Entry 6

This is our fourth design idea. We designed and built it in tandem with Dynamic Defenders as an alternative interpretation of the original allo idea: all players control part of one object. In this game, players each man one of three cannons and try to protect their ship from incoming enemies. They can also collect power-ups that change the nature of the shots their cannons produce. For this prototype, players must try to survive for as long as possible before their health bar reaches 0.

Jellies in Space

The idea of this design was to encourage player cooperation by binding them to one in-game object and tasking them with protecting the object (and themselves by extension). Faculty and client response was positive, particularly with regard to its potential for expansion. They found the controller, a rough implementation of the Dynamic Defenders controller, unintuitive and they felt that having the spaceship rotate automatically was more of a hindrance than a help. Based on our client feedback we decided to move forward with this premise, and create a design for a full game around it.

Project allo – Entry 5

This is our third design idea. Since faculty responded positively to being able to freely bounce around, we decided to change the design to resurrect our initial goal of a cooperative experience while maintaining the player agency they liked. In this game, players must work together to protect a constantly-changing VIP player from hazards coming at them from offscreen. If a VIP is hit, they lose their status and the title shifts to another player. Players must try to survive for as long as possible; once all players have been hit as VIP, the game is over.

Dyanmic Defenders

This prototype was designed in response to positive feedback from our previous Bouncing Billiards prototype. We wanted to test a mechanic of giving players full agency in determining what they do, while incorporating game mechanics that require them to work together and help each other. Responses were positive, with the biggest issues being the learning difficulty and the incomplete quick-time interaction events. We ultimately discarded this idea in favor of our fourth prototype because we could not justify how the game could be expanded into a more comprehensive final product that required 14 people to make.

Project allo – Entry 4

This is our second design idea. Using the basic mechanics of pool and applying our multi-player bouncing jellies, 2-4 players engage in a chaotic race to get the most balls into the pockets. After pocketing all of the regular balls, The Crazy Eight ball will appear and begin chasing the nearest player. All of the players must work together to pocket The Crazy Eight; however, they can only hit it safely from behind, lest they be consumed. If the players successfully pocket The Crazy Eight, the players who remain alive get bonus points. If they all get eaten, then the winner is determined by his/her score from pocketing the normal balls.

Bouncing Billiards

This prototype was designed in response to the failures of our first prototype. Though the implementation of that prototype was flawed, the idea of bouncing around as jelly elicited numerous positive responses. As a result we made a simple game that gives players the full freedom to bounce around. Though they each share the same objective, they can go about achieving it in different ways: skill shots of knocking balls into pockets, getting last touches on balls that have been hit by other players, or just launching themselves into other players to prevent them from scoring. Several faculty particularly enjoyed bouncing into and knocking each other around. The feedback from this prototype inspired our third prototype.

Project allo – Entry 3

This is our first design idea. Players each control a portion of the gelatinous creature onscreen in order to generate force that makes it move. Each component of the creature operates like a slingshot, players can pull on their portion, release, and apply a force in the opposite direction of their stretch. They need to coordinate their efforts in order to make the creature move in the net direction they desire. The prototype includes 3 demo levels with collectible items, as well as blocks that need to be smashed into before reaching the level end.


This design idea was an experiment to see if players could coordinate their collective movement by applying forces to their in-game avatar, essentially if they could work together to control one body, and have fun doing it. Unfortunately, this design did not prove successful. Faculty players found the controls unintuitive and movement stilted, as well as lacking a clear objective and a compelling reason to engage with the game at all. This was due in part to an incomplete control interface; however, the design implementation was fundamentally flawed in that it didn’t allow players enough control over what they were supposed to be doing. The amount of force generated by one player slingshotting barely moved the body, and even then it didn’t usually behave in the manner they intended. We discarded this idea after receiving feedback during our quarter milestone presentation.

Project allo – Entry 2

My team and I came up with a movement mechanic for the cooperative gameplay we are aiming for. We are now building prototypes to test the mechanic, as well as different applications of it. Players will move by stretching and releasing different parts of their in-game avatar in order to produce a net force that propels it in their target direction. The first prototype will allow us to test the movement system when applied to goal of getting from point A to a choice of either point B or point C.

Prototype 1

The second prototype will allow us to test the movement system when applied to the goal of pushing an external object from point A to a choice of either point B or C (similar to the concept of pool or billiards).

Prototype 2

Project allo – Entry 1

Project ‘allo’ is the game I’m co-designing for my final semester at the Entertainment Technology Center of Carnegie Mellon University (in the spring of 2015). I am working as part of two student teams with Electonic Arts’ Office of the Chief Creative Officer under the direction of Richard Hilleman and Tom Corbett. Together with team Thunder Egg in Redwood, California, we are creating a connected game experience. Our challenge for this project is to create a game-within-a-game in which players must balance multiple gameplay mechanics simultaneously. We will be targeting players who don’t fall in the category of “core gamers” through simple mechanics that allow for an easy-to-learn and fun experience.

Our challenge has been distributed across two teams, my 8-person group in Pittsburgh and our 6-person group of classmates at EA’s campus in Redwood, California. We have been charged with creating the experience of a game-within-a-game. Using an un-announced platform, we will create a game that tasks players with balancing multiple game mechanics that affect and control each other.

The very first thing we needed to do was to figure out what it means to be ‘a game-within-a-game’. I’ve struggled to come to a workable definition. So far, to me it means an experience where players interact with characters or a world that inherently possess some level of autonomy. In other words, the player produces stimulus (which could be in any number of different forms) that affects the state and actions of the characters and/or game world. However; myriad other interpretations exist. For example, in Settlers of Catan™ players must mine resources in order to achieve the win objective; however, to do so most effectively they have to work with and inhibit each other in managing their resources. So the experience is a board game with an economical game inside of it. At the end of the day I suspect there is no actual definitive answer, which is presumably the point of assigning it as our design challenge. My design team will do its best to come up with something that fulfills this challenge.

In order to create a game-within-a-game, we have been focusing on mechanics that involve cooperative multi-player interactions, i.e., players have to work together in order to perform the tasks that the game demands of them. Some ideas include players controlling parts of a the same in-game avatar, working together to construct and deploy items, and working together to defeat in-game opponents. Others involve teams of players working together to defeat each other.


This is a blog of my activities on my game design journey. As I move through design projects, I will chart my journey: decisions my team and I have made, reasoning, retrospective analysis, etc. I hope it will provide an interesting cross section of my experience as a designer, as well as a reference for my future consultation. This is an ongoing personal pursuit.