Quote Originally Posted by Grekumah View Post
This is something that is difficult for us to address at the moment as we would have to send data each time you open the menu to see which tier you currently have. We're concerned about this largely affecting UI response time.

Similarly the same holds true for saving the data client-side as well. Since all of the trait data for this would have to be saved, it would consume large amounts of memory, which also makes this feature difficult to implement.
From a strictly technical perspective - lets assume that you have, on average, 14 job traits. The Tier information only requires 1 byte of data per job trait - so that is 14 bytes of extra transmitted data. 14 bytes of memory client side to store this information.

This would literally have no measurable impact on UI performance or memory footprint.