[Feature, Not Bug] Missing Config File Reports in Debug.Log

Bug Reports relating to the 097 core are moved to this forum once solved.

Moderator: POL Developer

Locked
User avatar
OldnGrey
POL Expert
Posts: 657
Joined: Sat Feb 04, 2006 6:26 pm

[Feature, Not Bug] Missing Config File Reports in Debug.Log

Post by OldnGrey » Fri Aug 22, 2008 1:32 am

Can I also bring up something that I thought was promised in an earlier core but maybe forgotten.

debug.log has entries complaining if a package does not have itemdesc.cfg and npcdesc.cfg files.
This is probably when we use such things as: :*:itemdesc and :*:npcdesc

Is this a simple fix?

MuadDib
Former Developer
Posts: 1090
Joined: Sun Feb 12, 2006 9:50 pm
Location: Cross Lanes, WV

Re: Bring out your bugs

Post by MuadDib » Tue Dec 30, 2008 10:31 am

OldnGrey wrote:Can I also bring up something that I thought was promised in an earlier core but maybe forgotten.

debug.log has entries complaining if a package does not have itemdesc.cfg and npcdesc.cfg files.
This is probably when we use such things as: :*:itemdesc and :*:npcdesc

Is this a simple fix?
Yes and no. I don't feel like coding in all the common config names to ignore the report on (hehe). So instead you get this:

Code: Select all

12-30 MuadDib:
        Added : POL.Cfg::ReportMissingConfigs 0/1 (Default 1). Handles if Missing Config File
                reports are printed to the Debug.Log file. These are reports for example, when
                you use :*:npcdesc to open all npcdesc files in a script but not all packages
                of course will have this file.

Locked