Upcoming Events
Unite 2010
11/10 - 11/12 @ Montréal, Canada

GDC China
12/5 - 12/7 @ Shanghai, China

Asia Game Show 2010
12/24 - 12/27  

GDC 2011
2/28 - 3/4 @ San Francisco, CA

More events...
Quick Stats
96 people currently visiting GDNet.
2406 articles in the reference section.

Help us fight cancer!
Join SETI Team GDNet!
Link to us Events 4 Gamers
Intel sponsors gamedev.net search:

 The Map
 Unit Data

 RAM Considerations

 Printable version
 Discuss this article
 in the forums

This article is the first in what will be a short series of articles about Tile/Map-Based Games Techniques. This first article will cover the primary data structures of such a game: the main map structure and the unit structures.

My primary assumption is that the "look" you are wanting is similar to Command & Conquer, WarCraft, Ultima Online, and so on, either in "straight overhead" or isometric representation. My secondary assumption is that you already have at least the basic concept for your game. These articles will not cover game design in any real depth. Instead we will be focusing on implementation issues.

Data structure and coding examples will mostly be taken from my currrent project, Artifact. Artifact is an Internet-based, client-server, multi-player, persistent-world, real-time strategy game. Artifact is currently in pre-release, with full release scheduled for Fall 1999. For more information and screen shots of the game, check out the Artifact web page: http://www.samugames.com/artifact

Next : The Map