Inspiration

We took heavy inspiration from Duck Life, specifically Duck Life Battle, where you can train ducks by playing minigames, with additional themes from Super Auto Pets. We wanted to do something that is doable in the limited time and fesible enough where the project can be relatively polished by the end.

What it does

Auto Quack is an auto battler where players select a team of ducks, each one of four different classes, and fight against other parties of ducks. In between matches, players can train one of their ducks at a time to increase their stats. Each class has their own auto attack, with specific targeting rules, and one unique ability. During the battle, duck action order is based on their speed stat, and on an action, a duck can do one of two actions, auto attack if their ability isn't charged, or the ability if its charged. A duck's ability is charged by auto attacking.

How we built it

We programmed the game in python and displayed the graphics using PyGame. All assets were created using InkScape.

Challenges we ran into

Challenges with PyGameGUI

We had to tackle different ways of accepting file paths for images to different operating systens so that it would work on all our devices.

Making unique minigames for each stat

Not re-using some minigames and making a unique game for each stat made it difficult to put more focus onto the autobattler mechanics, which could also in turn make it more difficult to add more stats in the future.

The core gameplay went pretty smoothly, but having to add four more minigames on top of that added a lot more to our plate and complicated our UI codebase mostly.

Accomplishments that we're proud of

  • Producing a decent library of assets that are all similar.
  • Developing four unique minigames on top of the core game
  • Finishing the project / staying in scope

What we learned

PyGame

We've never developed a game before in PyGame, but we decided to use it as it seemed like the right tool for the amount of complexity we wanted to do.

Games have a lot of graphics

Some of us haven't developed a game before. Developing a game means you have to deal with graphics... a lot, especially something as UI heavy as our game. It was definately a learning experience, but a fun one!

Getting better a separating logic and graphics

To those that have developed games before, we feel we got better at separating the concerned between the UI ( our game scenes and minigames ), and our logic ( our battler scheduler and duck units ).

What's next for AutoQuack

UI animations

We didn't get to adding animation to our UI and some minigame elements. We'd love to have them, as they'd add a lot more polish to the overall experience and help with affordances and user experience.

More ducks

Love to add more characters that ultilize "passives" and could use different resources for specials that arn't just charge.

Buffs and debuffs

Maybe a Defense stat and specials that increase speed for the battle, or increase health for the battle and resets.

Multiplayer

Couch Coop or Multiplayer support so you can team build and theory craft against your friends.

Sound and music

Would make the game a lot more enjoyable.

Controll Support

Is mostly a nice to have, but would make it a lot easier to add to the Quackbot!

Share this project:

Updates

Submission history