Options for control on how the parameters can be used

[testgita]

• Option to do one param per request, for more fine tuned approches
  • Option to include wordlist of potential values(fucks up complexity, so add a warning for it, if youre gonna do it at all)
• Options to group params in a request in specific ways(only put requests from the same wordlist file in the same requests)
• Havent noticed exactly how you approach a 403, but I'd suggest to have an option to binary search which parameters caused it and include it in another box, so the user can remove words like "onerror" from their lists, of whatever they wanna do with that info(or add a blacklist wordlist so even if theyre found in wordlist they wont be used for the following sessions)
• Have an option to pause and let the user continue when they want if 429 was encountered

Im not asking for these, I'm just giving you some ideas, maybe theyre bad, maybe youll like them. Cheers

[bebiksior]

Thanks for all feature ideas, will be implementing some of those in the next days. Just pushed a commit for:

Have an option to pause and let the user continue when they want if 429 was encountered

3a1613a

This one will be included in the next release :D