The way I was going to go with a Pathfinder Gestalt addon was similar to how I implemented the play test for Mythic characters. You have the player add "three" characters. One is your Wizard, one is your Cleric, and one is a "gestalt" class. The gestalt class lets you pick your two classes for "level 1" it then figures out your saves, skills, and hit points and assigns it to itself. It then takes the wizard class and cleric levels and takes them out of the leveling process. You end up with a Level 1 character with three classes but two of them are only used for their "Class Specials" and the "Gestalt" class is used for Skills, HP, BAB, Caster Level, and saves.
At level "2" you add two more class levels of say wizard/cleric but could be other classes. And on the Gestalt class tab you would have a class special to pick the level two classes. As we are taking the two classes out of the leveling process we should have no problem supporting characters up to level 20. The gestalt class just has 20 class specials allowing for picking two classes that are combine together. Granted its not "perfect" but it will allow you to easily combine any two classes and it will support two caster classes. Obviously its allot of work and I have not even finished it in Pathfinder (other than theory) but that was my "idea" to fix the issue. |
Quote:
|
Quote:
Basically you strip all "hero.hitdice" tags and reset the hero fields (tHitDice) yourself manually at like post-levels/10. Which in Pathfinder at least is "right" after all the class and Hit Dice have been calculated. So I then remove all the hitdice tags and reset fields to zero. This also included BAB and Save Progression values which will be pulled from the Gestalt class. Then "recalculate" those Hit Dice values and re-add the tags back to the hero. In this case changing the addition of "3HD" of classes into 1HD of classes. Everything from that point forwards sees "1HD" of classes. :D Then at least in Pathfinder I also had found a special "tag" that when applied to a class would remove the "hit Point" area of the classes so that the wizard/cleric couldn't type in their hit point and instead it would only be placed onto the "gestalt" level. In theory Pathfinder is built from the code base of d20 so it "should" all work. Of course in theory the bumble bee can't fly! ;) |
So you created a new tab named Gestalt, or you created a new class named gestalt?
Quote:
|
Quote:
|
That would be lovely if it were possible, that wouldn't be a fix, but a full on permanent solution but in order to do that you'd need extensive knowledge of how hero labs was coded wouldn't you?
And staff permission to change how the program functioned. Yikes, thats.. yikes. |
Quote:
I am just putting out an "idea" but not one that is "easy". ;) :p Quote:
So the above is a theory for how someone like Sendric maybe able to build something for the community. The variant or archetype methods do currently work for both "d20 and pathfinder". |
Quote:
BTW, this was more or less the path I was heading down anyway. The area I ran into major trouble was removing the other class(es) from the skills tab. Any ideas on how to do that would be greatly appreciated. |
Gestalt(s) are the 2nd ed. multiclassing method brought to 3.5 through Unearthed Arcana. Taking two classes and taking the better options between the two. They're new classes in their own right. If you're going to edit source code, you might just want to build a new gestalt component based similarly on classes that uses a foreach loop and takes the best progression from each class. You will end up with a lot of scripts doing it this way though. It will be time intensive to do it though.
Have you tried building a new Gestalt class instead? You could use pull down menus possibly and then tell hero lab to make the class features available through tags. You'd still need the foreach loops, but it would take less time to build. |
Quote:
Ultimately, there may not be a good solution with how the d20 system is currently set up. |
All times are GMT -8. The time now is 02:49 PM. |
Powered by vBulletin® - Copyright ©2000 - 2024, vBulletin Solutions, Inc.
wolflair.com copyright ©1998-2016 Lone Wolf Development, Inc. View our Privacy Policy here.