• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Reading/comparing to feild contents

Bluephoenix

Well-known member
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.
 
There was a post a while back about looking at the Diety field, but if I recall correctly Mathias said it was impractical.
 
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:
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

not practical given that its user-entered text, but at least its workable.
(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 :rolleyes:)
 
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 :D
 
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 :o
 
Back
Top