Shadow I'd prefer the single user file method for the update, however I'd also request that the different authors be credited to their own user files and not merged into one.
I had only planned to merge together the .user files per AP. So in example right now I sort of the following:
PFRPG_Council_of_Thieves_Bestiary.user
PFRPG_Council_of_Thieves_AP.user
PFRPG_Rise_of_the_Runelords_Bestiary.user
PFRPG_Rise_of_the_Runelords_AP.user
So it would still be separate per AP but it would shrink things down for say Carrion Crown where I have:
PFRPG_Carrion_Crown_Bestiary_AP43.user
PFRPG_Carrion_Crown_Bestiary_AP44.user
PFRPG_Carrion_Crown_Bestiary_AP45.user
PFRPG_Carrion_Crown_Bestiary_AP46.user
PFRPG_Carrion_Crown_Bestiary_AP47.user
PFRPG_Carrion_Crown_Bestiary_AP48.user
When a fix comes in I think its allot easier to have to update just one .user and not have to search through several .user file to find the issue.
So in the end I then combine everything into one .hl that would allow for the community, I think IMHO anyways, to be able to download and install a single file with all the current AP community created material. Plus it would make it more guaranteed that the different data sets will play nicely with each also.
Plus I think its wrong to not "reuse" code as it just makes it easier for the next person then make the same exact Thing 5 different ways. Especially sense it seems like allot of these .user files eventually fall to
me to "maintain" as peoples real lives get in the way.
That is just my thought anyways.