Cogito, ergo sum
This actor marks objectives in an Assault type map. See Mapping For AS (UT). If game type is not Assault, this actor destroys itself before game starts.
You need to make this in your assault levels to make them work.
To make the time limit for your assault level you need to open the last FortStandard's properties and select defense time and put what ever you want the time limit to be for your level.
You will need to plan and build your level before using this actor. Once you have built your level place a FortStandard VERY CLOSE to the objective, as there are two ways to trigger this actor: damage and touch. First a list of all the actor specific variables you will need to be familiar with:
- When this objective has been triggered, the mission will end.
- When damage is taken, the fort standard will flash. Not sure what the damage threshold for this is.
- If true, bots will charge when they are within a specified radius.
- Bots will use a voicepack recording if they have accomplished this objective.
- If true, the fort standard will be visible as a small flag in game. Almost always set false.
- Set to true if you want the objective to be triggered by touch instead of damage.
- This is the distance from which bots will begin charging if bForceRadius is set true.
- This has several slots for calling multiple events. Similar to a Dispatcher.
- The amount of damage that is needed to trigger DamageEvent. Different damage amounts can be set for different events.
- In which order bots should defend the objectives. The higher the number, the higher the Priority. I have no idea if there is a limit to the amount of objectives, or how big a number to put here. I do know that you can only place seven objectives in the AssaultInfo actor. (Explained later)
- Simply the amount of time in minutes that players have to complete the level. The default value is ten, meaning ten minutes. But I have found out by fiddling that if you have different values in this field for each FortStandard, the engine will take the highest value as the intended game time limit
- This is the message to be shown when objective is destroyed. Used in combination with the FortName value.
- Tag of the SpectatorCam you are using as an end camera. I do not know if each standard needs this or if it is only the final.
- The tag of the fort which defenders should fall back to. I would recommend leaving this blank, and utilizing the DefensePriority property to indicate for the bots where to go.
- Name of the objective. Will be shown with the destroyed message.
- The Tag of the nearest PathNode looking in the direction of the attackers (see Match These Tags for more information). Bots should reach this node before they reach the FortStandard.
SabbathCat : Hey Mango, nice work collating. Hope you stick around a while to add some more, definitely a pro already with WIKI mark-up. I added the pathnode tag thing. As observed from a fair few AS maps from Epic. :)
Tarquin: Nice stuff, but should maybe be moved to Mapping For AS (UT)? :)
King Mango: Yup will do. New here, but am getting the hang of the method. Thanks guys :D!!
Tarquin: the props list says set DefenseTime to the same value for each one, but the top paragraphs say you only need to set it for the final Standard. Which is true?
MythOpus: I believe you only have to set the time in the AssaultInfo... or at least, thats how I remember it. I'ts been so long O_o
King Mango I have found out by experimentation regarding the correct info for DefenseTime. Page reflects changes.
SabbathKatze: Do the Damage Events actually work? I've tried linking them to both a Movers Tag and Event, and neither seems to fire them off. :S?
King Mango My apologies, I misinformed as to defense priority. It has been fixed. Couldn't figure out why my bots kept trying to attack and defend from the second objective as I was playtesting. Then changed the values, and batta-boom, batta-bing, they are working fine.
Also, fortstandards in Assault maps are affected by ZEROPING weapons, the zeroping weapons just can't hit the fortstandards, it would be great to know why, see
for more info on ZeroPing
tarnationsauce2 It seems FortStandards are hard coded at a maximum of 16 (0-15).