![]() |
Adding Quadruped via script
I'm working on a new construct modification, for a custom, sentient construct race in a home game, to add extra legs. *note: The price and crafting reqs here are place holders for now, those details are not yet worked out.
The custom race is your standard "humanoid" shape, and the limbs are coded up as alternate race traits, the same as the other construct modifications. The intent is that a character could get these installed later in game either by having Craft Construct and meeting the other reqs and doing it themselves, or having someone else do the upgrade. I've gotten 95% of my end-goal completed. Limit 2, doesn't allow "Increase Movement Speed" modification using an EXPREQ to prohibit the combination (flavor text will justify this somehow when it's updated), but each leg increases speed by 5 feet. However, adding two legs does not increase the carry capacity for being a quadruped. I've tried a few script combinations, and my latest doesn't generate any errors, but still does not apply the effects. I'm using a total of 3 scripts: Code:
Any help/guidance is appreciated. |
Hero.Quadruped and Hero.Undersized need to be on the hero, not the race, in order to affect the character. An early script on races copies them from the race to the hero, which is how races that are always quadrupedal work, but you're assigning it pretty late - too late for that racial script.
|
Thanks Mathias. I did try
Code:
perform hero.assign[Helper.Quadruped] Thank you again!! |
I have a similar problem. I have a special feat allowing a character to change shape to a hybrid elk-centaur. This feat assigns Helper.Quadruped to the hero at First/100, yet nothing seems to happen (adjustments to CMD, in particular) though I can see that the tag is indeed on the hero. Is First/100 still too late, or should I apply the tag to the race so it is then applied to the hero? Or some other solution?
|
Nothing should ever be done before First/500 unless there's a specific reason for it - the early clutter in HL is a real problem and you should always avoid adding to it. The racial script that copies the tag from race to hero works at First/650.
There must be something else going on if your feat isn't working, because that sounds fine for the tag. |
Quote:
Is there another hidden process that would be triggered when the tag is copied from the race to the hero, but not if the tag is directly assigned to the hero from a script on a feat? |
The overrun and trip maneuvers check herofield[tNumLegs].value - if that's greater than 2, it triggers the bonuses to those materials. The only relation those have to Helper.Quadruped is that if Helper.Quadruped is on the race at First/600, then rNumLegs is set to 4 (if the initial value was 0 - that way, it saves data entry on races), and later, rNumLegs's value is copied over to tNumLegs on the hero.
The rules for those maneuvers say if you have 3+ legs you get a bonus on those, so not just quadrupeds. |
That's probably where my script is failing: as the tag is added directly to the hero by the feat, it's never on the race itself, so it does not trigger those modifications. I'll adjust the script to assign the tag to the original race. Thanks!
|
All times are GMT -8. The time now is 09:03 AM. |
Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.