I have figured out how to get the Character stats above the bonuses in the Character Builder. However, I can't figure out how to do the same for the Exported character sheet. The bonuses always end up on top. How do I change this so the stats are on top and the bonuses are in the little circles below?
I would just like to know why we can't choose what version of the character sheet to use?? I really dont like the default sheet style I would much prefer something more closely resembling the traditional character sheets downloaded from WotC. Just makes it easier since I've used those sheets since the start of 5e. Just think it should be a choice what style sheet you prefer is all.
I would just like to know why we can't choose what version of the character sheet to use?? I really dont like the default sheet style I would much prefer something more closely resembling the traditional character sheets downloaded from WotC. Just makes it easier since I've used those sheets since the start of 5e. Just think it should be a choice what style sheet you prefer is all.
The character sheet data is available as JSON, just writing your own parser, apply some transformation and create your own.
If Jason is a programmer you are all set, otherwise good luck ! The JSON format of the character sheet is not for the faint of heart, especially as it does not have the final values like a plain final Armor Class value.
you make your request like there's someone sitting around thinking that the style of the exported sheet is in the first 20 pages of their todo list. ...a feature which adds no additional capabilities to the web site or brings any new revenue. i like greg's feedback. if you don't like the way it looks, change it. if you don't know how, figure it out.
I didn’t request a gorram thing. You better check yourself and then go back and check who requested what.
If Jason is a programmer you are all set, otherwise good luck ! The JSON format of the character sheet is not for the faint of heart, especially as it does not have the final values like a plain final Armor Class value.
Back it up a few steps for my edification please. What is a JSON, what does it mean, what does it do, and where/how would one even go about finding one. And if one does locate a JSON, what does one do with it? I presume it doesn’t go into a toaster.
Basically, explain it like you would explain it to a 40 year old Gen Xer who last did any computer programming back when Windows 3.1 was still “new” and never did it again after that.
If Jason is a programmer you are all set, otherwise good luck ! The JSON format of the character sheet is not for the faint of heart, especially as it does not have the final values like a plain final Armor Class value.
Back it up a few steps for my edification please. What is a JSON, what does it mean, what does it do, and where/how would one even go about finding one. And if one does locate a JSON, what does one do with it? I presume it doesn’t go into a toaster.
Basically, explain it like you would explain it to a 40 year old Gen Xer who last did any computer programming back when Windows 3.1 was still “new” and never did it again after that.
So you can type a reply on this forum, you are typing "plain text" just good old a,b,c etc. But you have a little toolbar with buttons B I U to bold things, italics things, etc. That toolbar transforms your text into HTML e.g. <html><b>this is now bold</b> and <u>this is underlined</u></html> HTML is a structured text document. The structure is for instance each opening "tag" e.g. <b> is accompanied by a closing tag e.g. </b>.
JSON is another "structured text document". The structure is a "key" and a value e.g. "character name" : "legolas". An value can be a list of values. e.g. "attributes" : [ "strength": "13", "intelligence": "14", "wisdom" : "12", "dexterity" : "19", "constitution" : "13", "charisma" : "15"] ]
Ideally DDB would define as simple a JSON structure as possible to provide the character sheet content needed to create a character sheet. e.g. "character sheet" : [ "attributes" : [blah] , "saving throws" : [blah], weapons, skills, spells etc]
Once you have something in JSON you can take any modern programming or scripting language (Javascript, Java, etc) to manipulate it and populate another structured text document such as Microsoft Word XML, or HTML or populate a PDF file in order to create your own personalized beautiful custom character sheet.
Thank you for taking the time. Okay. I’m good w/ html, I have no problem fixing stuff here w/ html. We used that back in the day. So JSON is a different language that does similar things, kinda like the tooltips too I suppose. I imagine that it is easier to work with than html, or that it is more compatible with newer stuff that you mentioned like java. Is it preferable because it is easier to define your own values? Have I got that close enough to follow a conversation?
Thank you for taking the time. Okay. I’m good w/ html, I have no problem fixing stuff here w/ html. We used that back in the day. So JSON is a different language that does similar things, kinda like the tooltips too I suppose. I imagine that it is easier to work with than html, or that it is more compatible with newer stuff that you mentioned like java. Is it preferable because it is easier to define your own values? Have I got that close enough to follow a conversation?
HTML is structured for browsers to display the data as a formatted document, not for pure data, XML is a structured text that uses tags and designed for pure data. It looks similar <charactersheet><abilities><str>13</str><int>14</int> etc </abilities></charactersheet> but all those extra opening and closing tags make the document very verbose, difficult to read with eyeballs and most importantly for internet programming, it is much larger in total size than needed. JSON is far smaller, easier to read, easy to write directly into javascript etc. So JSON is the current defacto standard for moving data around in web programming. Both XML and JSON have the same language support but web programmers only use JSON. Either can define hierarchal data, you can just do it faster and read it easier in JSON.
I’ll say!! I have an easier time reading XML. Of course, we learned about that stuff back in the day. I forgot most of the nuance, but I can still read the stuff. Like, for example this makes sense to me:
It is hard to read because of the bloat, but I understand all of it. I even get the <i> as compared to <em>. That al make sense somewhere in my long term memory.
That JSON was gibberish to me. The stuff you wrote in the post before I could at least follow.
Hopefully a simple request.
I have figured out how to get the Character stats above the bonuses in the Character Builder. However, I can't figure out how to do the same for the Exported character sheet. The bonuses always end up on top. How do I change this so the stats are on top and the bonuses are in the little circles below?
Oh, and if possible, how do I get the character portrait to Export? (The exported sheet has no portrait, even though it's there in the builder.)
Not sure you can change it in the PDF export. Or if you can, I've not found how. Like you I prefer the numbers big and the bonuses small.
WOTC lies. We know that WOTC lies. WOTC knows that we know that WOTC lies. We know that WOTC knows that we know that WOTC lies. And still they lie.
Because of the above (a paraphrase from Orwell) I no longer post to the forums -- PM me if you need help or anything.
I would just like to know why we can't choose what version of the character sheet to use?? I really dont like the default sheet style I would much prefer something more closely resembling the traditional character sheets downloaded from WotC. Just makes it easier since I've used those sheets since the start of 5e. Just think it should be a choice what style sheet you prefer is all.
The character sheet data is available as JSON, just writing your own parser, apply some transformation and create your own.
You say that like people know what that means.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
It means you get your friend Jason to do it for you...right?
If Jason is a programmer you are all set, otherwise good luck ! The JSON format of the character sheet is not for the faint of heart, especially as it does not have the final values like a plain final Armor Class value.
My buddy Jason doesn’t even play D&D. How about Tom? I know a Tom who is both a programmer and plays D&D. Would that work?
And why does it matter if I’m parsimonious?
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
I didn’t request a gorram thing. You better check yourself and then go back and check who requested what.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
i did and deleted my post with a loud 'oops', but you saw it first. sorry.
to the OP, yes it probably is a simple request, but can't imagine its a priority at all.
Guide to the Five Factions (PWYW)
Deck of Decks
No blood, no foul.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
Back it up a few steps for my edification please. What is a JSON, what does it mean, what does it do, and where/how would one even go about finding one. And if one does locate a JSON, what does one do with it? I presume it doesn’t go into a toaster.
Basically, explain it like you would explain it to a 40 year old Gen Xer who last did any computer programming back when Windows 3.1 was still “new” and never did it again after that.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
So you can type a reply on this forum, you are typing "plain text" just good old a,b,c etc. But you have a little toolbar with buttons B I U to bold things, italics things, etc. That toolbar transforms your text into HTML e.g. <html><b>this is now bold</b> and <u>this is underlined</u></html> HTML is a structured text document. The structure is for instance each opening "tag" e.g. <b> is accompanied by a closing tag e.g. </b>.
JSON is another "structured text document". The structure is a "key" and a value e.g. "character name" : "legolas". An value can be a list of values.
e.g. "attributes" : [ "strength": "13", "intelligence": "14", "wisdom" : "12", "dexterity" : "19", "constitution" : "13", "charisma" : "15"] ]
Ideally DDB would define as simple a JSON structure as possible to provide the character sheet content needed to create a character sheet. e.g.
"character sheet" : [ "attributes" : [blah] , "saving throws" : [blah], weapons, skills, spells etc]
Once you have something in JSON you can take any modern programming or scripting language (Javascript, Java, etc) to manipulate it and populate another structured text document such as Microsoft Word XML, or HTML or populate a PDF file in order to create your own personalized beautiful custom character sheet.
Thank you for taking the time. Okay. I’m good w/ html, I have no problem fixing stuff here w/ html. We used that back in the day. So JSON is a different language that does similar things, kinda like the tooltips too I suppose. I imagine that it is easier to work with than html, or that it is more compatible with newer stuff that you mentioned like java. Is it preferable because it is easier to define your own values? Have I got that close enough to follow a conversation?
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting
HTML is structured for browsers to display the data as a formatted document, not for pure data, XML is a structured text that uses tags and designed for pure data. It looks similar
<charactersheet><abilities><str>13</str><int>14</int> etc </abilities></charactersheet>
but all those extra opening and closing tags make the document very verbose, difficult to read with eyeballs and most importantly for internet programming, it is much larger in total size than needed. JSON is far smaller, easier to read, easy to write directly into javascript etc. So JSON is the current defacto standard for moving data around in web programming.
Both XML and JSON have the same language support but web programmers only use JSON. Either can define hierarchal data, you can just do it faster and read it easier in JSON.
Unfortunately the JSON that is the DDB JSON is bloated with a lot of what I would call junk and so it is not easy to eyeball the structure at all.
https://character-service.dndbeyond.com/character/v3/character/28965228
I’ll say!! I have an easier time reading XML. Of course, we learned about that stuff back in the day. I forgot most of the nuance, but I can still read the stuff. Like, for example this makes sense to me:
It is hard to read because of the bloat, but I understand all of it. I even get the <i> as compared to <em>. That al make sense somewhere in my long term memory.
That JSON was gibberish to me. The stuff you wrote in the post before I could at least follow.
Creating Epic Boons on DDB
DDB Buyers' Guide
Hardcovers, DDB & You
Content Troubleshooting