Changes

• Check for match of 75% or better and uses best command it finds if not found exact (option to turn off in !set core
• redone the Check Command Process to use isset instead of Checking all commands and comparing
• Changed Size check so it doesnt check output from the cut function as it is already small enough
• added Error output for denied Access to commands (turn off in !set core)
• Fixed bug were Ext_privgroup output would output to normal privgroup if large enough to be split

This is in Normal Releases of Bebot

Ever thought about the soundex or methaphone functions of php to compare the commands pronunciation? Never tried by myself...

I would suggest using similar_text(). Soundex and metaphone will most likely not catch instances where the first and second letter have been exchanged for example !tiem instead of !item.

For short commands like "is" typed as "si" all would fail. For longer commands like "member" vs "members" all would succeed.

There is some discussion as to the speed of similar_text() but that, as I understand it, is only relevant for really long (20000 characters+) texts.

The question is how one would go about implementing this. There are two scenarios that I see as fesable.

The first is to run trough the command list and check for an exact match like we're doing today. If no matches are found run trough again but this time check for the best match with similar text. If no command match more than 75% reply with a command not found. If one or more are matched with 75% or higher tell the user that we're assuming the best match. If two commands score exactly the same and both are above 75% tell the user that there are two possible matches and create a link to each of the two with the parameters as they were passed.

The second is to process commands with similar_text() and save the best match in a temporary variable array. If no 100% are found find the best match and if it's above 75% assume that it's the one the user wanted.


The danger here is when the command "lick" is removed and someone with access to the "kick" command hasn't been notified. So when that person tries to !lick someuser that user will be unexpectedly booted. To remedy this one can define a treshold for commands so that !kick will have to be 100% exact while !members can be 92% which is the difference between "member" and "members" (93% if you incude the command character)


The code I used to test this can be found on my server.

I hope that helps.

soundex() and metaphone is for illiterate problems, not typos.
similar_text() would be a lot better than mine, but I needed to kill some time and it gave me something to do .

If an exact match is found, another loop would go over using similar_text() compare, and any match over set % is stored, and when it's done the highest (if any) will be used. More with same, just output a blob as Blue said.
It shouldn't be hard to implement it either, and don't think it would be slow, not hard to try.

And Glara... this is a post about a smarter bot, not smarter user... and it's so much easier to make the bot smarter. The users will always be dimwits...

ive done it ill be posting code in about 5 min :p

Corrected a Spelling Error
Added option to Turn off Disabled Commands Errors msg
Fixed bug were it did a search even tho it had found the command but user didnt have permission to use

This post = Total Posts: 8000

And Glara... this is a post about a smarter bot, not smarter user... and it's so much easier to make the bot smarter. The users will always be dimwits...

Then again, if people learn to expect a bot to understand any mistyped command they throw at it they will get even more lazy and dimwitted and make their friends the same by telling them to use an essentially wrong command to achieve something "because it is close enough" and "it works".

You know the apparently American habit of typing something that maybe resembles a word and adding a (sp?) after it to show your ignorance while at the same time making believe it is OK...

[edit] And I agree with Blueeagle above, as well.

[edit2] "help" is your friend, if the choice was mine I'd focus more on up to date help files of all the bot commands instead of adding an AI to parse users trying to guess what that undocumented feature was... That would be a smart bot, one that actually knows all its commands and can tell the user how to use them.

The idea is to make the bot react to simple typos (ehois, tiems, etc) and not to make people lazy and dumber, even if that's a side effect. Nothing in this world is perfect.
But it's really hard to make a function (unless you predefine all typos) that'll know when it's a typo or when it's a dumb user.