Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Pathfinder 1e sheet transfer

Via the Community Sheet, I was able to import a substantial number of characters.   But... my players prefer the standard Roll20 Sheet as that is what we have used for years and they are comfortable with.   What I noticed is that most information (Attributes, Classes, etc.) do not carry over when I switch the sheet template on the game. How do I get all these characters to transfer between sheets?  This is a HUGE effort to do manually for the entire campaign...
1670736090
Gauss
Forum Champion
If they don't have the same attributes there is really no way to do so.  My suggestion in that case would be to duplicate your campaign, then in the duplicate switch the character sheets.  Next, put them up side by side in two windows. Open the same character in both games. Start manually reproducing the data.  It will go a lot faster than switching back and forth. 
@Gauss, thank you for the reply.  I can do the same from the original HeroLab with side x side..   just A LOT of npc's and monsters.  As indicated, a big effort to do it manually in addition to the maps, characters, tokens, scenarios, etc...   That they are not compatible is disappointing, to say the least.  At a minimum I would have expected some standardization in the meta-data elements.  I guess I expected the sheets to be more UI than execution.
1670738940
Gauss
Forum Champion
ben n. said: @Gauss, thank you for the reply.  I can do the same from the original HeroLab with side x side..   just A LOT of npc's and monsters.  As indicated, a big effort to do it manually in addition to the maps, characters, tokens, scenarios, etc...   That they are not compatible is disappointing, to say the least.  At a minimum I would have expected some standardization in the meta-data elements.  I guess I expected the sheets to be more UI than execution. Every sheet is whatever the coder made it, there is no standardization that I am aware of. It is as simple as 'what did they name the Attribute' that could be causing things to break.  BUT, I am not an expert on sheets (just using them), so maybe someone will come along with some information that will help. Maybe a browser extension or API script could do the job. IF someone were to make one. (Note: API scripts require a Pro account.)
1670776946
Kraynic
Pro
Sheet Author
Just a little clarification on what Gauss is saying here.  The attribute name in question is what is set in the html, not the label you see.  This html attribute is what gets used when you manually create macros: @{attributenamehere}.  As an example, the character sheet you start with may use "str" for strength, but the one you switch to uses "strength", then that attribute will not display on the new sheet (though you may be able to find it on the Attributes & Abilities tab.  Since it is using a different html label, that means that any sheetworker set up to calculate a strength modifier will not pick up the original value, since it is looking for the label used in that sheet, not the previous one.  The strength modifier may or may not be labeled differently as well. Another thing to keep in mind is that all that information that no longer lines up with the html designations of the new sheet still exists.  All of that is stored as part of the sheet data, but simply doesn't display because it doesn't match up with the new sheet html structure.  This is especially true of repeating sections: inventory, spells, feats, etc.  This means that if you change sheets mid-game and then recreate whatever info doesn't display in the new sheet, you are running with sheets that have nearly double the data saved in them than if you had recreated the characters from the start.  It is definitely more work to start fresh, but it is best to start fresh if you want your character sheets to be as slim and fast as they can be.
I get it..  long time software engineer myself, so CCSS, style sheets, etc. is all natural to me.  It's the lack of standardization, or at least published elements, that irk me.  I won't even get into the lack of import and/or conversion here, but if the underlying character database has standard elements, then these should be published and enforced by roll20 for community sheets and such.