Why define Game as a class?

In game.py, Game is defined as a class. Why did Kenneth make Game into a class? Is this standard practice in Python OOP? I'm not challenging it, I'm just wondering.

That is, why not just write game.py as a plain old python script, with something like a play_game() function that does pretty much the same as Game.__init__(self) -- it would call, in the proper order, the other functions that are defined in game.py?

I tried rewriting game.py without defining a class within it (deleted the word "self" heaven knows how many times), and the game ran okay but for some difficulty I had in coding the conditions of the while loop that was originally within the __init__ method.

Here's what I wrote:

import blah blah blah

monsters = [Goblin(), Dragon(), Troll()]

# deleted the setup(self) method, put its code within play_game()

def other methods...
...

def play_game():
    player = Character()
    monster = get_next_monster(monsters) 

    while player.hit_points and (monster.hit_points > 0 or len(monsters) != 0):
        print('\n'+'='*20)
        print(player)
        monster_turn(monster, player)
        print('-'*20)
        player_turn(player, monster)
        cleanup(monster, player)
        print('\n'+'='*20)

    if player.hit_points > 0:
        print("You win!")
    else:
        print("You lose!")
    sys.exit()

I suppose with some more tweaking it could be made workable.

But my question is, in general: should a python file that imports several other class-defining files in order to run a bunch of statements and commands to do something (as game.py does) itself also be a class object?