Many itemdesc.cfg files or one very large itemdesc.cfg file?

[Yukiko]

This has been a long running issue between myself and my assistant. Should we have many itemdesc.cfg files spread throughout the packages or should we have everything in one large file? I can see organizational reasons for having them split throughout the various packages and such. It makes it easier for portability sake when you want to pull a package for whatever reason or maybe you want to share a package with someone to have the items associated with that package contained within it. Somehow it just seems right to split things up like that. Granted items such as craftable weapons and armour are harder to organize properly. Do you put them in the combat package or in the appropriate crafting package, ie. blacksmithing, bowcraft, etc.? I choose to have all weapons and armour in the combat package.

Is there any reason why items could not be in one huge itemdesc.cfg file? Would this affect POLs efficiency or operation? I couldn't see why it would but I figured I'd ask for opinions from the community.

[xeon]

Hi Yukiko,
we prefer to have many itemdesc.cfg. It's a modular design, which allow more flexibility.

[Austin]

I prefer sorted too - that's why I made the package format that started in the 097 distro.

Long ago people did put everything into the pol/config/itemdesc.cfg file and all the scripts into the pol/scripts/ directory. You and your assistant could do it that way; the option is still there.

[Yukiko]

Thanks Xeon and Austin. I gather there's no performance hit with them being all in one file? Truthfully I like items separated into the relative packages too. It does get murky though when it comes to weapons and armour; whether they should be in the package that crafts them or in the combat package, so I just put all those in the combat package.

Thanks again.