Is your feature request related to a problem? Please describe.
Right now, one needs to duplicate the block_list for both challenge and matchmaking sections if there are certain accounts they want their BOTs to avoid.
Describe the solution you'd like
Making the matchmaking block list default to the challenge one when left empty could be a good starting solution.
General inheritance would be a more desirable target, allowing matchmaking to extend the blocked list from challenge section (use case: adding there engines that don't want to receive challenges from you, but you have no reason to block otherwise). A flag could be added to control this behavior (such has _inherit_challenge_blocklist) and when set to true, both lists could be merged for matchmaking.
Is your feature request related to a problem? Please describe. Right now, one needs to duplicate the
block_listfor both challenge and matchmaking sections if there are certain accounts they want their BOTs to avoid.Describe the solution you'd like