Creature group - Revision history

BryanDerksen: add navigational template

2010-02-02T21:36:46Z

add navigational template

BryanDerksen: category

2009-07-02T16:50:51Z

BryanDerksen: imported from extranet

2009-06-27T17:14:40Z

imported from extranet

New page

!!Note: This page was imported from a year-old document, may need updating.!!

Assigning groups to creatures:

*Creatures that start as non-hostile should get assigned the 'Neutral' group.
*Creatures that start as hostile should get assigned the 'Hostile' group.
*Creatures that can end up turning hostile towards other creatures should get a unique group.
*The Neutral group is always non-hostile towards every group in the game
*The Player group is always hostile towards the Hostile group
*The Friendly group is always hostile towards the Hostile group.
*The Friendly group is always non-hostile towards the Player group.

To create a custom creature group:
# Open the toolset_groups.xls 2DA
# Place a new entry at the end of the file for your group
# Turn the xls file into a GDA file (need defined process for accomplishing this) and place in override if testing local. Check in to perforce to include in nightly build.
# Now to use the group, use the SetGroupHostility function to set who the group is hostile towards.

== Functions ==

UT_CombatStart(object oCreatureA, object oCreatureB)

Triggers combat between 2 creatures.

This function will switch the creature's group to be the 'hostile' group if it's current group is 'neutral' or 'friendly'. No other groups will be switched — for these cases the function will just set the 2 groups hostile. This function does not change global hostility status between the Player, Neutral, Friendly and Hostile groups. This function does nothing else. The perception system will trigger the combat itself.

UT_CombatStop(object oCreatureA, object oCreatureB)

Stops combat between 2 creatures.

This function will switch the creature's group to be the 'neutral' group if it's current group is 'hostile'. This function does not change global hostility status between the Player, Neutral, Friendly and Hostile groups. No other groups will be switched — for these cases the function will just set the 2 groups non-hostile. This function will clear all commands from both creatures but will do nothing else.

== Examples ==

=== Party is attacked by 1 or more hostiles ===

DESIGNER:
#Assigns the 'hostile' group to each enemy

SYSTEM:
#Perception triggers combat when the enemy noticed the player

=== Party attacks a single non-hostile NPC after dialog ===

DESIGNER:
#Assigns the enemy the non-hostile group
#Runs the Combat_Start() function with the player and NPC as parameters

SYSTEM:
#Switches the NPC's group to the 'hostile' group
#Perception triggers combat automatically

=== Party attacks X non-hostile enemies after dialog ===

DESIGNER:
#Assigns all enemy the non-hostile group
#Runs the Combat_Start() function for each non-hostile NPC with the player and non-hostile NPC as parameters.
SYSTEM:
#Switches each NPC's group to the 'hostile' group
#Perception triggers combat automatically

=== X non-hostiles attack Y non-hostiles ===

DESIGNER:
#Assigns unique group IDs for both groups of NPCs
#Runs the Combat_Start() function once with a creature from each group as parameters
SYSTEM:
#Sets the 2 groups hostile towards each other (not switching groups!)
#Perception causes them to start attacking each other

=== X hostiles attack Y hostiles -> player joins in ===

DESIGNER:
#Assigns unique group IDs for both groups of NPCs
#Runs the Combat_Start() function once with a creature from each group as parameters
#Runs the Combat_Start() function once with the player and a creature from one group as parameters
#Runs the Combat_Start() function once with the player and a creature from the second group as parameters

SYSTEM:
#Sets the 2 groups hostile towards each other (not switching groups!)
#Sets the 2 groups hostile towards the player group (not switch groups!)
#Perception causes them to start attacking each other and the player's party

=== Player fights a group of enemies, one enemy surrenders ===

DESIGNER:
#Trigger combat using Combat_Start()
#Run Combat_Stop() using each enemy and the player as parameters

SYSTEM:
#Stop combat for each enemy and party member
#Change the group of each enemy to 'non-hostile' only if they are currently hostile. Otherwise, set the NPC's group and the player group as non-hostile.

← Older revision		Revision as of 16:50, 2 July 2009
Line 91:		Line 91:
	#Stop combat for each enemy and party member		#Stop combat for each enemy and party member
	#Change the group of each enemy to 'non-hostile' only if they are currently hostile. Otherwise, set the NPC's group and the player group as non-hostile.		#Change the group of each enemy to 'non-hostile' only if they are currently hostile. Otherwise, set the NPC's group and the player group as non-hostile.
		+
		+	[[Category:Creatures]]

@@ Line 1: / Line 1: @@
-!!Note: This page was imported from a year-old document, may need updating.!!
+{{infobox creature}}
 Assigning groups to creatures:
@@ Line 19: / Line 19: @@
 == Functions ==
-UT_CombatStart(object oCreatureA, object oCreatureB)
+[[UT_CombatStart]](object oCreatureA, object oCreatureB)
 Triggers combat between 2 creatures.
@@ Line 25: / Line 25: @@
 This function will switch the creature's group to be the 'hostile' group if it's current group is 'neutral' or 'friendly'. No other groups will be switched &mdash;  for these cases the function will just set the 2 groups hostile. This function does not change global hostility status between the Player, Neutral, Friendly and Hostile groups. This function does nothing else. The perception system will trigger the combat itself.
-UT_CombatStop(object oCreatureA, object oCreatureB)
+[[UT_CombatStop]](object oCreatureA, object oCreatureB)
 Stops combat between 2 creatures.