Changes between Version 3 and Version 4 of Aura_Templates

Timestamp:

Jun 9, 2014, 8:01:17 PM (10 years ago)

Author:

sanderd17

Comment:

--

Aura_Templates

@@ -31 +31 @@
 '''Affects''' determines the classes it affects, listed as "Class1+Class2 Class3", which means Class3 OR (Class1 AND Class2). The aura will only have an effect on the listed classes.
 
-'''AffectedPlayers''' defines on which players it will act (a hero might cause the enemy to have less armour). The possible values are '''Player''' (yourself), '''Ally''', ''MutualAlly''' or '''Enemy'''. This value defaults to Player.
+'''!AffectedPlayers''' defines on which players it will act (a hero might cause the enemy to have less armour). The possible values are '''Player''' (yourself), '''Ally''', '''MutualAlly''' or '''Enemy'''. This value defaults to Player.
 
 '''Modifications''' are list of modifications that will be applied. Similarly structured as with technologies. A modification consists out of key, which presents the name of the value that will be changed, and either '''Add''' or '''Multiply''' to resp. add or multiply the value of the affected entity with something. Note that the actions should be reversible (they are reversed when the aura carrying entity is killed), so multiplications with 0 are not allowed. All other values are supported.
@@ -37 +37 @@
 Note that the list of modifiable unit properties is the same as with the Technologies (see TechModifications), but as '/' is not valid as an XML key, the '/' signs are replaced with dots. So Health.Max instead of Health/Max. 
 
-'''AuraName''' and '''AuraDescription''' are not mandatory, but will appear in various UI elements. 
+'''!AuraName''' and '''!AuraDescription''' are not mandatory, but will appear in various UI elements.