Think about better approach.

During sign up on a client side, the user is not added to the database, thus causing FK error

It will add up a new (maybe unnecessary) layer for security check, and database related work. However, there are only 2 tasks that are done: text fetch and saving race data. We could make the game server more computing-heavy (network-heavy), and the web server more responsive for web connections (how?).

Also, the web server will have a firebase token user sign up processing and it will create a user "before" the race data will get saved (for non-existent user). One important notice of this is that the communication between servers can be always secure, because they will have whitelisted IP addresses.

Personal Page:
- Show last race date (1 day ago) (MadinaB) P.S. Write tests
- Show best race ever (by cpm) (MadinaB)
- Races won
- Allow country specification (Aibek)

• Design points system (IN NEXT VERSION)
  - Design accuracy system (Aibek)
  - Make a user's input colored on inaccurate typing, and vice-versa (Aibek)
  - Show last race's wpm/cpm (Madina)
• Allow conversion from wpm to cpm (IN NEXT VERSION)
  - Allow showing first race's date (Aibek)
  - Show a graphic of improvement (of races)** (Aibek)

Settings:
- Language selection* (Scores for different languages should be separate) (Aibek)

Leaderboard:
- Show last 20 best racers (include only today's races) (Aibek)
- Show best races of all time (Aibek)

Other:
- Design/develop a way of recording a winner of race (Aibek)
- Make it possible to end game if a user goes 'back' or stops the game. (Aibek)

• Develop a friend system*** (IN NEXT VERSION)

• Check API request's parameter's length, and security

• Allow viewing other users' profile pages** (IN NEXT VERSION)

• Create a group of races (IN NEXT VERSION)

• Create individual races (IN NEXT VERSION)

• Add social tools (Facebook, Twitter)
  - Add adds, monetize** (Aibek)
  - Add bots for gaming* (Aibek)
  - Make anonymous playing possible (Aibek)
  - After a game ends, show a window of general post-race info (Aibek)

  • Show a best wpm made for a text (IN NEXT VERSION)

• Show available texts (IN NEXT VERSION)

• Make possible to choose specific texts and race on them (IN NEXT VERSION)

• Show time of finishing some text/race (IN NEXT VERSION)

• Add tests***

  • Conduct load testing on all servers, make tweaks
  • Add unit tests
  • Add end-to-end tests?

• Add notifications support***
  - Check if a user can play from two devices at the same time
  - What happens if a user enters an app and do not visit personal page, will them be able to play game and save data? (Aibek)

• Add sounds (IN NEXT VERSION)

• Write a shell script for initializing a working environment (like IP change)

We could make it download before the modal is actually show.

And make the ad as a different component.

If a user disconnects during "find partners" phase, and connects again, there is a chance that they will play against themselves. Their cpm will be zero.

If a user enters a game, then the network is lost (for example wifi is off), then after some time a user reconnects again, the client will ask for two new games.

The player is however disconnected from old game.

Also error object is not rendered normally, should made as string

App currently works only in online, without the connection to the Internet, it does not work

Write here

1. All clients disconnect before game ends -> The game should immediately stop, and no results should be saved into DB, the game entry in Redis should be deleted

2. There are multiple clients, all except one disconnect -> The game should continue, there should not be an entry in redis, and the data of single player should be saved into DB.

3. All players finish the game, one loses and another wins -> Both players should be saved into DB, no game record should be left in Redis

4. One player creates a room, then immediately exits it, and then enters again while the room has not yet started -> An (authenticated) user should be able to enter the room, however should be replaced. However, when playing anonymously should not be replaced, the result from disconnected players just has to be not saved into DB. The client should disconnect from a room, which was written in its socket._serverData.roomKey during creation of room or assignation to it. The client should flush the roomKey after gameEnd/disconnect.

5. If user (both anonymous and authenticated) is disconnected, then they should be marked in redis as disconnected. They should be not saved to DB.

6. Game was created, however all players left -> the game should not even start

7. First player creates a new game, after it starts, second player creates another game -> There should be two completely separate games.

8. Bots should be created, if there less than some amount of players

9. Anonymous limiter (maximum 50 games from one IP) should be present, check this if a user signs up then, or signs in

10. Maximum players in room should be checked

11. Disallow same ip address from creation of too many rooms

12. Make game-server encrypt data between client and server, and make it unfakeable

13. Test for leaked timers periodically, delete them automatically

14. When a game finishes, all sockets should be closed

15. When a user send too many racedata requests -> The user should be blocked and connection should be closed, the player also needs to be removed from room.

Undefined socket value

Line GameTextInput.js:47

Add nicknames, and other info

Think on ways to do that with existing architecture.

It must fade away on back click on android, and if clicked on the background

Players are not saved in DB if they are not winners (finish text), but still it is a buggy behavior.

There are many other race conditions..

On personal page, on the first app entry, the user sign in form is being showed up. Instead, it should show a loading button or image and then show the correct page.

Probably using Firebase Logs would help

On a first app entry, when a user signs in to the app, there is a inconsistency between firebase and the web-server. The user is not persisted in the web-server.

For example, if a client sends request in order to get the basic information of the user, it receives 400 error and crashes.

It can happen both when a user signs up or signs in.

We actually must send a request to create the user on the webserver (on sign in/up), and only then send the requests for their info.

Error: Forbidden action game:5598d57b-9988-4c74-9df6-d6c255f84d6f:en
File "/Users/admin/Documents/UNIST/8semester/typemasters-game/game-server/index.js", line 325, in _validateClient
const err = new Error('Forbidden action ' + data.roomKey)
File "/Users/admin/Documents/UNIST/8semester/typemasters-game/game-server/index.js", line 250, in Command.callback
if (!_validateClient(room, data, socket)) {
...
(8 additional frame(s) were not displayed)

Watch on sentry

When a user wins/finishes a game quickly (before timeout), his CPM is still computed by game server as if they are still playing. Instead, the game server should save his data and stop updating it, also record his winning position.

Detect ip addresses of anonymous users and put limits on amount of times they can play per day. For example, 50. Also, send a message to client that their limit is expired, so they better sign up.

There might be some race condition

The MySQL datetime is stored in UTC, however we somehow need to convert it to the local time

The game window is lost and the race is still saved to DB, not interrupted.

The statistics queries stop showing information, because of failed joins