1. załadowanie gry: game -> serwer 'markGame', serwer-> game 'playersInfo'
2. Gra -> serwer 'gameReady'

3.0 Serwer -> game 'nextPlayerTurn' (id) 3.1 Gra - wyświetla: Tura gracza {id} 3.2 Serwer -> player 'yourTurn'(ilomaKostkami) i czekam na 'diceValue' 3.3 Android - uruchomienie aktywności 'dice' lub więcej kostek 3.4 Android -> serwer 'diceValue' (diceValue) 3.5 Serwer odbiera 'diceValue' 3.6 Serwer -> game 'playerDice'(id, diceValue) 3.7 Gra - ruch awatara 4 3.7.1 Gra -> serwer 'finish' 3.7.2 Gra -> serwer 'specialGrid'('nazwa') 3.8 Serwer odbiera opcjonalny event 3.8.1 'finish' - rzuca wyjątek 3.8.2 'specialGrid' - rozpoczęcie nowej minigry (osobny zestaw instrukcji) 3.8 Gra -> serwer 'endTurn' 3.9 if(game !== undefined) jump to 3.0

'castle' 'stadium' 'challenge4' 'challenge5' 'challenge6' 'townHall' 'oneVsAll'

Getting started

Aby pobrać zależności: npm install

Uruchomienie: npm start - wywołanie skryptu "start" z pliku package.json - domyślnie development mode

Aplikacja uruchamia się z odpowiednim profilem na podstawie zmiennej NODE_ENV Na przykład: SET NODE_ENV=development && node server.js - development mode SET NODE_ENV=test && node server.js - tryb do testów

Do uruchomienia bazy danych potrzebujemy serwera MySQL:

• włączamy serwer MySQL
• jeśli nie mamy bazy pollub73 uruchamiamy skrypt tworzący: node scripts/create_dev_database.js"
• Uruchamiamy aplikację npm start lub node server.js.

HttpApi(localhost:8081)

• '/'- home page

• '/login' - login to app if you already have an account

• '/signup' - add new administrator profile

• '/profile' - access to this site after successfully login

• '/logout'

• '/stoptimegame' - Stop Time minigame

• '/test' - Phaser game test

SocketIO server API

Common api for both player and game:

• Handled events:

  • 'connection' - emitted after io.connect call by client, like this: io.connect('/1') where '1' is a room number. After connection application is waiting for 'setName' or 'markGame' events, to identify client as player or game (browser).
  • 'playerName' - player name setter - after this event, application identify socket as a player and will create a new player object. In parameter expected string with player name.
  • 'markGame' - after this event socket will be marked as a game (browser).

Api for game:

• Handled events:

  • 'disconnect' - not implemented, application throws Error.

• Emitted events:

  • 'playersInfo' - in args array of objects (players) with two properties: 'name' and 'inRoomId'. Array length is number of the players. Emitted after 'markGame' event.
  • 'stopTime' - emitted after handle 'stopTime' event from player, in args number - player.in_room_id
  • 'playerDice' - emitted after handle 'diceValue' event from player, in args object with 'id', and 'value' (dice results) keys.

Api for player:

• Handled events:

  • 'disconnect' - player will be removed from room and from database.
  • 'stopButton' - emit event 'stopTime' to game socket
  • 'diceValue' - emit event 'playerDice' to game socket, in args expected number with dice results

Debugowanie

Ustawić zmienne środowiskowe za pomocą komendy 'set' w terminalu. set DEBUG=*

Testy

Aby uruchomić wszystkie testy korzystamy z komendy: npm test Albo korzystamy z IDE. Pozdr. ✨🐢🚀✨