AW-Competitive Outline

[JaviTrek]

Welcome to the team! Whether you are just getting your feet wet with programming or already have made some pull requests to production, there will always be a space for you to help and learn about web development.

Our Project: AW-Competitive

Our goal is to recreate Advance Wars on a website. This would constitute creating the basic structure (navbar, home page, footer, etc), creating an user interface where players can see the game/map/grid, creating the game logic (how much can this unit move, impassable terrain, damage calculations) and creating a backend infrastructure for moves to be communicated across devices (HTTP request, chess notation JSON files, websocket?).

So what exactly is Advance Wars (AW)?

Advance Wars is a 2001 Gameboy game. Its genre is strategy and its very similar to chess in certain ways.You have a grid/board (a map) and you have units that move in tiles. Some units move 3 spaces, others move 6 spaces, etc. However, unlike chess, you build your own units rather than start with a pre-made selection. Also, units have their own health/HP and they deal different damage values to different units (imagine a soldier hitting a tank with its rifle, would barely scratch the tank. Therefore dealing next to no damage).

An image of an Advance Wars match.

Our Minimum Viable Product (MVP)

What we need to do at the very least in this 8 weeks we’ll have to work in order to produce a decent enough demo :

• Have core website parts (navbar, home page, footer, color branding, logo, etc).
• Have a functional game/grid
  • It displays terrain and unit animations adequately.
  • Have a CO/Character section with income, unit count and army total value.
  • Be able to deal damage adequately, taking terrain into account.
  • Unit movement takes terrain into account, units just don’t move freely to any tiles they want.
  • Players can’t move their opponents units.
  • After a unit performs an action, it gets the “waited/used” status, being unable to perform another action until the next turn.
  • Players can pass the turn to each other and “waited/used” unit status is removed from the active player’s units.
  • Be able to produce units and only units the player can actually afford.
  • Render units, terrain, menus, etc correctly and cleanly.
  • Be able to save gamestate (send JSON chess notation to server).
  • This is all working correctly on a website outside of a local environment (Not a deal breaker but, would be amazing if done).

MVP+

So, did we meet all the requirements above? Then we can start about these things:

• Implement air/water units.
• Implement more CO/characters.
• Implement CO/character powers.
• Implement animations when used.
• Implement more than 2 players in one match (3-4).