Member
Join Date: Nov 2010
Posts: 70
|
while entering the stats for the millennial chainmail relic (MIC p.20), I found myself needing to compare to the Deity usertext field in order to check if the character meets the requirements for the item.
having looked through the pick/tag lists in debug and found nothing I figured I might get an answer here. still looking for other usable examples, will post back if i find one. |
#1 |
Senior Member
Volunteer Data File Contributor
Join Date: Mar 2007
Posts: 1,245
|
There was a post a while back about looking at the Diety field, but if I recall correctly Mathias said it was impractical.
|
#2 |
Member
Join Date: Nov 2010
Posts: 70
|
thats a shame, as its the only way I can think of turning on/off the relic powers for the chainmail (and other relics) since that is usually the only trigger.
perhaps while Impractical it might work in this case as it is triggering (or not) an ability rather than a prerequisite for a class or other addition to the character. edit: found the quick and dirty method, which I might use for the relic as a trigger and leave a note in the item summary/description to check deity spelling. Code:
@valid = 0 var result as number result = compare(hero.child[background].field[bDeity].text, "Somename") if (result = 0) then @valid = 1 endif also as I understand, the original reason for not including deity as a drop-list or menu similar to classes was potential size based on the available material. Given that the feats list alone is now massive, and that there is excellent source control (dragonlance and other campaign settings added/removed at hero configuration) perhaps Lonewolf might take a second look at adding functionality for conditions and requirements based on deities. a short list after taking some thought: Favored Weapons Domain Restriction Relic Triggers and Requirements Alignment Restrictions (reduces error potential) Class Restrictions and Requirements other misc ability triggers. Last edited by Bluephoenix; November 16th, 2010 at 03:10 PM. |
#3 |
Member
Join Date: Nov 2010
Posts: 70
|
created a trigger script for the chainmail that works, with a caveat regarding the spelling requirements and that reconizes the correct spelling regardless of capitalization.
Code:
var result as number var testspell as number testspell = compare(hero.child[background].field[bDeity].text, "Corellon Laerthian") if (testspell = 0) then result = compare(hero.child[background].field[bDeity].text, "Corellon Laerthian") elseif(testspell = 1) then result = compare(hero.child[background].field[bDeity].text, "corellon laerthian") endif if (result = 0) then hero.child[xFastHeal].field[Value].value = 3 endif (imho anyone playing with deity-triggered relics should be intelligent enough to read the warning/caveat, but I'm sure I'll be proven wrong somewhere ) |
#4 |
Senior Member
Volunteer Data File Contributor
Join Date: Mar 2007
Posts: 1,245
|
Corellon Laerthian is a hard one. I always want to spell it "Corellon Larethian"
|
#5 |
Member
Join Date: Nov 2010
Posts: 70
|
yeah, I put a (Check Deity Spelling!) addendum to the warnings for the eval rules, should sort it if it pops up as a warning.
on other notes, I think I'm finally getting the hang of the tag/pick/etc ids and scripting system |
#6 |
Senior Member
Join Date: Feb 2007
Location: Nottinghamshire, United Kingdom
Posts: 1,265
|
Quote:
link to wikipedia https://secure.wikimedia.org/wikiped...llon_Larethian |
|
#7 |
Member
Join Date: Nov 2010
Posts: 70
|
Doh! I should go back and fix that....
been so used to writing it that way for years I guess I proved myself wrong then |
#8 |
|
|