Small issue with client.wait_for

[Martyn0324]

I'm having a small problem with client.wait_for feature for a minigame I'm developing for my bot. Upon initiating the minigame using a command, the bot asks the user to make a choice and then have to wait for user's response.
If the user answer the bot right on next message, things works fine. However, if the user answer with something other than the desired response, then the bot will just cancel everything. Is there a way to avoid this?

Example - Working just fine
User: $choice
Bot: Ok. Choose 1 or 2
User: 2
Bot: Is this really your choice?´
User: Yes
Bot: Fine

Example - Unwanted situation
User: $choice
Bot: Ok. Choose 1 or 2
User: 2
Bot: Is this really your choice?
User: Maybe
User: Yes
(Command is cancelled and user has to start everything over again)

Here's the code I'm using:

#Irrelevant line: Just for context

 def confirmation(confirmation):
            return confirmation.author == opponent

#This is the one that really matters:

await ctx.send('Cráááá! Is this really your choice?')
            try:
                confirm = await client.wait_for('message', timeout=20, check = confirmation)
            except asyncio.TimeoutError:
                return await ctx.send("Crááááá! Are you gonna choose it or not?")
            else:
                if confirm.content.lower() == 'no':
                    await ctx.send("Crááááá! Then call me when you make up your mind. Don't waste my time! Crááááa!")
                if confirm.content.lower() == 'yes':
                    await ctx.send("Cráááááá! Very well, then. Now, it's " + str(ctx.author.mention) + "'s turn to choose!")

[Rapptz]

Your check should constrain the content you care about as well.

def check(message):
    return message.author == opponent and message.content.lower() in ('no', 'yes')

[Martyn0324]

Wow, so simple... Thanks!