To allow you to select Crusader Aura to be permanently on, do the following:
Edit the file contained in: CustomClasses\Fpsware Paladin\Class Specific\Settings\UIElements.xml
Lines 126 changed to -
<Value>Automatic|Concetration Aura|Devotion Aura|Retribution Aura|Crusader Aura</Value>
Actually, it looks like there may be a typo there too which I woudln't have picked up on. Should probably have Concentration Aura rather than what is listed.
ie
<Value>Automatic|Concentration Aura|Devotion Aura|Retribution Aura|Crusader Aura</Value>
Hi1674 you know me so well
But... in this case, I (re)made most of my CCs in a way that if the end user wants to, they can edit the XML files. This allows some changes that would otherwise require you to edit the actual CC (code) files.
Mortium, thanks for pointing out the typo, I'll fix that in the next build. Fortunately, its only an aura that is rarely used.
EDIT: My next CC modification *may* include an XML file where the user can change the logic of almost any spells if they so desire. IE. you may want to change a spell to only cast given a specific situation that is not available in the UI or not coded into the CC. In this case, you could add some additional logic, or modify the existing CC logic.
Lets say (Mage, Counterspell) has the following logic:
PHP:
return Utils.CCheck(dpsSpell, "clc:" + Settings.Counterspell, "target_is:casting");
This will cast Counterspell as soon as possible, but only if the target is casting. You could make the following change:
PHP:
return
Utils.CCheck(dpsSpell, "clc:" + Settings.Counterspell, "target_is:casting","target_is:caster");
This would restrict it to CASTERS (NPCs with mana or players of a specific class) only.
This change can be done in an XML file. Basically allowing the ADVANCED user to change the CCs logic as they see fit.
