I use the Codex to manage a large LitRPG project with many specialized entries stored under the Other entry type, including classes, abilities, resources, attributes, status effects, factions, and species. Custom Categories provide a useful way to associate tags with particular entry types. However, the Associated Custom Details section appears to support only dropdown custom details. It does not allow me to associate other custom-detail types, such as Line, Text, or Codex Reference. This prevents me from creating a complete reusable structure for entries identified by a particular tag or custom category. For example, I would like to create an Ability category associated with the Ability tag. When I create or classify an Other entry as an Ability, Novelcrafter should automatically make the relevant Ability custom details available. Those details might include: * Ability Category as a dropdown * Resource Cost as a line field * Governing Class as a Codex Reference * Progression Rules as a text field At present, I cannot associate most of these fields with the Ability category or tag. I must remember which custom details belong to each kind of entry and add them manually every time. This becomes frustrating and time-consuming in a large project. It also increases the risk of inconsistent entries, forgotten fields, and custom details being added to the wrong type of record. I would like Custom Categories to support associating every available custom-detail type, including: * Line * Text * Dropdown * Codex Reference * Any other supported custom-detail format Ideally, Novelcrafter would use the entry’s primary type and assigned tag or custom category to determine which custom details belong to that entry. When the relevant tag is applied, the associated fields should become available automatically. Removing the tag could hide those fields without deleting any values already entered. I understand that this association could function purely as a visual organization feature. It would not need to alter how custom-detail values work, provide additional AI context, or create a functional relationship between the tag and the stored information. Simply showing the appropriate custom details when an entry has the associated type or tag would be an extremely helpful quality-of-life improvement. This would make the Other entry type much more practical for projects that require several specialized subtypes. It would also let authors create consistent templates for concepts that do not fit Character, Location, Object, Lore, or Subplot. Please consider expanding Associated Custom Details beyond dropdown fields and allowing custom details to be connected to custom categories or their associated tags. Even as a visual association, this change would remove a large amount of repetitive setup and make complex Codex projects easier to maintain.
