Design pattern for procedural terrain assets

Posted by Alex on Game Development See other posts from Game Development or by Alex
Published on 2012-06-19T16:19:30Z Indexed on 2012/06/19 21:25 UTC
Read the original article Hit count: 453

I'm developing a procedural terrain class at the moment and am stuck on the correct design pattern. The terrain is 2D and is constructed from a series of (x,y) points. I currently have a method that just randomly adds points to an array of points to generate a random spread of points. However I need a more elaborate system for generating the terrain.

The terrain will be built form a series of re-accuring terrain structures eg. a pit, jump, hill etc. Each structure will have some randomness assigned to it, each height of hill will be random, pit size will be random etc. Each terrain structure will have:

  • A property detailing the number of points making up that structure
  • A method for generating the points (not absolutely necessary)

My current thinking is to have a class for each terrain structure, create a fixed amount of terrain elements ahead of the player, loop over these and add the corresponding points to the game.

What is the best way to create these procedural terrain structures when they are ultimately just a set of functions for generating terrain elements? Is a class for each terrain element excessive?

I'm developing the game for iphone so any objective-c related answers would be welcome.

© Game Development or respective owner

Related posts about iphone

Related posts about box2d