I've searched through the wiki, and maybe I'm not just finding it. I think this is just a syntax problem. Say I've got a big robot with 6 hit locations, and I want to show the general status of its HP on a token bar. My locations have attributes on the character sheet backend, @{StructureHead} @{StructureTorso} etc, manually entered since the system only uses single HP totals and thus only has one HP attribute not six separate ones. Each total has a current and max value, and I'm hoping to combine the six totals together and link that to a single bar on a token. While it may not show that a limb has been blown off, peppering the target with multiple hits that scatter between the locations should diminish the bar enough for the general damage to be evident at a glance. I know this can be done, because some of the D&D sheets combine current HP and temp HP on the same bar, but I'm not figuring out the syntax. EDIT: That might require pro sub for the API, which is over my head at this point. Nothing against upping my sub to pro, but the learning curve made my ears bleed. I tried making a seventh attribute, @{StructureCombined} then had it reference the other six added together, but it doesn't seem to calculate. Of course, I think the necessity of @{Selected|StructureCombined} or @{UnitName|StructureCombined} is likely to interfere with it. Does it require the target's unique name for an attribute to reference another attribute? (I tried variations of that, but haven't guessed the correct syntax) Is there a different way to have a bar on a token call a value other than selecting the attribute from the drop-down? I'm trying to avoid needing the unit's unique name, given that I want this to be a general macro for a range of such robots (PCs are mecha-pilots often fighting other mecha, in a game system that isn't mecha-friendly and thus house-ruled halfway to the moon). Thus far I have a mountain of macros that all rely on @{Selected|X} and @{Target|X} given that I'm literally writing hundreds of macros here, so needing the unit's unique name would make this much more intensive (may not have any choice though).