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.

I believe these three threads are the best hints for others on this subject:OneTwoThree

Using that knowledge and Mathias posts in here, I have a panel_class.dat file now, which spawns new tabs for each class bootstrapped to the hero. Also chatting with RavenX, the way to customize the panel is to have one panel definition and express tags to turn on/off different types of class features (spells, bonus feats, etc).

Pathfinder class agent uses a unique cHelpWiz and a copy of cWizard for each level in the class. Is this required for agent processing? Or is it simply a relic of Pathfinder's need to track level by level for things like favored class features and similar?

Plus I still don't understand how to do pathfinder style Primary, Secondary, Tertiary, Quad framework (like Ranger Bonus Feat and etc). I'm turning all my stuff into one fixed table and they choose options. So there will be a helper custom for each choice. A waste of picks/things/memory.

Mathias may be taking a break Post-GenCon. I'm hoping once he gets back he can help us all out (well at least me), and explain a couple of things I can't seem to get.

Namely, how to structure the agent side of things like "Bonus Monk Feats" and the like. Where, you have generic slots (1, 2, 3, and 4) for doing generic class features and have the agent tab handle all the interface. The closest I can get is to not do anything similar, and to bootstrap a thing per class feature and display all class features needing choices in a table. That isn't ideal and can lead to scrolling. Not to mention it is more difficult to determine if you picked duplicates and other issues.