Content Addition · Articles & templates · Created by
DCoward
declined
plaintext plain-text entry
What functionality is missing? What is unsatisfying with the current situation?
I'd like to be able to designate "Human" or any other race without needing to link to an article. It bogs down how many items I have and I feel compelled to fill them out or at least move them in a reasonable location in my organization. The same want applies to ethnicity, rank, really anything that ostensibly needs to link to another article.
How does this feature request address the current situation?
While it's fine to have the option to link to articles, having an option for plaintext would be a simple accommodation for people who are working on things like a DnD campaign or a location in real life where it may not exactly be necessary to create these articles in order to say what they are. For instance, everyone knows what humans are in a generic sense. This addition accommodates the want of being descriptive about the details of a character without needing to clutter workspace if everyone is expected to know what a given thing is.
What are other uses for this feature request?
As alluded to, this doesn't just stop at race or ethnicity, but those are big ones. Especially in the context of a DnD campaign or something adjacent to that, where you have a lot of races that are already extremely detailed - you simply don't want to have to make an article for "elf", nor "half-elf", nor "half-orc" etc. Sometimes you do for homebrew changes, but generally? A lot of this is assumed knowledge. Expanding this to every applicable option that requires an article, but instead could have a plaintext placeholder would greatly assist with workflow as well (less starting and stopping).
The Team's Response
This feature already existed under the name "Variables"
Current score
20/300 Votes · +1150 points