GURPS Monster Hunters 1 - preliminary data file. Anyone want to finish it?

RobKamm · 08-15-2011, 07:05 PM

I've been playing with the Commando template with an eye towards testing Eric's possible solution. Sadly, no, adding the aliaslist to the subsequent select list doesn't seem to work (but it doesn't crash the program, so that's something).

I think I'll experiment with a dummy-trait in each of the character template selects. Something like "_MotivationalLensTrait". The cost would be variable and defined by the user. It would be taboo to itself (thus calling attention to it for subsequent replacement). The user would then need to go to a separate Motivational Lens Additional Choices template to select the appropriate trait(s). This is pretty ugly, and would require close use of the book -- users couldn't just sit down at the computer and whip out a character easily.

It has been suggested that the motivational lenses could be done as separate templates called from within the character templates. The problem here is that when you call a template (lens) from within a template you can't have select lists in the subordinate lens.

I'm thinking that we'll have to use the alternative technique. Have a hidden attribute, call it MotivationalLensCount, that defaults to 0. Each lens then gives(+1 to ST:MotivationalLens). Then include a needs(ST:MotivationalLens = 1) in the character templates. This will leave an unfulfilled needs in GCA that can be picked up by the user by going in and selecting an appropriate lens from a separate list of templates.

I'll upload to the repository in the next couple of days with a working sample using the Commando and at least a couple of the lenses in place.

08-15-2011, 07:05 PM	#13
RobKamm Join Date: Sep 2004 Location: Chicago	Re: GURPS Monster Hunters 1 - preliminary data file. Anyone want to finish it? I've been playing with the Commando template with an eye towards testing Eric's possible solution. Sadly, no, adding the aliaslist to the subsequent select list doesn't seem to work (but it doesn't crash the program, so that's something). I think I'll experiment with a dummy-trait in each of the character template selects. Something like "_MotivationalLensTrait". The cost would be variable and defined by the user. It would be taboo to itself (thus calling attention to it for subsequent replacement). The user would then need to go to a separate Motivational Lens Additional Choices template to select the appropriate trait(s). This is pretty ugly, and would require close use of the book -- users couldn't just sit down at the computer and whip out a character easily. It has been suggested that the motivational lenses could be done as separate templates called from within the character templates. The problem here is that when you call a template (lens) from within a template you can't have select lists in the subordinate lens. I'm thinking that we'll have to use the alternative technique. Have a hidden attribute, call it MotivationalLensCount, that defaults to 0. Each lens then gives(+1 to ST:MotivationalLens). Then include a needs(ST:MotivationalLens = 1) in the character templates. This will leave an unfulfilled needs in GCA that can be picked up by the user by going in and selecting an appropriate lens from a separate list of templates. I'll upload to the repository in the next couple of days with a working sample using the Commando and at least a couple of the lenses in place.