Roll20 keeps wanting to load the 5e (2014) character sheet

This isn't causing me serious malfunctions (yet), but it's a PitA that takes time and attention every time I load up my game. I'm starting up a small D&D 5E (2024) game, which I created as such. At some point, though, Roll20 got the idea that I'm running a mixed 2014/2024 game, because whenever I load the game up I get a little message: Just a heads up.... It looks like the content you selected uses a different sheet than the one set for your game, so we've automatically enabled both sheets for you. Check it out! Sometimes it has, in fact, automatically loaded the D&D 5E (2014) Sheet alongside the 2024 (which I then unload, which sometimes takes multiple tries); other times, it simply shows a prompt in the Settings > Game Character Sheets to add the 2014 sheet (which I do not click on). I did at one point transmogrify in some 2014 "NPCs" (AoE templates, actually), but when I unloaded the 2014 character sheet, they all got booted to the Archive folder, from which I can neither delete or fix them.  Every character/NPC in the Journal is now only 2024. My concern is that I've seen remarks about mixed-character-sheet games having problems, and if for some reason this game thinks it's "mixed," no matter how often I try to indicate otherwise,  I'm worried other problems might crop up.   How do I f igure out what content is making Roll20 think I have or want the 2014 character sheet?  I've done enough work in this game that I really don't want to have to rebuild it from scratch.

Hi *** Dave,  Load the 2014 character sheet into your game. If that doesn't automatically unarchive the 2014 characters then please do so manually.  Next, delete them.  Then you should be able to remove the 2014 sheet without any notifications. (Assuming you are not using a published module that used 2014 sheets.) Archived characters are not removed from the game, they are just 'out of sight'. They are still technically present in the Journal tab, so not every character/NPC is only 2024 in your game's Journal tab.

Aha! I will give that a try -- thanks!

*** Dave said: My concern is that I've seen remarks about mixed-character-sheet games having problems, and if for some reason this game thinks it's "mixed," no matter how often I try to indicate otherwise,  I'm worried other problems might crop up.   I am currently running a mixed-sheet game. Other than some macros not being able to read from both sheets in the same call, I haven't run into any serious problems. Is there anything in particular you've heard or run across?

And it worked perfectly.  Thanks again, @Gauss!

Hey, @keithcurtis -- main issue I ran across was, in fact, with macros and mods/APIs and the like. The inconsistency of what worked with which seemed like it would be a problem, and struck my paranoid developer heart as increasing the likelihood of some future bad drug interaction. (I.e., I may be over-reacting, but just running clean with one or the other seems like the safest bet.)

Most of those issues are because of using macros geared towards one sheet with the other. Complicating this is a not-uncommon error people make where they use the same name for multiple characters. The system doesn't know which character to pull from when the name is the same.  None of that should be damaging, it'll just throw an error or have an unexpected result. 

*** Dave said: Hey, @keithcurtis -- main issue I ran across was, in fact, with macros and mods/APIs and the like. The inconsistency of what worked with which seemed like it would be a problem, and struck my paranoid developer heart as increasing the likelihood of some future bad drug interaction. (I.e., I may be over-reacting, but just running clean with one or the other seems like the safest bet.) Yeah, Mod scripts are gradually being modified and updated to work with the Beacon sheet. Not a simple process, but progress is being made. I think the cross-sheet macro is not going to ever be a thing, though. A macro launched by a 2014 sheet cannot get values from a 2024 sheet (thus making  Macro Character Sheetst  very difficult to maintain), and vice versa. And a generic macro that can affect either sheet, cannot affect both sheets in one call. Fortunately, as macros go, this latter is not that common. But the limitation is going to be there. My campaign is mixed because I have so much automation invested in the 2014 sheet that I'd be loathe to give it up. I applaud your courage in making the jump!

Thanks. Our main campaign, which is just starting up, uses a 5e/2014 module, so it made sense to run it in the legacy character sheet and all.  We're also starting another game for Tuesday nights that we want to be a bit lighter weight, so it seemed to be an opportunity to start learning about 5.5e/2024. For both I played with seeing if we could do it a blend, but the issues between the two character sheets and the Mod/macro jiggery-pokery needed to make it kinda-sorta work ... well, made me think that the KISS principle applies and trying to keep them "pure" within their version would be easiest.