Looks cool. How about for multiple levels, with different tree.ini files? And how about security, couldn't someone just edit the tree.ini and mess up the level? Instead, why not leave all the tree models where they are in game, and then store each one's position in an array when the level is loaded, then destroy it. Sure, it might take another second to load, but it'll get rid of those issues I stated.


--Eric