ShadowChemosh
Well-known member
Thanks. Which is part of why it takes so long to merge stuff in to the data set. First I do my best to have every official HL package and then have to test to make sure that a) nothing clashes with Duplicate Thing IDs. If it does happen I have to find some work around. Often adding another 2 letters to the name of the Thing in the editor so it no longer clashes.Shadow you need to be careful with the Adventure Path monsters too, many of them are in print in the Bestiary books.
Then I remove the official packages down to what I know is needed. Then try and reload everything again to make sure someone didn't bootstrap something from another "new" official package. If they did then I often see how much work it is to duplicate the one thing. If too much is being used from a new package then we add it to the list as being required.
Whats happening next is that some editors are using a Race from Official Package because the race is already done. They then create the .por file for say the AP and while the CB loads correctly when the .por file goes to load then the person gets crashes. This one I am not too sure what I plan to do other than using Mathias's RegEx to create a list of all the required packages the .por uses.
So then we would end up with a list that is required to "load" the CB and another to "use" the .por files. Seems like it could get pretty confusing.
