Feature description

We are using the dojo-starter web folder but we haven't check anything inside yet. We should go through it & adapt it to our needs (maybe use Vue?) & be sure that everything works correctly.

Acceptance criteria

• The code in web/ is checked
• The code in web/ is cleaned for our needs
• The code in web/ is ready for the next implementations of the game.

Feature description

The CI should include a step that deploys the website located in web/ after every pushes to main.
For example, see rollyourown.

Acceptance criteria

• new CI step added + works

Feature description

Now that the design are roughly documented, let's implement them.
We will start by implementing the overall models & the Lobby system so players can join/leave/create lobbies & create a new game.

Acceptance criteria

• Models created in `src/models/,
• System created in src/systems,

Blocking: #12

Feature description

As soon as the compositions are created, we can assign random roles to players using the Randomizer entity.

Acceptance criteria

• the src/systems/game.cairo file has been updated & assign random roles for each player.

Feature description

After the implementation of the Lobby & the main Game models / systems, we will have to work on the game loops. There's stil uncertainty on how it will exactly works so we have to figure this out.

Acceptance criteria

• A solution have been found + documented for the game loops & we have a list of things to do next.

Feature description

The lobby system have been included & tested.
We can then now implement the Game system & test it.

Acceptance criteria

• Game system in src/systems/game.cairo
• Related unit tests in tests/systems/test_game.cairo

Feature description

Learn more about Dojo and create a document with every components needed (Models etc...)

Acceptance criteria

• A PR introducing a new docs/ folder with the design
• New tasks describing the components to create.

Feature description

Now that the Lobby system have been implemented we need to test it carefully.
That means creating new Models & checking their state after the system calls.

Acceptance criteria

• Unit tests have been added.

Feature description

Currently the CI only runs sozo build without sozo test (because we have 0 tests basically).
Once the unit tests have been created, we need to re-add them in the CI.

Acceptance criteria

• The CI have been updated with the tests.

Feature description

The docs are not up to date with the latest changes & things to come, they need to be updated.

Acceptance criteria

• New documentation is docs

Feature description

Cairo released components not so far ago.
We should check if they work with dojo contracts, if yes we should start by creating a component to access the .world() parameter.

Acceptance criteria

Checked + Added in code if possible.

Bug Report

Werewolves of Cairo version: 0.0.1

Current behavior: sozo test runs two times the same tests

Expected behavior: Tests should run only once

Steps to reproduce: Run sozo test

Related code: N/A

Other information: Probably a bug with sozo, need to investigate

Feature description

Depending on the number of players, we should have certain compositions possibles.
For example, for only 3 players, the composition might be:

• 2 Townfolks,
• 1 Werewolf

It must be done for every number between 3 & 12. We can probably add multiple compositions possibles sometimes (or do it later).

Acceptance criteria

• Compositions have been added in src/data/compositions.cairo

Feature description

Create a Figma for the team & start thinking about which pages would be needed for the game (for example: login, home, lobby creation etc...)

Acceptance criteria

• Figma created
• We have an idea of what pages we will need (either on the figma or in a docs/ folder)

Feature description

Multiplayer game so we need names for players.

Acceptance criteria

• An abstraction have been added, now we would have:
  Profile => profile of a player wallet with avatar, name etc...
  Waiter => player waiting in lobby,
  Player => player in game.