Confirmed users
293
edits
| Line 8: | Line 8: | ||
The user should be given an option to have all rules match, or just one (AND/OR difference) | The user should be given an option to have all rules match, or just one (AND/OR difference) | ||
The filter rule system should be based on 4 fields: | The filter rule system should be based on 4 fields: | ||
#The Type of the rule ( | #The Type of the rule (see below) | ||
#The type of match done. This can be any of: | #The type of match done. This can be any of: | ||
#*An exact match. This is easiest. | #*An exact match. This is easiest. | ||
| Line 16: | Line 16: | ||
#* Regular Expression. Expected by power users. | #* Regular Expression. Expected by power users. | ||
#* Function match. Used by the client itself and obviously also by plugins/scripts. | #* Function match. Used by the client itself and obviously also by plugins/scripts. | ||
#The text | #The text or regular expression we're matching to. | ||
#Optional negation field. Easier than adding 'Does not' entries for everything mentioned in field 2. | #Optional negation field. Easier than adding 'Does not' entries for everything mentioned in field 2. | ||
| Line 29: | Line 29: | ||
* Message types (INFO, JOIN, PART, QUIT, etc., and we need a way to get nice names for all those stupid response codes (end of list, whatever)) | * Message types (INFO, JOIN, PART, QUIT, etc., and we need a way to get nice names for all those stupid response codes (end of list, whatever)) | ||
* Current away message. | * Current away message. | ||
* Use a function to match based on all available data. | |||
== Filter Actions == | == Filter Actions == | ||