Lone Wolf Development Forums  

Go Back   Lone Wolf Development Forums > Hero Lab Forums > HL - Authoring Kit


Thread Tools Display Modes
Join Date: Mar 2015
Posts: 74

Old January 25th, 2018, 02:48 AM
I have recently tinkering with an old project of mine and have a small question.

The game system in question lets you take 2 classes at character creation. When you get these classes you get a couple of abilities from them for free. There is an option, with GM permission, to change these abilities for others from the same class. To allow for this I added them with Autoadd to allow for user changing rather than as a bootstrap.

However, later in the game, you can gain a third/forth/fifth class. These extra classes do not give the free abilities.

I have a system that tags each class with the order in which it was taken (first, second, extra), but is there away to make the autoadds conditional, so they are not applied when the extra class tag is present?

Would the best option to be to create one helper ability (with the autoadds), that is conditionally bootstrapped?

I know the other option is to remove all autoadds and make the user select the class abilities themselves, I prefer setting them up correctly in the first instance, and allowing a later change.
JakeMilo is offline   #1 Reply With Quote
Senior Member
Lone Wolf Staff
Join Date: May 2005
Posts: 12,395

Old January 25th, 2018, 08:03 AM
Autoadds don't have the same conditional options that bootstraps do.

I would recommend bootstrapping these abilities, but then set up a system where the user can check a box on each bootstrapped ability to remove it, and allow it to be replaced. But use tags to mark the suppression - set up your tags so that no table will show the ability, and so that scripts on the ability won't run, and anything bootstrapped by these abilities will have a component script that travels to their root pick, notices that tag, and assigns the same tag to itself.

(Oh, minor detail - make sure that there's a single table that never hides the abilities - and that that's the only table where you're actually showing the "remove" checkbox - they just turn gray on that table if the box is checked. That way, if the user accidentally checks the box, the ability doesn't immediately vanish, preventing them from un-checking the box).
Mathias is offline   #2 Reply With Quote
Join Date: Mar 2015
Posts: 74

Old January 26th, 2018, 12:39 AM
Thanks for getting back to me Mathias.
JakeMilo is offline   #3 Reply With Quote

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT -8. The time now is 08:35 PM.

Powered by vBulletin® - Copyright ©2000 - 2019, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.