MOD API issues in Jumpgate w/ TOkens

Hey all I 'm having difficulties with Jumpgate utilising my coding for some quick access with the tokens for the new 2024 sheets . All of these work with the 2014 (legacy ) edition of the game but I was hoping to convert to the new sheets whilst still being able to utilise MOD API on the tokens in my game . Seemingly nothing works not even group initative or bump . Any information on solutions or if the problem is for naught would be greatly appreciated as I have a game to DM tomorrow and quickly need to either convert all the character sheets back to 2014 sheets or preferably allow my MOD API to work alongside the new Jumpgate Sheet Any information on solutions or if the problem is for naught would be greatly appreciated as I have a game to DM tomorrow and quickly need to either convert all the character sheets back to 2014 sheets or preferably allow my MOD API to work alongside the new Jumpgate Sheet , Features and Tokens . Thanks Ikarus

Hi Ikarus Adiuvat! Most mods that deal with character sheets will not work with a sheet created using Beacon (such as the 2024 sheet). Progress is being made in that area, but I personally don't foresee any time in the future where we have as rich and powerful access to the sheet's values. Virtually every script that deals with sheets will need to be re-written for Beacon as bits and pieces become available. Group Initiative is completely incompatible at the moment. I am not sure why Bump and the Token Mod macro you are showing are not working, though. Have you checked your mod page to make sure that the sandbox is running?

Keith you are a legend. Thank you so much. My main issue was with the token mod quick adjust I coded and just swapping back to the the default mod API sorted the entire problem. I am forever grateful my friend. Thanks, Ikarus

I'm guessing this is the answer to my problem as well (posted in the ScriptCards#2 thread) - many features of Scriptcards don't seem to work with Jumpgate / Beacon, specifically regarding accessing sheet attributes.

Yup. This is a well-known issue with the Beacon Sheets. They store their data in an entirely different way than classic sheets. Time of writing there is no workaround, but I do know that people are working on it.

keithcurtis said: Hi Ikarus Adiuvat! Most mods that deal with character sheets will not work with a sheet created using Beacon (such as the 2024 sheet). Progress is being made in that area, but I personally don't foresee any time in the future where we have as rich and powerful access to the sheet's values. Virtually every script that deals with sheets will need to be re-written for Beacon as bits and pieces become available. Group Initiative is completely incompatible at the moment. That is bad news. I'll wait a bit until I switch my sheets to Beacon, then.

Any news on this?

Not the sort you'll like. I don't think scripters are going to do anything until the sheet is out of beta, more finalized, and they decide whether this is a sheet that is worth supporting. Yes, the sheet emerged from it's "official" beta waaaaaaaaaaay back on Sept 17... but that was... ...prior to character leveling working ...while still suffering from a problem that causes sheets to go blank ...without the ability to link bars to custom attributes ...with an inherent data-model problem that, in order to fix character-leveling, required users to REBUILD characters they'd already built ...not to mention the score of small clerical errors that are getting detected and corrected (a modifier not applying correctly, or over-applying itself, or a bit of data being wrong, etc.)... The point is, all of that is the sort of stuff you would expect to occur during a beta test period -- a character REBUILD? on a production sheet? The Sept 17 release wasn't a production-ready release. It was a panicked "we have to have some sort of release that we call production-ready or we'll lose userbase to other platforms who will have a 2024-rules-ready sheet" release. Eventually, we'll get an announcement that everything on the sheet that is going to be exposed to the API has been exposed to the API. At that point, scripters are going to have to make a decision. Better able to determine IF they are going to be able to update their script, and knowing HOW they would need to change it, they are going to have to evaluate WHETHER they should. Is it worth it? They be looking at trustability -- the sheet has already had a POST-BETA required character rebuild; Jumpgate had a UNILATERAL reworking of path objects; Roll20 is not concerned with making changes that undermine players' lived-UX if the change aligns with an imagined "ideal-UX". Is it worth it to code if Roll20 is willing to unilaterally break things? They'll also be looking at the sheet roadmap -- will a demiplane sheet replace this one at some point, and is it worth it to code in the meantime? They'll also be looking at usage of the sheet, and other sheet options -- there are some rumblings about crowd-funding a community sheet in the style of the 2014 sheet (with all of the 2014 UX including scripts), but built to better accommodate 2024 rules. If something like that happens, scripters might opt not to update their scripts to work with Beacon sheets. As far as timing,  I've heard 3-6 months before the sheet is "stable," which I think is really optimistic... which only begins the clock on Scripters deciding what they're going to do, let alone the doing of those things.

timmaugh has pretty concisely given the current state of affairs. Even if scripters were totally on board with supporting the sheet, it isn't possible yet with the tools that are provided. Though the utility of the sheet in this regard will doubtless improve over time, I see no indication and have little hope that we will see the level of power that scripts have over classic sheets. They simply have gone too far down one development path to allow that to easily be done. Any tools they give us will necessarily be constrained by the bits they choose to expose or make available. The same thing goes for Macros. There is no way to even trigger a sheet action (like an attack) via macro. I really have no idea what the future holds. That being said, most non-sheet macros and scripts are fairly well supported, with the exception of the terrible, awful decision to flip the coordinate system on paths. This is mind-bogglingly destructive and remains completely unexplained to my knowledge. Things will improve over time, I believe, but I do not foresee a time when things will be as good as they used to be for macros and mods.

Thanks to timmaugh and keithcurtis for their state-of-the-beacon-sheet summaries. It's better to know than not to know.