I'd love to see the attributes adjusted so you can put more than one or two words. For example, I have characters that have multiple nicknames (some of which are only used by certain characters), but I don't have room to put them all!
I'd also love to see custom attributes added. I have some characters that need attributes like Social Class, so it would be awesome if we could add our own!
I'd like to suggest for Attributes:Personality the addition of Dungeons and Dragons (D&D) Alignments. The basic 9: Lawful good, Neutral good, Chaotic good, Lawful neutral, True neutral, Chaotic neutral, Lawful evil, Neutral evil, Chaotic evil.
I'd also love to see the ability to duplicate some attributes on Basic Info. It covers a lot of bases, but assumes that characters can only have one hair or eye colour for example. Characters can have many reasons for needing multiples, such as dying their hair several times, or even dying part of their hair. They could have heterochromia. Or there could be any number or fantastical explanations in a story that require more than one skin tone, like an alien whose skin bears certain patterns.
I truly hope this comes to fruition. Being able to assign an "Innate Magical School" or "Enneagram Personality Type" with fields based off of a customized list or configuration somewhere (say, a folder in the Encyclopedia) would make Blaze exceptionally easier and more intuitive to use. It would allow true customization for a project over canned choices, especially if applied to any given article/page type. This would be a true killer feature for me and is the feature I wish for most.
In the coming few weeks, I'll probably be updating the autotagging feature in manuscript to include matching with "nicknames" in most story elements from the basic info panel. Since we'll want to give you the ability to control autotagging separately from nicknames (since multiple items might already have the same nickname), I'll probably roll out a new tag field called "Autotag Alias" which will be used to match in your text as your write.
While we realize it can be annoying to not be able to create your own attributes in that panel (or add duplicate attributes), ensuring that we have some sort of standard "structure" of the data that lives in that panel helps immensely with new features like the autotag aliases. We're really excited to have this panel be the basis for upcoming features for the site (imagine things like filtering characters for height, or selecting all characters of a certain religion, or seeing how many characters live in each country or state).
You can always use other panel types to organize data in the same way you might in the Basic Info panel, but do we think scrolling through options in the Basic Info panel can also help inspire users and get past Blank Page Syndrome as well. A lot of you are way more creative with these attributes than we could be when the team brainstormed them the first go-around, so we created a form to submit suggestions for new attributes and we encourage you to submit as many times as you'd like! We'll try to go through this form and add them into the site on a fairly regular basis.
While we hope to keep this panel as uniform as possible, we're definitely open to hearing feedback on additional ways to improve it! If there are any other interactions you'd like to have with it (perhaps a "checkbox" type attribute, or an actual calendar input for dates), let me know here - we can chat about it and I can get it on our roadmap!
Can you clarify if this means you won't be adding custom fields to the Basic Info panel, or is it still possible down the line? I personally don't mind if the data types are limited to simple strings, I just want to be able to give a basic info field its own name instead of trying to fit it into an existing category!
This is true for more than just characters. I'm working on locations and the location attribute has options for Star but not Star System, Planet but not Moon, no option for asteroid, comit, dwarf planet etc.
Implementing every option for every possible use case is impossible, but allowing users to add their own solves it easily.
In order to cater for the enormous variation in possible projects, Campfire Blaze absoluetely needs to shift from specific solutions to extremely generalized ones.
The argument that structure is a must in order for key functions to operate demonstrates, in my opinion, a failure to anticipate the needs of the target audience.
If it is still their goal, as they've stated in response to previous requests for custom attributes, to provide the ability to view associated data structures, such as deriving a country's entire population from the field that always exists as part of locations in it, then they need to create systems so that users can define these associations themselves, for their custom attributes.
Anything short of that and the Campfire Blaze team will be perpetually adding ever more specific attributes and attribute cases, while simultaneously failing to provide in any way for setting-unique features.