Exercise #10 - "Us versus It"

US vs. It

Summary: La Boulange Jeffrey and I took a day together to balance a game of US vs. It. Because we were not able to make it on the original day (due to GDC), we scheduled a day together to finally make a balanced game. At first, we assigned the tanks certain properties, but the Robot would seem to either destroy them too easily or in turn be defeated to easily. It was actually a monotonous experience at times because we had to keep implementing theories over and over and over. Eventually, we finally came up with a formula in which the Robot does reach victory but barely manages to survive in the process. We know that this formula works because both Jeffrey and I have taken our own respective playthroughs and have achieved different but similar results. Both playthroughs of ours had different routes but both ultimately ended with a lifepoint of 1 for the robot. 

Included we also have a simulation of a player who is inexperienced and did not read the directions. They will just barely lose because they did not read or know about the ability to use the special bomb.

Technical

Game Rules:

10 Turns

Laser Eye

Special Bomb (Lose a Turn)

Properties:

Orange:

Green:

Purple:

Tests:

Move Forward                                                                                                                                    10

Move Forward                                                                                                                                    10

Laser Eye                                                                                                                                           8 (-2)

Move Forward                                                                                                                                      8

Move Forward                                                                                                                                   6 (-2)

Special Bomb                                                                                                                                     5 (-1)

Lost Turn                                                                                                                                           4 (-1)

Move Forward                                                                                                                                   2 (-2)

Move Forward                                                                                                                                   1 (-1)

Move Forward                                                                                                                                       1

WIN                                                                                                                                                      1

Move Forward                                                                                                                                    10

Move Forward                                                                                                                                   8 (-2)

Laser Eye                                                                                                                                           8 (-2)

Move Forward                                                                                                                                   7 (-1)

Move Forward                                                                                                                                   5 (-2)

Special Bomb                                                                                                                                     4 (-1)

Lost Turn                                                                                                                                           4 (-1)

Move Forward                                                                                                                                   2 (-2)

Move Forward                                                                                                                                   1 (-1)

Move Forward                                                                                                                                       1

WIN                                                                                                                                                      1

Move Forward                                                                                                                                    10

Move Forward                                                                                                                                    10

Laser Eye                                                                                                                                           8 (-2)

Move Forward                                                                                                                                      8

Move Forward                                                                                                                                  6 (-2) 

Move Forward                                                                                                                                   3 (-3)

Move Forward                                                                                                                                   1 (-2)

Move Forward                                                                                                                                       0

LOSS                                                                                                                                                    0

List #3

Work due by 25th of March, 2014

Assigned
- Review Chapters 1-8 for Exam
- Mid-Term Exam Due Online
- All Mid Season Work Completed

Personal
- Exercise #3b: High Concept ALPHA (Alternate Game)
  - Program Type
  - Game Development Document

Exercise #9: Far Cry Map*

March 24th, 2014

This is where I would have placed my image of my team's far cry map. That is, if the console we were working on didn't crash and lose our save data...

I couldn't help but think how heartbreaking this must feel in the actual video game industry.

I feel that this was going to happen sooner or later. But, in a way I think it may be a blessing in disguise. Because I've learned early on that, in the future, if I ever work on anything at all, I need to back it up. Maybe even in several different places.

Technical Description:

Prototype Specs:
Map for a 1st Person Shooter
2 Opposing Strips of Buildings
Middle Obstacle (Ship)
(Spawn Point) Forest before Town Entrance

Visual Description:

If the Map we made were still in existence, it would have looked as followed. The map was simple. Our team thought of creating a map with two opposing towns. Kind of like a western movie with saloons and bars. In the middle of the two strips of buildings was an empty plane of sand. It was quite funny actually, as the map started of as really simple. What made the experience very memorable was what our team did with the mistakes we made. Because our team was unfamiliar with the controls, we at times would indent parts of the map on accident. In this case, one of us accidentally indented the middle between the buildings. So now, this area meant to be a barren center for shoot outs to occur was now in conflict with this bulge in the ground. As we tried to fix it, we found it much more interesting to work around it. What we did was actually add things to the hole. We first added water. Then added a boat. Then removed that boat and added a ship. So we had a ship in a small pond next to the sand. It made no sense at all. We definitely let our imaginations get ahead of ourselves. But we decided to keep it. I think this event was the catalyst that set off the rest of the map. After that we got more impulsive and ambitious. We put a Huge tree in the middle of an apartment project. We added machine guns to the ship in the pond in the middle of the sand. We added dirt bikes. We added a forest next to the town. At this point our imagination had no bounds.

This map we made no longer was grounded in reality. And it was all a product of that one mistake. Though in the future, we must give ourselves limits, I feel that this was a very therapeutic event because it allowed us to let go of our mental limitations and let our imaginations flow. This was an important event for me because in the last few years, I feel as if I have been holding back my creativity with my overly-critical views on reality and fantasy. It made me learn that in order to be creative and create new ideas, one must grasp the fact that if the program in which you are using is not bound by limits, then neither should you be.

Exercise #3 (Alternate) - High Concept Statement B

March 23rd, 2014:

Information:

After much thinking and consideration, I have decided to postpone/substitute my original idea for a video game. As mentioned in a previous post, I was set on making my own personal fighting game called PFE (Prototype Fighting Engine). Though still a high possibility in the future, I believe that there is another project idea calling for my attention right now. There are many reasons why I am changing direction but to pinpoint the reason is mainly because of my experience with Flowlab. Originally, When I was working with Flowlab, I didn't see myself going in the direction of a 2d Platformer. However, I found myself spending more and more time in Flowlab than originally planned. I fell in love with the fact that I was creating more and more with what started out as nothing. As I continued working on the project, more and more ideas came about to what my first video game would be. Not to say I couldn't have also gained some ideas through MUGEN or another program, I felt that Flowlab gave me a feel for the limits of my abilities and the kind of direction I would like for my first game. I'm on the fence in terms of which program to use, whether it be Flowlab or GameMaker, but I am absolutely positive that I want to make a 2d NES Style Platformer Game.

My Final High Concept:

This is the final phases of my decision making process. There is very little time; thus less opportunities to make changes. This is what will ultimately come... or not come by the end of May.

My idea is to have a classic video game. Something that I can make now with my lack of programming knowledge and artistic ability. The game will hopefully be smooth and easy to play. I'm making sure the game has a very simple story line in order to coincide with these deficiencies I have as a designer.

G-Robot will have many basic elements common to NES games. Of course shooting and jumping will be an available option. The game will have basic enemies and personally made backgrounds.  This game will take influences from NES games like Megaman and Mario. I'm aiming for a visual style resembling that of Megaman specifically. Character designs will be influenced by a variety of different areas, one of them definitely being Gundam.

If I can achieve the goals I've set for myself, I can at least provide a GDD or an unfinished demo by the end of May. I am looking to make this game with either Flowlab or GameMaker.

Provided Graphics:

So far this is what I have done towards the game.

From Flowlab, I have some designs of what the main character will look like and a heavily unfinished first stage.

(Also provided is the original Powerpoint pitch)

G-Robot Original Powerpoint

Exercise #8: Basic Sketchup Design

February 21st, 2014*

1st Sketchup Using Models From Warehouse

Custom Basic Sketchup - Top Side View

Side View

Right Side View

Perspective View

Perspective View #2

Details:

On my first day with Sketchup I exclusively used models from the 3d Warehouse. It was a great way for me to get used to the system and learn how to implement models into a free 3d space. I actually found it difficult, however, to create the setting I wanted with the models in the 3d Warehouse. Originally, I wanted to create a city with a broken highway and ruined buildings. This was difficult to make as there were limited amounts of models that matched this description. Though results were fast at first, I soon came to a plateau in which most of the models didn’t help with the synergetic theme I was looking for. Eventually, I decided to stop working on my original design.

Later, I opted for a more simple approach. I decided to create my own environment. I watched a few Sketchup tutorials on youtube and learned the very basics of creating models. Eventually, I ended making my very own basic models. Ultimately, I made a model of a warehouse. To simulate some physical models I’ve seen in real life, I decided to give it a “half-open” look where you could clearly see the inside of an otherwise blocked off building. Inside it has a default character model, barrels, boxes, and cargo. I also created a small room in the far left corner and added a ventilation shaft in the upper region of the model. Outside the building itself is a car and some pavement road. The car was actually the most difficult model to create because of its various lines and curves.

The overall purpose of the model is to be a location for a 3d Shooter Game. In terms of setting, I can imagine this area as a place where the main character would be engaged in a shootout. The cargo boxes would serve as a form of coverage from gunfire. The ventilation shafts could be crawled into to escape by finding a way on top of the cargo boxes. I can also see the barrels being used as a device to eliminate multiple enemies at once. Finally, the car would be the goal. 

Exercise #6 - Flowlab IO

January 30th, 2014

Make a simple game with a background, surface and player character based on the startup tutorials in 'flow lab'

General Information:
In class, we got our first taste at game creation on a simple and accessible platform. We used an online web tool called Flowlab. It's a new and very helpful tool for anyone who wants to design a simple and playable online game. It doesn't require any knowledge of programming and is highly customizable. There are some default sprites and objects to start your game from. Each piece you build with is in the shape of a small square.

With Flowlab, users are allowed to create and customize sprites, add and link behaviors, as well as design the background and gameworld. Learning all of this can be done in a short period of time.

Personal Reaction:
I had a great time experimenting with Flowlab. I was happy to find out that there is a program basic enough to be used by a newcomer like me.

It was quite surprising how much time I allowed myself to spend on such a program. Using Flowlab gave me a great deal of inspiration into making games of this kind. It made me feel as if I could make anything as long as I dedicated the proper amount of time and effort into it. 

Through lots of trail and error, I'm very happy that I made something playable out of literally nothing but small pieces.

I don't think this is the last I'll see of Flowlab. I can see myself doing more than just the introductory lesson I've done today. With a little more time and creativity, I feel I can customize the basic sprites given to me and make something that more represents my style and views.

The Game:
Up There

I created a very simple sidescrolling game in Flowlab. I used the default sprites and objects to create a stage. I kept the game world very basic. I didn't design any aspects of the user interface; This is because the UI is for more advanced users. I decided to focus on the basics in the background and gameworld.

The objective of the game is to simply gain the coin at the end of the stage. To get there, the player must be able to jump without falling into the crevices.

Link to My Flowlab Game

List #2

Work due by 7th of February, 2014

Assigned
- Read Ch. 4-5
- Exercise #3: High Concept
- Exercise #4a: Game Appraisal 
- Exercise #4b: Video Game Excellence

- Exercise #5: Cartoon Network Game Creator

- Exercise #6: Flowlab IO

- Exercise #7: Emotional Tone Powerpoint

Personal
- Prototype Fighting Engine: PFE - Preparation
  - Program Type
  - Game Development Document 

Exercise #3 - High Concept Statement (Original Game Idea Paragraph)

January 17th, 2014* (Date Assigned)

Write a high concept statement: a few sentences that give a general flavor of your game. You can make references to other games, movies, books or any other media if your game contains similar characters, actions, or ideas.

My High Concept for Game:

General Mind Map for PFE (Incomplete Ver.)

My idea for an original video game is a 2D game in the fighting game genre called PFE (Prototype Fighting Engine). The fighting game will have all the elements of modern fighters. However, there will be differences in the style and mechanics in comparison to current fighting games.

The reason why I want the game to have 2D graphics is because I want this fighting game to go back to its roots. Nowadays, fighting games have fallen into the 3D trend, where character models and backgrounds are three dimensional. Aesthetically, I believe that 2D Games are just as visually pleasing and beautiful as 3D games.

PFE will have several elements similar to typical fighting games. The game will have multiple characters, stages, combos, super moves. What will be different about this game is how the game can be played. There will be super moves that can be gained in two different ways; Beginner and Expert modes. Before a match starts, the Player will be able to choose either mode. Specifically, beginner mode allows the Player to gain super meter (comeback mechanic) as they are attacked. Expert mode allows the Player to gain super meter as they are attacking/being aggressive. The purpose of this mechanic is to allow beginners a chance to succeed while simultaneously providing a mode that is accommodating for veteran and skilled players. Also, I'm hoping that the mode would allow more personality and diversity within the game.

Visually, I want this game to have clean and smooth looking sprites. Just because the game is 2D does not mean the sprites have to be of 8 bit quality. A good example of this would be games like Guilty Gear, Blazblue, or King of Fighters XIII. Another aesthetic component of this game with be that it will be darker. I believe fighting games are not respected as sometimes they are depicted as too cartoony. For PFE, I want it to be dark, cool, and serious. 

The players themselves can choose whoever they like. There will be a total of 5* selectable characters and a few unselectable characters. The unselectible character will either be secret bosses or the boss himself/herself.

As for the programs. These are what I'm planning to use at this stage:

Flash

Game Maker

MUGEN

King of Fighter's Style will be a huge insiration for this Project

Exercise #1 - Ball Game Assignment

January 10th, 2014* (Date Assigned)

Summary:

Originally, my first day of class was supposed to be this day. Unfortunately, I did not get to attend for various reasons. However, I did get to catch up and am now up to date. I just thought I would post the assignment that was originally due. 

I was very happy and excited to do this particular assignment because this is my first time ever making up a game idea for myself. I apologize if it comes off as overly boring or simple. Hopefully, as I develop in creativity and skills, I can be capable of developing more complex and interesting games. 

Assignment Description:

Ball Game Challenge 

Create a competitive game for two players and a ball that does not involve throwing it or kicking it.  Prove that it is a game by showing how it contains all the essential elements.

Game Title: Sprint Ball

Game Description: A simple game that requires two things. A ball and stamina. The preferred area of play is in a location the approximate size of a basketball court. This game requires a great deal of cardio as each round will require a sprint(s). The game goes as followed:

The game starts as the ball is placed directly in the middle of the arena. The players are facing opposite directions, with their backs turned toward one another and both are unable to see their opponent. In the middle of the two of them is the ball. The game officially starts when both players agree to sprint. The objective is to run to the end of the court and back to the ball in the middle. The first player to grab and hold the ball (past the waist) earns ten points. Winners are determined by being the first to gain 50 points (can be adjusted to 20-40 points for victory). 

However, after each round, the game changes from a symmetrical balance to an asymmetrical balance. The winner of each round is put at a disadvantage every time, as the winner loses two feet of ball space the following round.

Game Elements:

1) Play
- The player is fully in control of his/her fate. Their ability to outrun their opponent is essential to their success. In this game, the more athletically healthy and experienced runner should win. However, as the game goes on, the two foot ball gaps should obstruct the superior runner from achieving a 50-0 end score.
2) Pretending
- We imagine that the ball in the middle has some significance. The ball itself in this "magic circle" has a significance of ten points. 
3) Goals
- The goal in this game is simple. Be faster than your opponent.
- But at the same time remembering that you can't always be faster due to health limitations. You have to keep in mind the long-term goal of victory. Can the pace you set for the first game be met in the third or fourth? The game can be strategical in that one may even pace themselves one round, giving their opponent a great opportunity to steal a round, while one recovers and regains two feet of ball space in return.
4) Rules
- Basic Rules:
a) Requires 2 Players
b) Requires a Ball
c) Arena the size of a Basketball Court (preferred)
d)The Ball = 10 points.
e) The Winner of each round loses 2 Feet of Ball Space in their Opponent's Favor.
f) Termination Condition requires the Winner acquire 50 points before the Opponent can.

- Miscellaneous:
a) Additional Rules:
  - Ball Type is Adjustable; Preferred Lighter Weight.
  - The Arena can be bigger of smaller depending on preference. However, one might want to adjust the Two Foot Ball Space Handicap according to area.
  - Termination Condition Points can be adjusted due to average staminas.
 b) Other
  - No Late Starts, No False Starts.
  - Tie Rounds: (Where both Players grab the Ball at the same time) Results in both Players receiving ten points and NO Handicap to either side for the following round. Tie rounds also force the ball back to the middle of the arena regardless of previous advantage.
  - If a Game results in a score of 50-50, an Overall Tie, the game will then be decided by a Final                   Termination Round. This round is played as followed:
    - Both Players Start at the END of the court instead of being next to the ball.
    - First Player to grab the Ball earns a final 10 points to bring the score to 60-50.
    - If a Tie occurs in the Termination Round, both Players must play until there is a Winner.


Thoughts:

Originally, I didn't think I could make an applicable game with just a ball with no kicking or throwing. But, I learned that from a simple idea, you can come up with all sorts of options.

I just combined a few things that I knew I liked. I like to run on my free time so I thought that this game would be well suited for people who like to get in exercise in daily. I also decided that it should be competitive game because I've always liked how competition seemed to get me focused; how it helped make me lose myself in the game. I think the combination of exercise and competition as my goals ultimately helped me make a game in which, I believe, gives you the sensation of not realizing you are actually exercising. With that, I came up with a game called Sprint Ball.

My first idea I had with Sprint Ball revolved around possibly hiding it. Generally, everyone who plays games requiring a ball desires to possess it one way or another. I first thought of making the ball like a treasure. But, eventually I determined that I didn't want to make a hide and seek game at the moment because this was going to be my first game. Ultimately, I decided that I'd go really simple. 

So I just thought of having two people running really fast at the same object. The idea of running after the ball while simultaneously seeing your opponent do the same thing made the game more competitive to me. I was not too sure how applicable this game would be in real life but I liked how it sounded in my mind.

Lastly, During my thinking process, what I kept asking myself was how do I give the ball significance? In all the games I could think of, the ball has some sort of neutrality. I wanted the ball to be more than just neutral. For me, the ball needed to be positive but at the same time also be a curse. I really wanted there to be some penalty or handicap for grabbing it. So I made winning a round result in the Two Feet Ball Space Handicap. And because I integrated this idea, I think that it added a whole lot more strategy to an otherwise very simple game.

Truly, even now, I still  don't know how this game really turned out. But, as of right now, I'm happy that it's something that is mine and something that I created. The first game I've ever made.

List #1

WORK due by the 24th of January, 2014.

Assigned
- Read Ch. 3
- Paragraph Summary on Blogger
- Wikimedia Commons Image
- Updating and Emailing

Personal
- Review and Complete
 1) Items originally assigned on the 10th of January
   a) Check Insight Documents
- Find Program to prep for "Prototype"

Exercise #2 - Collaborative Chess - My First Day of Class

January 17th, 2014* (Date Attended)

David Cox's Game 100 (12PM-3:50PM)

This day was my first time attending the Game 100 - Introduction to Game Worlds class. This is also my first time ever being in a class that focused purely on video games. To put it very lightly, I'm excited... 

Unfortunately, I missed the first day of class due to being uninformed. As soon as I was informed, I did everything in my power to be there the second day. Thankfully, Mr. Cox (The Instructor) was incredibly welcoming and flexible. He allowed multiple students, including myself, to add into the class. Due to his adjustments, I am now able to attend the most interesting, pivotal, and most importantly applicable class in my life.

I should have been following my passion like this a LONG time ago.

Back to the point. The first day of class was the most important day of public education I have ever encountered. I was incredibly excited. The classroom seemed electric with motivation and true passion. I saw other people who loved video games just as much, if not more, than I do. My first day in class, I realized, "I'm home. I'm doing exactly what I should be doing."

More specifically, I learned more about video games in a condensed form than I ever could've imagined. It gives me great relief to hear the instructor himself has actually worked in the field in which he teaches. Mr. Cox taught us multiple techniques and values in those three hours and fifty minutes he gave us. He taught us the basics on the history of video games. We learned about what makes a video game good or bad; What makes a video game for that matter. He also discussed not disrespecting your player. Which is important!

After his presentation was over, he taught us how to use programs. More specifically, he taught us how to use a program called Freemind. Freemind is an excellent program because it visually depicts on screen the processes that typically go through a creative writer/thinker's mind. It taught me that an idea sprouts from a single idea and branches outward. It is incredibly important to utilize this program because it helps keep track of the connections within a story. Naturally, many creative writers can keep track of this in their own mind. Unfortunately for me, I am not that smart or talented. This program will definitely help me and be used in the future. I have already downloaded this program and am optimistic of its potential future use.

Now I realize that Mr. Cox's intentions on teaching us the program was to give us the ability to prototype our eventual future game. After we finished our mindmaps, he obliged us to share our ideas to the class. Many people in the class had amazing ideas much different from mine. It made me remember how diverse and unique we all are. And afterwords, we were asked to collaborate in teams with others with similar visions.

Ultimately, I ended up in a group with 5 people, really stretching the limits of groups. On average, most groups in class were of 2-3 persons. Oops. Consequentially, we learned a hard lesson that day.

We were assigned a group project called, "Collaborative Chess." The purpose of this project was to come up with a unique idea for a custom game of chess. The pieces could retain any properties we desired and we could place the pieces however we liked. It was an exciting prospect. I had never been more involved in any project in school like this. In our team was some very talented individuals. One team member suggested making the game's bjective be centered around getting all colored pieces to opposing sides. Another suggested creating obstacles in the center. We had really solid ideas I felt. But one very apparent problem came up. Time.

Time became a very serious factor because of our large group. We as a group made the mistake of using too much time discussing rather than doing. Ultimately, what ended up happening was that we were given five minutes to finish up. In these five minutes, we had to crunch time and quickly and efficiently choose a game type. We had to discard all previous ideas and take whatever idea suited best for the time we were given. We all felt if we had more time, the game would have come out better. However, we did our try our best for the time we had.

I learned many lessons from that mini project. If I ever want to work for a video game company, I must learn these key facts. Is that time is very much a factor. Crunch time in video games is a very real and prevalent thing that I must prepare for regularly; but hopefully can avoid. Another is that sometimes, too many ideas can be, not necessarily bad, but be an obstruction to true progress. Like they say, "too much thought but no action."

In summary, I learned a great deal about video games and lessons abut life itself. I am incredibly excited for this class. I feel that this is the first step. I'm finally following my heart with this class. And I feel like you can never go wrong living like that. I'm hoping that this class is the beginning of something beautiful for me.