• Home
• T3A:Online
• Tournaments & Games
• Replays
• Tutorials
• Mods
• Maps
• Downloads
• Forum
• Showcase
• Users
• Links
• Help

Quick Lists

Top Rated Popular New Updated Last Comments Users

Page 1 2 3 4 5 6 7 8 9 10 11

B3. Complicating the issue.

Let's say you want Faramir to dismount when there are a lot of Pikemen around. He is pretty vulnerable to Pikemen when mounted, so this would make sense.
This is 'one' way of dealing with the issue. A similiar way can be implemented to make him mount again, replacing the above described rather simple procedure of letting him mount.
Bear with me.

Let's have a look at one of the most interesting modules. It was used originally just to let Sting glow when orcs where near:

              

Code

Behavior = SpecialEnemySenseUpdate ModuleTag_StingSeesOrcs     SpecialEnemyFilter = ANY +ORC +URUK +MordorShelob     ScanRange = 200     ScanInterval = 2000 End

This Module lets Frodo sense specific enemies when they are at a range of 200 or less. The module checks for enemies ever 2 seconds.

Faramir needs this to be a bit modifier. In the end, it should look like this:

              

Code

Behavior = SpecialEnemySenseUpdate ModuleTag_FaramirSeesPikemen     SpecialEnemyFilter = ANY +PIKEMAN ENEMIES     ScanRange = 100     ScanInterval = 2000 End

He will now sense Enemy Pikemen at a range of 100 'feet' (roughly the diameter of standard horde).
This module does one thing, and one thing only. It sets the ModelCondition 'SPECIAL_ENEMY_NEAR' when it's conditions are met.
Now we need this ModelCondition to actually DO something.
With Frodo, it made Sting glow. This was done with and additional W3DDraw-module.
But to make it trigger a SpecialPower, we will need an upgrade. And we also want it removed when the conditions are gone, so it can be reacquired and once again trigger the dismount when the conditions are met again at a later date.
AND we want Faramir to mount again when the Pikemen are gone.
This is the way to do it:

First we need two OBJECT-upgrades. There are some suitable unused ones already defined, but for clarity's sake, i will make up new ones.

              

Code

Upgrade Upgrade_DismountNOW     Type = OBJECT End Upgrade Upgrade_MountNOW     Type = OBJECT End

Next, we need to adjust Faramir's LUAFunctions, or rather add two more to his set.

To explain briefly, the LUAFunctions of an object continuously check during the game if certain conditions are met. If they are, they will trigger a scripted response.
There are quite some useful triggers that can be used for the function, specifically a ModelCondition (or the sudden absence of a ModelCondition) can be used as a trigger!

Which 'EventLists' is used is defined in the object's module called 'AIUpdateInterface'

This is what we have for Faramir:
              

Code

Behavior = AIUpdateInterface ModuleTag_03     AutoAcquireEnemiesWhenIdle = Yes ATTACK_BUILDINGS STEALTHED     MoodAttackCheckRate = 500     HoldGroundCloseRangeDistance = 41 End

Many other objects have an additional line which defines the LUAFunction-list used. Like Frodo:
              

Code

Behavior = AIUpdateInterface ModuleTag_03     AutoAcquireEnemiesWhenIdle = Yes ATTACK_BUILDINGS     MoodAttackCheckRate = 500     AILuaEventsList = FrodoFunctions     HoldGroundCloseRangeDistance = 40     CanAttackWhileContained = Yes End

So, i'll add a line with a new (yet undefined) list:
              

Code

AILuaEventsList = FaramirFunctions

My new module for Faramir will now look like this:
              

Code

Behavior = AIUpdateInterface ModuleTag_03     AutoAcquireEnemiesWhenIdle = Yes ATTACK_BUILDINGS STEALTHED     MoodAttackCheckRate = 500     AILuaEventsList = FaramirFunctions     HoldGroundCloseRangeDistance = 41 End

Now it's time to define Faramir's LUAFunction-set (in 'data\scripts\scriptevents.xml')

At the top of the file, you'll find a list of common triggers. Some are system triggers (so called 'InternalEvents' like 'OnCreated') some are ModelConditionTriggers ('ModelConditionEvent' like 'Moving').
The last ones have a set of condition definitions, listing ModelConditions with a '+' (to signify this ModelCondition must be present) and '-' (to signify it is not allowed to be present).

I'll make two new ones:
              

Code

<ModelConditionEvent Name="OnEnemyNear">     <Conditions>+SPECIAL_ENEMY_NEAR</Conditions> </ModelConditionEvent> <ModelConditionEvent Name="OnEnemyNOTNear">     <Conditions>-SPECIAL_ENEMY_NEAR</Conditions> </ModelConditionEvent>

Scroll down. You'll find a lot of EventLists. I'll make a new one for Faramir by copying one that inherits the BaseScriptFunctions (that contain nothing), for exaxmple:
              

Code

<EventList Name="InfantryFunctions" Inherit="BaseScriptFunctions">     <EventHandler EventName="BeAfraidOfBalrog" ScriptFunctionName="BecomeAfraidOfBalrog" DebugSingleStep="false"/>     <EventHandler EventName="BeAfraidOfRampage" ScriptFunctionName="BecomeAfraidOfRampage" DebugSingleStep="false"/>     <EventHandler EventName="BeTerrified" ScriptFunctionName="BecomeTerrified" DebugSingleStep="false"/>     <EventHandler EventName="BeUncontrollablyAfraid" ScriptFunctionName="BecomeUncontrollablyAfraid" DebugSingleStep="false"/> </EventList>

Now i have this:
              

Code

<EventList Name="FaramirFunctions" Inherit="BaseScriptFunctions">     <EventHandler EventName="OnEnemyNear" ScriptFunctionName="BecomeDismounted" DebugSingleStep="false"/>     <EventHandler EventName="OnEnemyNOTNear" ScriptFunctionName="BecomeMounted" DebugSingleStep="false"/> </EventList>

As you can see, i already inserted two new ScriptFunctions, 'BecomeDismounted' and 'BecomeMounted'.
Now i will need to define them.

Open up 'scripts.lua' (in 'data\scripts\')

You'll see a list of functions that can be triggered by any condition in 'scriptevents.xml'
Now i insert my new functions, which would look like this:

              

Code

function BecomeDismounted(self)     ObjectRemoveUpgrade( self, "Upgrade_MountNOW" )     ObjectGrantUpgrade( self, "Upgrade_DismountNOW" ) end function BecomeMounted(self)     ObjectRemoveUpgrade( self, "Upgrade_DismountNOW" )     ObjectGrantUpgrade( self, "Upgrade_MountNOW" ) end

Pretty self-explanatory, right?

All we need to do now is redo our DoCommand modules:

We already have this:
              

Code

// Switch CommandSet when MOUNTED Behavior = MonitorConditionUpdate ModuleTag_CommandSetSwapper     WeaponSetFlags = MOUNTED     WeaponToggleCommandSet = GondorFaramirCommandSetMounted End

Now we add two modified modules to the object code:
              

Code

Behavior = DoCommandUpgrade Module_DoCommandMount         TriggeredBy = Upgrade_ObjectLevel3 Upgrade_ObjectUnderAIControl Upgrade_MountNOW     RequiresAllTriggers = Yes     GetUpgradeCommandButtonName = Command_ToggleMount End Behavior = DoCommandUpgrade Module_DoCommandDismount     TriggeredBy = Upgrade_ObjectUnderAIControl Upgrade_DismountNOW     RequiresAllTriggers = Yes     GetUpgradeCommandButtonName = Command_ToggleDismount End

As mentioned earlier, you may need two differently named CommandButtons and two different CommandSets for it to work flawlessly.


RESULT INGAME:

When created, the LUAscripts immediately recognize the missing 'SPECIAL_ENEMY_NEAR' ModelCondition and give the yet unmounted Faramir the upgrade 'Upgrade_MountNOW' which will do nothing (yet) until he is level 3.
Then he will immediately mount his horse. If Pikemen are near, the flag 'SPECIAL_ENEMY_NEAR' is set, 'Upgrade_MountNOW' is removed, 'Upgrade_DismountNOW' is granted, this in turn triggers the dismount. The reverse happens as soon as the PIKEMEN are gone for at least 2 seconds.
And all of this will only work in the presence of the upgrade 'Upgrade_ObjectUnderAIControl' and so is only set into motion for AI-PLAYERS ONLY!


Next page: Making Faramir use 'Wounding Arrow' ONLY when appropriate (good for many other abilities as well)


-------------------------------------------------------------------------------------------------------------------------------------------------------------------

Previous Next