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

FX error on automations

Tested new fx on macro and receive this error message TypeError: E.replaceAll is not a function This is my macro %{-OeNiFFN06IHJy0F8Zyu|repeating_attack_Vwvl0pcqc_attack} /fx beam-acid @{selected|token_id} @{target|token_id}
1763594753
Gauss
Forum Champion
Hi Ozzy,  Unfortunately that is not the real macro. You need to supply the output of the command ( %{.....} ).  Which character sheet are you using?
1763596222

Edited 1763596829
Ozzy
Pro
Gauss  said: Hi Ozzy,  Unfortunately that is not the real macro. You need to supply the output of the command ( %{.....} ).         This macro was created by clicking on the 3 dots of the fire bolt spell. And the spell is working. Which character sheet are you using?      2024
1763609738
Gauss
Forum Champion
Odd, I got the error once just using the /fx command.  Can you test the /fx command all by itself and see if it happens again?
1763656772

Edited 1763656991
Ozzy
Pro
Running only the /fx command, it works corretly. Could it be a conflict with an exinting API? I' running SmartAoE, for exemple.
1763672258

Edited 1763672387
Gauss
Forum Champion
Ozzy,  In my testing in one game just running the fx command is borked. I created a new game and tested and the command worked fine.  Then I tested in the new game a macro that is the Fire Bolt command with /fx command after (as stated above in the thread) and it worked.  So I am guessing there is something wrong with certain characters. This is something that is going to require the Devs.  I suggest filing a Help Center request with Roll20, make sure you check your console log when you get the error. I am seeing a console log error generated when the chat error is generated. 
Thanks