Oh wow, that does look really good.
Yeah, I'm just worried it's another design element to juggle/master but I think it will be worth it. Quite like the idea of colour coding the core books (maybe sections)Left off the the fairy, war mechanoid and immortal coz they on the other table as might be odd too duplicate them when we have a visual table style.
Right, its fine when its just text, but I think it It'd be cumbersome coupled with the pictures.Color coding seems genuis to me.
If you don't mind my well-intended nitpicking:* 10 and 12 are misspelled in the pictures* class descriptions didn't end in a full stop, race descriptions do* Quirk isn't capitalised in the bullet points* the last bullet point should end in a full stop* "Each Chart Corresponds" should be "Each chart corresponds"* without the actual list of Quirks I can't say much, but the difference between a Quirk and Trait is not clear from these few pages
Quirk will have a visual table and starts on the next page which will make everything much clearer. I have a slight layout issue where I have a large amount of white space at the bottom of the right page (under the QUirk description) but it's not enough to put the first row of the Quirk Table on. I may shunt it over to the next page to keep them together.
...but maybe we can make the distinction clearer in the text too.
E.g a Trait is a broad brush stroke in defining you character's core. Quirk is what makes them unique/special/different.
So, a Trait is like a sort of concept or archetype (e.g. master thief, brave knight, or vengeful young noble), whereas a Quirk is a small and special thing that have mechanics not necessarily tied to the Aptitudes, right?
That sums it up pretty nicely. I could add a little bulleted summary of each quality to the intro, maybe?
Quality meaning; Trait, Calling, Quirk, etc
Yes!!Would tie all the concepts together and give reader holistic view prior to reading the whole section!And I turn it into a nice flow chart :-)
If your layout allows it, I personally would appreciate it (but again, with the examples provided that may be unnecessary).
I'll add it to my "to-do's"