I think you ve got it right, Bryan. We should use the same format as CRITRANGE, since our main support is d20. This will allow things like some funky weaponsMessage 1 of 10 , Mar 1, 2005View SourceI think you've got it right, Bryan. We should use the same format as CRITRANGE, since our main support is d20. This will allow things like some funky weapons that are considered "unweildy" for some OGL/d20 products. Or a flaw I've been thinking of that increases the range a character fumbles on... Other objects besides the equipment will be able to modify that number, where as a free-text means it is permanent, and we might as well go to a simple SPROP instead of a special tag just for that.
For other game systems, like the ones Kevin mentioned, eventually we could set a Base number for fumble in GameMode (d20 would be 1) and then the range goes from there.
Not having it as a free text (I.e. a value it can use) will make it easier for GMGen for combat tracking stuff.....
For the stuff like "Fumble on natural 1, then confirmed miss" that sounds like a good candidate for a SPROP tag on the equipment, or SA for the character if it differs from that game's normal rules.
... range. ... EQMODs, ... item ... EQMODs ... a ... would ... understand ... at ... Except, PCGen only supports D20 systems. I am confoosed... :/ UnlessMessage 1 of 10 , Mar 1, 2005View Source--- In firstname.lastname@example.org, "merton_monk" <merton_monk@y...> wrote:
> --- In email@example.com, "Evan" <evan.miller@f...> wrote:
> > > Goes in Equipment files
> > >
> > > *** New 5.7.15
> > > Tag Name: FUMBLERANGE:x
> > >
> > > Variables Used (x): Text (Equipment fumble range)
> > >
> > > What it does:
> > > This is text which indicates the equipments fumble or error
> > This tagEQMODs,
> > > may also be used in EQMOD lines. If an equipment item has
> > theitem
> > > FUMBLERANGE text from the EQMOD supercedes the text from the
> > itselfEQMODs
> > > (EQMODs applied to the primary weapon head trumps text in
> > applied toa
> > > the secondary weapon head).
> > >
> > > Example:
> > >
> > > FUMBLERANGE:1-3
> > > Indicates and error range of 1-3.
> > >
> > > FUMBLERANGE:Natural 1
> > > Indicates and error range of a natural 1.
> > >
> > Nice. However, why not keep the same format as CRITRANGE? Just
> > FUMBLERANGE:3 for 1-3, or FUMBLERANGE:1 for a natural 1? Itwould
> > be a bit more intuitive to keep them the same (although Iunderstand
> > that the coding is probably done on it at this point).at
> For D20 I think your suggestion is spot-on. Thinking outside of d20,
> I'm not sure if we can assume that a fumble-range will always start
> 1.Except, PCGen only supports D20 systems. I am confoosed... :/
Unless looking forward PCGen is going to be supporting more than D20
and so this was coded with that in mind.
I know there's the forthcoming RPG Tookit program. I have a wait and
see attitude about RPG Toolkit. I like PCGen because I can program
books I buy into it... if RPG Toolkit uses LST then great, if it uses
something like XML, I'll probably skip it. I don't want to have to
learn a whole new programming language to use the program.