if(functionA() = true AND functionB()=true){
	Print=”Success”;
}else if(functionA() = true AND functionB()=false){
	Print “Success”;
}

The first step is to convert this code into Boolean algebra. Let functionA() be denoted as A and functionB() as B.

At this point, it should be obvious how to simplify this expression using other methods. But we’re interested in Karnaugh Maps. The first step in setting up the Karnaugh Map is setting up the table. Create a table, as shown. Each cell of the table represents the result of a product pair. For example, the first cell in the table is AB.

Now, place the results of the product pairs in the table for our expression AB + AB’. From this expression we know that AB is true and AB’ is true. Denote true as 1 and false as 0.

Take note of adjacent cells that are true and circle them.

Next we gather all the circled variables and write them down

Remove duplicates from the list: we have two As, we simply combine them as one variable. We also must remove opposites. B and B’ (“B and not B”) are opposites. Remove them from the list as well. This leaves us with A, which cannot be reduced any further and is the simplified version of AB + AB’.

Now that we have our simplified expression, we can convert it back into code. Our new cleaned up code becomes:

If (functionA() = true){
	Print (“Success”);
}

This was an extremely simple example of how Karnaugh Maps can be used to simplify code. They’re even more useful when dealing with more complex Boolean expressions. For further reading, I suggest the following:

• Digital Logic – Karnaugh Maps
• Wikipedia: Karnaugh Map
• Karnaugh Map Minimizer – A great program to help simplify Karnaugh Maps

The pinnacle of Greek architecture – the Parthenon, was constructed over two thousand years ago in Athens, Greece. It was a temple of their guardian goddess Athena, a treasury, and the center of their society. Over the course of history, it was also a battlefield and was nearly destroyed completely numerous times. In the distant future, havoc will once again return to this proven battleground, during The Unreal Tournament.

With utmost respect to detail, I meticulously recreated this Greek masterpiece. The Parthenon’s layout was perfect for a deathmatch, which came as no surprise due to its history. The map is an exact scale reproduction of the original, and even contains recreations of the some of its sculptures. Each one of the Parthenon’s 65 pillars rests exactly where it would be, as if you stood there in person. Historical accuracy is interesting, but some inaccuracies were inevitable, in order to make the level more fun to play. I discuss these design choices, and show off the map in my latest demo reel.

The demo reel can be watched via Youtube, via YouTube. A higher quality, full HD version is also available (recommended) and of course the map is available for download and play for the PC version Unreal Tournament 3.

Created using:

• UnrealEd
• Adobe Photoshop
• 3ds Max 2009
• Zbrush 3
• Bodypaint 3d
• Adobe Audition

Gearbox Software nailed it. I’ll be the first to say it: no other RPG or MMO has ever scaled from level to level as well as Borderlands does. From level 1 to level 50, Borderlands throws perfectly balanced enemies at the player. And when that’s done, get ready for play through #2, because increases in difficultly seamlessly and is just as fun the 2nd time around.

While playing through Borderlands, especially during the main quest, every battle is just as entertaining as the last, because Gearbox tweaked the level system to perfection. You never find yourself in an unbalanced fight. Then when another player joins, the enemies are scaled to a more difficult level flawlessly. The game is always challenging, from start to finish, but never too hard or too easy. Other great RPGs, like Diablo II couldn’t even balance itself this well.

From a game developer’s standpoint, this is one of the hardest things to do. It is extremely difficult to gauge how difficult an enemy should be for a player at a certain time. Then when you add multiple players to mix, it becomes even harder to balance game difficulty. But Gearbox did it, and they did it well. The level system is very sensitive, and each level counts. When a player walks into an area against enemies their level, or a level higher, they know they’re in the right place. With the exception of side quests, which can be too easy if not done right away, the player always seems to be the right level at the right time.

In retrospect, there weren’t many battles in the game stood out. Instead, every fight was a ton of fun throughout the entire game, thanks to Gearbox’s perfect balancing through scaling. This game scales so well, that the player can start a 2nd play through, at the same level they previously completed the game at, and still expect to have just as much fun the 2nd time around. This level of replayability is unheard of in both RPG and FPS genres, and certainly has set the standard for games to come.

#5 Masters of Doom

While not a technical book, there’s a lot to learn from Masters of Doom – a book that follows the early history of iD Software and its founders. Its interesting reading about John Carmack and John Romero and how their brilliance helped transformed the game industry into what it is today. It’s also quite entertaining reading about parts of the industry that haven’t changed, like bad eating habits, immature jokes and unavoidable “crunch time”. Since it’s a book about two of the most successful game developers in the industry, it’s a great motivational book as well.

Overview

A matchmaking service is responsible for pairing players with one another when they want to play your game online. When a player’s game client connects to the service, the service finds all available matches that aren’t full and connects them to the match. The matchmaking service we design in this tutorial can be used in either a peer-to-peer or a client server model.
Online matches can’t happen if your matchmaking service is down, so designing your service for scalability and reliability is very important. We’ll discuss some of the basic philosophies used when designing your service and discuss why some of the technologies used in this tutorial were chosen.

Why Google App Engine?

A lot of factors need to be considered when determining the infrastructure for your matchmaking service. It’s a critical part of your multiplayer game – if it fails, players won’t be able to play your game. Since reliability is likely your top priority, you know you’ll likely be using a scalable cloud solution. The cloud provider you choose will likely be based on whether you need an IaaS or a PaaS cloud model.

For your matchmaking service, a PaaS approach makes a lot of sense. As a PaaS, this is where Google App Engine comes in. GAE lets you deploy your service rapidly and with minimal maintenance required afterwards. There’s no need for database administration, monitoring instances, or updating server software for years after release. During development, this also lets you focus on your matchmaking code instead of strategies for maintaining it.

GAE works for a matchmaking service because it’s very simple and has low requirements. If pricing is an issue, latency is a major factor (every millisecond counts), or your clients need to use UDP, then GAE might not be for you.

Cloud Endpoints

Another benefit from using GAE is that Google provides some very useful tools to aid in developing your services. Cloud Endpoints is one of them. Cloud Endpoints aids in creating an API for your service. In this example, we generate the API for our game clients to interface with using Cloud Endpoints.
Cloud Endpoints speeds up API development greatly. It also provides some pretty nifty tools for debugging and generating documentation for your API.

The Data

Typically, a matchmaking service doesn’t need a complex database to drive it. I like to keep things simple, so that I can take advantage of the speed and scalability of a NoSQL solution. GAE’s Datastore is great option for this and that’s what we’ll use in this tutorial. If your project needs a relational db, look into Google’s Cloud SQL.

• Adobe Photoshop
• Adobe Illustrator
• Adobe After Effects
• Autodesk 3ds Max 2009
• Pixologic Zbrush 3
• Maxon Bodypaint 3d
• And I’m currently learning to use Autodesk Maya

I’ve worked as a graphic designer for numerous years, from which I developed many of my texturing skills. I can 3d model as well. When I create a level, I like creating my own assets and I’ve even found myself recording and editing sounds for map use. Each map I create begins on pen and paper and I use my knowledge of ancient architecture whenever possible. Everytime I create a map, I try to become a better designer, modeler and artist.

My experiences as a Game Journalist, and most importantly, as a gamer have and continue to have a major role in each level I design. I don’t just like video games, I know why I like them and I use this knowledge in my own designs.

Showcase

DM-Parthenon Demo Reel

A historically inspired map, featuring the ancient Greek Parthenon. Created for Unreal Tournament 3.