Game Dev Blog Of Blake Leftwich

More art is coming in. Looking great so far!

2011-08-28T12:15:00.000-04:00

Smoothing animation

2011-08-20T11:27:00.001-04:00

Smoothing animation today for the new art style. It's looking good so far.

Challenge system in place. Getting three stars on each level unlocks a special challenge.

2011-08-01T19:03:00.000-04:00

Awards and save system complete.

2011-07-31T01:08:00.001-04:00

Player Feedback & User Interface: Don't Overdo It. Don't Underthink It

2011-07-28T11:03:00.009-04:00

I've spent many sleepless nights trying to figure out the most efficient way to configure UI (User Interface) and present information to the player. The process being an iterative one means that its never too late to make a game just a wee bit better. A lot of time can be wasted on this and that's a problem.

Another issue? Underthinkin' the importance of UI. That can blow the whole game.

If a problem is visual (like it is with UI design):

Don't even turn on the computer. Work on it with good ole pencil and paper.
Make a list of information the player absolutely needs to know and when they need to know it. This helps you begin to understand what the player should pay attention to, what screen it should appear on and how it affects the flow and understanding of the game.
Then sort it in order of importance-very important for UI. This helps you decide how easy it should be to find this information. Can it be buried in a menu? (i.e. credits) Should it be in the corner for occasional reference? (i.e. number of lives left) Should it be only a glance away or even directly in the players line of sight? (i.e Mario shrinks when he's hit). I personally believe the reason that scoring as a motivation for play has nearly disappeared (except for casual/arcade games) is that the score has traditionally been all the way up in the corner where nobody can see it. If you want a player to care about or understand something it should be visible at all times and call attention to itself.
Simplify to avoid clutter and repeat these steps.

Solution found.

2011-07-26T12:41:00.002-04:00

One particularly ingenious playing piece was tough to code because it went outside the scope of the game engine. It works now though and considering the time and effort I hope it ends up staying in the game!

The bottom line is that you have to be willing to cut your favorite idea or the thing you worked hardest on to make the game the best it can be. We will see what testers think of it.

Art assets should be coming in soon! Can't wait!

Visual Style

2011-07-22T17:38:00.003-04:00

After meeting with the artist we have decided on an art style. Soon assets will be coming in. I will share at least a few items. Also continuing with new tile gameplay possibilities.

UI changes

2011-07-13T15:18:00.003-04:00

I have changed the UI of the game to a simpler scheme. The player will have a menu available to them at all times in the form of a bar at the bottom of the screen. This keeps with my goal of having all options available in one step at anytime (without having to go into a menu) but consolidates the options to one area in order to avoid user confusion. The top of the screen will now only hold scoring information (current level, high score and current score).

New tile level design

2011-07-10T16:53:00.002-04:00

With two new types of tile in I am designing levels with a smooth learning curve for each type.

Added 2 new tile types.

2011-07-09T15:21:00.000-04:00

Added two new types of tile gameplay mechanisms for testing. I think at least one will stay in the final game.

Testing and Levels

2011-07-07T20:09:00.000-04:00

Added 20 more puzzles, redistributed them for a smoother difficulty curve, tweaked scoring and reviewed testing feedback.

The testers are hitting puzzles pretty early that stump them. I have created more easy and intermediate puzzles and pushed the difficult puzzles into later levels.

Let's call it NIXL

2011-07-07T10:22:00.000-04:00

The title of this project was originally NIXL but that name is most likely out. We'll refer to it as nixl for the sake of brevity..

I am designing and testing levels. There are little techniques you learn with time that can be applied to all puzzles but uninitiated testers seem to take many moves to solve puzzles that can be solved in 2 or 3 moves. Tweaking difficulty. It's tempting to jump in and start sliding tiles but if you think before you slide you get a much higher score.

The scoring is based on number of moves. The fewer moves it takes to solve the puzzle the higher the score.

Title Pending iOS Game In Development

2011-07-05T13:03:00.000-04:00

I have a new puzzle game coming soon! I will post updates as they happen. I have a version running but the rules are still being tweaked. It looks like it will feature at least 30 levels comprised of 1 to 7 puzzles per level.

How To Create and Publish a Podcast: Free

2010-10-22T16:57:00.025-04:00

Hi, I’m Matthew. I co-host, produce and edit the video game podcast “Under The Radar (Games)”. Each week we record, edit, upload and then publish our podcast to iTunes, as well as many other podcast directory services; and we don’t spend a dime on any of it. Here’s how…

Recording:

The first step to any podcast is recording your content. Considering how hard it is to get everybody in the same room once a week, we use SKYPE along with MP3 Skype Recorder to record our podcast. Simply download Skype, create an account and tell your co-host(s) to do the same. Then grab MP3 Skype Recorder and let it run in the background alongside Skype (make sure that when Skype asks you if you want to allow MP3 Skype Recorder, you select yes). MP3 Skype Recorder will record your calls and export them to MP3 files.

Editing:

Let’s say there was a big, boring pause in the middle of your recorded discussion, not very entertaining for the listener, right? That’s why we edit our podcast. First, download and install the free sound editor Audacity. Once you’re finished installing, open the program and drag your MP3 file onto it. If you’re new to this kind of audio-editing, it may take some getting used to. I’m sure there are plenty of tutorials out there that’ll explain the basics better than I can. Once you know what you’re doing, you’ll be able to cut-out sections of the audio that you don’t like, fade in and out, and maybe even add some music to spice things up. Once I’m finished editing I export to a .wav file so I can then run it through a program called The Levelator which will compress the audio so that no one is too loud or too quiet to hear. I export to .wav because The Levelator requires a .wav file rather than an MP3 to work its magic. Once The Levelator is finished with the file I bring it back into Audacity so I can export it as an .MP3 which is significantly smaller than a .WAV.

Hosting:

It took me a long time to find a place that would host our podcasts for free, allow unlimited bandwidth, and still offer the “direct-links” that are needed later on when creating our RSS Feed. Eventually I stumbled across The Internet Archive; they’re a non-profit service and a godsend for podcasters. Create an account, and then use the upload button to upload your podcast. While it’s uploading, you’ll be asked to input some simple information (i.e. title, description, tags, etc.). Once the upload has finished and you’ve completed all the required forms, select “Share My File”. You will then be brought to a page with the link “Your Page”, select it. Now right-click the link under “VBR MP3” and select “Copy Link Location”. The “direct-link” to our audio file/podcast is now copied to our clipboard and we can paste it wherever we’d like. This is the point at which I email the direct-link to my co-host Blake, who then creates/updates the RSS Feed. I’ll let Blake explain why we need an RSS feed, what program he uses to make the feed, and also how to get your podcast on iTunes.

Part II

Hello, I’m Blake, host and co-creator of “Under The Radar (Games)”. When I approached Matt with the idea for the podcast, there were two things that I was absolutely adamant about. First, it has to be more fun than work and second, it can’t cost us a cent! It’s definitely a blast to make the show thanks to our format and subject matter and the cost… well, we got pretty close to nothing! I am responsible for getting the podcast online once Matt edits it. Here’s how I do it for almost nuttin’…

RSS:

RSS is a format for publishing frequently updated content online. It’s what iTunes and most everyone else uses to distribute podcasts. An RSS feed is simply a text document in XML format that you will upload to an online host so iTunes and the rest of the world can use it to find your podcasts.

The good news is that you don’t have to know an RSS or XML from a hole in the ground. We use poderator.com, a free service that creates the podcast xml file for you. At poderator.com you can register for a free account and set up a “new show” in minutes.

Details:

Once you register an account at poderator you will be directed to the “Add a New Show” page where you will be prompted for information necessary to create your feed. This process is pretty self explanatory but I will try to elaborate on some things that could be confusing. In the “Add a New Show” page the required fields are:

Podcast Title
Your Website URL
This can be any website address. If you do not have a dedicated website address what about using your Facebook or Twitter page? UTR uses twitter.com/tweettheradar (our twitter page). If a user clicks on the link to our website in iTunes, it will go to this address.
Podcast Description
Optional Image URL
This is the location of the picture you want users to see when viewing your feed. It is usually a logo for your podcast. The max size is 144x144 pixels and the image must be in gif, jpg or png format. We use .png for transparencies and high quality. You can create an account and upload images for free at photobucket.com. After uploading you will be given a url to the image.
Podcast Author
Who makes this podcast? We plug our podcast email address here (mailtheradar@gmail.com). It will be visible in iTunes.
Podcast Image URL
A larger image that iTunes uses, we use the same podcast logo for both so all users no matter where they get the podcast see the same image for consistency. This image can be up to 300x300 pixels.
Podcast Summary
Podcast Subtitle
Podcast Search Keywords
Very important in helping iTunes users find your podcast. Make sure you include the title and subject of your podcast at least. We have tags like “3DS, playstation, xbox, 360, wii, kinect, games, video”
iTunes Category
Is your podcast explicit?

Press the Save and Continue button to add your first show. You can add more shows in the future by logging in and pressing the Add a New Episode button at the top. In the “Add a New Episode” there are more required fields:

Episode Title
Episode Description
Episode File URL
You will get this after uploading your mp3 at archive.org
File Type
MP3-Audio most likely.
Episode File Size
Just look at your mp3’s properties for this.
Episode Summary
255 characters max. Don’t go over or poderator will start wigging out.
Episode Search Keywords
Same as above but keywords should be for this specific episode.
Episode Duration
You should be able to find this in whatever you use to listen to or edit your podcast.
Is this episode explicit?

Press the Save Details and Continue Button here to move on. You will now see you list of podcasts on the left and buttons beside their titles for listening to, editing or deleting. Click the Publish your XML Feed button and on the next page there is a small link at the bottom of the text that reads “download your xml feed”. Click it and you have your very own RSS feed!

Your RSS Feed:

The final step is to rename this file to something more appetizing than Poderator.xml (the default name) and upload it! We call ours “utr.xml”.

Use Filezilla or another free FTP application to upload the xml file to your host. Your host website will have instructions for uploading through FTP. Once uploaded, when you navigate to it in your browser it will look like this: http://salutegames.com/utr.xml

Here's the catch. Unfortunately, I have yet to find a way to host the xml file for free. I'll leave it up to you to solve that problem but as for the UTR podcast: I have a site that I maintain called salutegames.com that we use to host the xml file. If you have a website anywhere just use it to host this xml file because 1) it is a tiny file and 2) archive.org pays for the bandwidth of downloading each mp3 that the xml file references. Your bandwidth will not be affected when users download your podcasts!

Publishing:

Remember there are many services out there other than iTunes that will distribute you podcast for free. Do some research! The more ways to get it, the more listeners you’ll have. Registering a new podcast on iTunes is free but can take a few days to get approved and start working. Here’s how to in a nutshell…

Test you feed in iTunes first!

Launch iTunes
Click Advanced>Subscribe to Podcast.
Enter your feed url (something like http://www.yoursite.com/yourpodcast.xml)
If you can subscribe, download and listen with no problems your xml is working.

Now submit to iTunes!

Start iTunes
Visit the following link:
https://phobos.apple.com/WebObjects/MZFinance.woa/wa/publishPodcast
This will open the iTunes podcast submission page in iTunes.
Follow the instructions.

That’s it! You have your very own podcast for next to nothing! Please listen to the "Under The Radar (Games)" podcast or support us by donating here or just saying hello at facebook.com/undertheradargames.

SGD 111 Intro to Simulation and Game Development Schedule

2010-08-22T20:21:00.000-04:00

Click on the title of this post to download the schedule for the SCC Fall 2010 SGD 111 Simulation and Game Development course.

SGD 111 Intro to Simulation and Game Development Syllabus

2010-08-22T20:14:00.000-04:00

Click the title to this post to download the SCC Fall 2010 syllabus for Intro to Simulation and Game Development.

XNA Tutorial: Scaling Sprites and Maintaining Aspect Ratio

2010-07-31T11:49:00.007-04:00

Download the XNA Tutorial: Scale Sprites doc and owl.png in a zip by clicking the title of this post!

SCALE SPRITES
Maintaining the aspect ratio for any size screen and scaling.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)ScaleSprites” using camel casing. ex. leftwichBlakeScaleSprites.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “ScaleSprites”.

Click OK

Step 2
Import an image: Right click Content in the Solution Explorer and Add>Existing Item> (find the owl.png file). This image is used courtesy of Turbomilk.com.

Step 3
Class-level variables: In the ScaleSprites class under SpriteBatch spriteBatch; write the following code:

//sprite stuff
Texture2D owl;
Rectangle owlRect;

//display settings
float displayWidth;
float displayHeight;
float owlWidthFactor;

Under sprite stuff we are simply creating the necessary Texture and Rectangle variable to draw and scale our sprite on the screen. Under display settings we are creating variables for storing scaling values.

Step 4
Load your content: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

owl = Content.Load<Texture2D>("owl");
scaleSprites();

Here we are loading the owl image and calling a method that will scale the sprites. You will understand this method in step 6.

Step 5
Initialize: In the Initialize method under // TODO: Add your initialization logic here write the following code:

displayHeight = GraphicsDevice.Viewport.Height;displayWidth = GraphicsDevice.Viewport.Width;

owlWidthFactor = 0.1f;

Step 6
Create our sprite scaling method: Under the Draw method after write the following code:

void scaleSprites()
{
   owlRect.Width = (int)((displayWidth * owlWidthFactor) + 0.5f);
   float aspectRatio = (float)owl.Width / owl.Height;
   owlRect.Height = (int)((owlRect.Width / aspectRatio) + 0.5f);
}

This method sets the width,height and aspect ratio of the owl image based on the size of the screen and the owlWidthFactor. Because of this code the owl will be the correct size and shape on any size screen.
Note: This method can be placed anywhere except inside one of the XNA methods that are automatically created for you. Putting it under the Draw method (at the bottom) is simply my personal preference.

Step 7
Draw our properly scaled owl: In the Draw method under // TODO: Add your drawing code here write the following code:

spriteBatch.Begin();
spriteBatch.Draw(owl, owlRect, Color.White);
spriteBatch.End();

This code starts and ends the drawing process. The parameters in the Draw method (owl, owlRect, Color.White)define the texture (picture), rectangle(shape, size and location of the picture) and it’s color filter (white is default) respectively.

Now tinker with the owlWidthFactor value in the Initialize method to see how the scaling and aspect ratio is maintained regardless of the image’s or screen’s size. 0.1 represents the default size. Try going larger and smaller, see what happens.

Save your file. You’re finished!

XNA Tutorial: Life Meter

2010-07-20T13:18:00.003-04:00

Download the XNA Tutorial: Life Meter doc and meter.jpg in a zip by clicking the title of this post!

LIFE METER
A quick life meter tutorial

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)LifeMeter” using camel casing. ex. leftwichBlakeLifeMeter.

In the Solution Explorer right-click the class (probably named something like Game1.cs) and select rename. Rename the class “LifeMeter”.

Click OK

Step 2
Import a life bar image: Right click Content in the Solution Explorer and Add>Existing Item> (find the meter.jpg file).

Step 3
Class-level variables: In the ArrayTime class under SpriteBatch spriteBatch; write the following code:

Texture2D lifeMeter;
Rectangle lifeRect;
int life = 200;//full meter

Step 4
Load your content: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

lifeMeter = Content.Load<Texture2D>("meter");

Step 5
Initialize method: In the Initialize method under // TODO: Add your initialization logic here write the following code:

//set the initial x,y,height and width of the lifeRect
lifeRect = new Rectangle(560, 30, 200, 20);

Step 6
Update method: In the Update method under // TODO: Add your update logic here write the following code:

while (lifeRect.Width > life)
{
lifeRect.Width -= 1;
}

The variable "life" controls the length of the bar. 200 is a full bar. When enemies collide with your ship you can use an equation like life -= 10; This will cause the meter to get shorter by 10 pixels. The width changes every frame if it is longer than “life” should be.

Step 7
Draw the life meter: In the Draw method under // TODO: Add your drawing code here write the following code:

spriteBatch.Begin();
spriteBatch.Draw(lifeMeter, lifeRect, Color.White);
spriteBatch.End();

Save your file. You’re finished!

Step 8
It is up to you how you want to reduce the “life” variable through code. One quick way to test it is to replace this.Exit();in the update method with life -= 1; This will allow you to press the back button on the controller to reduce life. Remember to put this.Exit(); back in when you’re finished!

Save your file. You’re done!

Ep. 42 Deadly Premonition: Under The Radar Games Podcast

2010-07-15T09:42:00.002-04:00

Ep. 42 Deadly Premonition (07/14/2010 09:09)
Play Now!

Let's get deadly with Deadly Premonition for Xbox 360. We're big horror fans and really pulling for this one so tune in and see if it lives up to our expectations! What makes you buy a game? That's our question of the week as we are joined by THE James Tillman. Is there a game you would like to know more about that the other guys aren't covering? Send suggestions, opinions and feedback to mailtheradar@gmail.com or follow us on twitter.com/tweettheradar. Thanks for your support!

Under The Radar Games Podcast 40: Metro 2033

2010-07-05T09:19:00.001-04:00

Ep. 40 Metro 2033
Tuesday, June 29, 2010 6:10 PM

Metro 2033 for Xbox 360 gets things sizzling this week for our new season! Steve Smith and Jeff Rivera emerge from a stupid dimension, cranium crushing conversation ensues. Is there a game you would like to know more about that the other guys aren't covering? Send suggestions, opinions and feedback to mailtheradar@gmail.com or follow us on twitter.com/tweettheradar. Thanks for your support!

New E3 UTR podcast Ep. 39 Demon's Souls!

2010-06-16T15:35:00.004-04:00

Ep. 39 Demon's Souls
Posted: Wed, 16 Jun 2010 12:09:10 GMT

Play Now

1 hour+ E3 special! It's almost Thursday which means it's time for another game (right in the middle of E3 season)! Howz about Demon's Souls for the PS3! I wonder what we think of it? Also, it's time to talk E3 with Jeff Rivera of stupidgamer.com. Is there a game you would like to know more about that the other guys aren't covering? Send suggestions, opinions and feedback to mailtheradar@gmail.com or follow us on twitter.com/tweettheradar. Thanks for your support!

XNA Tutorial 8: ArrayTime

2010-06-12T12:26:00.004-04:00

Download the XNA Tutorial 8: Array Time doc and beep sound in a zip by clicking the title of this post!

ARRAYTIME
Timers, arrays and a little error trapping too.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)ArrayTime” using camel casing. ex. leftwichBlakeArrayTime. Please be sure to put your full name in the solution name so I can grade it.

Make sure you locate this file in your folder on the network.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “ArrayTime”.

Click OK

Step 2
Import a few things: Right click Content in the Solution Explorer and Add>Existing Item> (find the beep.wav file)

Import a font: Right click Content in the Solution Explorer and Add>New Item> Sprite Font

Step 3
Class-level variables: In the ArrayTime class under SpriteBatch spriteBatch; write the following code:

SpriteFont font;

SoundEffect beepSound;

GamePadState pad1;

GamePadState oldPad1;

int timer;

int winningValue;

//create a integer array with 4 elements

int[] scores = new int[4];

string winnerName;

//create a string array and initialize with 
//specific elements;

string[] names = new string[] 

{

    "Gamepad 1 A","Gamepad 1 B","Gamepad 1 X","Gamepad 1 Y" 

};

We are creating two arrays here using two different techniques. The line:
int[] scores = new int[4]; creates an array that hold 4 integer values.

The next array declaration:

string[] names = new string[] 

{

    "Gamepad 1 A","Gamepad 1 B","Gamepad 1 X","Gamepad 1 Y" 

};

creates an array that can hold 4 string values and goes the extra step of defining the string elements. Note the position of the semicolon, this entire statement could be put on one line but was broken up for readability. It is a single statement.

Step 4
Load your content: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

beepSound = Content.Load<SoundEffect>("beep");
font = Content.Load<SpriteFont>("SpriteFont1");

Step 5
Update method: In the Update method under // TODO: Add your update logic here write the following code:

pad1 = GamePad.GetState(PlayerIndex.One);
//when start is pressed
if (pad1.Buttons.Start == ButtonState.Pressed)
{
      //reset scores to -1
      for (int i = 0; i < 4; i++)
      {
          scores[i] = -1;
      }
      //reset winnerName to ""
      winnerName = "";
      //reset timer to -120
      timer = -120;
}

//increment timer every frame
timer++;

//once timer reaches 0 (2 seconds after start)
if (timer == 0)
{
    beepSound.Play();
}

//if button is pressed once and score is
//at initial value
if (oldPad1.Buttons.A == ButtonState.Released &&
    pad1.Buttons.A == ButtonState.Pressed && scores[0] == -1)
{
    scores[0] = timer;
}
if (oldPad1.Buttons.B == ButtonState.Released &&
    pad1.Buttons.B == ButtonState.Pressed && scores[1] == -1)
{
    scores[1] = timer;
}
if (oldPad1.Buttons.X == ButtonState.Released &&
    pad1.Buttons.X == ButtonState.Pressed && scores[2] == -1)
{
    scores[2] = timer;
}
if (oldPad1.Buttons.Y == ButtonState.Released &&
    pad1.Buttons.Y == ButtonState.Pressed && scores[3] == -1)
{
    scores[3] = timer;
}

//if time is up (at 2 seconds after alarm)
if (timer == 120)
{
    //reset winning value
    winningValue = 120;
    //declare innerSubscript and initialize at zero
    int winnerSubscript = 0;
    //cycle through all 4 array cells
    for (int i = 0; i < 4; i++)
    {
        //check for lowest score (must be 0 or higher)
        if (scores[i] < winningValue && scores[i] > -1)
        {
             //if above conditions met this is the
             //lowest score
             winningValue = scores[i];
             //this is also correct cell location
             //for winnerName string
             winnerSubscript = i;
        }
    }

    //if winningValue >= then nobody pressed a button
    if (winningValue >= 120)
    {
        //therefore no winner
        winnerName = "**NO WINNER**";
    }
    else
    {
        //otherwise set correct winnerName
        //string and add the score on
        //the end for fun
        winnerName = names[winnerSubscript] + " wins with " + winningValue;
    }
}

//update last pad state
oldPad1 = pad1;

There is a lot of code here but do not let it intimidate you. Most of it reuses the same basics. The first if condition block resets the game values if the player press start. Notice that this is where we set the timer to its starting value and the score array elements to equal -1 with scores[i] = -1;.

We set the initial score values to -1 because if it was set to 0 it would qualify as a valid score. If that happened and the player didn’t press a button-they would have a score of 0, a perfect score (cheater)!

After that code we see: timer++; This is how we increase our timer every frame. Since this number is constantly changing we can use it to control timed functions like the 2 second pause before the alarm and the 2 second pause before the winner’s text is displayed.

After our button code you will see a conditional statement that tests for the timer to hit 120. This is when the game will check for the winner and display the winner message. Look at the following code:

for (int i = 0; i < 4; i++)
    {
        //check for lowest score
        //(must be 0 or higher)
        if (scores[i] < winningValue && scores[i] > -1)
        {
             //if above conditions met
             //this is the lowest score
             winningValue = scores[i];
             //this is also correct cell
             //location for winnerName string
             winnerSubscript = i;
        }
    }

This code uses a loop to check every score to see if it is the lowest number. The code also assigns the value of i to variable winnerScript . This ensures that the winning score and correct winning message string are the same.

Arrays are one of those programming conventions that takes a while to grasp and to understand its worth. Please email me or ask questions in person if you have them.

Step 6
Draw some text to show the winner: In the Draw method under // TODO: Add your drawing code here write the following code:

//if winnerName does not have a value yet
//do not execute the following code
if (winnerName != null)
{
    //set a location to display text
    Vector2 textVector = new Vector2(200, 100);
    //draw text
    spriteBatch.Begin();
    spriteBatch.DrawString(font, winnerName, textVector,        Color.Black);
    spriteBatch.End();
}

The most noteworthy code here is the error trapping technique of checking for null values. If we draw the text before winnerName is defined the program will crash. This will happen by default because the Draw method runs every frame (before the value of winnerName is defined).

By nesting our draw code inside a condition, we will now only draw if winnerName is defined.

null is the default value of any non-numerical uninitialized data type (numerical values are 0 by default).

Save your file. You’re finished!

XNA Tutorial: Q&D Scrolling Background

2010-06-10T09:59:00.006-04:00

Download XNA Tutorial: Q&D Scrolling Background doc and the tutorial image file in a zip by clicking on the title of this post.

Q&D SCROLLING BACKGROUND
A very simple horizontal scrolling background.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)ScrollingBackground” using camel casing. ex. leftwichBlakeScrollingBackground.

This is not a graded assignment.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “ScrollingBackground”.

Click OK

Step 2
Import the graphics: Right-click Content in the Solution Explorer. Add>Existing Item> (Find stars.png).

Step 3
Class-level variables: In the Game1 class under SpriteBatch spriteBatch; write the following code:

Texture2D sceneTexture;
Rectangle sceneRect1;
Rectangle sceneRect2;

int scene1X;
int scene2X;

int scrollSpeed;

Step 4
Load the content: In the Load Content method under // TODO: use this.Content to load your game content here write the following code:

sceneTexture = this.Content.Load<Texture2D>("stars");

Step 5
Initialize: In the Initialize method under // TODO: Add your initialization logic here write the following code:

scrollSpeed = 2;
scene1X = 0;
sceneRect1 = new Rectangle(scene1X, 0, 800, 600);
scene2X = scene1X + sceneRect1.Width;
sceneRect2 = new Rectangle(scene2X, 0, 800, 600);

Step 6
Draw: In the Draw method under // TODO: Add your drawing code here write the following code:

spriteBatch.Begin();
spriteBatch.Draw(sceneTexture, sceneRect1, Color.White);
spriteBatch.Draw(sceneTexture, sceneRect2, Color.White);
spriteBatch.End();

Press F5 to test your game. Make sure the stars image is appearing on screen before continuing.

Step 7
Update method: In the Update method under // TODO: Add your update logic here write the following code:

scene1X -= scrollSpeed;
scene2X -= scrollSpeed;
sceneRect1 = new Rectangle(scene1X, 0, 800, 600);
sceneRect2 = new Rectangle(scene2X, 0, 800, 600);

if (sceneRect1.X + sceneRect1.Width == 0)
{
scene1X = GraphicsDevice.Viewport.Width;
}
if (sceneRect2.X + sceneRect2.Width == 0)
{
scene2X = GraphicsDevice.Viewport.Width;
}

Press F5 to test your game. The stars should now scroll seamlessly. Important!: Using this simple method requires that the scrollSpeed value is evenly divisible by 800 (or the width of your screen and background image).

Save your file. You’re done!

XNA Tutorial: Movement

2010-06-07T17:16:00.003-04:00

Download the XNA Tutorial: Movement doc and image by clicking on the title of this post.

MOVEMENT
A few techniques for moving the player around the screen.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)Movement” using camel casing. ex. leftwichBlakeMovement

This tutorial will not be graded. It has been posted to give you more options when creating your games.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “Movement”.

Click OK

Step 2
Import your images: Right click Content in the Solution Explorer and Add>Existing Item> (find the astronaut.png file).

Step 3
Class-level variables: In the Movement class under SpriteBatch spriteBatch; write the following code:

Texture2D astronautTexture;

Rectangle astronautRect;

//controls the astronaut's X and Y position

int astronautX;

int astronautY;

//how many pixels the astronaut 
//moves per button press

int pixelSkip;

Step 4
Load your image: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

astronautTexture = this.Content.Load<Texture2D>("astronaut");

Step 5
Initialize your variables: In the Initialize method under // TODO: Add your initialization logic here write the following code:

//initialize man's X and Y position
astronautX = 380
astronautY = 240;
//now plug man's X and Y position
//into the Rectangle info
astronautRect = new Rectangle(astronautX, astronautY, 46, 58);
//initialize the pixels to
//move per button press
pixelSkip = 2;

Note: The last two values in the Rectangle definition (46, 58) are the width and height of the image respectively.

Step 6
Draw: In the Draw method under // TODO: Add your drawing code here write the following code:

spriteBatch.Begin();
spriteBatch.Draw(astronautTexture, astronautRect, Color.White);
spriteBatch.End();

Press F5 or the green play icon to debug and test your program. The astronaut should appear on the screen.

Step 7
Update method: In the Update method under // TODO: Add your update logic here write the following code:

GamePadState pad1 = GamePad.GetState(PlayerIndex.One);
if (pad1.DPad.Left == ButtonState.Pressed)
{
    astronautX -= pixelSkip;
}
if (pad1.DPad.Right == ButtonState.Pressed)
{
    astronautX += pixelSkip;
}
if (pad1.DPad.Up == ButtonState.Pressed)
{
    astronautY -= pixelSkip;
}
if (pad1.DPad.Down == ButtonState.Pressed)
{
    astronautY += pixelSkip;
}

//now plug man's X and Y new
//position into the Rectangle info
astronautRect = new Rectangle(astronautX, astronautY, 46, 58);

Press F5 or the green play icon to debug and test your program. The astronaut should now move with the dpad. You can tweak the pixelSkip variable in the initialize method to change the rate of movement. If you are happy with this control style you are finished! If you would like to try some other control styles, continue to the next step.

Part II
Adding inertia.

Step 8
Class-level variables: In the Movement class under SpriteBatch spriteBatch; write the following code:

Texture2D astronautTexture;
Rectangle astronautRect;
//controls the astronaut's
//X and Y position
int astronautX;
int astronautY;
//how many pixels the astronaut
//moves per button press
float pixelSkip;
//controls the speed of the
//astronaut in both directions
float ySpeed;
float xSpeed;

One very important change is that the pixelSkip has been changed to a float variable for more precise control.

Step 9
Initialize your Rectangle: In the Initialize method under // TODO: Add your initialization logic here write the following code:

//initialize man's X and Y position
astronautX = 380;
astronautY = 240;
//now plug man's X and Y position
//into the Rectangle info
astronautRect = new Rectangle(astronautX, astronautY, 46, 58);
//initialize the pixels to
//move per button press
pixelSkip = 0.2f;

Note: The last two values in the Rectangle definition (46, 58) are the width and height of the image respectively. The “f” at the end of the pixelSkip initialization is required for float variables.

Step 10
Update method: In the Update method under // TODO: Add your update logic here write the following code:

GamePadState pad1 = GamePad.GetState(PlayerIndex.One);
if (pad1.DPad.Left == ButtonState.Pressed)
{
    xSpeed -= pixelSkip;
}
if (pad1.DPad.Right == ButtonState.Pressed)
{
    xSpeed += pixelSkip;
}
if (pad1.DPad.Up == ButtonState.Pressed)
{
    ySpeed -= pixelSkip;
}
if (pad1.DPad.Down == ButtonState.Pressed)
{
    ySpeed += pixelSkip;
}

astronautRect.X += (int)xSpeed;
astronautRect.Y += (int)ySpeed;

Press F5 or the green play icon to debug and test your program. The astronaut should now move with the dpad. She moves with inertia and it takes a little longer to get started, stop and change direction.
Note: The code: astronautRect.X += (int)xSpeed; converts the xSpeed variable from a float into an int type (an int type is required in the Rectangle method).

If you are happy with this control style you are finished! If you would like to try some other control styles, continue to the next step.

Part III
Adding friction to slow the player down once moving.

Step 11
Class-level variables: In the Movement class under SpriteBatch spriteBatch; write the following code:

Texture2D astronautTexture;
Rectangle astronautRect;
//controls the astronaut's X and Y position
int astronautX;
int astronautY;
//how many pixels the astronaut
//moves per button press
float pixelSkip;
//controls the speed of the
//astronaut in both directions
float ySpeed;
float xSpeed;
//controls friction
float friction;

The only thing that changed from our previous code is that we added a friction variable.

Step 12
Initialize your Rectangle: In the Initialize method under // TODO: Add your initialization logic here write the following code:

//initialize man's X and Y position
astronautX = 380;
astronautY = 240;
//now plug man's X and Y position
//into the Rectangle info
astronautRect = new Rectangle(astronautX, astronautY, 46, 58);
//initialize the pixels to
//move per button press
pixelSkip = 0.2f;
//friction initialization
friction = 0.96f;

All we did was initialize our friction value.

Step 13
Update method: In the Update method under // TODO: Add your update logic here write the following code:

GamePadState pad1 = GamePad.GetState(PlayerIndex.One);
if (pad1.DPad.Left == ButtonState.Pressed)
{
    xSpeed -= pixelSkip;
}
if (pad1.DPad.Right == ButtonState.Pressed)
{
    xSpeed += pixelSkip;
}
if (pad1.DPad.Up == ButtonState.Pressed)
{
    ySpeed -= pixelSkip;
}
if (pad1.DPad.Down == ButtonState.Pressed)
{
    ySpeed += pixelSkip;
}

xSpeed *= friction;
ySpeed *= friction;

astronautRect.X += (int)xSpeed;
astronautRect.Y += (int)ySpeed;

Press F5 or the green play icon to debug and test your program. The astronaut should now move with the dpad. Now the astronaut slowly comes to a stop. Tweak the friction value in the initialize method for different results.

Tutorial complete!

XNA Exam 1: Game Project Rubric

2010-06-03T14:15:00.002-04:00

Download the XNA Exam 1: Game Project Rubric by clicking the title of this post.

EXAM 1 GAME PROJECT
Due at the beginning of class on Thursday June 17th

Rubric

•    5%
Use the XNA structure as it is intended, put draw code in the Draw method, initialize variables in the Initialize method and use the Update method for updating values, etc. (your gameplay code).

•    10%
Comment properly.

•    20%
Use input of either the keyboard or the controller. If you use the controller include vibration.

•    5%
Deploy the game to either the Xbox 360 or Windows, your choice. If the game does not run, you will receive a 0. The game must be displayed on the big screen. Make sure it works from the teacher’s station!

•    20%
Display an image on the screen at some point in the game.

•    20%
Use sound effects and music in the game.

•    20%
Display numeric text on the screen at some point (score, timer, etc.). The text must increase, decrease or change in some way at some point in the game. The text must not be the default size (you have to change the size from default).

You will not be graded on the graphics or sound quality, as long as the player can understand what is happening. You may use placeholder graphics (focus on the game code, not the visuals or sound).

You must give the presenter full attention with no interruptions. If you disrupt the class/presentation you may have points deducted from your exam grade.

Agenda
9:15     Record attendance
9:20     Take quiz on Chapters 5. Make sure you have read those chapters!
10:00     Game prep time. Make sure everything works!
10:15     Lunch/break
10:45     Game presentations start. First is Jak’s presentation
11:00     Questions/feedback
11:15     Zach’s presentantion
11:30     Questions/feedback
11:45     Rachel’s presentantion
12:00     Questions/feedback
12:15     Scottie’s presentantion
12:30     Questions/feedback

XNA Tutorial: Scrolling Background

2010-06-03T14:08:00.001-04:00

Download the XNA Tutorial: Scrolling Background, background image and ScrollingBackground class by clicking on the title of this post.

SCROLLING BACKGROUND
Vertical scrolling background

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)Scroller” using camel casing. ex. leftwichBlakeScroller.

This assignment will not be graded but is provided to give you more to work with for your game project.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “Scroller”.

Click OK

Step 2
Import the background image: Right click Content in the Solution Explorer and Add>Existing Item> (find stars.png ).

Step 3
Import the ScrollingBackground class: Right click the project file (usually named WindowsGame1 or something similar) in the Solution Explorer and Add>Existing Item> (Find the ScrollingBackground.cs file. You may have to set your file browser to show all types).

Next you must rename the namespace of the ScrollingBackground class to match the namespace of your Scroller class. Look for the line: namespace ScrollingBackgroundApp and change it to namespace leftwichBlakeScroller. Use your name instead as your did in step 1.

We are importing a class for scrolling backgrounds created by the XNA development community. Later you will learn how to create your own classes. This class may be changed to do things differently.

Step 4
Class-level variables: In the Scroller class under SpriteBatch spriteBatch; write the following code:

private ScrollingBackground myBackground;

Step 5
Load your sounds: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

myBackground = new ScrollingBackground();
Texture2D background = Content.Load("starfield");
myBackground.Load(GraphicsDevice, background);

Step 6
Update method: In the Update method under // TODO: Add your update logic here write the following code:

// The time since Update was called last.
float elapsed = (float)gameTime.ElapsedGameTime.TotalSeconds;
// Call the ScrollingBackground Update method
myBackground.Update(elapsed * 100);

Step 7
Draw method: In the Draw method under // TODO: Add your drawing code here write the following code

spriteBatch.Begin();
myBackground.Draw(spriteBatch);
spriteBatch.End();

Press F5 or the green play icon to debug and test your program. The background should slowly scroll vertically.

Your game code and ScrollingBackground.cs code can be adapted to scroll horizontally and at different speeds. Experiment!

Save your file. You’re finished!

XNA Tutorial: Collision

2010-06-02T10:30:00.004-04:00

Download the XNA Tutorial: Collision doc and image files zip by clicking on the title of this post.

COLLISION
Rectangle collision using the built in XNA Intersects method

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)Collision” using camel casing. ex. leftwichBlakeCollision.

This is not a graded assignment, it just to gives you more to work with when creating your games.

In the Solution Explorer right-click the class (probably named Game1.cs) and select rename. Rename the class “Collision”.

Click OK

Step 2
Import your images: Right click Content in the Solution Explorer and Add>Existing Item> (find the astronaut.png file and the ground.bmp file)

Step 3
Class-level variables: In the Collision class under SpriteBatch spriteBatch; write the following code:

Texture2D groundTexture;
Rectangle groundRect;
Texture2D astronautTexture;
Rectangle astronautRect;
//this will control the man's Y position
int astronautY;

Step 4
Load your images: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

groundTexture = this.Content.Load("ground");
astronautTexture = this.Content.Load("astronaut");

Step 5
Initialize your Rectangles: In the Initialize method under // TODO: Add your initialization logic here write the following code:

groundRect = new Rectangle(120, 400, 550, 108);
//initialize man's Y position
astronautY = 100;
//now plug man's Y position into the Rectangle info
astronautRect = new Rectangle(340, astronautY, 46, 58);

Step 6
Draw your images: In the Draw method under // TODO: Add your drawing code here write the following code:

spriteBatch.Begin();
spriteBatch.Draw(groundTexture, groundRect, Color.White);
spriteBatch.Draw(astronautTexture, astronautRect, Color.White);
spriteBatch.End();

Press F5 or the green play icon to debug and test your program. Just make sure your images are displaying on screen properly before moving on.

Step 7
Update method: In the Update method under // TODO: Add your update logic here write the following code:

//gravity
astronautY += 2;
//redefine the manRect with new value
astronautRect = new Rectangle(340, astronautY, 46, 58);
//collision condition
if (astronautRect.Intersects(groundRect))
{
//move up at the same rate man falls
astronautY -= 2;
}

The collision check occurs in the conditional statement above. Simply use this format: Rectangle1.Intersects(Rectangle2). Note that the Intersects method can only be used with Rectangles, not Textures.

Press F5 or the green play icon to debug and test your program. The astronaut should fall and stop when she hits the ground.

Save your file. You’re finished!

XNA Tutorial 7: Sound Stuff

2010-06-01T13:50:00.003-04:00

To download the XNA Tutorial 7: Sound Stuff tutorial and the sound files mentioned in the tutorial click the title of this post.

SOUND STUFF
Sounds and music.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)SoundStuff” using camel casing. ex. leftwichBlakeSoundStuff. Please be sure to put your full name in the solution name so I can grade it.

Make sure you locate this file in your folder on the network.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “SoundStuff”.

Click OK

Step 2
Import your sounds: Right click Content in the Solution Explorer and Add>Existing Item> (find the kick.wav file and the musicMP3.mp3 file)

Step 3
Class-level variables: In the SoundStuff class under SpriteBatch spriteBatch; write the following code:

SoundEffect kick; //kick sound effect
Song music; //music song
GamePadState pad1; // current pad state
GamePadState oldPad1; //last pad state

The SoundEffect type stores wav sounds, the Song type stores mp3s or wma.
We are reusing our old GamePadState technique to handle the button presses that control the sounds.

Step 4
Load your sounds: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

//load your kick drum SoundEffect
kick = Content.Load("kick");
//load your musicMP3 song
music = Content.Load("musicMP3");

Step 5
Update method: In the Update method under // TODO: Add your update logic here write the following code:

//store current gamepad state in pad1
pad1 = GamePad.GetState(PlayerIndex.One);
//make sure pad is connected
if (pad1.IsConnected)
   {
   //if last state released & current is pressed
   if (oldPad1.Buttons.A == ButtonState.Released && pad1.Buttons.A == ButtonState.Pressed)
      {
        kick.Play();//play kick
        }
//if last state released & current state is pressed
      if (oldPad1.Buttons.LeftShoulder == ButtonState.Released && pad1.Buttons.LeftShoulder == ButtonState.Pressed)
      {
       //if paused, resume, else play
       if (MediaPlayer.State == MediaState.Paused)
          {
           MediaPlayer.Resume();
          }
       else
          {
           MediaPlayer.Play(music);
          }
      }

    //if last state released & current is pressed
    if (oldPad1.Buttons.RightShoulder == ButtonState.Released && pad1.Buttons.RightShoulder == ButtonState.Pressed)
       {
       //if playing then pause
       if (MediaPlayer.State == MediaState.Playing)
           {
           MediaPlayer.Pause();
           }
       }

}

//set the last pad state to the current pad state
oldPad1 = pad1;

Press F5 or the green play icon to debug and test your program. The kick sound should play when you press the A button. The music will start when you press the left shoulder button. When you press right shoulder it will pause. When you press the left shoulder again the music will resume from where it was paused. Check closely to ensure that the music resumes properly.

The large update method above is comprised of what we have already learned. If you have any questions please contact me.

Save your file. You’re finished!

XNA Tutorial 6: Bash Buttons

2010-05-30T20:12:00.002-04:00

To download XNA Tutorial 6: Bash Buttons click on the title to this post.

BASH BUTTONS
Button input and scaling for multiple players.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)BashButtons” using camel casing. ex. leftwichBlakeBashButtons. Please be sure to put your full name in the solution name so I can grade it.

Make sure you locate this file in your folder on the network.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “BashButtons”.

Click OK

Step 2
Class-level variables: In the BashButtons class under SpriteBatch spriteBatch; write the following code:

//your display font

SpriteFont font;

//counts button presses

int count;

//tracks previous button state

GamePadState oldPad1;

Step 3
Load your font: In the LoadContent method under // TODO: use this.Content to load your game content here write the following code:

//load your font

font = Content.Load("spriteFont1");

Step 4
Update method: In the Update method under // TODO: Add your update logic here write the following code:

//declare pad1 as controller 1
GamePadState pad1 = GamePad.GetState(PlayerIndex.One);
//if start is pressed reset count to 0 and oldPad1
if (pad1.Buttons.Start == ButtonState.Pressed)
{
    count = 0;
    oldPad1 = pad1;
}
//if B is pressed and the last state was released then increase count by 1
if (oldPad1.Buttons.B == ButtonState.Released
    && pad1.Buttons.B == ButtonState.Pressed)
{
    count++;
}

oldPad1 = pad1;//oldPad1 now equals current pad state

Step 5
Draw: In the Draw method under // TODO: Add your drawing code here write the following code:

//convert count to a string called countString
string countString = count.ToString();
//declare a new Vector2 for DrawString method
Vector2 countVector = new Vector2(50, 400);

spriteBatch.Begin();
//DrawString method draws the font to the screen
spriteBatch.DrawString(font, countString, countVector, Color.Black);
spriteBatch.End();

Press F5 or the green play icon to debug and test your program. The value of zero should appear on the screen.

Step 6
Scale it!: Turn to page 109 in your textbook. Scale the game for 16 players by following the instructions on the following pages.

The final game should look like the screenshot on page 112. Once it does save your file. You’re finished!

XNA Tutorial: Deploying to an Xbox 360

2010-05-27T13:12:00.000-04:00

To download this tutorial click on the title of this post. I will update this post later.

DEPLOYING TO XBOX 360
Join creator’s club, download necessary software and test your programs on an Xbox 360.

Note: This process requires that you have a school email address (ending with .edu) to do it for free.
You can still do it otherwise but you will have to pay a minimum of $49.99

Go to https://www.dreamspark.com

Click on the XNA Game Studio 3.1 button in the middle of the screen.

If you are registered at dreamspark and logged in there will be two buttons at the bottom of the page. If you are not registered, click the register button and set up an account and log in.

Once you are signed in you can press the verify button to verify your eligibility. Follow the instructions on the verify page. It will prompt you to select a continent and country. After this more fields will appear for state and city. Once these are complete select your school from the list on the right side of the page and click continue.

The next pages asks for name, date of birth and you email address. Make sure you use your school email address on this page! Click verify.

Go to your school email address and you will have an email from dreamspark. In the email, click on the “activate” link and enter the code that was emailed to you.

Click the button.
Click the Download button.

Select XNA Game Studio again.

This time the page has a button at the bottom that reads “Get Key”. Click this button and copy the key that is generated.

Go to http://creators.xna.com

On this page select CREATORS>my profile and create a profile. Make sure you use your school email address on this page!
Once this is complete click HOME>membership. Scroll down to Step 4: Creator’s Club Premium Membership and click the words “Premium Membership” at the bottom of the box.

The next page lets you log in with you gamertag. If you do not have one you can make one here. Fill out this page and continue.
Fill out the billing information and continue.

On the next page you will be able to choose “Redeem Code” as a payment option. Do not enter a credit card here. You should not have to if you enter the code. Use the code that you copied earlier at the dreamspark website.

Enter your code and click “Redeem”.

You should now be able to log on to Xbox Live on your 360 and either sign in with your gamertag or “retrieve” your gamertag if you just created a new one online.
On your 360, go to Games Marketplace>All Games>Browse>X>XNA Creator’s Club. Download and install XNA Game Studio Connect.

Before you can continue make sure your Xbox 360 is online on the same network as your computer (most home router set ups will work).

On your computer press the Start button>All Programs>Microsoft XNA Game Studio>XNA Game Studio Device Center.

Click the Add button. Select Xbox 360 and name it. Click next. Your computer will ask you for a code. Go back to your Xbox 360.

Run the Game Studio Connect application (it will be located under All Games). It will give you a code to enter into the fields on your computer. Do this and click continue and it will connect.

You should now be able to deploy games to your Xbox360.

XNA Tutorial 4: Image Rectangle

2010-05-27T08:15:00.000-04:00

Download the XNA Tutorial 4: Image Rectangle by clicking on the title of this post.

XNA Tutorial 3: Controller Mood Light

2010-05-27T06:51:00.000-04:00

Download the XNA Tutorial 3: Controller Mood Light tutorial by clicking on the title of this post!

XNA Tutorial 2: Ultimate Mood Light

2010-05-22T19:00:00.001-04:00

Download XNA Tutorial 2: Ultimate Mood Light by clicking on the title of this post!

ULTIMATE MOOD LIGHT
Colors, variables, switches, comments and conditions.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)UltimateMoodLight” using camel casing. ex. leftwichBlakeUltimateMoodLight. You have just named the solution file. This file holds all information pertaining to this game. This is also what you click to open it you ever want to come back to this game project. Please be sure to put your full name in the solution name so I can grade it.

Make sure the path in the Location field is pointed to the correct location and also that “Create directory for Solution” is checked.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “UltimateMoodLight”.

Click OK

Step 2
Class-level variables: In the UltimateMoodLight class under SpriteBatch spriteBatch; write the following code:

// red, green and blue values for screen color

byte redIntensity;

byte greenIntensity;

byte blueIntensity;

// state representing either counting up or down

bool redCountingUp;

bool greenCountingUp;

bool blueCountingUp;

The byte type can contain a value from 0 to 255. The values if the colors never need to exceed 255 and it is always a best practice to use the most conservative type you can to conserve memory.

The bool type can only hold the value 0 or 1 (which can also be expressed with “true” or “false”). Bool types are best for variables that need to be either on or off. These variables are often called switches or flags.

Notice the use of comments here. Comments start with “//” and are not read by the compiler. You should always use comments to describe the purpose of your code. This can be worded anyway you see fit but should always be simple and easy to understand for anyone (not just you).

Step 3
Initialize: In the Initialize method under // TODO: Add your initialization logic here write the following code:

// set initial color values

redIntensity = 180;

greenIntensity = 0;

blueIntensity = 90;

// set initial counting state

redCountingUp = true;

greenCountingUp = true;

blueCountingUp = true;

This simply sets the variables we declaried at the top of the class to their initial states. These values could be set at the time of declaration but in this tutorial we are using the Initialize method to keep things organized. This is a matter of personal preference. The syntax to initialize a variable at declaration is TYPE IDENTIFIER = VALUE. For example: byte redIntensity = 180; or bool redCountingUp = true;

Step 4
Draw: In the Draw method under // TODO: Add your drawing code here write the following code:

// declare a new color

Color backgroundColor;

//instantiate the new color to define it

backgroundColor = new Color(redIntensity, greenIntensity, blueIntensity);

//change the screen color to "backgroundColor";

GraphicsDevice.Clear(backgroundColor);

The first line declares a variable type Color. We declare it here instead of at the class level because it does not need to be accessed outside of this method. This is another good practice for keeping things organized.

The second line defines the color by using the “new” keyword. This is called instantiation, it is the creation of an instance of the Color class. Notice that the Color is defined with the values we set in the Initialize method.

The final line colors the screen the new color we just created.

Press F5 or the green play icon to debug and test your program. So far it does not change color. The brains of the program is in the Update method. Continue to step 4.

Step 5
Update the values: In the Update method under // TODO: Add your drawing code here write the following code:

//update each color in turn

if (redIntensity == 255) redCountingUp = false;

if (redIntensity == 0) redCountingUp = true;

if (redCountingUp) redIntensity++; else redIntensity--;

if (greenIntensity == 255) greenCountingUp = false;

if (greenIntensity == 0) greenCountingUp = true;

if (greenCountingUp) greenIntensity++; else greenIntensity--;

if (blueIntensity == 255) blueCountingUp = false;

if (blueIntensity == 0) blueCountingUp = true;

if (blueCountingUp) blueIntensity++; else blueIntensity--;

The code above repeats three times for each color so I will only explain the first three lines. The first line uses a conditional statement to decide if it should change redCountingUp to false. Pay attention to the syntax as you will use this technique many times as a programmer. In english, this reads: If redIntensity is equal to 255 then make redCountingUp equal false. The “==” symbol is a comparison operator that checks for the equality of the values on either end of it. If these values are equal then the condition is true.

The second line does the same thing with different values.

The third line in english is: If redCountingUp is true then add 1 to redIntensity, otherwise subtract 1.
When testing conditions with a bool type variable no operator is need since it is either true or false.

The ++ operator adds 1 to the variable it is attached to. -- subtracts one from the variable it is attached to. By adding the “else” keyword, the conditional statement can do one thing if the condition is true and another if the condition is false.

Press F5 or the green play icon to debug and test your program. Now the color gradually changes making quite a display! Try playing with the colors. Can you make the screen cycle from black to white and back (without color)?

Save your file. You’re finished!

XNA Tutorial 1: First Program

2010-05-20T12:25:00.003-04:00

Download the XNA Tutorial 1: First Program tutorial by clicking on the title of this post.

Step 1
Start a new Game Project: File>New Project>Windows Game. In the Name field name the file “(lastname,firstname)FirstProgram” using camel casing. ex. leftwichBlakeFirstProgram. You have just named the solution file. This file holds all information pertaining to this game. This is also what you click to open it you ever want to come back to this game project. Please be sure to put your full name in the solution name so I can grade it.

Make sure the path in the Location field is pointed to the correct location and also that “Create directory for Solution” is checked.

In the Solution Explorer right-click the class (probably name Game1.cs) and select rename. Rename the class “FirstProgram”.

All the naming conventions you just used are my preference. They could be named whatever you want but you should always use meaningful names so anyone could easily understand their purpose. This is true for anything you name.

Click OK

Step 2
Test the game: Press F5 or the green play button to start debugging and test your program. You should see a blue screen. This is not a blue screen of death, nay, it is but the Blue Screen of Life! The color is the default background. You will learn how to change it later.

Save your file and quit.

SGD 123 Summer 2010 Course Schedule

2010-05-20T12:23:00.000-04:00

Download the SGD 123 Summer 2010 Course Schedule by clicking on the title of this post.

SGD 123 Summer 2010 Syllabus

2010-05-20T11:14:00.002-04:00

Download the SGD 123 Summer 2010 Syllabus by clicking on the title of this post.

XNA Tutorial: Display an object on screen and move it with the mouse.

2010-05-17T11:11:00.005-04:00

PART I Display an image on the screen

Step 1
Start a new Game Project: File>New Project>Windows Game. It is recommended that you use a meaningful name when creating your project but for this tutorial you can stick with the default name.

Step 2
Import the graphics: Right-click "Content" in the Solution Explorer (the list located on the right side of the screen). Add>Existing Item> (Find the image you want to use: must be .jpg, .bmp or .png). Click the Add button. You will see the file name listed under Content.

Step 3
Class-level Variables: At the top of the Game1 class under SpriteBatch spriteBatch; write the following code:

Texture2D imageTexture;
Vector2 imageLocation;
int imageX;
int imageY;

Texture2D objects hold image data. Vector2 objects hold 2D coordinates (our image’s location on the screen). imageX will be our ufo’s X location on screen, imageY will be the Y.

Step 4
Initialize the variables: in the initialize method under // TODO: Add your initialization logic here write the following code:

imageX = 0;
imageY = 0;
imageLocation = new Vector2(imageX, imageY);

We are setting the image’s initial location as 0 pixels to the right(X) and 0 pixels down(Y) from the top-right corner. Later, we will update the x,y coordinates to equal the mouse cursor’s x,y coordinates

Step 5
Load Graphics Content: In the Load Content method under // TODO: use this.Content to load your game content here Write the following code:

imageTexture = this.Content.Load("image");

Important! The word "image" in the line of code above may be different for you! Enter the name of the file that you imported as it appears under "Content" in the Solution Window. If your image is called "cat.jpg", your code needs to appear as: imageTexture = this.Content.Load("cat");

This loads the texture that we imported in step 2 into our program and assigns it to imageTexture. Note: You do not include the extension, only the file name.

Step 6
Draw the graphics on the screen: In the Draw method under // TODO: Add your drawing code here write the following code:

spriteBatch.Begin();
spriteBatch.Draw(imageTexture, imageLocation, Color.White);
spriteBatch.End();

The spritebatch object is automatically generated when you create a new Windows game. It is used to draw 2D images onscreen.

We have to initiate drawing with the Begin method (spriteBatch.Begin()). Once the Begin method is called we can draw as many objects onscreen as we want with the Draw method (spriteBatch.Draw(imageTexture, imageLocation, Color.White)). For this project however we only need the one image.

The Draw method accepts three parameters. A texture (imageTexture), the location of that texture (imageLocation) and a color filter (Color.White). Note: Color.White is the equivelent of no filter.

Press F5 or the green arrow to start debugging and test your program. You should see the image on the screen. Next we will make it follow the mouse cursor.

PART II Follow the mouse cursor
Step 7
Update the image coordinates: In the Update method under // TODO: Add your update logic here add the following code.

MouseState mouse;
mouse = Mouse.GetState();
imageX = mouse.X;
imageY = mouse.Y;
imageLocation = new Vector2(imageX, imageY);

The update method occurs every frame so everything that needs to happen all the time goes here. ex. controls, movement, etc.

First we are creating a variable of type MouseState called mouse. Mousestate is a built in XNA object that represents the mouse’s current state. Next we assign the value of the mouse’s current state to our mouse variable. The MouseState object has an x and y property (.X and .Y) that we will assign to our imageX and imageY. These values reflect the mouse cursor’s location onscreen. Finally we take those coordinates and instatiate a new Vector2 object which updates the value of imageLocation. Remember, this occurs every frame.

Press F5 or the green arrow to start debugging. The image onscreen now moves with the mouse cursor.
Project complete! Save your file and quit.

Support us!

2010-03-30T10:15:00.014-04:00

Just $1 away from an Under the Radar (Games) website. Help us make that happen! Thanks!

Under the Radar (Games) Podcast

2010-02-01T11:12:00.002-05:00

The last blog was about the Under the Radar (Games) Podcast logo I designed and created. This one is about the podcast itself.

THE ORIGIN OF THE UNDER THE RADAR (GAMES) PODCAST:
In the beginning there was Gamebot, a classic video game TV show my brother and I created back in '04. Gamebot was about reviewing classic games and covering classic game cons. We had a unique blend of dry humor and genuine (nerdy) love for the games and it was loved by the classic game community. It took many weeks to film and edit so episodes came out roughly every two months. The show aired on many stations along the east coast and we ended up releasing two DVDs and produced about 12 or so episodes. By 2007, due to my wanting to keep Gamebot alive even though I had no time to do so, the show had transitioned to a website to a blog to a forum to a podcast. The podcast was called Gamebot Live and was hosted by myself and my good friend Matt Taylor and occasionally, childhood pal Stephen Smith.

The Gamebot Live podcast, the last incarnation of Gamebot, was a lot of work. I had lots of ideas for the show, different segments, sound effects, transitions, guests. At the end of the day it was very time consuming to record and edit and became too expensive to host. Plus, there were other classic game podcasts out there doing a much better job (Retrocity-R.I.P). Episode 14-the last episode-aired in mid '08.

Roughly a year passed and I really wanted to do a new podcast about games. Matt and I tossed around lots of ideas and eventually came up with the following guidelines:

The show has to cost nothing, take little time, be more fun than work, come out every week, be about current games (not classic) and have one solid concept that works instead of a bunch of segments.

We came up with the idea of reviewing under the radar games because no one else was covering them and I tend to enjoy diamonds in the rough. I wanted to keep the method (from Gamebot) of playing games for the first time live. This creates a fresh opinion. I eventually created the outline that we have stuck with.

THE SHOW OUTLINE
1) Talk about our expectations for what the game will be like (or what we hope it is like). I wanted to do this because I believe this is an important stage of experiencing a game. I imagine what the game will play like and often have high expectations. That's why gamers are often disappointed when the game doesn't live up. Everybody daydreams about games before they play them, consciously or not. This is why cover art and screenshots are so important-they spark the imagination.

2) Play it for just enough time to get a first impression. Everyone knows that your first instinct is usually correct. We set a strict time limit of ten minutes with a game not including cutscenes, credits, etc. This time limit has softened over time. We will play as long as we need to try out the elements we want to understand. We often take notes too.

3) Spend more time with it for a final analysis. We discovered eventually that the 3rd step (the "long haul") was not necessary but we still do it from time to time.

NOT NECESSARY?!
Yes, the goal is to inform, not persuade. The first impression gives enough info to whet the listeners appetite. It is up to the individual to decide if a game is for them or not.

Matt and I also decided that sometimes we like to talk about the state of the industry and current news stories, and that our discussions can be very colorful-so why not put them in the show? We tagged an optional "overtime" segment at the end of the show. This was designed to be shut off if the listener didn't care. The discussions however became some of the most memorable and entertaining parts of the show and therefore became a standard feature.

We also occasionally include "minute musts", one minute rants about games that are must-play. This was a segment I came up with. I like segments. Old habits die hard.

The best thing about the overtime segment is that we can do what we want with it. Sometimes we read letters, sometimes we talk about news, we do whatever works that week.

OUTTAKES
Matt is great at finding outtakes and popping them on the very end of the show. These outtakes became discussions about what we are up to, another optional segment. Sometimes it's a single funny outtake, sometimes its a ten minute discussion about what we're playing.

ABOUT THE NAME
When Matt and I were searching our souls for the perfect name. Now frequent guest and devil's advocate James Tillman suggested "Why don't you just call it Under the Radar?" We were dumbstruck! The capper was when Matt suggested mailtheradar@gmail.com as the email address and Evan Jackson, another good friend, recommended that we name our twitter account tweettherradar. You get the gist-it became a nice theme. I whipped up the podcast logo and we were ready to rock but we recieved an email right after our first post about the show from another podcast called, you guessed it, Under the Radar Games. They asked us to change the name but they had just started too and we decided we had as much right to the name as they did. We said no. Our doppelganger is still out there in internet land somewhere coexisting. They are based in jolly old England anyway.

TECHNICAL STUFF
We found a way to host the show mp3s and create the feed for free through some creative researching. The feed xml itself is hosted at the salute games website (see below for a link). All editing is done by the cohost Matt Taylor. He is awesome and makes the show 10x better than it is. He uses Audacity and we record with Skype.

That's the story. If you want to hear the show you can get it on iTunes or directly from the feed at www.salutegames.com/utr. Contact us at mailtheradar@gmail.com and follow us on twitter at twitter.com/tweettheradar.

Feedback appreciated!

Under The Radar Podcast

2009-06-21T13:21:00.001-04:00

Under the Radar logo

The Radar Podcast

2009-06-21T12:44:00.001-04:00

An idea for the podcast logo.

Preliminary work on a Prehistoric Times flash game

2009-04-06T16:11:00.001-04:00

New Texture, Same Picture

2009-03-02T20:46:00.001-05:00

Have you seen this man?

2009-02-23T19:21:00.000-05:00

I wanted to share this screenshot from the Saloon Level!

Textures!

2009-02-20T11:19:00.000-05:00

I wanted to show a few textures I have been working on lately. I am currently creating a library of texture assets for future projects.

Spooks' Manor

2009-02-18T13:30:00.001-05:00

Spooks' manor is a spooky 2D platformer I am creating in Game Maker. It is approximately 65% complete.

Command Center Completed Level

2009-02-16T13:52:00.000-05:00

Whiteboxed Saloon (Unreal Editor III)

2009-02-14T12:39:00.000-05:00

Level Diagram:

Miscellanious Ideas

2009-02-14T09:02:00.001-05:00

also, i imagine that a beekeeper, a seamstress, a sheriff, his deputy and a minister decide to kill the devil
the beekeeper understands the nature of the insects and helps the seamstress create protective suits
the sheriff and deputy are trying to get this thing out of their town
and the minister thinks he is battling the devil
its kinda like the suit is your lifemeter-if it takes too much damage-it gets a hole in it and the insects devour you
also it'd be cool if you had to play the game as all of them but you chose which order they went in
so if one died-you didnt get an extra life you just had the next guy go in-who had different skills and attributes

The old , crude wooden shack stands at the end of the main street at the other end is the church. In between are various businesses lining both sides of the street usually bustling with trading, metal-smithing, baking and other daily business. This street is now barren. All the townspeople have left or are leaving.

Level Description

2009-02-14T09:01:00.000-05:00

The saloon at the end of the street gives off a strange aura in the hot, summer, dusty morning. It is quiet. The quaint two-story building itself is comprised of cheap wooden slats and a rusty tin roof, crudely put together on a shoestring budget. There are three wooden steps that lead up to the low porch with watering and feeding troughs for horses at the foot of these steps. The porch has banisters and rails that stretch from the four pillars that hold up the roof over it. The porch creaks and gives a little as you walk on it.
The opening at the top of the steps reveal a simple open door frame with swinging doors attached. On either side of the door are and on the right side of the building are windows. These, along with the six windows around the second floor, are all darkened as if there is a thin gray curtain covering them on the inside, but as you look through them the view is distorted, cloudy and unmoving. Over the swinging doors you can see light from the blaring sun behind you drape across a polished bar used to serve drinks from only a week before this happened. Behind the bar is a hint of a gray moving mass. As you move inside it is dark. Only the light coming in the main entrance lights the room. The windows only provide a gray glow. The floor is made of the same slats as the porch and still creaks as you walk while creatures shuffle and scamper under your feet.
The bar and entry-side coat rack is bare but there are chairs and tables around scattered with cards and coins. The saloon looks as if everyone just got up, left and never returned. The walls however are a different story. The gray hazy goo spread over the windows covers the walls as well. The original wood behind the sludge is still slightly visible because the goo is semi-transparent and some old metal painted signs are visible but unreadable. There are human carcasses trapped in the sludge on the walls, drawn up, twisted, rotten and sucked dry of life. They look down at you frozen in pain and fear. Behind the bar where a liquor rack used to be is an undulating mass of tentacles, tongues and thorns. It covers the entire wall. The thing is slowly moving and silent but stares at you with a shiny eye-like organ.
On the right side of the room are more tables and chairs and another window. On the left side are narrow wooden stairs with a banister covered in gray mucus that has snapped it into dangerous broken wooden shards. Below the stairs in the corner is an old piano covered in insects accompanied by the sound of random strings inside being plucked and the buzz of millions of vermin. There are also bugs crawling on the ceiling and occasionally fly in front of you (the player) but mostly huddled inside the piano and in the corners of the ceiling.
Upstairs are four rooms full of the broken remnants of beds and furniture. The entire top floor is lit only by two gray windows on the front and side walls of the building. The doors of the bedroom have nearly been torn off the frames and dark gray light from the rooms bleed into the short hallway that adjoins them. These are the rooms where the ladies that worked in the saloon rendered their services for the men. They are now full of strange and frantic animals that attack you on site. They stand between you and the soft parts of the creature covering the structure.
These soft, vulnerable parts are attack points to damage the thing controlling the saloon. If each of the four room’s soft parts are destroyed the creature can no longer protect its eye-like organ. This is its weak-point. The rooms upstairs are larger than they appear from the outside. In fact, they shift and change as some foreign airborne substance has invaded your body and made you prone to hallucination. However, for the most part these rooms remain simple, identical bedrooms full of broken furniture and dangerous beasts.
The game takes the approach that the people of this old western town have no knowledge that leads them to believe the creature is an alien. The strange thing appears and the animals and insects of the town begin to act strange and sickly after the alien bacteria arrives inside a falling star and begins to infect them like a parasite. The few people not scared out of town who decide to do something about this strange infestation believe the creature is from hell or perhaps the devil itself. They do not know it is an alien life form that has transformed the saloon into a feeding and breeding ground.

Level Narrative

2009-02-14T09:00:00.000-05:00

Inside this wooden shack the sunlight and noise are filtered out by windows and walls covered in thick gray mucus. Through the pane the black silhouette of a horse bellows, its belly bloated and body disfigured by the worm living inside it. The piano has become a giant nest for spiders, centipedes and all species of vermin unnaturally living together. Driven mad by the song of the devil, they tremble and devour each other on the strings composing a chaotic and broken song. The tables sit silently with cards and coins scattered atop them. One hand has been spread out face up, proudly displaying three queens with no swindler around to claim a sucker’s money. Instead, this warm, moist room is witnessed only by the lifeless eyes of the few foolish enough to let curiosity get the best of them, trapped inside the gray sludge that still squeezes nutrients from their body like juice from a fruit. Between the windows is a doorway. Unsealed by the gray mass, it continues to welcome patrons with its inviting swinging doors. From the outside in fact, the freshly swept porch and clean water troughs look quite normal and its strangeness could remain undetected on a dusty day if it weren’t for those poor damned horses barring the steps. Across from the entrance, sits the bar, polished and unchanged from its service just one week ago, bathing in the white morning sunlight in sharp contrast to the blackness around it. Encompassing the entire wall where the bartender once stood is best described as an opening, an orifice or a mouth with rows and flaps of horrid tendrils, horns and tongues. Buried deep inside is a shiny organ that peers out and shifts about like an eye. The gray goo stretches right up the banister to the rooms where the ladies used to entertain the men, clinching so tight that it broke the woodwork clean in two. And those rooms, with their doors hanging only by a few resilient screws, burst forth with all manners of wildlife from the plains, scraping and clawing at each other in the dark, possessed and frothing at the mouth. It was only by the grace of God that I saw that hell and crawled out alive. I plead with you to leave this place.

Level Design Assignment

2009-02-14T08:56:00.000-05:00

This is the assignment:

Choose one of the 4 themes listed below around which you will develop and design a level based around the theme. The first part of creating your level consists of coming up with a description of what the level will look like. You should use lots of colorful and descriptive words to let the reader know what the level will look like. Make sure to discuss the elements of lighting, color, time of day/year or season, history of the location, who lives or lived here, architectural style…

Level Theme Choices
Futuristic Team Sport: Team A vs Team B
Alien Old West Saloon
Candy Bar Factory where the candy bars are made with products found in the ocean.
Musician’s Junkyard

Little Big Fire Department

2009-02-14T08:37:00.000-05:00

I posted a new level on Little Big Planet called Little Big Fire Department. In this level you save trapped survivors from a burning city using a firetruck vehicle complete with a working water hose and ladder. Some structures must be scaled in order to rescue everyone and the level has a cliffhanger ending! Prizes include the firetruck, building, burning debris and survivor action figures.

My PSN name is INCREDIBLEWIZARD. Check out my level and give me tons of hearts if you think it's worthy -and feedback!

Little Big Doughnut Factory still has a planned revision by the way.

WILL POWER featuring Big Helga

2008-12-19T13:13:00.000-05:00

This is my final Flash Game Project for class.

WILL POWER

Inmate Model Complete

2008-12-19T10:58:00.001-05:00

This is the final model created in Maya, a cartoonish take on the character. Realistic pupil and tattoo textures, a smaller nose, UVs further tweaked to reduce stretching and better cloth geometry would have yielded more realism. You can see the concept art at the bottom.

Model Update

2008-12-16T13:13:00.000-05:00

I will be texturing my inmate model over the next few days. There is a little tweaking that still has to be done with the geometry, but this is nearly complete.

PONG! The Flash Experiments

2008-11-26T14:55:00.000-05:00

Snow Knife Model (Maya)

2008-10-31T14:48:00.001-04:00

Living in a Shoe Model (Maya)

2008-10-31T14:41:00.000-04:00

Fur or Animal Skin Texture (Photoshop)

2008-10-30T21:33:00.001-04:00

Inmate Carpet Knife Model (no texturing)

2008-10-26T14:41:00.000-04:00

Little Big Doughnut Factory Sketch

2008-10-25T15:33:00.000-04:00

This is my first sketch of the doughnut factory. Although the design will be tweaked throughout production, the main ideas I want to keep are the plinko style pegs, the defective doughnut chutes, hidden rooms, the side exits from the plinko board, the main elevator and the giant hungry customers. Future posts will include information on the different parts of the factory and how they work. Click the image for a closer look.

I will continue to create sketches and in the next post will elaborate on the characters and dialog I have planned. Feedback wanted!

Little Big Doughnut Factory

2008-10-10T14:19:00.000-04:00

I downloaded the Little Big Planet beta and it is one of the most addictive gaming experiences I have ever had. Since Tuesday, I have spent about four hours building my contribution; the Little Big Doughnut Factory. Because the beta ends Saturday night I am unable to complete the level but have posted it. According to Media Molecule (the developers), the levels will remain posted and accessible from the full game when it releases later this month. I have hidden prize bubbles throughout the level holding some of my own creations such as a four car rollercoaster, and a mechanical hook. I hope to pick up these prizes when I get the release copy and complete the Doughnut Factory. In an upcoming post I will include some sketches and ideas for the completed Doughnut Factory. All feedback is appreciated!

Inmate Concept Art

2008-10-08T16:44:00.000-04:00

This is concept art for an original character model I will be building with Maya. Click to enlarge.

He is a 78 year old man(approximate) who has served 12 years of his 125 year sentence. He was found guilty of four counts of murder in Henry County, Georgia. Although he has been called the Pine Lake Killer, he is an illegal immigrant believed to be of German ancestry with no documented name. He is unable to speak and has two distinguishing tattoos: A mark across the bridge of the nose connecting the eyes and a similar line extending from the corners of the mouth and ending in a curl underneath the cheekbones. He suffers from bodily swelling and bone degeneration.

Also in the picture are some of the items used in the Pine Lake Killings.

A carpet knife, a frayed appliance cable and a crude mask cut from tree bark.

I will update the blog with actual model images over the next few months. All feedback is welcome and encouraged.

CERNa Command Center CTF Level

2008-09-28T21:39:00.000-04:00

This is floor 1 of a two story capture the flag level I am creating for my level design class. This first draft was created in Sketchup and the final version will be built using the Unreal Engine.

The following level narrative establishes the history of the level...

It was just twenty years ago that this place was the command center for CERNa’s particle laboratory. The complex was originally built to research supersymmetric particles created by the LHC (Large Hadron Collider), the world’s most powerful atom smasher. After the Chinese took Switzerland, we were forced by the O.A. (Order Allies) to switch focus to military applications. For 21 months we were prisoners forced to do the work of the devil. Then CERNa was deemed unsafe and abandoned. The O.A. moved the operation north. That’s when some of us escaped but most of my colleagues were shot.

It’s true this was the birthplace of the weapon called Rapture. Once we understood how to make the new energy, they had us create a way to move it, then concentrate it to one area. Even though we didn’t know what the energy was, we were able to manifest it anywhere on the planet within 100 kilometers of a target. This spawned the Network movement in the West.

The Network infiltrated the CERNa command center looking for data that could be used to nullify the effects of Rapture. They restored the lab to 80% functionality under the nose of the O.A.

Now the command center is just part of a battlefield where factions fight for territory control. The laboratory was 300 meters below the Earth’s surface but is now above-ground and accessible from all sides due to the deformation of local terrain by bombs. The LHCa lining has deteriorated and exposure to the radiation is extremely dangerous particularly on the first floor bridge located directly over the LHCa cavity. The auxiliary power still allows use of the elevators and computers that haven’t been crushed by debris. Who knows, maybe it’s true that some valuable data could still be retrieved there.

I will continue to blog on the progress of this level. All questions, comments and concerns are encouraged!

Mighty Springstick (tentative title)

2008-09-26T23:10:00.000-04:00

When your balloon crashes into a rocky cliff, Toby, your best friend gets lost! Hop over spikes, stalactites and water traps as you traverse 12 stages of a mysterious island on your trusty springstick.

The goal in Mighty Springstick is to guide the avatar through four areas broken into 3 stages each. The player uses only the left and right arrow key to manuever and the pogostick never stops bouncing. The result is a game of timing and skill that is simple to learn but difficult to master.

Each stage is reset if the player collides with a rock, stactite or falls into a water trap or pit.

The stages are designed to be fast and addictive and are completed by touching the finish line. High scoring strategies include collecting all the nuts and bolts or reaching the goal quickly for a time bonus.

This demo was created in Gamemaker but the finished project will be a Flash game playable in any browser. I am aiming to complete the Flash version by 2009. Any questions, comments or concerns are encouraged!

Street Cred

2008-09-26T17:23:00.000-04:00

The Early Days
This is where I get to tell you about my long gaming history! It started at a pier-side arcade in Kure Beach. It was the early eighties when I pulled up a step-stool and plunked quarters into Donkey Kong, Space Invaders and marveled at Sub Hunt (I was too short to peer into the periscope).

Later, at an aunt's house, I discovered the Atari 2600. I played Combat and Pac-Man for hours and never thought twice about its flickery ghosts or inaccurate and unchanging maze that was nothing like its, to-me-unknown, coin-op version. That Christmas, my brother and I asked Santa for one and he came through!

For the next few years we bounced between our local arcade where we played games like Tron, Major Havoc, Zookeeper and Dragon's Lair to the Atari with Phoenix, Laser Blast, Frogger, Pitfall and more. Much more in fact, as we accumulated a collection of over 200 Atari 2600 games.

I cruised right through the video game crash without a hiccup, wondering why we could now get games at Revco for 50 cents each! My bro and I played and loved hundreds of games for the Atari, many of which are now considered the worst of the worst. It was about that time when I got hooked on a game at my local Food Town called Super Mario Bros.

The next part of this story is a doozy and I encourage you to go easy on me and recall the politics of your school playground (Our "Social Networking Site" of the time).

A kid named Charlie (I'll never forget that name!) teased me about my love for the Atari. He had the audacity to say the Atari was old and still playing it was akin to liking country music (Any country fans offended? Take it up with Charlie.). He stated that everyone had the Nintendo now and Atari "sucks". I had no idea what a Nintendo was but boycotted it on the spot!

A few months afterwards, a friend invited me over to play video games and when I got there, there was no Atari! Instead he had a strange gray box with weird controllers devoid of a joystick. I watched as he turned on this machine and began to play an arcade-perfect port of Super Mario Bros. I was stunned. We continued the evening with games of Duck Hunt and he even dusted off his already-obsolete R.O.B. to show me what it did. I was blown away but determined to stick to my guns.

That birthday I got the Atari 7800 with Food Fight and Xevious! They didn't have the graphics of the NES but they were loads of fun! Then I found Ballblazer by LucasArts and became obsessed!

Next came Christmas and with it, the Sega Master System. I mastered the built-in Hang-On!, playing it for hours at a time and found my SMS exclusive that was every bit as good as any NES game: Lord of the Sword. By this time I was reading game mags (still no internet yet) and saw a screenshot that looked better than any previous SMS or Nintendo title. I don't remember how I extorted $70 out of my parents but Phantasy Star was ultimately mine -and my first RPG (one of few)!

A year passed and the NES grew in popularity. I read tons of amazing game reviews and got hands-on time with Castlevania, The Legend of Zelda and Mike Tyson's Punch Out. I had no choice and swatted that monkey off my back!

That Christmas, NES, Metroid, Metal Gear, no explaination necessary. -Note: I feel that these games along with Castlevania 2, Pitfall 2 and Adventure are the reason that, to this day, my favorite genre is action-adventure games.

Epilogue
Still bittered by Evil Charlie's comments, I did eventually get closure when I got my first job and bought a Sega Genesis at launch for $299. This console trumped the NES and had Altered Beast to boot! From there my brother and I continued to grow our collection. He leaned toward Colecovision, Intellivision and many, many more pre-NES systems while I opted for NES-era and later. Meanwhile, I was still reading every video game rag I could get my hands on and eventually purchased a Playstation, PS2, GBA, NDS, Wii and PS3.

That's just the beginning of my video game legacy. I have first-hand experience with the NES craze, the SNES/Genesis war, the Sega console implosion, the birth of 3D and disc-based games I played the first first-person shooter before it became a genre and downloaded games on the Sega Channel before every home had the internet. My favorite games are too numerous to mention but I prefer third-person action-adventure, 2D platformers and classic games. Anyways, I hope this gives you some insight into who I am as a gamer.

First Blog

2008-09-26T17:00:00.000-04:00

Hello! This blog will be primarily focused on video games although anything goes. I will be presenting various game or related projects I am working on and post game ideas and screenshots. I might even review and talk about current industry news.