rmCreateTerrainMaxDistanceConstraint - seems like this is only useful to keep things close to a Terrain Type, but not actually on the Terrain Type. If max dist is set to 0, does this place objects on the edge of the terrain type?
What I really need is a function like this one:
rmCreateArea(string name, int parentAreaID)
but one that accepts a Class as the parent area:
rmCreateAreaInClass(string name, int parentClassID)
but that wish and 4 bucks will buy me a pint.
So anyway, I have each "pixel" that gets placed getting added to a class, so that Mexico is a class, and Alaska a class, and Greenland a class, etc. This makes placing resources in each area very easy using the rmPlaceObjectDefInRandomAreaOfClass function. I am also going to add a class to hold the shoreline of each areas for more specific placement of objects/resources.
The map is scalable, but smaller than 600x600 and you start to lose features, and water areas get too small to hold water. Do you think this too large for 1v1 games?