At the moment how the caching works on UserManager is flawed due to not taking account that async methods could load older versions of the user and caching them due to possible delays or when the data was updated the same time and the other tasks updated the cache faster and dismissing the new data.
This is not major issue due to how player data loading works on login, they are requested from the database itself and all updates like add exp are handled inside the database and being returned by it and updated to the player data
At the moment how the caching works on UserManager is flawed due to not taking account that async methods could load older versions of the user and caching them due to possible delays or when the data was updated the same time and the other tasks updated the cache faster and dismissing the new data.
This is not major issue due to how player data loading works on login, they are requested from the database itself and all updates like add exp are handled inside the database and being returned by it and updated to the player data