Virginity is a simple check (!data.children.length), same goes for cooldown index (data.status.cooldown_index), but I'm wondering how to implement it with caching in mind. It can't be permanently cached, because it can change rather quickly.
Perhaps a separate system for these two attributes, so that cattributes are loaded rapidly from localStorage and Virginity/CDI are calculated on the fly?
I think the best that can be done is to look at the table and cooldown name to determine which can certainly not be virgin and only check the ones that could be maybe.
Virginity is a simple check (!data.children.length), same goes for cooldown index (data.status.cooldown_index), but I'm wondering how to implement it with caching in mind. It can't be permanently cached, because it can change rather quickly.
Perhaps a separate system for these two attributes, so that cattributes are loaded rapidly from localStorage and Virginity/CDI are calculated on the fly?