Quote:
|
Originally Posted by CrapShoot
I like the idea of a script file. My initial thought of an implementation would be for the class specific actions.
|
Already possible, but with actions. An action can be class specific, even weapon specific: say you only want snipers and meds to camp a certain action - its possible! OR, you don't want certain classes to do an action - say you dont want axis engs just running onto the beach to get killed, but instead to wait back until someone plants - also possible. I don't want to tie a specific action to a specific bot tho - I was going to do that originally, but I've been doing a lot of thinking, and I want actions to be "suggestions", not "orders".
I think by default, I'd prefer to keep access to the actions themselves in the nav file, but I could make it where you could add an action externally, or perhaps control what nav file was loaded (maybe thru a CVAR). That way, if you wanted a nav file where all of the axis charged out onto the beach, and all of the allies sniped them at certain points, you could actually do that, without screwing up the default nav file.