• 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

Rather Abstract Question

F

Fugh

Member
This is a little "inside baseball" and might be better in the authoring forum.

I am coding in a lot of "tent pole" things (races, factions, deities) that load or bootstrap both racial specials and feats. My question is where should I be putting the eval script? The race or the racial special or the feat?

I.E. Elves get weapon proficiency with selected weapons, this bootstraps both the racial special Elven Weapon Familiarity and the feat Elven Weapon Proficiencies. The work happens in the racial special, the feat is just a shell/placeholder.

So I guess my question is which is best or most commonly used or most efficient? Or which is just plain your favorite?
 
Bootstrap the feats to the racial special.

I presume the racial special is bootstrapped to the race?

Run the scripts on the race that validates and activates the feat / special activation.
 
The authoring kit forum is for creating your own game systems from scratch. Please keep questions that are about one of the existing game system in the folder for that system.
 
I'd say put the scripts on the thing they apply to, the object that is meant to "perform" whatever the eval script does. That way you can check more easily whether something has been disabled, and stop the script if it is.

There may be things for which that isn't the best option, for whatever reason, but that's my general answer.
 
Aaron said:
I'd say put the scripts on the thing they apply to, the object that is meant to "perform" whatever the eval script does. That way you can check more easily whether something has been disabled, and stop the script if it is.

There may be things for which that isn't the best option, for whatever reason, but that's my general answer.
Click to expand...
Agreed that's how I do it also. It just seems to make logical sense and makes locating the script when you have to change/adjust something much easier.

One exception I can think of is Class weapon proficiencies as if the tags are not on the Class you can't see the list of weapons on the "Class" tab selection window.
 
You must log in or register to reply here.
Back
Top