Jumpgate/DnD 2024 API/Mods?

I'm running a game with Jumpgate and the new DnD 2024 sheet, and EVERY mod I've tried to add throws me an "unhandled promise rejection". Does ANYTHING work with this?

The 2024 sheet is not ready. ... Sorry, there was apparently more to that sentence: "The 2024 sheet is not ready for script interaction ... ... ...even though it's been out of beta for a month and a half." Not everything has been exposed to scripts, and even when it is, the data storage model is very, VERY different from standard sheets. That means that scripts that would interact with the sheet (like ChatSetAttr or Fetch) won't work without a significant rewrite). Similarly, there are a few problems with Jumpgate... from Paths absolutely being destroyed to bugs that affect certain types of scripts. The sad fact is that trying to run a Beacon-Gate game currently is about the worst place you could be in terms of UX, and there's no telling when it will get better. There are so many corners to knock off of either the 2024 sheet or Jumpgate that it's hard to call either of them anything close to a finished product. That means most script authors are going to wait until the platform becomes more standard and the upgrade requirements become clear before they start on any refactoring of their scripts. A problem Roll20 could/should have foreseen.

Any mod that interacts with a sheet, or that interacts with paths will most likely be a showstopper on a Beacon Sheet or Jumpgate, respectively. Things that interact with tokens or the general interface (Token-mod, Dynamic Lighting Tool, Simple Sound, perhaps Roll20Audio Master, for example) will probably still largely work with a few small exceptions. Unfortunately, many of the most popular scripts are pretty much dead right now. This includes things like ChatSetAttr, Group Check, Apply Damage, half of Reporter, Group Init, It's a Trap, Combat Master, Customizable Roll Listener, a good chunk of the metascript library, half of ScriptCard's capabilities. Some of these problems might be fixable with updates to Beacon sheets or jumpgate at some point in the future. However, most of them will need to be rewritten from scratch or have parallel code added to handle Jumpgate differences. In either case, there is no current way forward. The tools (some of which are being built, to be fair), just don't exist yet.

keithcurtis said: Any mod that interacts with a sheet, or that interacts with paths will most likely be a showstopper on a Beacon Sheet or Jumpgate, respectively. Things that interact with tokens or the general interface (Token-mod, Dynamic Lighting Tool, Simple Sound, perhaps Roll20Audio Master, for example) will probably still largely work with a few small exceptions. Unfortunately, many of the most popular scripts are pretty much dead right now. This includes things like ChatSetAttr, Group Check, Apply Damage, half of Reporter, Group Init, It's a Trap, Combat Master, Customizable Roll Listener, a good chunk of the metascript library, half of ScriptCard's capabilities. Some of these problems might be fixable with updates to Beacon sheets or jumpgate at some point in the future. However, most of them will need to be rewritten from scratch or have parallel code added to handle Jumpgate differences. In either case, there is no current way forward. The tools (some of which are being built, to be fair), just don't exist yet. That's the thing. This is EVERY mod. Colornote. Coloremote. API Heartbeat. ALL of them fail with the same error.

If it's every mod, then there's a different issue going on. API Heartbeat is pretty simple and doesn't interact with anything other than a macro name. You've tried both the regular and the experimental sandbox? Do Mods crash even on a brand new blank game ? If those questions don't reveal anything, then the best bet is to gather a / Console Log ( Chrome , Firefox )and file a  Help Center Request .

keithcurtis said: If it's every mod, then there's a different issue going on. API Heartbeat is pretty simple and doesn't interact with anything other than a macro name. You've tried both the regular and the experimental sandbox? Do Mods crash even on a brand new blank game ? If those questions don't reveal anything, then the best bet is to gather a / Console Log ( Chrome , Firefox )and file a  Help Center Request . That was the issue. Trying to load the experimental sandbox crashed everything. When I changed the dropdown to default (which is apparently NOT the default on Jumpgate), worked fine. Thanks for the pointer to the solution. :)

So essentially usinf existinf 5e api scripts for dnd 2024 games won't be applicable? Things like token action maker or turn tracker/ welcome package?

There are many scripts that will work just fine in a 2024 game.  Only scripts that are manipulating the character sheet won't work with the 2024 sheet.

Or in many cases, looking up values on the sheet. Only a small percentage of values on the sheet have been "exposed" to mod scripts. And even then, there is not parity of naming conventions between the 2014/2024 sheets.

There are certainly plenty of scripts that do work with Jumpgate that have nothing to do with the 2024 sheet.  And I have some sympathy with Roll20 for not prioritizing API support versus just getting the sheet out for entry-level DM/players.  They have limited resources. Pros who can use scripts (like me) are a subset of all the players and DMs.  An important subset, but still a subset.  The basics need to work for everyone first. That said, after a bit of experimentation, I wouldn't touch the 2024 5E sheet with the proverbial 10' pole.  The thing's a trainwreck, not just for lack of script support or the fact that they still seem to be addressing basic issues two months after release, but for abandoning four decades of classic sheet design for a somewhat improved version of the D&D Beyond sheet (which I've used, and hate with a passion; constantly clicking to open and close sub-panes is not game-friendly and half the time I can't find where to adjust something without a five minute mini-quest).  I'll likely have to use it eventually, as I introduce 2024 rules to my campaign, but I won't be happy.  I want a 2014 sheet that works with 2024 rules.  That is, of course, just my opinion.  I doubt I'm alone in it though. But the lack of script support is a part my unhappiness, although that at least seems like something Roll20 can address after the basics work (if they want to).  I have homebrew scrpts that interact with the 2014 sheet, as well as using other standard ones.  I really wouldn't want to go back to a game without sheet scripts.