Currently, the Subclass handler caches progressions separately from how the rest of the Framework does. We could simplify that section of the code by using the Utils.CacheOrRetrieveProgression function (or Utils.CacheOrRetrieve(guid, type) introduced in PR #52 , and use up less memory.
Currently, the Subclass handler caches progressions separately from how the rest of the Framework does. We could simplify that section of the code by using the
Utils.CacheOrRetrieveProgression
function (orUtils.CacheOrRetrieve(guid, type)
introduced in PR #52 , and use up less memory.