Utility: FG Print Tool (Print campaigns or character sheets)

Quote:

---

Originally Posted by LordEntrails

I have been unable to resolve Advanced Stories. This is because each story entry is made of of multiple <block> elements and I don't know enough to get the for-select command to work.

---

I don't know anything about coding but I can contribute to problem solving through brainstorming. i.e: this html example from Brave's AI assistant:

Attachment 61863

Especially if this part can be translated into xsl:

• Wrap each block element (e.g., paragraphs, headings, lists) within an <option> element. This will create a menu option for each block element.
• Ensure each <option> element has a value attribute containing a unique value for the corresponding block element. If no value attribute is included, the value defaults to the text contained inside the element.

https://www.w3schools.com/tags/tag_select.asp has some test codes to run.

# XSL version

"Choose" command is used in this, I imagine this can be added to the code to make the dropdown menu (if I understand the problem correctly) to have more blocks.

Attachment 61864


Hope this helps.

Thanks. I'm working on updating my map images at the moment but will get back to this shortly. I'll post what I figure out. Appreciate the ideas :)

Quote:

---

Originally Posted by LordEntrails

Thanks. I'm working on updating my map images at the moment but will get back to this shortly. I'll post what I figure out. Appreciate the ideas :)

---

Happy to help :) No need to rush. Thank you for working on this util, it would be a loss to see it broken.

Curious what the status of this is, and what i need to click on to have a working version in 2025.

Quote:

---

Originally Posted by lousilver

Curious what the status of this is, and what i need to click on to have a working version in 2025.

---

It should still be working. Check the first post and download a copy from there. Let us know if you have any trouble running it and what operating system you have.

I didn't see FGPrintTool.exe in the zip file. I ran FG Character Tool.exe. it's running in unity.

I picked PringCampaign_5E.xsl
I picked my campaign.

All i see are NPCs and item records, no stories. I use the book, so my stories aren't numbered like in the video. but i didn't see any stories in the output.xml

windows 10

also, sometimes the file browser has corrupted text so you can't read files. I tried changing the xml source because i had picked the wrong one, and the field became perma blank, so i had to restart the program.

Yes, the PrintCampaign_5E.xsl uses the path for basic Story entries in the campaign and does not point to the reference manual/advanced story entries. The path would need to be changed in the XSL file to appoint to this new location. The easiest way to do that is to make a duplicate of the XSL file for your own use and then modify it. Look at your campaign's db.xml file to see the path structure of where your data is located and then modify the story section to use this path instead.

Quote:

---

Originally Posted by ddavison

Yes, the PrintCampaign_5E.xsl uses the path for basic Story entries in the campaign and does not point to the reference manual/advanced story entries. The path would need to be changed in the XSL file to appoint to this new location. The easiest way to do that is to make a duplicate of the XSL file for your own use and then modify it. Look at your campaign's db.xml file to see the path structure of where your data is located and then modify the story section to use this path instead.

---

I had some mild success. I noticed that simple stories are termed 'encounter', and that advanced stories are 'refmanualdata'. So I saved a copy of PrintCampaign_5E.xsl and replaced all instances of the former with the latter. This resulted in the titles of each record being included in the output, which was actually in record order rather than alphabetical order so that was nice. but none of the record content was included. I suspect this might be due to the a difference in the internal structure between simple and advanced stories, as the latter can have multiple blocks. maybe i can puzzle this out later.

Exactly. You are on the right track. The refmanualdata nodes have children nodes for the various blocks of text that are included, along with extra information for any frames our layouts you have.

You can leave the story one there and duplicate it so it looks at the refmanualdata records. Then you will need to look at the children of those nodes and make templates for the children. Finally call the appy-templates for each of the children so it knows how you want to format the output. You can probably map various frames to new CSS classes that resemble the same styling options.

If you use something like ChatGPT, just make sure to tell it that it has to be compatible with XSL 1.0. There are lots of new and easy to use features in later versions of XSLT but Unity only supports the 1.0 version.

See the xml files I have uploaded to earlier in this thread to see what improvements I've made. Please share any improvements you make.
edit: my simple efforts did not come up with a way to export advanced stories. I'm sure it's achievable, I just haven't tried very hard as I don't currently have the need for advanced story export.

I was able to cobble some frankenstein solution together that served my need. but it is not robust, and I'd be hesitant to unleash it on the universe. However, if someone is trying to print an advanced story instead of a simple story with a single block in it, then this works. Essentially you replace all instances of 'encounter' with 'refmanualdata', then find this block and replace <xsl:apply-templates select="text" /> with <xsl:apply-templates select="./blocks/*/text" />.

Code:

---

  <xsl:template match="//refmanualdata/category">
        <div class="page">
            <xsl:for-each select="./*">
                <div class="story">
                <a>
                    <xsl:attribute name="name">
                        <xsl:value-of select="name()" />
                    </xsl:attribute>
                </a>                           
                <h1><xsl:value-of select="./name" /></h1>
                <xsl:apply-templates select="./blocks/*/text" />
                </div>
            </xsl:for-each>                               
        </div>   
    </xsl:template>

---

Would love to see this as a Linux usable program as well

Quote:

---

Originally Posted by LordEntrails

See the xml files I have uploaded to earlier in this thread to see what improvements I've made.

---

&

Quote:

---

Originally Posted by lousilver

I was able to cobble some frankenstein solution together that served my need. but it is not robust, and I'd be hesitant to unleash it on the universe. However, if someone is trying to print an advanced story instead of a simple story with a single block in it, then this works.

---

Feedback on the printed material: I used the latest 5e LE file from LordEntrails and edited it as per lousilver's code. Here's the result.

* Almost all the text is there.
* There's no pics, links, header block and the text in it, or the text in frames.
* The arrangement of the titles in printed material is not the same as the source material. This may be due to Pages created in different time (i.e: 02. Index is created way after 059. Blah blah)
* If there is coding characters such as "<>" in the text, print tool doesn't show them.

* It prints beautiful tables, even with alternating colors
* Chat bubble is nice white frame (no links created if there is a link to web)

My module consists only in text & tables, I don't know about character sheets & feats / spells, etc.
Hope this helps.

Quote:

---

Originally Posted by Tempered7

* The arrangement of the titles in printed material is not the same as the source material. This may be due to Pages created in different time (i.e: 02. Index is created way after 059. Blah blah)

---

It's by record id, not index id. Each time you create a new advanced story it gets record id + 1. but if it was actually inserted between indexed page 1 & 3, it will get printed after them, not in between as desired. This may also apply to the blocks within the story itself.

You could change this by redirecting the for loop over the index rather than the record id, but then you'd have to "look up" the record id from the index, rather than iterate over the records directly. Or you could do what i did, and create each story in index order. Also keep in mind that advanced stories are found in the story tab, if you don't save them to a group, the sit unassigned. and if you delete it from the index, it is NOT deleted from the story records. So you will have orphaned story records, unless you delete them directly.

I understood only some parts of what you wrote but failed at creating that loop even though I tried for 2 days. Coding is hard.
Thanks for explaining though. From now on, I'll write the text to player notes and then everything is finished I'll pass them to index.
Your edit on Lord's xsl file still printed everything so I can recreate the module in another ruleset and add the text easily.

Thank you all who worked on this app :)

Hi all, forgive me if this has been mentioned before.
I've created a Legacy 5e campaign and would like to print the character sheets.
Using the tool from this thread (2022 version) I can get a basic sheet but there is no spell information for my spellcasters and the fonts are all over the place - giant text in some fields, etc.
I've tried each of the 5E XML sheet options supplied with the tool and get similar results.

Starting to work on this again. Working on getting Advanced Stories/Ref Manual/Campaign Books to print. If anyone has made any improvements since the last updates and is up to sharing, would appreciate it :)

Significant improvements have been made for campaign export of D&D 5E, both Legacy and 2024 formats. The following objects are supported: Encounters, Random Encounters, Images (in Advanced Stories), Items, NPCs, Parcels, Tables, Vehicles, Locations, Quests, Basic Stories, Advanced Stories, Spells. The following is not supported, but I plan to figure this out: Story Templates. The following are not exported and I don't have plans to add them; Backgrounds, Classes, Feats, Skills, and Species.

Requirements/Restrictions

• All items have to be local to the campaign, including images and tokens
  
  • except NPC tokens from an encounter that is linked in a story, for now. See below.
  
  
• For images to render in the html output they need to be placed in folders relative to the html file
  
  • /tokens
  • /campaign/images or /images (not sure which one this xslt is using...)
  
  
• Two columns in advanced stories are not exported in two columns, they are converted sequentially, left then right. This meets my needs but others may desire to change this behavior.
• NPC stat blocks will include Portraits, then Tokens, then 3D Flat images if they exist

Known Issues

• Story Templates are untested, I have not done anything with them so...
• Random Encounters are untested, but the code accounts for it and should work.
• I've tried to remove the token images from the Encounter links embedded in Stories but have failed. No idea where they are coming from.
• Links in stories to Spells and other Stories don't work, the hyperlink is always wrong.
• Formatting of Locations is minimal.
• Objects are exported according to there db ID, which is based on the prder they are created, not the order they appear in the campaign book.

I've included both the .xsl file and a sample db.xml file I've been testing with. I did not include images so you will need to replace those.

Edit: sorting alphabetical was easier than I expected. Have not updated the xslt here, but it's just having to fully define the sort for stories and advanced stories. The code is:

Code:

---

<xsl:template match="//encounter/category">
    <div class="page">
        <xsl:for-each select="./*">
            <xsl:sort select="name" order="ascending" data-type="text" />
<div class="story">
...

---

and

Code:

---

<xsl:template match="//reference/refmanualdata/category | //reference/refmanualdata[not(category)]">
    <div class="page">
        <xsl:for-each select="./*">
            <xsl:sort select="name" order="ascending" data-type="text" />
...

---

Quote:

---

Originally Posted by QuothDRaven191

Hi all, forgive me if this has been mentioned before.
I've created a Legacy 5e campaign and would like to print the character sheets.
Using the tool from this thread (2022 version) I can get a basic sheet but there is no spell information for my spellcasters and the fonts are all over the place - giant text in some fields, etc.
I've tried each of the 5E XML sheet options supplied with the tool and get similar results.

---

This is probably because the spells are not contained in the campaign, they are referenced from modules that you have loaded. This tool can only export from campaign content, not loaded modules.

Quote:

---

Originally Posted by LordEntrails

This is probably because the spells are not contained in the campaign, they are referenced from modules that you have loaded. This tool can only export from campaign content, not loaded modules.

---

Spell data is copied to the character sheet when spells are added to the character sheet by drag/drop. The data should be there in the exported character sheet XML.