6 PM – Python Game Development – Sebastian

Today We Did

1. Finished entirety of balloon class
2. Created bad balloons with 50/50 chance
3. Added text to each balloon
4. You can always find the code we wrote in class in my Gitlab repository here:
   https://gitlab.com/gsugiart/tue-6-pm-flappy-bird/-/tree/Sebastian?ref_type=heads
5. AYC Logic’s observed holidays: https://www.ayclogic.com/observed-holidays/
6. In case you need anything, feel free to email me at sebastian@ayclogic.com

Homework

1. Homework: By now we should all have cloned our new repositories, and put in our cropped sprites. Next we will focus on blitting our players and enemies.
   1. Before you begin to code, please coordinate closely with your partner first to brainstorm what exactly will be done, and write all plans on the project proposal (below what has already been written).
      1. Write your name (and your partner will write theirs), and either player/enemy (depending on which you will be developing).
      2. Below your section you just made for yourself, you will give a detailed explanation of how the player/enemy will move (which buttons, which directions, what sprites, what actions it can take like hitting or shooting).
      3. Please be as detailed as possible. This is now your section that you’re responsible for on the project, so you need to make sure that your partner and I both understand what you’re trying to do.
   2. Remember, the detailed planning is the most important part of this homework assignment. Please take enough time to really think about how you want your portion of the game to work.
   3. Once you finish the detailed planning (it should take 10-20 minutes to give enough detail), begin writing the basics for your player/enemy code.
      1. Create the file, class, constructor, and update methods.
      2. Think about what parameters the constructor should take in based on how you explained the player/enemy would move and do damage (x, y, screen, maybe size, etc.), and add attributes for the ones that need to be saved.
      3. Let your partner know when you’re done! Send them an email so they know to pull/update their code.
   4. Don’t worry about blitting yet. If you think you have more time, then please spend more time adding to your detailed explanation.