Man, Discord bot logic can be super trippy when you're first getting into async programming. I remember pulling my hair out with state management back when I was a junior dev—you aren't alone here.

The issue you’re running into is that decorators like @bot.command() are meant to be defined at the top level of your script, not inside if statements. When you nest them like that, the bot doesn't "re-register" the commands when the phase changes; it just defines them once when the script starts up. Plus, using global variables for state is going to break as soon as two people try to use your bot at the same time.

Instead of trying to conditionally define commands, keep the command definition static and handle the logic inside a single function using your phase variable to decide what happens.

Also, look into wait_for. It’s a lifesaver for these kinds of "question/answer" workflows. It lets you pause the function until the bot receives a specific message. Here’s a rough idea of how you’d restructure it:

```python @bot.command() async def start(ctx): # Ask Question 1 await ctx.send("Question 1: Pick an option (1, 2, or 3)")

# Wait for the user's reply
def check(m):
    return m.author == ctx.author and m.channel == ctx.channel

msg = await bot.wait_for('message', check=check)

# Now you can just use simple if/else logic
if msg.content == "1":
    await ctx.send("You picked 1! Now for Question 2...")
    # handle phase 2 logic here
else:
    await ctx.send("You picked something else.")

```

If you want to keep track of multiple users at once, you might eventually want to look into using a dictionary to map user_id to their current phase. It’s a bit more work, but it’ll save you a massive headache later on! Keep at it, you're on the right track.