Allow the user to specify certain values that they want flagged (with a user specified message) in the list bans and edit bans page. This can be a handle or Steam ID on list bans, and handle, Steam ID, notes, banning admin, etc on Edit Bans. When on List Bans, the field that got flagged will be highlighted with a background colour, may want to consider showing the user specified message a title attribute, but that's to be decided. When on Edit Bans, the user specified warning will be shown at the top of the page in a warning box (no highlighting).
This will be beneficial in flagging repeat offenders (Steam ID), or common evasion usernames for further review by CS LE. Usually we want to up repeat offender's bans as a "last chance before permanent" thing, but very often the bans are missed when scrolling through the list.
Out of simplicity (different lists for every single field is going to crowd up the config page so fast), have it scan through every single available field against the list. Additionally, store the list of values to compare against as hashes (probably SHA-256), just to prevent any potential issues with data being leaked (ban notes and reasons may be contained in the config) by people carelessly showing/sending their config.
Allow the user to specify certain values that they want flagged (with a user specified message) in the list bans and edit bans page. This can be a handle or Steam ID on list bans, and handle, Steam ID, notes, banning admin, etc on Edit Bans. When on List Bans, the field that got flagged will be highlighted with a background colour, may want to consider showing the user specified message a title attribute, but that's to be decided. When on Edit Bans, the user specified warning will be shown at the top of the page in a warning box (no highlighting).
This will be beneficial in flagging repeat offenders (Steam ID), or common evasion usernames for further review by CS LE. Usually we want to up repeat offender's bans as a "last chance before permanent" thing, but very often the bans are missed when scrolling through the list.
Out of simplicity (different lists for every single field is going to crowd up the config page so fast), have it scan through every single available field against the list. Additionally, store the list of values to compare against as hashes (probably SHA-256), just to prevent any potential issues with data being leaked (ban notes and reasons may be contained in the config) by people carelessly showing/sending their config.