Home

A vigilante, an arsonist and pigeons.

We bring you, Singed Feathers! --A strategy game where you fight for the fate of pigeons.

Become a master strategist and be matched against willing opponents, or invite a friend to their demise. Be creative and design a playing field to your advantage. Share your meticulous creations with others, or take the challenge of owning up on a field designed by your enemy. But before you begin there’s one question: save the pigeons or burn them?

What side will you choose?

Detailed Description

Our vision is to make a game where two players play opposing roles, either choosing to save pigeons or to burn them. Players make their decisions simultaneously then watch them resolve in a deterministic way; promoting strategy through clear pre-determined behaviour. Players, in addition to playing against others, may choose to create levels and share them with other players through a server based service. Along with the level sharing service, there will be a service for pairing players up for games. This matchmaking service will allow players to easily find others willing to play. Despite the game being a multiplayer game, the main design feature will be level creation. For this reason the game will run from the client level, requiring validations from a server side service mostly only while playing with other players.

Game Components

Map-maker

• Lvl test
• Map validation

Gameplay

Matchmaking

• Invite based initially

UI

Mobile API

Persistence

Backend

Game Roles

There would be two roles, GoodGuy and BadGuy.

In the simplest version of this game, all levels would be GoodGuy against BadGuy (more on this later) with objectives as described below.

• BadGuy: Burn enough pigeons to win (amount specified by the level) by using some of your items (x1 per turn) to burn the pigeons.

• GoodGuy: Herd the pigeons to safety (by using some of your items [x1 per turn] or by leading individual pigeons), so that you save enough pigeons to win (amount specified by the level).

Road Map

Timeline

• First official sprint will start on Thursday Feb 2nd.
• Each sprint will be 1 week long.
• Last sprint will be from March 30th - April 6th
• Final project implementation is on the 10th
• From the 6th to the 10th is for bug fixes and small changes, nothing major.
• This gives us 9 sprints in total to work with.
• Before discussing details we should aim to have an MVP by sprint 7 at minimum. (This could change drastically, but it gives us some flexibility)