You are right, basically i have some properties that need to be initialized based on the initial attributes when you create a new pc (Initial SAN, breaking point, max wp, initial WP), after the character is created any further change on those attributes will only change the max WP and none of the other properties. To do so i had used an hidden flag that is triggered once the attributes are changed by the user for the first time. I had 3 options for doing it 1) i make the hidden flag non hidden (through a toggle) and i hope that the players remember to trigger it when they start the game 2) i let all the attributes empty so that thr player is forced to fill them at least once 3) Since it's incredibly rare that a player would manage to finish a scenario without losing SAN,HP, and WP., i would initialize at character creation the values of tge attributes to their default value (10), and the flag will be trigger the first time the player change the Attributes or the first time they change the initial SAN, WP or HP. The change of color was for option 3 to give the player a visual reminder: the color of WP, HP, SAN would have been red until you either set the attributes or you modify the initial values of SAN, WP, HP. (This is why i needed to change color to the input) Option 1 would have been nice to implement but it would have ruined the design of the sheet so i discarded it (moreover it would have meant makinf a one time button that wasn't really necessary). Option 3 had several advantages but there were limit cases (homescenes and ritual) that would have make it risky to implement. In the end i went with option 2 that was the simplest one but requires a bit more work from the player.