I'm recently been programming something for a little while, and I was trying to figure out a way to map out larger objects without meticulously placing each instance where I need it to be (for the sake of argument, a tree, perhaps).
This tree, for example, is comprised of 6 parts, 3 of which are the trunk, middle and top, and other 3 are the opposite sides. The tree itself it an object, not a turf. When I decided that I need these trees in a lot of places, I created a piece of code that happens during run-time that adds the separate parts of the tree next to the the original instance; it creates 5 copies, changing the icon_state, layer, density, and location (obviously, one or two tiles away, depending on the part of the tree) as needed.
My question, however, is if this is a good practice to consider using when making maps so I can create a larger map in a less amount of time, or is the use of that many objects placing an unnecessary workload for the server. Should they instead be a turf? What other options are available?
Thanks for your response, it is greatly appreciated.
Jan 10 2009, 4:52 pm