Open Zarhog opened 1 month ago
This requires a code refactor to support it as currently the class tab contains all the code for both subclass and class, which interact dynamically. Splitting them into two separate tabs is non-trivial as a result. Also this same change will have to be made for Level Up [#107]. So these two issues are interdependent. I would suggest that #107 should be done first. Then the Level Up application would need to be similarly refactored to support an extra tab for the subclass.
(noted) i will plan my budget accordingly :)
This is a request to sepereate the tow due to how long class text is, i belive it would be A. Visual better and B. be a better visual indicator if subclass is needed