@Epic I was able to add everything easily like this. Thank you for all the improvements and work you've done, truly.
However, after testing the scripts in all situations, I noticed some malfunctions:
Problem 1: When I set, or automatically trigger, a ban on the registered account, from all three places— namely, the nickname list, the input, and the badwords— an automatic whois query is triggered each time.
So I tried removing this part from the alias code:
| whois $2
But the result is that nothing works anymore. How do you get rid of that whois that keeps appearing without the script stopping
working?
Second problem: To the badwords:
on @*:TEXT:*i want combo ban*:#Mairel: set %bcombo $true | bacc $chan $nick
I had to add this:
| .ban $chan $nick 2
Because if someone who doesn't have the registered nickname writes any badwords, the ban won't be triggered, nothing happens.
Now, however, by adding the other ban code, when a ban is triggered, I still get the following message in the Status:
#Mairel *!*@exemple.org b Channel ban list already contains *!*@exemple.org
This is because the type 2 ban is already present in the "combo" ban, so I had to change it by adding the type 3 ban, like this:
| .ban $chan $nick 3
So now, when someone says a bad word, a type 2 ban, an account ban (the combo), and a type 3 ban are triggered.
I only managed to get it to work by doing this, but I think it's forced to work this way, forcing three types of bans. I think it should be fixed so that if the nickname is registered, both the type 2 and account bans are triggered, while if it's not registered, only the type 2 ban is triggered,
or at most, a type 2 ban and the ability to add others as needed.
