stlmpp / biomercs-api-old

Contato

biomercs-api-old's Issues

Fix stages coming in the wrong order

Stages are coming in the wrong order in some end-points:
score/table-top
score/table-player

Add "order" column to most of the tables

• Game
• Mode
• Stage
• Character
• Type
• Platform

Add search api

A general search for users, scores, etc

Achievements

Add achievements to the application

Ideas:

• Submit a score in each game
• Submit a score in each mode
• Beat your own high score
• Beat a score of someone you're following
• Beat a WR
• Follow somone
• Be followed by someone
• Submit a score with someone you're following

Add score approvals

• Define how the approvals will work

Score will have a column status, and a history (ScoreApproval), there will be 2 types of approval, user and admin, user being a duo score, and admin being, well, admin

• Do not return the scores in the queries if it's not approved

There will be specific end-points to get the rejected and not approved scores

• The approval system will be based in the worlds records, but will depend on other things too, like average score, etc

This will need more thinking

Improve roles system

• Add more roles
• Roles based on games/game-modes/etc

Add Reason and Report Reason tables

This will store the reasons for a report, user will select one or more of these to report

Refactor Player concept

• There will be a Player entity
• Player will have a relation with Score Player, User and Steam Profile
• User will not be necessary anymore to create scores

Add CharacterCostume table

Costume table will have a relation of ManyToOne with Character, and the lists that includes characters will take into consideration this table too.

Relations:

ManyToOne -> Character
idCharacter -> id

Maybe I'll have to create another table GameModeCharacterCostume... I don't know yet

E.g.

Character: "Chris"
Costumes: ["BSSA", "STARS", "Costume 1"]

Refactor login and register

Login and register needs a refactor

• Implement confirmation on e-mail only by code, and not link (related stLmpp/biomercs-api#2)
• Google login (won't do)
• Implement Steam login

Create a method to update score

The user will be able to edit some info about the score, and depending on what he edited, the score will need a second approval.

This will also create a new column (version), to see how many times the score was updated

Remove relation between tables and file upload

Maintain only the prefix for the image in the table, like re5, public-assembly, etc (needs to be defined)

• Character
• Game
• Game Mode
• Platform
• Stage

Optimize score table queries

The queries are very slow right now

• Characters (profile)
• Top scores (general)

Add user settings

Add a new table to save user settings, like date format, etc

Add comments in the user and score

• User
• Score

Fix route params not using the enum

Some routes are not using the RouteParamEnum to define the params/queryParams

Add Game Mode Stage entity

This will be needed to record the max enemies in the stage, on the game mode

Add one more role "Owner"

This role will be able to create users, assign roles, and have the overall control of an admin

Add websockets

Emit events when:

• Create table to register the events (notifications)
• User submit a new score
• User start following you
• User score is approved/rejected

Update mailing templates

For confirmation and password reset, maybe do something like a code instead of a link to reset/confirm.
Also, add confirmation mail to e-mail changing

• Confirmation
• Reset password

reCAPTCHA v3

Related: stLmpp/biomercs#26

• Score approval
• Login
• Register