Sources...

[ShadowChemosh]

I was trying to organize my list of custom sources better as I have a good number of them now. I was hoping I could make my own Parent sources that I could then add source books under them as children. In example make one called "Paizo" or "Super Genius Games".

I found this old POST in the d20 forums and tried to use. I hoped it would still work in pathfinder as they are pretty close.

Here is what I used:

<usesource source="SGG" name="Super Genius Games" selectable="no"/>

and I get the following error: line 16 - Unrecognized attribute 'selectable' in element 'usesource'

Line 16 I double checked is the above....

Is their a new element name? Can this be done in Pathfinder?

Thanks

[huntercc]

Try this:

<usesource source="SGG" name="Super Genius Games"/>

FYI, this can be done via the editor as well.

[ShadowChemosh]

Thanks, but that just makes it a normal Source. Which yep I do all the time in the editor.

What I am trying to do is make it a Parent source. Like how things like "Pathfinder Society", "Sources", "Pathfinder Adventure Paths" or "House Rules" are parent sources. This way I can make Children sources that go under it.

That old post shows how to do that, but I guess it only works in d20 not Pathfinder as I get an error. So hoping their is a new element type that allows it to be made for pathfinder.

[huntercc]

Gotcha... didn't understand your full intent. Not sure how to do that one

[huntercc]

I got it, but it involves creating a new file. I got this from reviewing the Authoring Kit documentation, and the Savage Worlds source files:

1 - Create a new file called MySources.1st (the name is unimportant, but it must have an extension of .1st) and save it to your "pathfinder" data directory

2 - Insert the following code and save:

<?xml version="1.0" encoding="ISO-8859-1"?>
<document signature="Hero Lab Structure">

  <source
    id="SGG"
    name="Super Genius Games"
    selectable="no"
    sortorder="0"
    description="Any description you want">
    </source>

  <source
    id="SGGMon"
    name="My Monsters"
    parent="SGG"
    description="Any description">
    </source>

  </document>

3 - Just add your child source to any "thing" as you normally would

4 - Reload the data files

I've tested this successfully myself, it should work for you as well!

[ShadowChemosh]

Awesome! Thank you Huntercc.

Too bad I have to create a new file, but it will work for my players at least.

Thank you.

[Grog]

Good find.

I'm going to try that myself.

Grog

[rob]

You can designate any source as a parent source by simply defining a new source and identifying the desired source as its parent. So if you define SourceA and then want SourceB to be its child, assign SourceB to a thing and specify SourceA as the "Parent Source" when assigning SourceB.

Of course, the only way to define a brand new source within the Editor is to assign a thing to it. If you simply want to create a new source that has *no* things assigned to it, you need to define the source manually within a data file. For that, the syntax is defined within the Authoring Kit wiki, and the examples above will work.

[ShadowChemosh]

Originally Posted by rob

You can designate any source as a parent source by simply defining a new source and identifying the desired source as its parent. So if you define SourceA and then want SourceB to be its child, assign SourceB to a thing and specify SourceA as the "Parent Source" when assigning SourceB.

Well this was the very first thing I did. Well if I am understanding what you are saying. In example I have a new source called SGG. Then I tried to create a new source called SGG1 that had SGG as it's parent. This was all done from inside the editor. What I got was an error message about 'Selectable' sources can't be chosen. Or something like that but I am not near HL to get the exact error message right now.

Do I need to do the above outside the editor directly in the XML .user file somehow?

Thanks

[rob]

Doh! I completely forgot that we added that stipulation awhile back. You're right. It's not valid to have a source be both a parent *and* have things dependent upon it. We changed that because it could enable some very strange and confusing behaviors to be established.

You *will* need to define the parent source separately within its own data file, following the example given by huntercc in post #5.

Sorry for the confusion. :-(