Probably something stupid, what am I doing wrong

I'm calling on attributes from a target with @{target|Attacker|Dodge} and it keeps reporting that it can't find the attribute. I've tried troubleshooting with many different attributes including stings, integers, and dice rolls. None of the attributes will work. What am I missing? I've used this in other campaigns for things like AC just fine. @{target|Attacker|token_name} works fine so I can't figure out the issue

Is the token linked to the character sheet? That would explain why token_name (a property of the token) works but Dodge (an attribute of the character) doesn't.

It appears that you'll requesting an optional parameter that doesn't exist (dodge) The format should be @{Target|AttributeName} without the third optional param. example: @{Target|Dodge} would return the value of the 'Dodge' attribute of the selected target. @{Target|Attacker} would return the value of the 'Attacker' attribute of the selected target. If you're trying to use multiple targets in your macro you have to call them separately. @{target|TargetABC|Dodge} and @{target|TargetXYZ|Dodge} respectively. (where TargetABC can be any name you want to call it as long as they're different) *** Or more simply, as Brian suggested, your token may not be linked to a character sheet where the attribute you're referencing exists

@Brian, definitely linked @Mark The second parameter is the prompt title (also used as a variable) you can prompt multiple different targets that prompt different names in the grey box at the top of the screen. See my macro below that is known to work. Good idea though @Kristin I'm pretty sure I tried both and I'm almost certain it's capped. Trying everyones suggestions now. I'll edit this post with my results EDIT: Just tried all this and it was all case sensitive. I even went through and changed everything to be consistently lowercase just to be sure. No go.... At least I don't feel as stupid now... Here is an example that I know works vs the one I was using now Works /em stabs with his wakizashi, the jagged blade ripping flesh. at @{target|Victim|token_name } [[1d20+@{BAB}+((floor(@{DEX-base}+@{DEX-enhance})/2)-5)+@{Attack4Enhancement}+(((?{Number of attacks this round?|1})-1)*(-5))]] vs ([[ @{target|Victim|AC} ]]) AC for [[1d6+((floor(@STR-base})/2)-5)+@{Attack4Enhancement}+((?{Sneak Attack?|0})*(@{sneakattack}d6)) ]] slashing or piercing damage and [[2d6]] bleed damage plus [[2d6]] Acid and [[2d6]] Holy ^^^This one even had a call the pull the Fort attribute for a poison resist until this last update when I removed it for consistency with the other players (The GM would use the roll, until it rolled poorly for his boss and he tried to say he got to roll it, all I ask for is consistency :P) Broken - NONE of the attribute calls work except token name /emas @{target|Attacker|token_name} strikes a foe. [[((3d6)*-1)+(?{Skill|0}+?{Modifier|0})]] /emas @{target|Defender|token_name} Tries to defend [[((3d6)*-1)+( @{target|Defender|dodge}) ]] /emas @{target|Attacker|token_name} deals @{target|Attacker|attacktype } damage [[(( @{target|Attacker|attack} -(?{DR|0}))*( @{target|Attacker|dmgmulti}) )]]

OK I'm going to go ahead an post a bug report. If I take this macro @{target|Defender|token_name} attempts to dodge [[((3d6)*-1)+@{target|Defender|AC}]] and put it into the DnD campaign that is my friend has been running for 8 months or so it works fine, but if I plug the same macro (with the appropriate Attribute created for AC) into my brand new campaign that I'm trying to make for gurps I get the error and it can't find the attributes. Basically I'm not crazy or stupid, it works PERFECT in one campaign and does not work at all in a new campaign. Progress is halted on my game until this can get figured out.

do you have the new character sheets enabled? They function by creating attributes and if you happen to have the same naming convention you end up with duplicates that throw a wrench in things.

I do have character sheets enabled but they don't use the attributes I'm trying to call on. I did check for that since on release day I was reading threads where people character sheets weren't working correctly because of that. Pathfinder uses AC-Dodge, AC-misc, AC-Flat and some others. My user created value that I continue to reference (so I don't break all my old macros more than I have to) is just AC. Gurps doesn't use an AC variable at all so it's wholly unique to that campaign. Thanks for the suggestion though, this is the kind of lateral thinking that I'm hoping will come up with a solution. When I get off work I think I'll create another campaign and test the macro in that one, and also in one of my other old campaigns to see if I can find a pattern. There's definitely something fishy going on here since it will work fine in one campaign and not in another.

Test Results (I decided I had time while I was still on lunch ^_^) Friends old campaign: Works My Old campaign: Works My NEW GURPS campaign: Doesn't work My NEW bug test 1 GURPS campaign: Doesn't work My NEW bug test 2 Pathfinder campaign: Doesn't work

Tinker , please send me a join link to both your working and broken campaigns. Perhaps I can figure out why things are not working.

I'm not having problems now (Last confirmed at 12 pm my time [in china] that there was an issue). One of my campaigns didn't have the character sheet attached correctly but one of the test campaigns did. I'm going to chalk it up to the aforementioned stupid thing on my end and assume I fixed something that wasn't obvious while messing around with things. It still boggles my mind though. The token did have a name....some of the tokens were attached to sheets, some weren't (but were set as the default token, which I know isn't good enough). Thanks for the feedback and help, I'm not sure if something I followed here did it or something changed elsewhere but it's now functioning.

Ok, if it comes up again let us know.

Will do, I'm pretty sure it was something dumb on my part. I'm the "primary tech guy" for our other campaign. But that speaks more to the others disinterest or lack of skill rather than to my exceptional talents ^_^ I just wish I knew what changed. Now for the fun part of figuring out how much I can macro gurps out. It's such a delightfully terrible system, this should be fun.