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

Issue with @target

Hi, Hope someone can help out. For NPC attacks I've added vs AC @{target|AC} so for example Slam  vs AC @{target|AC} and for months this has worked by adding the AC of the targeted character in the attack description so we can see if the roll is a hit or a miss without having to check the characters current AC. Over the last couple of days this has stopped working so I'm wondering if anyone is aware of something having changed in the background to stop this working. Thanks in advance
1745403130
Ulti
Pro
Sheet Author
API Scripter
I've opened a ticket about  that issue on Jumpgate, and that was 4 weeks ago, but didn't receive any answer. I also posted my issue in the Jumpgate thread, and the best answer I got was 2 weeks ago " We are still investigating this as a high priority to figure out/resolve which set of circumstances cause it ". For me it seems that the bug only happens on old enough pages, so you could re-create the pages where this happens. But copying pages seems to copy the bug.
Ulti, Good to know it's not just me. For me it's occurring on new and old pages. Tried adjusting to  @{target|Bar 2} but that didn't work either. Guess I'll have to live with it and hope it starts working again soon.
1746192998
David M.
Pro
API Scripter
Not sure if it's related, but I'm seeing issues as well. The following chat commands: @{target|Choose a Target|token_id} and @{selected|token_id} are returning two different values for the same token. In addition, the target query is returning the same token_id for all tokens. I deleted these tokens and dragged new ones out. The problem seemed to disappear for a while, but came back again, this time returning a different "same" token_id for all tokens.