But, I, loved, those, commas.:DQuote:
Originally Posted by Trenloe
Thanks for the update, it's been working great so far in my Exodus, and now Obsidian Twilight games. Good show.
Cheers,
SF
Printable View
But, I, loved, those, commas.:DQuote:
Originally Posted by Trenloe
Thanks for the update, it's been working great so far in my Exodus, and now Obsidian Twilight games. Good show.
Cheers,
SF
The change has only been made in the dev version, which won't be released for a while yet. So, enjoy those commas for a little while longer.Quote:
Originally Posted by S Ferguson
I was hoping, at some point, to have written a small extension that would have used the XP values from the creatures when creating an encounter - so that it would auto total the XP for the whole encounter and calculate the CR too. This would help GMs to make challenging (or not) encounters on the fly and would also allow the adjusted XP of the encounter to be used when dragged to the party sheet for XP allocation.
That's an excellent idea. Hope to see it in the beta!;)Quote:
Originally Posted by Trenloe
That's great - thanks, Trenloe!Quote:
Originally Posted by Trenloe
Might I be so bold as to make a few more constructive suggestions? Of course, I don't know how feasible these are, so feel free to ignore them.
Firstly, could the creature's languages appear in the Languages slot on the Main tab, not as text in the Other tab?
Secondly, could the text formatting in the Other tab be adjusted to make it more clear and easy to read (like the standard layout)? I've attached a screenshot of an NPC where I've edited the text alongside the one straight from the parser to show what I mean.
Note that these aren't criticisms - the parser is already great; I'm just hoping to make it even greater!
I don't know why I didn't do this in the first place. Looking at the original software specification I wrote for this I don't have languages as an FG field for an NPC so I must have missed that.Quote:
Originally Posted by Callum
It's an easy fix so I've included it in the dev code.
Yeah, a lot more could be done on the Other tab in terms of better formatting - that is a nice to have at the moment, but I will look into it at some point. Just keep in mind that the more carriage returns/new lines there are in the other tab then the longer the page will be - this could be very long for some high CR creatures and require a lot of scrolling! :-o But, if it is more readable then that is probably preferable.Quote:
Originally Posted by Callum
Is it possible to do single spacing for some of that stuff on the 'Other' Tab? When I was working on some critters I messed around with doing spell lists as a 'list' and it condensed the information into a smart looking format.. the only problem was it bulleted all the spell levels which wasn't so great.
Readable is preferable to less scrolling IMO.
The issue here is that not all HTML tags are supported by the formatted text control. Some of this is discussed here: https://www.fantasygrounds.com/forum...ad.php?t=14323Quote:
Originally Posted by Blackfoot
The main tag that is not supported is the break <br> tag that would be nice here. There may be a possibility of using table specifications to reduce the blank space between rows.
If someone can mess around and come up with a nice format that works within the FG 3.5e/PF ruleset for the NPC other tab formatted text control then I'll consider putting it in the next release of the parser. At the moment, for me, this is a very low priority and there are other pieces of functionality I want to work on before I look into making the other tab "pretty". :)
That the spirit, function before form, how dada-esque of you.;)Quote:
Originally Posted by Trenloe
I agree absolutely that making it look pretty isn't a good use of time! Putting all the spell names in italics, for example, would take an age to code and isn't necessary. However, spacing stuff out is much easier to do, and the main thing that improves readability and usability, in my opinion. The second most important thing is making the headings bold (which you have already done). I'd also keep the underlining just for sections (such as Tactics), and drop the colons.Quote:
Originally Posted by Trenloe
So you just need to go from this:
to this:Code:<text type="formattedtext">
<p><b><u>Spells Known</u>:</b> (CL 1st; concentration +2) 1st (2/day)-cure light wounds, hideous laughter (DC 12) 0 (at will)-daze (DC 11), ghost sound (DC 11), mage hand, message</p>
<p><b><u>Tactics</u>:</b> <b>During Combat</b> The warchanter continues her bardic performance during combat, using her whip to try to trip PCs. She casts hideous laughter on any PC who seems to be particularly dangerous, and cure light wounds on herself after she is first wounded. <b>Morale</b> The warchanter fights to the death.</p>
</text>
Code:<text type="formattedtext">
<p><b>Spells Known </b>(CL 1st; concentration +2) </p>
<p>1st (2/day) - cure light wounds, hideous laughter (DC 12) </p>
<p>0 (at will) - daze (DC 11), ghost sound (DC 11), mage hand, message </p>
<p><b><u>Tactics </u></b></p>
<p><b></b><b>During Combat </b>The warchanter continues her bardic performance during combat, using her whip to try to trip PCs. She casts hideous laughter on any PC who seems to be particularly dangerous, and cure light wounds on herself after she is first wounded. <b></b></p>
<p><b>Morale </b>The warchanter fights to the death. </p>
</text>
Using the paragraph "<p>" tags is exactly what I originally used when I first started doing some formatting in the "other" tab. This creates a double new line - i.e. a blank line between each paragraph tag.
But, as mentioned above (post #155), for creatures with a lot of info in the other tab this results in a very long entry - which has to be scrolled through, even with a big window. It seemed clunky, so I removed the <p> for anything other than new sections.