I'm just going to skip this week's poll to ask you what feature you would like to see added next, because I can guess your answer: The Mystic.
However, the Mystic is a large UA article, with all the subclasses, psionic disciplines and psionic talents. So, please don't expect me to tackle this one fully in a short time scale. I can probably do a quick release today/tomorrow that includes the Mystic, as long as it doesn't need to include the psionic disciplines.
The psionic disciplines are something completely new that none of the other classes has. It basically is a class feature that grants you a certain number of choices, similar to the Warlock Invocations, but the amount of explanatory text and options per discipline is unprecedented.I can do them the same way as other optional choices for classes and put them on the third page (e.g. Warlock Invocations), but there really isn't enough space to put 10 psionic disciplines -and- 4 psionic talents in that section.
Thus, the question I have for you is:How would you like to see the psionic disciplines be handled by the sheet?
EDIT: By selecting either of the "Just get the mystic out ASAP!" options, I will have the sheet include the psionic disciplines as an option to be put on the third-page notes section, but without the disciplines having any descriptions.
EDIT2: Some people are suggesting to making a new page just for class features or for all of these type of 'extra' class features that are now going to the third page's notes section.Although I really appreciate your suggestions and I don't want to take away from your input on this project, I do want to explain why that wouldn't work as an end-all future-proof remedy.If, for example, I would make a page that is solely dedicated to class features, that page would need to have a single, big, multi-line text field where all the class features would go into, as Acrobat doesn't make it possible to detect if a field is full, so the automation will never be able to take anything that is overflowing in a field and move it to another field. Then, this field will only be a bit longer than the current class feature field. Meaning that there still will be a lot of multiclassing scenarios where this field will overflow, all the while having a character sheet that is less aesthetic and less practical.If, in another example, I would have the sheet no longer use the notes section on the third page and instead make a dedicated page for these kind of overflow class features, it would have the exact some problems as mentioned in the above example. The page would be a single, big text field, which would only come in handy for those multiclassing scenarios where you suddenly need a lot of space for these kind of 'extra' features.My suggested work-around for both these problems is to have you simply take a good look at your generated character and move the text to your desired location. This is the entire reason that the sheet is editable and WYSIWYG, so that the automation doesn't 'force' you to adhere to any kind of standard, while keeping everything working smoothly for any single-classed character.Again, I don't want to diminish your desire to make suggestions, as I read all of them! I just feel that this discussion has gotten a bit off track and given some of you the idea that there is a simply fix for these kind of questions for the future by making a page with a single multi-line text field.