you should be able to use @{target|HP|bar1} / @{target|HP|bar1|max}. but at the moment it is bugged, and removes the second target|HP|, leaving the @{bar1|max} and adding another } to the end. the bug here is that it reformats itself incorrectly upon saving. this is easily repeatable, by making a macro that targets max value of any attribute or bar and saving it. this is how I believe it should work: basically, it means you have to name your target to pull a max value (this is true of any max value, whether a bar or an attribute). its not clearly stated in the wiki (at last check) but the format for pulling a target value is {target|value} for a simple check on current value of a single target, and to allow for multiple targets in a single macro there is a naming convention. By adding a name to a target you end up with this: {target|name|value} so, by putting in {target|value|max} you are actually naming the target value and searching for the value of max, which is incorrect. I have found that it is a good habit to name ALL your target checks as you make macros, as this get you in the habit of doing it correctly for more complex checks. as a side-note, using multiple targets in not documented, but entirely possible. you can use target to pull in opposed skill checks as needed, by using target rather than selected to allow for very quick and easy management of things like bluff vs sense motive, sleight of hand vs spot, intimidate vs level check, and so on. by having it use two targets (skillName and target or vs are my preferences for opposed checks such as these) you simply click the macro and then select your first target, then the target rolling the opposed check. very nice and tidy, especially in a gm whisper that puts it into one easy to read line. an example(in use in my current d20 game): /w DM @{target|sleight of hand|token_name}'s sleight of hand [[1d20+@{target|sleight of hand|sleight-of-hand}+@{target|sleight of hand|dex}]] vs @{target|vs|token_name}'s spot [[1d20+@{target|vs|spot}+@{target|vs|wis}]] as you can see, you can use spacing in your target names, and it is simple enough to make them descriptive, as it will print the target name when asking you for that target, making it easy to know which target you are currently picking. of course, that example requires the targets to have the relevant stats on their journal sheets, but I find that if you work with a template it is easy enough to make sure that each character has every skill even if at skill level 0 on their sheets.
