bug with %{selected|NPCActionX}

Detailed Description of the Problem hi roll20 team 1st off i love the work and i am loving the site and all the updates 2ed my spelling is very bad and i apologize now so recently i was adding in monsters for my DND 5e campaign and was using the npc sheet that is provided after filling out the Actions ( and enter in any of the textboxes brake the macros at the point the enter is located) i added in the token action using %{selected|NPCAction1} for row 1 and so on, but when i used the macro button all i got was "%{selected|NPCAction2}" after sum trouble shooting (i have a diploma in software development) i found that if the name of the macro is NPCAction2 the macro fails and just returns "%{selected|NPCAction2}" Steps to Reproduce the Problem naming the macro sum thing like Bite it works fine Description of Your Setup Operating System Windows Windows 8.1 Screen Resolution 2560 x 1440 Web Browser Chrome 41.0.2272.89 Browser Size 1262 x 1301 Color Depth 24 bit Javascript Enabled Flash Version 17.0.-1 Cookies Enabled

Hi Mason, I'm not having any issues calling the actions with the %{selected|NPCAction#} syntax. For example: This rolls the roll template when I use %{selected|NPCAction1} } The one caveat I'd give is that the roll templates do not handle multiline text fields correctly at the time. If your Description or Effect field has an returns in them it will break the template.

hi sorry if i was not clear, when the name is NPCAction2 the macro will not run For example:{ and you get } but when the name is Bite (or anything els) then it works fine this shows the problem the best running the macros from token macro bar the second macro with the name of NPCAction2 the returns %{selected|NPCAction2}

That's because you're overriding the sheet NPCAction2 macro with the one on the Attributes & Abilities page or your campaign macros. It's just calling itself.

HoneyBadger said: That's because you're overriding the sheet NPCAction2 macro with the one on the Attributes & Abilities page or your campaign macros. It's just calling itself. oh. of cores that is the problem now i understand, thanks for getting back to me hopefully this will help anyone els with the same problem