[ d20statblock.org ] a grammar

[CRGreathouse]

It seems the variety of EBNF I currently use is not the right one for the tools available on these URLS. Anyway, adaptation shall be easy as soon as we find the right tool.

Yeah, each one's different. I wouldn't worry about it; I'll have to make minor changes afetr the fact anyway.

also if you guys have all the monsters and stuff in statblock format and stuff from SRD posted it would be a GREAT help to the community.


I know you are trying to set a standard here but if you could take, say the monster manual, and convert it into statblock or even the Creature collection that would be awesome!

I'd like to do this some time. Perhaps the SRD information is written well enough that I could parse it directly (with a program I have yet to write), but until then there are others who have put the MM into less predictable, but still useful stat blocks.

 

[jmettraux]

also if you guys have all the monsters and stuff in statblock format and stuff from SRD posted it would be a GREAT help to the community.


I know you are trying to set a standard

Of course it would be a perfect pivot format.

People could also exchange their character sheets and their NPCs among all the progs supporting this format.

I'm sure Eric is working on an XSL doc for outputting eTools characters into the standard.

When I downloaded PCGEN's 3.0.0, I couldn't find any stat block template for export, is it included in 3.1.0 now ?

 

[CRGreathouse]

When I downloaded PCGEN's 3.0.0, I couldn't find any stat block template for export, is it included in 3.1.0 now ?

I was working on a PC Gen standard stat block output, but the template is restrictive - there are things that are hard-coded that prevent full compliance.

 

[jmettraux]

I was working on a PC Gen standard stat block output, but the template is restrictive - there are things that are hard-coded that prevent full compliance.

Could you write a small report of those hard-coded things you encountered : it could speed up PC Gen developers.
I know it's not their priority right now...
But being able to generate a [N]PC with PC Gen and then do 'in flight' management with dgsh or RPM is .

Please !

 

[jmettraux]

Another version of the grammar :

http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/dgsh/dgsh/import_samples/standard.ebnf
http://cvs.sourceforge.net/cgi-bin/...rev=HEAD&content-type=text/vnd.viewcvs-markup

diff:
http://cvs.sourceforge.net/cgi-bin/...port_samples/standard.ebnf.diff?r1=1.2&r2=1.3


Charles, could you validate my assumptions about the 'Spd' elements ?

Could you also validate this stat block :

Variant Orc: CR 1/2; Medium-size Humanoid; hd 1d8; hp 4; Init +1; Speed 20 ft, climb 15 ft, base 30 ft, climb 20 ft; AC 15; Melee longsword +2 (1d8/crit 19-20); Melee battle axe (1d8/crit x3); Ranged short bow +2 (1d6/crit x3); SQ low-light vision, light sensitivity; SV Fort +2, Ref +1, Will -1; Str 12, Dex 13, Con 11, Int 8, Wis 8, Cha 7.

Skills and Feats: Listen +4, Spot +3; Alertness.

Thanks !

 

[CRGreathouse]

Variant Orc: CR 1/2; Medium-size Humanoid; hd 1d8; hp 4; Init +1; Speed 20 ft, climb 15 ft, base 30 ft, climb 20 ft; AC 15; Melee longsword +2 (1d8/crit 19-20); Melee battle axe (1d8/crit x3); Ranged short bow +2 (1d6/crit x3); SQ low-light vision, light sensitivity; SV Fort +2, Ref +1, Will -1; Str 12, Dex 13, Con 11, Int 8, Wis 8, Cha 7.

Skills and Feats: Listen +4, Spot +3; Alertness.

Variant Orc: CR 1/2; Medium-size Humanoid (orc); HD 1d8; hp 4; Init +1; Speed 20 ft, climb 15 ft; AC 15 (+1 Dex, +4 scale mail); Melee longsword +2 (1d8+1/crit 19-20), battleaxe +2 (1d8+1/crit x3); Ranged short bow +2 (1d6/crit x3); SQ low-light vision, light sensitivity; SV Fort +2, Ref +1, Will -1; Str 12, Dex 13, Con 11, Int 8, Wis 8, Cha 7.

Skills and Feats: Listen +4, Spot +3; Alertness.

****

A shortcoming (in my opinion) of the format is that it does not include base speed. Perhaps this should be changed: it was originally chosen because it was easy to figure out, but with classed monsters, it's not so easy.

The two lines between "Cha 7." and "Skills and Feats" aren't required (only one is needed), but it's allowed.

I'll have to tweak these eventually, to account for the 3 possible formats (like HTML's transitional, frameset, and strict).

 

[CRGreathouse]

This might also be useful :

http://www.gnu.org/manual/bison/html_mono/bison.html

I wasn't having any luck downloading this. Is it just me, or is the link dead?

Edit: The doenload link, not the link you provided.

 

[DMFTodd]

I'm sure Eric is working on an XSL doc for outputting eTools characters into the standard.

I had a fan put one together for DM's Familiar already. You can find it on the DMF webpage, download section.

There's a PCGen sheet there as well that does a standard stat block.

But being able to generate a [N]PC with PC Gen and then do 'in flight' management with dgsh or RPM is .

What's DM's Familiar, chopped liver ? DMF can already do this for PCGen and E:Tools.

 

[jmettraux]

What's DM's Familiar, chopped liver ? DMF can already do this for PCGen and E:Tools.

Sorry, I didn't mention your product

The bravest logo dragon is yours.

And DM Familiar is listed in d20statblock.org's supporters.

All my excuses to you, Todd.

 

[jmettraux]

The two lines between "Cha 7." and "Skills and Feats" aren't required (only one is needed), but it's allowed.

<=>

statBlock: headSection newLine skillsAndFeatsSection newLine specialSection newLine spellsPreparedSection+ newLine domainSpellsSection newLine knownSpellsSection+ newLine equipmentSection

newLine: ("\n" | "\n\n")