So here is the video.
Like I mentioned above, I added quite a bit. And like always, most if it is in the code. Like the whole iceberg metaphor. But here you can see enemy AI. A simple “J” press in the level blueprint sets my worker as their target. Underneath every unit is a blue/red decal. They show up on cursor over/selection and the color is determined by whether or not said AI is on your team. You can’t select enemy units. Team is determined by 1 of 2 things. If you place the unit in the level, you can set the team, ID and starting/total health in the “Details” panel. Otherwise, when spawned by a player, that player’s team number is assigned to the unit. I have set this up so that it DOES SUPPORT multiplayer. There is no multiplayer built in, though.
The only thing left is final detail. I include fog of war in what I consider to be the polishing-steps of this process. That will be a bit tricky as I don’t currently know how to make scene assets visible to one player but not another. That’s the only problem as of right now.
I also have a few things that I’d like to add just to make it a bit nicer. Some blueprinted volumes that can be custom sizes that spawn resources every x amount of seconds, the limit being determined by top-down area of volume. I’d also like each of the structures to be “built” by a worker. Whenever structure is placed, the nearest worker runs to the building and slowly fills the health/build progress of the structure. And a few other, minor things.
SOON!
Like always, this is still 100% in blueprints. Everything you see (except the selection decal) is either shipped with UE4 or free on the marketplace (death/attack animations). Everything is built to be customized without ruining function.
Thanks!
Edit: I also forgot to mention about color coding guides. Every single set of nodes are grouped together by relation. I’ve commented everything in every one of my blueprints (there are tons). Several hundred variables and functions are all carefully grouped in color coded comment boxes with descriptions of what they do. Each comment box is color coded as a guide for anyone who uses the template:
Blue = modify, add to, remove functions and variables at no cost to underlying function
Green = add to functions and variables safely, modifying variables and functions is on a per asset basis but usually safe, removing functions or variables may cause errors
Orange = these functions and variables should only be modified, added to, or removed if you really need to change something and you know what you’re doing
Red = these functions and variables are at the core of the RTS system. If you delete something that’s red, you are why we can’t have nice stuff.