Outdated Sources 1st

[Frodie]

How do you hide an outdated sources in a 1st file.

[Mathias]

If you can't just delete them, then you'll need to be more specific about what you mean by "hide".

[Frodie]

Sorry, it used to be if a source had the same name but two different id's they would just show up as one source. Seem now they show up as two different sources.

I have a little bit of down time an thought I might work on the old Modern Path files a bit and I thought I would start with the source in the 1st file.

We could strip put the old source files (they are no longer used in the user files), but it will mess up all the old save characters. IDK, not a big deal, what do yall think?

[ShadowChemosh]

You can not have "more" than one source id with the same "unique" value. They are "unique". My first question would be which "two" are we actually talking about?

Second issue is that now that Modern is in the community pack we don't do ANY changes that causes "errors" on purpose to be tossed to gamers. I don't need dozens of emails and posts about an issue.

If you are "deprecating" a source what we can do is set it up to be "grayed" out so it can not be selected anymore. But existing characters will not get errors about "missing" sources. You can do this by changing the "selectable" element to "no". Though I would recommend we do a proof of concept testing here as I have never had the need to remove an old source. We would also want to make sure no Things are attached to this source before deprecating it.

To get everyone on the same page HERE is the file is that Frodie is talking about. I don't see any "duplicate" source ID's?

[Frodie]

It's ok, like I said, not a big deal. I guess the best way to explain what I am talking about is to look at all the sources that show up when you start up the setting. So I added a screen shot.

Anyways, I don't want to break anything or have a bunch of post about something not working. So, l'll just leave it be, NP.

[ShadowChemosh]

Originally Posted by Frodie

It's ok, like I said, not a big deal. I guess the best way to explain what I am talking about is to look at all the sources that show up when you start up the setting. So I added a screen shot.

Anyways, I don't want to break anything or have a bunch of post about something not working. So, l'll just leave it be, NP.

This appears to be a totally different bug. If you look at the .1st file you have two "different" sources named "MSRD Base Classes and Skills" (sourceid.MPMSRD and sourceid.GRCMP2MSR).

So correct we need to now figure out "which" of these is the one you want to "keep" and which one we are going to deprecate.

Then we have to find all the "Things" that source marked to these ID's and move them over.

End result is we do want to fix this. Which I agreed above but we need to fix it in a "nice" friendly way to gamers.

[ShadowChemosh]

Using GitHub to do the search we can see that HERE that "GRCMP2MSR" has a few Things source marked to it.

HERE we can see that "MPMSRD" has nothing source marked to it.

Please go ahead and change the MPMSRD source in the .1st file to selectable "NO" please and change its "description" to be something like 'Not used'. At least that will prevent the confusion of having to check mark the option "twice".

[ShadowChemosh]

@Mathias other then making the "source" not able to be selected in the Configure Your Hero window. Any way to "deprecate/obsolete" the source in a way that will not cause saved .por files from tossing an error?

I am sort of thinking no actually but it don't hurt to ask.

[Mathias]

    <!-- The Ultimate Magic playtest is finished -->
    <silentsource source="UMPLaytest"/>

    <!-- The Ultimate Combat playtest is finished -->
    <silentsource source="UCPlaytest"/>

Check the loadmods.dat file in d20 - those are lines from Pathfinder's loadmods file. Those elements are within a <loadmods></loadmods> element.

Important note from the reference:

-Requires that the source NEVER again be used within the data files

(Although having accidentally broken that rule, it's caught by the compiler, and will simply prevent you from compiling until you fix it).

[ShadowChemosh]

Oh that is pretty cool. Thanks!

@Frodie I will take a look tonight at getting that added to obsolete the "MPMSRD" source.