Investigate Attribute Lists

Oliver commented

2026-04-09 19:25:21 +00:00

Owner

Problem:
Having many attributes causes the character sheet to become very unwieldy to use.

Solution:
We should have some way to have a more condensed view of all (or a subset) of the attributes.

This was originally requested by: @firevisor in Discord

Problem: Having many attributes causes the character sheet to become very unwieldy to use. Solution: We should have some way to have a more condensed view of all (or a subset) of the attributes. --- This was originally requested by: `@firevisor` in Discord

Oliver added this to the v3.0.0 milestone 2026-04-09 19:25:21 +00:00

Oliver added the

labels 2026-04-09 19:25:21 +00:00

Oliver commented

2026-04-13 06:38:42 +00:00

Author

Owner

The implementation of this is going to be done via a new tab. Each attribute will have a new property indicating whether it's above the fold or not. And the tab will only appear if any of the attributes are set to appear below the fold.

Oliver commented

2026-04-17 06:04:51 +00:00

Author

Owner

Maybe... I think I could use Items for attributes, as they can be accessed synchronously for the roll data, and the token updating can be done via async updating. I need to investigate whether or not these could be properly detected as token attributes, because that would be the primary detractor from doing it this way.

Another thing that would be super annoying is trying to do a data migration, since there currently isn't any system version indicator within the settings or elsewhere. The migration will probably need to be a one-time migration that runs on world start in order to move all of the Actor-data attributes into correctly formatted attribute items

Maybe... I think I could use Items for attributes, as they can be accessed synchronously for the roll data, and the token updating can be done via async updating. I need to investigate whether or not these could be properly detected as token attributes, because that would be the primary detractor from doing it this way. Another thing that would be super annoying is trying to do a data migration, since there currently isn't any system version indicator within the settings or elsewhere. The migration will probably need to be a one-time migration that runs on world start in order to move all of the Actor-data attributes into correctly formatted attribute items

Oliver commented

2026-04-19 17:32:17 +00:00

Author

Owner

Problems Solved:

Detecting Attribute Items as token values:
- This is solved by adding a prepareDerivedData to the Actor data model that collates all of the items into the correct attributes
- No additional overriding needs to be done in the TokenDocument
Updating Attribute Items from token:
- This can be done by adding a preUpdate to actors that redirects the update from the Actor into the item, the cause for this being preUpdate is that it should also happen when updating one the attribute values via the raw API
- The resulting token update flow is a bit weird, but should be a better solution in the long-term than only allowing those updates to be forwarded via the modifyTokenAttribute function itself

Problems Solved: - Detecting Attribute Items as token values: - This is solved by adding a `prepareDerivedData` to the Actor data model that collates all of the items into the correct attributes - No additional overriding needs to be done in the TokenDocument - Updating Attribute Items from token: - This can be done by adding a preUpdate to actors that redirects the update from the Actor into the item, the cause for this being preUpdate is that it should also happen when updating one the attribute values via the raw API - The resulting token update flow is a bit weird, but should be a better solution in the long-term than only allowing those updates to be forwarded via the `modifyTokenAttribute` function itself

Oliver added reference feature/attribute-items

2026-04-19 21:16:00 +00:00

Oliver closed this issue

2026-04-27 02:13:11 +00:00

Rows
Columns

Investigate Attribute Lists #66