GenKitty  said:  The system will look to the 'Character Sheet' tab before it looks to your 'Attributes & Abilities' tab for values.  The builtin character sheet will fill your attributes&abilities page with a lot of... less useful things. Only stuff made via the built-in character sheet will auto-update, because those are the only fields the sheet knows about and you can't tell it to look at these other, user-created, fields. And sometimes it will utterly hijack your ability-macros in the weirdest of ways that I can't diagnose.   I don't know what you're talking about, Kitty. All attributes on the character sheet are backed by attributes on the Attributes & Abilities page. The character sheet is simply something for presenting the data that was already functioning as part of the system. "Less useful things" is being disingenuous to the character sheet authors, who generally spend a lot of time making the sheet work and have everything you need for the character.   Issues between attributes on a character sheet and attributes created manually are a matter of naming conflicts, especially if you create an attribute with the same name as an autocalc field and give it a different value.  Also, I feel like it's kind of rude to imply that character sheets aren't worth using when helping someone trying to learn the system, especially considering the effort the community puts into the various sheets.     Secret Wizard  said:  Apparently, the @thing to bring up an attribute only works for the attributes listed on the character, which makes sense. However, these attributes seem to automatically update with the character and the ones I create do not.  Is that kind of upkeep mandatory? Why can't I create attributes that auto-update with the character sheet info?    I'm not entirely sure what you mean by "auto-update", nor what you're doing where changing a character sheet value works for attributes in a macro, but changing a manually-created attribute does not.  Character sheets have "autocalc fields", which are attributes that reference other attributes, and the display on the character sheet tab is automatically updated by applying the formula. Beyond that, nothing updates automatically, though (and even that isn't  technically  automatic, as the autocalc field isn't actually changing, just the attributes that it uses for the calculation). If you change the value of the attribute, no matter where it comes from, the value is updated when you use it in a macro.     Secret Wizard  said:  Another thing that bothers me is that when I create characters they get all these "junk" attributes, like @Will-trait and stuff like that, but they don't get a simple @Will attribute.  Is there any way to get newly made character sheets to only get the useful attributes or a preset number of attributes?    @{will} exists on the Pathfinder sheet, however it is an autocalc field using @{willbase}, @{willabilitymod}, @{willmagicmod}, @{willmiscmod}, and @{willtempmod}. If you tried to define your own @{will}, it could cause problems since there already exists an autocalc @{will}. However, the pathfinder sheet does not have @{willpower} or @{will-save} or something, so creating one would not create conflicts.  I will grant that a character sheet will create many more attributes than you would create yourself if you were making a character without a character sheet present (sheet authors generally creature attributes to enable functionality like tabs on the sheet, and copy the game's paper sheet presentation in order to be familiar to players, including breakdown of calculated characteristics which means more backing attributes), and this can make it difficult yo  find  an attribute you need on the third tab. At this time, there is no way to prevent that. There are plans in the future to have alternate configurations available, instead of every character in the campaign using the same thing. Once implemented, that  might  let you for example create an NPC sheet with few or no attributes, while creating a fully functional PC sheet for your players. That's in the future, though.