2024 Character Sheet Macros/Token Actions

Roll20 has stated on Twitter and their roadmap that macro support has already been added. However, i t seems there are still a number of features that don't work regarding macros on the 2024 character sheet. Here are some of the things I tried. Token actions don't support "selected|" macros. When I type them in the chat with a selected 2024 character token, they work. But from token actions, they don't. It says no tokens are selected, but it's a token action. They only appear when the token is selected. The repeating attributes don't exist. I tried using one of the repeating attacks from a 2014 character, selected a 2024 character, and pasted it into the chat. It works for the 2014 character, but not the 2024 character which doesn't recognize the repeating attack macro.

Hi Sillvva, As for the second bullet point, the structure of character data is verrrrrrrrrrrrrrrrrrrrrrrry different for a beacon sheet compared to a non-beacon sheet. In fact, it's going to be verrrrrrrrrrrrrrrrrrry different from one beacon sheet to the next (i.e., from "DnD 5E 2024" to "Marvel" to "Despised: User Base v20" )... a fact that is going to break most system-agnostic scripts. We were promised "100% parity", but that probably doesn't include mapping attribute names (or methods of referencing) from the 2014 sheet to the 2024 sheet. Meaning that existing macros/abilities would have to be rebuilt. Unfortunately there is no documentation for the sheet at the moment... so we're left with something we've been told works without actually being able to, you know, make it work. As for your first bullet, I can reproduce this. Are you using Jumpgate? It seems that these messages are being sent with the token (or character as the speaker). Here is a token-action-button-spawned-message from legacy (on the left) compared to one from Jumpgate (on the right): "Geopsis" is the name of the character/token. My guess is that the character is the "who" of the message, that's where the game is looking for any selected tokens -- and it will, of course, not find any. I would suggest opening a ticket for this. I will try to do the same.

timmaugh said: As for the second bullet point, the structure of character data is verrrrrrrrrrrrrrrrrrrrrrrry different for a beacon sheet compared to a non-beacon sheet. In fact, it's going to be verrrrrrrrrrrrrrrrrrry different from one beacon sheet to the next (i.e., from "DnD 5E 2024" to "Marvel" to "Despised: User Base v20" )... a fact that is going to break most system-agnostic scripts. This is why Beacon is a massive mistake. What is the point of a unified VTT if no element is compatible with another?

Tuo said: timmaugh said: As for the second bullet point, the structure of character data is verrrrrrrrrrrrrrrrrrrrrrrry different for a beacon sheet compared to a non-beacon sheet. In fact, it's going to be verrrrrrrrrrrrrrrrrrry different from one beacon sheet to the next (i.e., from "DnD 5E 2024" to "Marvel" to "Despised: User Base v20" )... a fact that is going to break most system-agnostic scripts. This is why Beacon is a massive mistake. What is the point of a unified VTT if no element is compatible with another? I completely agree. And specifically about scripts... Scripts are a MASSIVE value-add for Pro membership, and a value that Roll20 didn't have to build or maintain. It was like the best possible racket: they get all the free labor of people writing the scripts *and* they get the Pro membership money from people wanting to use those scripts. All they had to do was not screw it over. And the way they're implementing Beacon is screwing it over. I don't think I'm alone in saying that scripts are the ONLY reason I have Pro.

As for your first bullet, I can reproduce this. Are you using Jumpgate? Yes, I added it to my character creation room to try it out. Thankfully everything still works with my 2014 sheets, so I just have to manually enter every single detail on a 2014 sheet, since the 2024 compendium doesn't work on those.