Oh and another thing, what do you (and rest of the people here) think of RTS camera that when you zoom in it slightly rotates pitch-wise? I have mixed feelings about that, sometime that makes for a nicer look, but sometime it’s much more useful to just be able to fast zoom in and out without totally getting my camera rotated… I believe even Starcraft II has similar feature but could be wrong… Any others tasks for the camera, apart that one? Can you rotate it like yaw-wise? Oh right, I haven’t played Civilizations but I have played Tropico, so I definitely know what you mean. Anotehr possible use is when you click on the icon for your unit on HUD, it will focus that unit. If you’ve played Civilizations/Tropico… you might have come across this many times. You can click on this notification and it will automatically focus on the said unit.

Now you will get a notitication like ‘Unit 2 is taking damage’. Now one of your units on the other side of the map is taking too much damage. What I mean is suppose you have deployed several units on the map and they are far aprt. If any other member wants to do that…Feel free. Although i dont intend to make every object clickable in this game. In AOE 3 we could select any item and the UI showed the details. Just sharing some ideas as a huge RTS fan + I used to work with Unit圓D so modularization was a big part of their prefab system…īasic object should exist, let think of it as an entity… That should be like the basic building block of anything… Do you remember an RTS where you could select, I don’t know, rock, waterfall, tree, any prop in the map and in UI it would say sonething like “Rock”, along with its picture and perhaps even a hp bar? now granted, there is little sense in being able to select any rock over the entire map but you can see the effect of it… If you want to make some object (prop) selectable make it of a class entity… Further, if you want to make it destructable and showing its hp bar in the ui/gui what about a boolean “isDestructable?” toggle as a object field?

Although, as you said we still need to decide quickly about gameplay mechanics. If you intend to change gameplay mechanics sometimes later, then this setup will bite you.

One problem with this approach is you fisrt need to identiofy all the gameplay specifics and how they all work toegthor. By doign this I was able to implement a projectile based power, self healing power, …all using the same class. When I want a new power, I extend th Power class and tweak the values for variables like HealthBonus, ArmurBonus, InstantBonus, OverTimeBonus, BonusDuration, CastEffect, HitEffect, …(actually there was well over 50 proeprties). Later I created a base class Power and an interface which defined some functions like (ApplyEffects, GetHealthBonus, GetReistanceBonus…). Different powers do diferent tings, some increas/decrease health, some affect speed, resistance… So initially I created sveral powers and hardcoded their efefcts. For instance in a hoby project that I am working on, I have powers that I caan assing to charcters. By doing this, a modder/designer can simply extend a blueprint form it and tweak the properties to create something entirely new. Ok one way to achieve it (kind of) is to make the Collectibles, Powers…very generic and with a lot of properties exposed.

Starcraft 2 project haven classes