2024 Monster Stat Blocks Do Not Import Into Games With Spellcasting Enabled

When you import a 2024 D&D Monster into a Jumpgate game, using the Legacy sheets, it does not have the "Spellcasting NPC" box checked, which means that the spells are not shown by default.  Once you go in and check the box, it will then show all the spell as correct and expected. Once the box is checked, you also need to manually go in and set the correct Spellcasting Ability, which is defaulted to "None" still. If this was intentional (for loading speed maybe?) then I believe it should be changed, as not only is this quite frustrating to have to go in and enable, especially if you are importing many sheets at a time, but for people who aren't aware or beginners they might not have any idea what is wrong or how to fix it.  I've tested across multiple different stat blocks, it seems to be pretty universal for 2024 monsters with spellcasting abilities.  Using both Chromium based browser and Firefox. This is when pulling from the Compendium inside a Jumpgate game.

(image did not get included with original post)

Hi JmanX! Yup, this is for the same reason you cannot drag a 2024 spell to a 2014 sheet. The data structure is incompatible. Backward compatibility is limited, and this is unlikely to change.

keithcurtis said: Hi JmanX! Yup, this is for the same reason you cannot drag a 2024 spell to a 2014 sheet. The data structure is incompatible. Backward compatibility is limited, and this is unlikely to change. Hey Keith, the thing is though, the spells ARE there on the sheets.  Once you click the Spellcasting NPC check box they all appear. All that needs to change is to make sure that box is checked and the right spellcasting ability is set.  This doesn't appear to be that kind of issue since all the spells are imported correctly, just not visible at first.

Huh. That's news to me. I don't know if it's new behavior or I just never explored deeply enough. It appears that all of the spells are still the 2014 versions, though. My guess is that it is matching the name, and providing spell content that matches the data structure needed by the sheet (i.e. 2014 spells go on a 2014 sheet). That's very interesting. Thanks for the  find! I worked on a script a while back that looks for spells cast by the 2014 sheet and whispers a link to the 2024 version in the compendium (assuming you have the PHB). It doesn't cast the 2024 version, but it does give you a reference. Would that be of value?

I have posted the script here, for anyone interested: [Script] 2024 Spell Reference for Dual Sheet Games

Hi Keith, that is a useful script.  But it does not solve this bug/error, which I'm hoping by pointing out here can be solved by having whoever is responsible for setting up these sheets to go in and check the "Spellcasting NPC" boxes and set the correct Spellcasting Ability.  Thanks for trying to help though :)

Right. The script was tangential. If you want to call Roll20's attention to the issue, though, the best way is a  Help Center Request . The 2014 does not seem to be a major focus, so you may not see an immediate solution, but every report emphasizes the need for a fix.