Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Macro's that work fine in an older campaign not functional in a campaign created since Data Delve.

From <a href="https://app.roll20.net/forum/post/888488/probably-" rel="nofollow">https://app.roll20.net/forum/post/888488/probably-</a>... 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. This happens for any attempt to call attributes using the target command token_name works fine. Basically, 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.
1401587950

Edited 1401587981
Riley D.
Roll20 Team
Did you add a Character Sheet template to your new campaign? Also, when you say it works fine in the old campaign, have you tried it in the old campaign since Wednesday morning? It may be something the new update broke.
1401595377

Edited 1401595415
Yes, if you reference my other post you'll see I was banging my head against the wall trying to figure it out. In order to trouble shoot, I wrote it and tested it in my friends DnD campaign (@7:30 yesterday) then copied it into MY campaign that was created the day of the release and tested it (@7:35 yesterday) but it wouldn't work so I posted here (@7:48). Precisely the same formula, both campaigns have character sheets active (the older one had character sheets added and mine was created with them from the get go). I'm no coder but the only difference between the campaigns is their age and which character sheet they use. Note: I'm not using attributes created by the character sheet in either of the test cases. Both attributes are user created.
1401596396

Edited 1401596474
I decided to run a test....The macro's work fine in any campaign in my list from before the update, but every single campaign I've created since the same macro (Copy and pasted) fails to find the variable requested. All have character sheets except one. All tested since my last post....even the ones I'd tried already. Friends old campaign: Works My Old campaign (No character sheet): 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 There's definitely something going on with newly created campaigns that is interfering with the target macro calling attributes.
I have attempted to recreate your bug, and failed. I copy-pastaed the line @{target|Defender|token_name} attempts to dodge [[((3d6)*-1)+@{target|Defender|AC}]] into three campaigns and did not get any error. Edit: I used chat commands, didn't bother to make any actual macros. My old game: Works My new game: Works Someone else's game: Works Are you absolutely sure you're not making a typo somewhere? The target attribute is recorded correctly (as an attribute, not just in the character sheet)? The token HAS a name, even if not visible to everyone? I dunno what else it would be. -Phnord
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.