You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A lot of actors have a note on languages such as "Understands Sylvan but cannot speak" or similar. Currently we input these in the languages.custom field, but this then appears as a language of its own. For example it would end up with both "Sylvan" and "(understands but cannot speak)". It would be good if each language had some further configuration available.
where config would be an (extension of) ObjectField where users can define, for each language, whether they are unable to read, speak, and/or write it.
As for displaying it on the actor sheet, perhaps a similar method to what is currently done for physical damage bypasses (mgc, sil, ada) with icons rather than long-form notes.
A lot of actors have a note on languages such as "Understands Sylvan but cannot speak" or similar. Currently we input these in the
languages.custom
field, but this then appears as a language of its own. For example it would end up with both "Sylvan" and "(understands but cannot speak)". It would be good if each language had some further configuration available.The data could possibly appear like,
where
config
would be an (extension of)ObjectField
where users can define, for each language, whether they are unable to read, speak, and/or write it.As for displaying it on the actor sheet, perhaps a similar method to what is currently done for physical damage bypasses (mgc, sil, ada) with icons rather than long-form notes.
Possibly related: #1982
The text was updated successfully, but these errors were encountered: