<snip>

 
When to use CLASSLEVEL=name instead of CL. And an example of
how to use it.

Such as:
ADD:WEAPONBONUS(TOHIT|2+((CLASSLEVEL=Archer)/5)|Crossbow
(Heavy)|Crossbow (Light)|Shortbow|Longbow|)
in class.lst?

 <snip> 

I've noticed a few messages coming through the list lately that are starting
to take on an unappreciative tone of indignation concerning what PCGen does
or doesn't do.  Phrases like "Why the hell doesn't PCGen do <insert favorite
feature here>", "Why the hell *does* PCGen do <insert favorite pet peeve
here>" or "There's been plenty of time to add <insert source book here>, why
hasn't it been done yet" have been cropping up a bit more frequently of
late.

Please bear in mind that this program is *not* commercial software, and that
the developers are doing this on their own time, and without any recompense,
except for the ability to use what they've created.  As someone who has an
alter ego attempting to be part of the developer team, though one who hasn't
contributed much because of time and a struggle to learn Java, I can tell
you that such comments don't exactly sit will with that alter ego, and I can
imagine that those who *are* contributing on a regular, productive basis,
might feel much the same way, if not more so.

That said, I don't expect people to keep their mouths shut about perceived
problems with PCGen.  One of the things that has helped this program grow to
it's current stature is the constant input and contribution from the
community at large.  If you see what you think is a problem, by all means
bring it up, but do it in such a way as to acknowledge that the people who
are going to take care of it for you don't really have to, if they don't
want to.

If there is a feature that you really need, check over the FReq list at
SourceForge, it might already be there, in some form.  If not, then set
forth your ideas on the list for discussion.  It may be that others want
what you want, even if not in exactly the same form.  Discussion on the list
will likely reveal that, and hammering out ideas, so as to make them more
generic and generally useful will only help PCGen in the long run.

If there is a source book or some other source material that you really
want, which isn't represented by an existing LST file, instead of griping
about its absence, get a copy of the LST file syntax document and have a go
at creating it yourself.  There are plenty of people on the mailing list who
can help you over the rough spots.  *Most* of the LST files were created by
users of the program who then chose to share them with others.

If you find a problem with a LST file, such as something coded incorrectly,
try to fix it before posting a message whining about it on the list.  Then
post your fix on the list.  Numerous fixes have been found and corrected by
users, and later incorporated into the production release of the files.

In short, it's very counterproductive to b-tch about a program that you are
getting for free, so if you see a problem, see what you can do to fix it,
rather than just complaining about it.

Longwinded, slightly exasperated, Brad

*hands back the soapbox, claps*

Hear hear!  I believe you got to it before me by about 3 minutes. :)

Personally, anyone that simply complains (as outlined below by Brad)
I simply plan to ignore, as they obviously have nothing to contribute
to the discusion.

You forgot something though, Brad.  Begging. *evil grin*  Begging is
perfectly acceptable to get a feature you want added/re-added.  It
also seems to have successfully worked just recently.

Mynex

--- In pcgen@y..., "STILES, BRAD" <BRAD.STILES@s...> wrote:
> I've noticed a few messages coming through the list lately that are
starting
> to take on an unappreciative tone of indignation concerning what
PCGen does
> or doesn't do.  Phrases like "Why the hell doesn't PCGen do <insert
favorite
> feature here>", "Why the hell *does* PCGen do <insert favorite pet
peeve
> here>" or "There's been plenty of time to add <insert source book
here>, why
> hasn't it been done yet" have been cropping up a bit more
frequently of
> late.
>
> Please bear in mind that this program is *not* commercial software,
and that
> the developers are doing this on their own time, and without any
recompense,
> except for the ability to use what they've created.  As someone who
has an
> alter ego attempting to be part of the developer team, though one
who hasn't
> contributed much because of time and a struggle to learn Java, I
can tell
> you that such comments don't exactly sit will with that alter ego,
and I can
> imagine that those who *are* contributing on a regular, productive
basis,
> might feel much the same way, if not more so.
>
> That said, I don't expect people to keep their mouths shut about
perceived
> problems with PCGen.  One of the things that has helped this
program grow to
> it's current stature is the constant input and contribution from the
> community at large.  If you see what you think is a problem, by all
means
> bring it up, but do it in such a way as to acknowledge that the
people who
> are going to take care of it for you don't really have to, if they
don't
> want to.
>
> If there is a feature that you really need, check over the FReq
list at
> SourceForge, it might already be there, in some form.  If not, then
set
> forth your ideas on the list for discussion.  It may be that others
want
> what you want, even if not in exactly the same form.  Discussion on
the list
> will likely reveal that, and hammering out ideas, so as to make
them more
> generic and generally useful will only help PCGen in the long run.
>
> If there is a source book or some other source material that you
really
> want, which isn't represented by an existing LST file, instead of
griping
> about its absence, get a copy of the LST file syntax document and
have a go
> at creating it yourself.  There are plenty of people on the mailing
list who
> can help you over the rough spots.  *Most* of the LST files were
created by
> users of the program who then chose to share them with others.
>
> If you find a problem with a LST file, such as something coded
incorrectly,
> try to fix it before posting a message whining about it on the
list.  Then
> post your fix on the list.  Numerous fixes have been found and
corrected by
> users, and later incorporated into the production release of the
files.
>
> In short, it's very counterproductive to b-tch about a program that
you are
> getting for free, so if you see a problem, see what you can do to
fix it,
> rather than just complaining about it.
>
> Longwinded, slightly exasperated, Brad

I'm just wondering about the current status of the lst files.  Are there plans
to convert them to another format, such as XML, soon?  If not, is anyone
currently working on a lst file creator?  I know I saw a magic item creator a
long time ago....

Thanks,
Chris Moyer

-----Original Message-----
From: rodac@... [mailto:rodac@...]
Sent: Sunday, September 30, 2001 11:11 PM
To: pcgen@yahoogroups.com
Subject: [pcgen] AGE tag from race lst and age function in race.java question

The customize doc says:

AGE:min:dice:sides:dice:sides:dice:sides</td>
    the minimum age for the race and the number of dice and sides
used - the
    first dice:sides pair is used for Barbarian, Rogue and Sorcerer.
The second pair is used
    for Bard, Fighter, Paladin and Ranger. The last pair is used for
Cleric, Druid, Monk and
    Wizard

And in race.java the code is shown as:

public void rollAgeForClass(String className)
      {
            if (Globals.getCurrentPC() == null)
            {
                  return;
            }
            boolean startCounting = false;
            final StringTokenizer aTok = new StringTokenizer
(ageString, ":", false);

            // For XML migration, there is a separate entry for
each class,
            // and the classes are attributes, so users can
define new ones
            // but still give them age features.
            int i = 2;
            if (className.equals("Barbarian") || className.equals
("Rogue") ||
                  className.equals("Sorcerer"))
            {
                  i = 0;
            }
            else if (className.equals("Bard") || className.equals
("Fighter") ||
                  className.equals("Paladin") ||
className.equals("Ranger"))
            {
                  i = 1;
            }
            int min = 0;
            int diceNum = 0;
            int diceSide = 0;
            int total = 0;
            Random aRand = new Random();
            if (aTok.countTokens() < 7)
            {
                  return;
            }
            min = Integer.parseInt(aTok.nextToken());
            while (i > 0)
            {
                  aTok.nextToken();
                  aTok.nextToken();
                  i--;
            }
            diceNum = Integer.parseInt(aTok.nextToken());
            diceSide = Integer.parseInt(aTok.nextToken());
            total = min;
            while (diceNum > 0)
            {
                  int roll = aRand.nextInt(diceSide);
                  if (roll < 0) roll = -roll;
                  total += roll + 1;
                  diceNum--;
            }
            Globals.getCurrentPC().setAge(total);
      }


So my question is why are only some of the classes defined in the
race.java for the age roll and then the other question is why are the
ones defined even there. Shouldnt the calls be made aginst the info
in the tag from the race lst? I am looking through the code to
familiarize myself with java and how the java files interact with
each other and the lst files and this has me confused. Is something
wrong here or is it just me?



To unsubscribe from this group, send an email to:
pcgen-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

And speaking of "asking for help with .lst files ..." I've asked a
few times for help recently and they seem to keep getting lost in the
traffic. So, here goes again ;)

I'm trying to finish Fleet Runner of Ehlonna and I can't get the
bonus spellcast to work. Could someone please explain, slowly and
clearly, to a non-programmer?

What I need to do and can't: Add bonus spellcast slots, level
selectable by user, to existing divine spellcasting classes possesed.
Unfortunately, I can't get my head around the Customise.html section
on the choose tag and my attempts at defining this don't seem to do
anything; except that my version seems to think that Fleet Runner is
a spell-casting class of its own.

Advice, please, I would really like to get this one finished and
incorporated.

MarK

--- In pcgen@y..., mynex2k1@y... wrote:
>
> *hands back the soapbox, claps*
>
> Hear hear!  I believe you got to it before me by about 3 minutes. :)
>
> Personally, anyone that simply complains (as outlined below by
Brad)
> I simply plan to ignore, as they obviously have nothing to
contribute
> to the discusion.
>
> You forgot something though, Brad.  Begging. *evil grin*  Begging
is
> perfectly acceptable to get a feature you want added/re-added.  It
> also seems to have successfully worked just recently.
>
> Mynex
>
> --- In pcgen@y..., "STILES, BRAD" <BRAD.STILES@s...> wrote:
> > I've noticed a few messages coming through the list lately that
are
> starting
> > to take on an unappreciative tone of indignation concerning what
> PCGen does
> > or doesn't do.  Phrases like "Why the hell doesn't PCGen do
<insert
> favorite
> > feature here>", "Why the hell *does* PCGen do <insert favorite
pet
> peeve
> > here>" or "There's been plenty of time to add <insert source book
> here>, why
> > hasn't it been done yet" have been cropping up a bit more
> frequently of
> > late.
> >
> > Please bear in mind that this program is *not* commercial
software,
> and that
> > the developers are doing this on their own time, and without any
> recompense,
> > except for the ability to use what they've created.  As someone
who
> has an
> > alter ego attempting to be part of the developer team, though one
> who hasn't
> > contributed much because of time and a struggle to learn Java, I
> can tell
> > you that such comments don't exactly sit will with that alter
ego,
> and I can
> > imagine that those who *are* contributing on a regular,
productive
> basis,
> > might feel much the same way, if not more so.
> >
> > That said, I don't expect people to keep their mouths shut about
> perceived
> > problems with PCGen.  One of the things that has helped this
> program grow to
> > it's current stature is the constant input and contribution from
the
> > community at large.  If you see what you think is a problem, by
all
> means
> > bring it up, but do it in such a way as to acknowledge that the
> people who
> > are going to take care of it for you don't really have to, if
they
> don't
> > want to.
> >
> > If there is a feature that you really need, check over the FReq
> list at
> > SourceForge, it might already be there, in some form.  If not,
then
> set
> > forth your ideas on the list for discussion.  It may be that
others
> want
> > what you want, even if not in exactly the same form.  Discussion
on
> the list
> > will likely reveal that, and hammering out ideas, so as to make
> them more
> > generic and generally useful will only help PCGen in the long run.
> >
> > If there is a source book or some other source material that you
> really
> > want, which isn't represented by an existing LST file, instead of
> griping
> > about its absence, get a copy of the LST file syntax document and
> have a go
> > at creating it yourself.  There are plenty of people on the
mailing
> list who
> > can help you over the rough spots.  *Most* of the LST files were
> created by
> > users of the program who then chose to share them with others.
> >
> > If you find a problem with a LST file, such as something coded
> incorrectly,
> > try to fix it before posting a message whining about it on the
> list.  Then
> > post your fix on the list.  Numerous fixes have been found and
> corrected by
> > users, and later incorporated into the production release of the
> files.
> >
> > In short, it's very counterproductive to b-tch about a program
that
> you are
> > getting for free, so if you see a problem, see what you can do to
> fix it,
> > rather than just complaining about it.
> >
> > Longwinded, slightly exasperated, Brad

> -----Original Message-----
> From: Damian [mailto:damian@...]


> that's odd.  i thought age was simply a fuction of race,
> not class............ though i can see where it should
> be a fucntion of class.  being a mage prolly takes more
> years of study than beating things up with a sharp piece
> of metal.

I think the age in question is the age at which someone of that class is
likely to become first level, not the actual age of the character.  As you
pointed out, a warrior is likely to become a professional before a mage.

No prob!

FYI, I did have a few minutes, and it seems to be working with
PRETEMPLATE:x|y where if have Template x or y it meets the Prereq.

Tom

> Thank you.  This is required for the new PrC in Dragon #288, and I do
> believe we'll be needing it again for other PrC's as they show up.
>
> Mynex
>

I've found several errors in the Defenders of the Faith class.lst file
(besides the features that aren't implemented yet). These errors include
classes that have their own spell lists not knowing any of the spells,
classes with the bad BAB progression getting the medium one and vice versa,
superceded special abilities not being removed, missing prereqs, etc. I'm
currently going through all the classes and trying to correct them. When I'm
done I'll upload them for others to check for any new errors, or errors
corrected that weren't errors...

I just thought I'd post this as a warning to those using the files that not
everything will show up the way you're expecting it to.

I've been working on a "simple" LST generator, but I've been side-
tracked by the Export window and bug-squashing lately.  Once I have
the first component (Skill LSTs) done I'll put what I've got up in
CVS and other people can start whacking away at the other LST
modules.  I'm going to be gone this coming weekend, so it may be two
weeks before I get something good in.  Or maybe I can take my laptop
with me this weekend... ;)

-Lone Jedi
(Jason)

--- In pcgen@y..., "Chris Moyer" <chris@c...> wrote:
> I'm just wondering about the current status of the lst files.  Are
there plans to convert them to another format, such as XML, soon?  If
not, is anyone currently working on a lst file creator?  I know I saw
a magic item creator a long time ago....
>
> Thanks,
> Chris Moyer

A while ago there was a discussion about Hospitaler domains and the note
that access to other domains was lost and how to implement this. While
fixing up the dofclass.lst file, I noticed that there is errata from Sage
Advice that indicates the Spells entry in the Hospitaler class (which refers
to the domain issue) shouldn't be there, and that the Spells per Day entry
is the correct one. This second entry makes no mention of hospitalers losing
(or gaining) any domains. Just thought that I'd point that out, so if anyone
was thinking of working on adding removal of domains, it can be moved down
on the priority list.

While I'm thinking about it, is anyone working on the features needed for
Defenders of the Faith (particularly adding a specific domain and adding
caster levels to characters that don't have a previous spellcasting level)?

David Culliford wrote:
>
> Just uplaoded a new and improved MM - lots of changes. All done up to
> C - been busy everybody, only got back from over seas, I'm on it
> know. If anyone has done any thing, please mail them to me:
> dculliford@... and I'll include them into my files.

Issue: You're not giving the monsters ranks in skills, you're giving
them bonuses. We can give them ranks now (thanks brian), so we should.
--
A broken reflection on the surface of never . Emily Smirle
from here to forever and back               . <smirle4498@...>
total viscosity into fluidity               . Proud owner of MSEELP
only the pulse of infinity                  . #008 and #009
          - MDFMK "Hydroelectric"

This bug was previously recorded as #461585.  It happens with either
the Martial or Exotic Weapon Proficiency feats with characters that
automatically have proficiency with either Martial or Exotic
weapons.  It's a real pain in the behind.  :)




--- In pcgen@y..., Martin Brabander <kemlyn1@p...> wrote:
> I have been having a little problem with trying to give a 1st level
> rogue Martial Weapon Proficiency in Sword (long) with 2.17 (with the
> second 2.17 list files)
>
> With just the PHB loaded, I created a human rogue 1st level.
>
> 1.    Switched to the feats tab - Filter 'qualified'. 2 feats to
> allocate.
> 2.    Select 'Martial Weapon proficiency'  Selection box comes up as
> routine with Rapier, Sap, Shortbow, Shortbow (composite) and Sword
> (short) already shown as selected.
> 3.    Select Sword (long) Apparently no problem up to here.
> 4     Click close (Dialogue box appears "Java.lang.String")
> 5     Close with OK - Martial Weapon proficiency is shown as
selected,
> but I still have 2 feats left to allocate.  When I go into the
selection
> box, I have lost both Sword (long) and the previous Sap, Shortbow,
> Shortbow (composite) and Sword (short).  All that is now showing is
> Rapier.
>
> Am I missing something in the rules that says Rogues can't use a
long
> sword, or have I found a bug?
> I can upload a .pcg file ifg you need it.
>
> Martin

Hear, hear!  That was well stated.  As a fellow free software
developer (though I haven't contributed anything to PCGen itself), I
want to second Brad's comments, and reiterate that if you want a
feature added or fixed, the LEAST effective thing you can do is rant
about it.  Before you rant, THINK.  If someone gave you a free car,
would you complain because the paint was chipped, or the hood was
dented? ;)

Again, well-stated, Brad.

- Jamis Buck
   jgb3@...
   http://www.d20reviews.com/generators

--- In pcgen@y..., "STILES, BRAD" <BRAD.STILES@s...> wrote:
> I've noticed a few messages coming through the list lately that are
starting
> to take on an unappreciative tone of indignation concerning what
PCGen does
> or doesn't do.  Phrases like "Why the hell doesn't PCGen do <insert
favorite
> feature here>", "Why the hell *does* PCGen do <insert favorite pet peeve
> here>" or "There's been plenty of time to add <insert source book
here>, why
> hasn't it been done yet" have been cropping up a bit more frequently of
> late.
>
> Please bear in mind that this program is *not* commercial software,
and that
> the developers are doing this on their own time, and without any
recompense,
> except for the ability to use what they've created.  As someone who
has an
> alter ego attempting to be part of the developer team, though one
who hasn't
> contributed much because of time and a struggle to learn Java, I can
tell
> you that such comments don't exactly sit will with that alter ego,
and I can
> imagine that those who *are* contributing on a regular, productive
basis,
> might feel much the same way, if not more so.
>
> That said, I don't expect people to keep their mouths shut about
perceived
> problems with PCGen.  One of the things that has helped this program
grow to
> it's current stature is the constant input and contribution from the
> community at large.  If you see what you think is a problem, by all
means
> bring it up, but do it in such a way as to acknowledge that the
people who
> are going to take care of it for you don't really have to, if they don't
> want to.
>
> If there is a feature that you really need, check over the FReq list at
> SourceForge, it might already be there, in some form.  If not, then set
> forth your ideas on the list for discussion.  It may be that others want
> what you want, even if not in exactly the same form.  Discussion on
the list
> will likely reveal that, and hammering out ideas, so as to make them
more
> generic and generally useful will only help PCGen in the long run.
>
> If there is a source book or some other source material that you really
> want, which isn't represented by an existing LST file, instead of
griping
> about its absence, get a copy of the LST file syntax document and
have a go
> at creating it yourself.  There are plenty of people on the mailing
list who
> can help you over the rough spots.  *Most* of the LST files were
created by
> users of the program who then chose to share them with others.
>
> If you find a problem with a LST file, such as something coded
incorrectly,
> try to fix it before posting a message whining about it on the list.
  Then
> post your fix on the list.  Numerous fixes have been found and
corrected by
> users, and later incorporated into the production release of the files.
>
> In short, it's very counterproductive to b-tch about a program that
you are
> getting for free, so if you see a problem, see what you can do to
fix it,
> rather than just complaining about it.
>
> Longwinded, slightly exasperated, Brad

Maybe we should put a disclaimer on the Splash Screen of the
application.


"PCGen freeware; developed in the free time of it's
programmers. We understand it is not finished and not
perfect. Use it with that in mind and please politely help us
find bugs. If you desire additional features polite and
detailed requests made to our yahoo group are appreciated.
But please understand we have many things in work and will
not be able to handle all requests promptly. See the Help
menu for appropriate contact information."






--- "STILES, BRAD" <BRAD.STILES@...> wrote:
> I've noticed a few messages coming through the list lately
> that are starting
> to take on an unappreciative tone of indignation concerning
> what PCGen does
> or doesn't do.  Phrases like "Why the hell doesn't PCGen do
> <insert favorite
> feature here>", "Why the hell *does* PCGen do <insert
> favorite pet peeve
> here>" or "There's been plenty of time to add <insert
> source book here>, why
> hasn't it been done yet" have been cropping up a bit more
> frequently of
> late.


__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

This is a request to anyone making updates of fixes in an
existing lst file.

DO NOT base your work around the copy you got from the latest
release of PCGen. That is quite often NOT the newest copy.

Rather always begin your work by downloading the latest copy
from CVS. Do your work, then before uploading make sure the
copy in CVS has not been updated while you were working. If
it has; get the latest CVS ---again--- and put your updates
into it. Then check CVS yet again...

Only if you are sure there has been no update to CVS since
you started your work should you post your file to the
group's file repository.

You can get the CVS files one at a time here:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/pcgen/lst/


If I hadn't been a little cautious last night, including a
few new uploads that were in the release files directory
would have wiped out several changes made in CVS. As it was I
noticed the recent changes and manually merged the data in
the various files.

__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

Dammit people, check this stuff...

Just a few hours ago somebody wiped out several fixes to
lggdeity.lst by putting the one in yahoo groups into the CVS
list.

I did this last night... if you read the CVS history you'll
see that.

Only my copy also included the changes from version 1.9 and
1.10 merged together.

Now the new verion 1.11 is missing some of this as the one
that was in yahoo groups was NOT CURRENT !!!

We need to take this file back to version 1.10

__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

Same thing here....

Needs to go back one version to a copy I manually merged.

__________________________________________________
Do You Yahoo!?
Listen to your Yahoo! Mail messages from any phone.
http://phone.yahoo.com

You can already get that with the EQ tags.  We can certainly make
these available to the WEAPON tags, it just didn't seem necessary at
the time.

-bryan
--- In pcgen@y..., Emily Smirle <smirle4498@h...> wrote:
> Tim Evans wrote:
> > As a temp work around, how about making so that on the Character
> > template there are some extra fields, so as well as
>
> <snip> While we're on the topic of extra fields for WEAPON, is
there a
> chance that we could have all the equipment fields enabled on
WEAPON% ie
> WEAPON%.COST, WEAPON%.WEIGHT and so on? this would be darned useful
for
> some of the character sheets I use.
> --
> A broken reflection on the surface of never . Emily Smirle
> from here to forever and back               . <smirle4498@h...>
> total viscosity into fluidity               . Proud owner of MSEELP
> only the pulse of infinity                  . #008 and #009
>          - MDFMK "Hydroelectric"

--- In pcgen@y..., Arcady <arcady0@y...> wrote:
> Dammit people, check this stuff...
>
> Just a few hours ago somebody wiped out several fixes to
> lggdeity.lst by putting the one in yahoo groups into the CVS
> list.
>
> I did this last night... if you read the CVS history you'll
> see that.

Which is the whole reason for the incvs folder here on yahoo. Move
stuff there *before* you put it in cvs. That way there is no risk of
the same stuff being done twice.

/Jonas, not feeling very repentant.

I think I'll default it to not be visible.  You'd have to
intentionally set a preference to turn it on - so only those who
really wanted it would see it.  It kind of breaks the character-based
paradigm, though I liked it myself.  For the statblock.htm and
csheet.htm templates, which don't use any styles, the display was
just fine.

-Bryan

--- In pcgen@y..., lonejedi70@h... wrote:
> When I worked on parties and auto-source loading I had to modify
the
> Unload button to also unload all PCs, but there were a few
developer-
> types that relied on PCs staying loaded while they unloaded, then
re-
> loaded, modified source LSTs.  As a comprimise, I set up the Unload
> button to work differently based on whether you're in debug mode or
> not.
>
> Maybe we can do the same with the Preview tab.  If you're indebug
> mode it's there, otherwise it's gone.  I loved getting rid of the
> Preview tab since it never worked well.  I'd rather not see it come
> back full-time, but as a debug option I'm all for it.
>
> -Lone Jedi
> (Jason)
>
> --- In pcgen@y..., bd_92@y... wrote:
> > Give it to me as an option! Please Merton! I use this feature to
> see
> > how my character sheet will turn out and what it will look like
> with
> > all the different templates. Different templates look and do
> > different things as you know, but with the preview tab allows me
to
> > pick and choose the right one for the job. I thought I went mad
and
> i
> > wasn't seeing something, but it was ripped out.
> >
> >
> > Powers that be allow us to have this back or put it as an option,
> the
> > file->preview is a let down to the almighty preview tab!! Myself,
> DM,
> > and fellow gamers in Florida agree!!

I think there's only one person here who has permissions to move stuff
on the yahoo groups however.

Which is why I sent out emails.

Last night I noticed that the lggdeity and mm files that had been
uploaded were based on old versions of the files and not the newest
versions. So I made changes to make sure they were based on the newest
ones, and uploaded that to CVS.

Then emailed the group saying they were in CVS.

--- In pcgen@y..., pjak@y... wrote:
> --- In pcgen@y..., Arcady <arcady0@y...> wrote:
> > Dammit people, check this stuff...
> >
> > Just a few hours ago somebody wiped out several fixes to
> > lggdeity.lst by putting the one in yahoo groups into the CVS
> > list.
> >
> > I did this last night... if you read the CVS history you'll
> > see that.
>
> Which is the whole reason for the incvs folder here on yahoo. Move
> stuff there *before* you put it in cvs. That way there is no risk of
> the same stuff being done twice.
>
> /Jonas, not feeling very repentant.

Great! As Emily mentions, we can now add actual ranks instead of just
bonuses. BONUS:SKILL=name|RANK|number would do the trick. I believe
you have to do a separate bonus tag for each skill.  Thanks for all
your work!  Only 52,314,224 more critters to go... ;)

-Bryan

--- In pcgen@y..., "David Culliford" <dculliford@d...> wrote:
> Just uplaoded a new and improved MM - lots of changes. All done up
to
> C - been busy everybody, only got back from over seas, I'm on it
> know. If anyone has done any thing, please mail them to me:
> dculliford@d... and I'll include them into my files.

Heh - I'll add it as an option as I've already stated, but just to be
clear about it... the "Preview" within PCGen *did* export the file to
currentPC.htm so it could be displayed... so it was pretty much
exporting, it's just that it would then be displayed within PCGen
instead of a browser.  Any kind of style sheet would give it fits -
and most templates use style sheets of some kind - notable exceptions
being statblock and csheet.

-Bryan

--- In pcgen@y..., bd_92@y... wrote:
> Yes i know that was a nice lil feature to automatically export it
but
> I had grown to like changing the template on the fly and looking at
> it in the PCGen browser window before epxorting. That's the whole
> point of the preview tab to show what I am going to be looking at,
if
> I don't like the template I choose another one in the window drop
> down. I don't like having to click around everywhere to do this.
Just
> gimme the tab and a happy camper I will be.
>
> --- In pcgen@y..., brentab@e... wrote:
> > Different templates may do different things but once you've found
> one
> > that you like, why on earth would you change it?
> >
> > Besides, last I looked the Export popup had a Template button for
> you
> > to use.
> >
> >
> >
> > --- In pcgen@y..., bd_92@y... wrote:
> > > Give it to me as an option! Please Merton! I use this feature
to
> > see
> > > how my character sheet will turn out and what it will look like
> > with
> > > all the different templates. Different templates look and do
> > > different things as you know, but with the preview tab allows
me
> to
> > > pick and choose the right one for the job. I thought I went mad
> and
> > i
> > > wasn't seeing something, but it was ripped out.
> > >
> > >
> > > Powers that be allow us to have this back or put it as an
option,
> > the
> > > file->preview is a let down to the almighty preview tab!!
Myself,
> > DM,
> > > and fellow gamers in Florida agree!!
> > >
> > >

Right - those that would use AGESET:2 don't need to be specified,
because 2 is the default. The way it works no you can actually, in
the race.lst file, supply any number of sides/dice tuples. For
example, AGE:14,6,2,6,3,6,4,6,5,6,6 would have a minimum age of 14
(the first value) with 5 sides/dice tuples, meaning that you could
specify AGESET:0 to get the 2d6 tuple (the first pair) up through
AGESET:4 to get the last tuple of 6d6.  Since the PHB broke them into
3 sets, it seemed reasonable that all races should define them that
way.  Now you can define as many tuples as you want, but the third
one (AGESET:2) is the default one. As I type this, that should be
changed so that AGESET:0 is the default and the AGE: tag would only
require 3 entries at a minimum... AGE:min,sides,dice   in the case
that no matter what class a race took, it's starting age was always
in the same range. This is an easy behind-the-scenes change that
wouldn't affect anyone.
-Bryan

--- In pcgen@y..., Arcady <arcady0@y...> wrote:
> Just grabbed the new CVS...
>
> I noticed that some of the classes are missing the AGESET tag.
>
> Is this because there is a default value of some kind?
>
> What are the valid settings for it?
>
> AGESET:0
> AGESET:1
> AGESET:2   (Default?)
>
> I ask because I'm updating the Sovereign Stone and Traps and
Treachery core
> classes right now to match.
>
> World of Fahla: http://home.pacbell.net/arcady0/fahla/
> /.)\ Arcady <0){{{{><
> \(@/ Projects: http://www.geocities.com/arcady0/

That's partly why I've tried to release mid-week, so if there were
any catastrophic problems we'd have at least a chance to correct them
before the weekend games.  I've been trying to follow a weekly
schedule, just because we are constantly fixing bugs and I want
everyone to have access to those fixes as quickly as possible. I used
to release on a daily basis, so this weekly business seems downright
slow! ;)

My current methodology is to pick some bugs that really need to be
fixed for the next release, and when those are done I'll release it,
along with whatever feature/goodies anyone has thrown in.  I'm
getting some people on board who will focus on testing, which has
been a dire need, so that should help us avoid some of the problems
that have ocurred in the past.  I'd like to release about once a
week, but will only do so after appropriate tests have been
performed.  This may slow things down a bit, but I'm not going to tie
myself to a specific schedule.  I think everyone understands that
this is a work-in-progress and that we're all doing our best with the
amount of time that we have to dedicate to it.

-Bryan

--- In pcgen@y..., "Gary" <dinthron@y...> wrote:
> I would change the scheduling slightly.  Most gaming is done on the
> weekends, so a new version by Thursday night, for Friday usage
would
> be better.
>

Do you know how to do this? If not, I can send you the cvs commands.

dave

On Tue, Oct 02, 2001 at 10:05:11AM -0700, Arcady wrote:
> Same thing here....
>
> Needs to go back one version to a copy I manually merged.
>
> __________________________________________________
> Do You Yahoo!?
> Listen to your Yahoo! Mail messages from any phone.
> http://phone.yahoo.com
>
>
> To unsubscribe from this group, send an email to:
> pcgen-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>

Yay! Welcome to SourceForge. :)

I think the trouble-shooting stuff should go in
pcgen.sourceforge.net, since I suspect that most of it will be non-
data-file related. Some of it will fall under the scope of your
project, but I'd rather keep all the trouble-shooting stuff in one
place for ease of reference. Or did you have something more specific
in mind?

-Bryan

--- In pcgen@y..., mynex2k1@y... wrote:
>
>
> I repeat from a few days ago 'stupid yahoo.  anyways'
>
> Project: PCGen:Data Manipulation (PCGen:DM) has been approved at SF.
> https://sourceforge.net/projects/pcgendm/
>
> This is for list file testing, data directory structure testing,
and
> anything else related to list files that would require testing.
Yes
> it would probably double up some of the work being done at PCGen
> itself, but this is again for testing purposes.
>
> I've added Bryan as an admin already, I would guess that Arcady and
> Jonas would like to be in on this (I know I would like them on
> this. :o), but I would like to know before I go randomly adding
> people. :)  Anyone else interested in working on list file stuff
that
> is not currently listed as a developer in PCGen, let me know, and I
> will add you.
>
> This also let's those of us not overly familiar with CVS to get
used
> to it, so we don't commit something and accidently over-write
> something important.
>
> I will make a base "data" directory in CVS a "final" directory in
CVS
> for the Data Directory Structure that works (not going to populate
it
> yet until we work it out), a "test" directory for not-fully
supported
> stuff in the list files .
>
> This will let us cleanup the list files so that for Bryan's
'official
> releases' everything in the list files that is supported will be in
> there, and there is a place to see what still needs support.  I
don't
> expect to 'release' anything for PCGen from the 'final' directory
> until we have it all working with the pcc files (pcc files loading
> other pcc files), but it gives us a place to start.
>
> \pcgendm\data\final
> \pcgendm\data\test
>
> I am not working tonight, so I will work on the CVS end of this and
> get that working, make sure that *I* can access and commit stuff
> before I start adding any more people.
>
> Anything I'm missing?  Should I make a spot for trouble
> shooting 'just prior to release' of PCGen stuff?
>
> Mynex

Soitanly, nyuk nyuk nyuk.
:)
-Bryan
p.s. that's 3 stooges (Curly) for yes.

--- In pcgen@y..., "Bonisagus" <bonisagus@t...> wrote:
> PRETEXT: sounds like exactly what I need, would be very useful.
>
> Can I make that a formal request then?
>
>
> Bonisagus
>

--- In pcgen@y..., "arcady" <arcady0@y...> wrote:
> I think there's only one person here who has permissions to move
stuff
> on the yahoo groups however.
>
> Which is why I sent out emails.

Didn't mean to sound as grumpy as I did. Guess I've simply gotten
used to being the only one moving stuff about. ;-)

But seriously, if you're going to be doing it, you should talk to
Bryan about getting permission to move files.

/Jonas, who shouldn't be responding to mails before he wraps himself
around some dinner