Macro stopped working after last update?

%{selected|repeating_npcaction_$0_npc_action} this macro and only this macro for any new NPC's I create now. It does not give an error it just doesn't do anything. Usually it is a multi-attack and it is mostly just description text,that I use with others attached like this for two of the same attack: %{selected|repeating_npcaction_$0_npc_action} <this shows nothing at all whether I attach others or not %{selected|repeating_npcaction_$1_npc_action} < this does what it is supposed to %{selected|repeating_npcaction_$1_npc_action} < this also does what it is supposed to. I have deleted the macro and saved the NPC then re added it again saving, I have also deleted the action doing the same thing, I have reloaded the game and the campaign. I am at a loss.

I assume this is using the D&D 2014 npc sheets? Is the game on Jumpgate or legacy?

yes 2014, and it is legacy. I don't trust anything that is not finished and tested, especially if they are still working on it.

I can't seem to replicate the issue, what's the full content of the action?

Action title: Multi-attack Action text: The ogre makes two bash attacks. nothing else Just checked and it is working now.  It took almost 2 hours to recognize it? I would say it was on my end if everything else didn't work, but everything else does and did. I will update it later if the problem continues, but I have to go to work.

Since you are using the D&D 2014 sheet you can also use my  Statblock Macro Mule  for chat menus that will display NPC and PC attacks, rolls, etc.  It’s available to any subscription level, but as a Plus user you can simply import it from a game I have set up to export into your Character Vault. 

Okay just happened again except this time when I deleted and re-added it all it worked, But another macro that worked before stopped working afterward. I have plenty of memory still over 3 GB. saw something about clearing the chat archive, No dice. I had all this added a few year ago no problem then they changed how macros work again, everything was fine until the new sheet update. Now it seems to act as though there is a severe memory leak, guess I will just wait for them to discover the problem, and hopefully fix it in the next few months to a year. I can use the break from re-doing all the work I already did anyways.

The problem is still persisting the macro that was working then stopped after I re-entered a different one continues to not work. Tried making another NPC and now 2 of the macros don't work, so it is getting worse.

Hi Parker! Does the problem persist if you test in a private browsing window or on a different browser? Does it persist if you test in a different game or a copy of your existing one?

Yes it persists with different browser, yes it persists with a different game, i have tried it all. All the previous entries have no problems, and it only started after the new sheet update There are many posts coming in with similar issues since the update, there is obviously a exponential problem stemming from the new sheets and you all need to figure that out. The longer you wait the worse it is going to get, if what I am experiencing is any indication.

The problem has nothing to do with macros and everything to do with the sheet, it does not recognize the input for some reason and I have to repeatedly input the same information on multiple times while keeping the previous entries and test each one until it does register and then delete all the others it didn't. then do it all over again with the next and the next, then test them all and reenter any that no longer work, so 1 npc instead of taking 3-10 minutes takes anywhere from 40 minutes to over an hour now, before it all works.

Okay there must be something with the way the new sheets generate actions, as it only happens with actions, bonus actions, legendary actions, and mystic actions. And only the ones where there is description text only, and nothing filled out in the rest. So I am assuming there is something in the program for the new sheets that force you to enter something in the extension. And it does not recognize it if there isn't any? But why then does it eventually realize when you enter it 3-7 times? I don't know but at least it is something to help narrow it down and a place to start looking.

Skip what I just said about descriptions only now attacks are just rolling the attack and not the damage. It is getting worse every time I log on to do something.

Hmm. I am unable to duplicate this behavior. Here are my test steps D&D 5e (2014) Sheet Classic environment Mac/Chrome Create new character (NPC), open sheet. drag a short sword onto the sheet to create an action drag the default token onto the board from the Journal panel with token selected, run: %{selected|repeating_npcaction_$0_npc_action}  I get the attack rolled in chat, with attack and damage (and a buttload of description text, but that's a compendium drag bug). Alternative test ... Create new character (NPC), open sheet. create a new action called "name" with description "test" drag the default token onto the board from the Journal panel with token selected, run: %{selected|repeating_npcaction_$0_npc_action}  I get the action displayed in chat. Am I missing a step, or is there a different test I can run? If not, your best bet is to collect a  Console Log ( Chrome , Firefox ) fromt he time you get the error, and file a  Help Center Request  to get dev attention. Be sure to include detailed repro steps and a link to the game and a sample existing token for them to investigate.

keithcurtis said: Hmm. I am unable to duplicate this behavior. Here are my test steps D&D 5e (2014) Sheet Classic environment Mac/Chrome Create new character (NPC), open sheet. drag a short sword onto the sheet to create an action drag the default token onto the board from the Journal panel with token selected, run: %{selected|repeating_npcaction_$0_npc_action}  I get the attack rolled in chat, with attack and damage (and a buttload of description text, but that's a compendium drag bug). Alternative test ... Create new character (NPC), open sheet. create a new action called "name" with description "test" drag the default token onto the board from the Journal panel with token selected, run: %{selected|repeating_npcaction_$0_npc_action}  I get the action displayed in chat. Am I missing a step, or is there a different test I can run? If not, your best bet is to collect a  Console Log ( Chrome , Firefox ) fromt he time you get the error, and file a  Help Center Request  to get dev attention. Be sure to include detailed repro steps and a link to the game and a sample existing token for them to investigate. IT has nothing to do with the macros and everything to do with the sheet as when I click the action from the sheet the same thing happens nothing. There is no error message just nothing, I have to re-enter the same information 6,7,8 times now before clicking to test and one finally registers, when it started it I only had to re-enter the info only once or twice. There is nothing to show them when there is no error registered, and I am not that computer savvy to make a video or anything.

Hi Parker K.,  Could you PM me an invite to your game? I'd like to see if it is a game level issue. 

For anyone following:  The problem is in creating new entries in the D&D 5e (2014) character sheet on the NPC side of things. Example: creating a new attack, bonus action, etc.  For the most part testing in Parker's game had no problems, although there was one instance of an attack not "taking" after being created.  I suspect this may be related to some other reports of character sheets not "taking" changes, such as checkboxes not registering etc.  If this occurs again Parker will contact me so I can see if it can be reproduced. 

I just noticed that it was not updating some of the ability scores on the sheet as well, but it was still storing the correct number on the input side. I had to recheck everything and delete the number showing incorrectly and reenter to fix it. Everything after yesterday is still good, and showing correctly. Just letting people know just encase, as it is not something I immediately noticed, provably because the other was more obvious, and concerning. But everything is good now.