With the new servant handling, all planner tabs have the same values now accidentally, as they all use the same user servant object. This needs to be fixed in some way, without reintroducing the previous memory leak.
Possible solutions:
removing the central user servant list and instead having separate objects for each list, updating the objects in the planner lists when a roster update happens
reintroducing composition (user servant having a base servant field, planner servant having a user servant field) but doing it without the memory leak reappearing
With the new servant handling, all planner tabs have the same values now accidentally, as they all use the same user servant object. This needs to be fixed in some way, without reintroducing the previous memory leak.
Possible solutions: