Description of the new feature / enhancement

*The following assumes that this functionality is not already a feature of EXCD, that I am unaware of, or misunderstanding.

This is not a problem per se, and in fact EXCD doing its job properly: What and how many mods are installed can lead to the EXCD log rapidly exceeding 10000 lines (In a stress testing scenario exceeding 100000 was easily achieved).

Being able to blacklist certain errors from the log would allow the user to choose to omit certain expected/accepted errors and curate this list to more easily identify errors that are, situationally, of more concern or notability.

Whitelisting would allow the inclusion of messages that are clearly errors but not prefixed with [ERR or [WRN in the log. For example, [Debug] errors, or others that are logged on a line after a similar plugin/terminological prefix.

Proposed technical implementation details

A config style blacklist and/or whitelist file (or possibly to be integrated into the current config file) which can be used to define strings, that if detected by EXCD, are omitted from, or included in, the log file. Related true/false style setting toggles could be an expansion upon this feature concept (which I will save for another post/discussion).

The following examples are inspired by my current log, and may highlight considerations/limitations for this idea, in regard to syntax or practical implementation:

Blakclisting:

• "this is intended"
• "Texture 'OSSNTR/"
• "PartLoader Warning: Variable"

Whitelisting:

• "Cannot find"
• "Not found for"