Advertisement
Guest User

Untitled

a guest
Dec 8th, 2019
147
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.83 KB | None | 0 0
  1. General:
  2.  
  3. 1h Main frontend design for the system, accessed by the navbar - will show people a breakdown of what they can do with it and CTA buttons
  4. 1h Base team framework including private frontend, allowing users to create a max of one team, and allowing them to be in any amount as members
  5. 1h Team customization in private and on the admin dashboard, allowing people to configure name and upload a logo.
  6. 1h Allow leaders to send players invitations, players will have a "invites" panel where they can accept or deny
  7. 1h Addition to the end-user profile page of the teams they are in, allowing them to view members, and their own personal win/loss history with a link to each team
  8. This profile page should also have individual player stats, k/d, total wins losses etc, all the appropriate ratios
  9. 1h Log match results to the admin dashboard and to the private frontend
  10. 1h Ensure everything is properly locked behind the necessary barrier of discord link and server presence
  11.  
  12.  
  13.  
  14. Match Processing:
  15.  
  16. 1h WebRCON system with request-response for the matches
  17. 1h Allow leaders to start a match, this will let them select a team to fight
  18. 1h Upon selecting a team, the app must contact a list of servers configurable to find an open match, and that server is assigned to the game,
  19. if there are no available servers it will say try again later, servers are busy
  20. 1h When the servers are available the opposing team gets an invitation and a timer starts, if everybody on both sides accepts within the timer then the
  21. game starts and they will be locked in
  22. 1h Temp-ban system, if somebody who accepts fails to show for any reason they will receive a temporary ban that increases each time it happens, and
  23. they will not be allowed to play. This temp ban will be instantiated by an HTTP API that the associated gameserver must call manually
  24. 1h When the game starts, it is put into progress and can be seen in an ongoing games list on the main frontend.
  25. 1h Nobody can participate in any games while they have a game in progress in any capacity, there can only be one game in progress per player.
  26. 1h The game is suspended in an "in progress" mode until the associated server sends back the match results, these results are saved in a match history
  27. and can be seen on user pages, recent matches, etc. Once the saved results have been posted users are free to start a new match if they want
  28. 1h Active matches section on the admin dashboard where you can force close a match with manual results, in case of server problems
  29. 1h Match history on the admin dashboard where it is possible to wipe a match from existance, removing it from stats of members of both teams
  30. 1h Team page that shows a rundown of individual player stats with a link to the players personal pages. Each team page will have wins and losses, ratio of them,
  31. but not averaged individual player stats.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement