Jonathan Zhou, Michael Tu, Andrew Boyaciliger, Jake Stifelman
Repository Link: https://github.com/jonathanzhou1/OMatch
OMatch! is a platform dedicated to creating fun and competitive 5 v 5 basketball games at the OMAC. The frontend interface allows users to create persistent profiles to store their information such as name, basketball position, and keep track of win-loss records, and find 5 v 5 matches with people of similar skill levels to them based on ELO rating and matchmaking algorithms on the backend. Through this, we hope that students and community members in Providence will be enabled to have optimized, fun games that they can plan out ahead of time with players that are less intimidating because of similar skill levels.
Currently, you will have to start the backend server by running the main program in 'Server.java'. You should see a message saying that Server started at http://localhost:3232. Then, run the frontend interface by going into the 'OMatch/omatch' directory and running npm run dev and going to http://localhost:5173.
Note: For matchmaking, you will need a minimum of 10 users queued.
profile-add <name> <position>- The profile addition handler manages the addition of profiles to the backend database. Any players with exactly the same name and position will be treated as different players with a different ID, so it is imperative that you use the editing handler for editing or deleting players.
- The
namequery has to do with the player's name, taken in as a UTF-8 String. - The
positionquery has to do with the player's position, and it can be one of five possibile strings. Any other string put here will result in an error:POINT_GUARDSHOOTING_GUARDSMALL_FORWARDPOWER_FORWARDCENTER
profile-view <id>- The profile view handler retrieves all relevant data to the player, including, name, position, ELO ranking, and W/L ratio.
- The
idkeyword is a randomized, unique ID for each player. 20 characters long. If noidkeyword is present, the handler will return the list of all players
profile-edit <action> <id> (name) (position)- The profile edit handler manages the editing and/or deleting of players.
- The
actionquery has to do with whether the player in question is being edited or deleted. As of such, it can be one of two strings, "edit" or "delete". These strings are not case-sensitive - The
idkeyword is a randomized, unique ID for each player. 20 characters long. - The
namequery is the player's new name, only recognized when the action is set to edit. This keyword is optional and the player's name will not be updated if it is not present. - The
positionquery is the player's updated position. These keywords are the same as for theprofile-addhandler. As with the name, this keyword is optional and will not be updated if it is not present.
match-end <id> <playerWon>- The match end handler is called when a player indicates that the match has ended and that they think the court can be freed. It should be noted however, that the handler requires all players to have a query associated with them for the handler to automatically delete the match and update the players' stats.
- The
idkeyword is a randomized, unique ID for each player. 20 characters long. - The
playerWonkeyword is linked to how the player did in that game. It can be one of the following. Any other words will be interpreted as a loss:winlosetie
match-view- Returns a list of match objects, each containing details about the court the match is taking place on, as well as teams and their respective players.
queue-view- Returns either the queue or the position of a player within the queue
queue-add <id>- Adds a player to the matchmaking queue. When the queue length is 10, the first 10 players in the queue will be dequeued into a match. Whether this has happened will be represented by the NewCourtAdded boolean, which will be true if a new court has been added, and false otherwise.
- The
idkeyword is a randomized, unique ID for each player. 20 characters long.
There are 6 various response and error codes from the backend API.
| Result | Meaning |
|---|---|
success |
The operation was parsed correctly and there were no issues, internal or external, with your request. |
error_bad_request |
The most common error. This is thrown when a query is missing or when the contents of the query do not meet the specificationg of the API. More information is shown in the details portion of the response. |
error_server |
There has been an internal server error while processing your request. Possible diagnostics include sending the request again or sending angry messages to the developers, which is the less preferred option. |
error_datastore |
There was a failure in the datastore portion of the server. The recommended course of action here is to check over your datastore object and test its functionality. |
matchmaking_error |
There has been an internal matchmaker error. Additional testing and review of matchmakers will allay this error. |
matchmaking_full |
Every alotted court has been filled up, the player has successfully been added to the queue, but they need to wait until other people leave to free them a space. |
For the sake of brevity, some example queries will have the following two aliases instead of the entire object. This is because these objects are either very large, repititious, or both; and, therefore need to be aliased under a smaller name. They are the following:
playerN
{
"id":{ID},
"losses":{Losses},
"name":{name},
"position":{Position},
"skillLevel":{Skill Level},
"wins":{Wins}
}
matchN
{
"outcome":"ONGOING",
"team1":
{
"avgSkill":10.0,
"players":
[
{player1},
{player2},
{player3},
{player4},
{player5}
],
"size":5
},
"team2":
{
"avgSkill":10.0,
"players":
[
{player6},
{player7},
{player8},
{player9},
{player10}
],
"size":5
}
Successful requests
1. profile-add?name=Josh Joshington&position=SMALL_FORWARD&id=a0Xd2wuFh9oGb3aJuv4K
{
"result":"success",
"playerID":"a0Xd2wuFh9oGb3aJuv4K",
"queries":
["name","position"]
}
- profile-add?name=Baka Sussy&position=CENTER&id=awWo0cH6jw4Ib8fD9Fgi
{
"result":"success",
"playerID":"awWo0cH6jw4Ib8fD9Fgi",
"queries":
["name","position"]
}
Unsuccessful requests
- profile-add
{
"result":"error_bad_request",
"details":"Error in specifying 'id' variable: id neccesary",
"queries":[]
}
- profile-add?id=1234567890
{
"result":"error_bad_request",
"details":"Error in specifying 'name' variable: name neccesary",
"queries":["id"]
}
- profile-add?id=1234567890&name=Sussy%20Baka
{
"result":"error_bad_request",
"details":"Error in specifying 'id' variable. Please use 'POINT_GUARD', 'SHOOTING_GUARD', 'SMALL_FORWARD', 'POWER_FORWARD', or 'CENTER' in your position query: position query neccesary",
"queries":["name","id"]
}
- profile-add?id=1234567890&name=Sussy%20Baka&position=CENTER (Note: this is only in the case where you have already added this ID to the database)
{
"result":"error_bad_request",
"details":"Player already exists in the database, please use edit handler instead: Player to be added already exists within database. Please use updatePlayer in this instance.",
"queries":["name","id","position"]
}
Successful requests
1. profile-view?id=a0Xd2wuFh9oGb3aJuv4K
{
"result":"success",
"player":
{
"id":"a0Xd2wuFh9oGb3aJuv4K",
"name":"Josh Joshington",
"skillLevel":9001.112,
"wins":12,
"losses":0,
"Position":"SMALL_FORWARD"
},
"queries":
["id"]
}
- profile-view?id=awWo0cH6jw4Ib8fD9Fgi
{
"result":"success",
"player":
{
"id":"awWo0cH6jw4Ib8fD9Fgi",
"name":"Baka Sussy",
"skillLevel":235,
"wins":6,
"losses":29,
"Position":"CENTER"
},
"queries": ["id"]
}
- profile-view
{
"result":"success",
"players":
{
"a0Xd2wuFh9oGb3aJuv4K":
{
"id":"a0Xd2wuFh9oGb3aJuv4K",
"losses":0,
"name":"Josh Joshington",
"position":"SMALL_FORWARD",
"skillLevel":10.0,
"wins":0},
"awWo0cH6jw4Ib8fD9Fgi":
{
"id":"awWo0cH6jw4Ib8fD9Fgi",
"losses":0,
"name":Baka Sussy",
"position":"CENTER",
"skillLevel":10.0,"wins":0
}
},
"queries":[]
}
- profile-view (Empty list)
{
"result":"success",
"players":{},
"queries":[]
}
Unsuccessful requests
- profile-view?id=incorrectID
{
"result":"error_bad_request",
"details":"No item found within the database: No Player found with corresponding ID",
"queries":["id"]
}
Successful requests
1. profile-edit?action=delete&id=a0Xd2wuFh9oGb3aJuv4K
{
"result":"success",
"queries":
["action","id"]
}
- profile-edit?action=eDiT&id=awWo0cH6jw4Ib8fD9Fgi&name=Sussy Baka&position=SHOOTING_GUARD
{
"result":"success",
"queries":
["action","id","name","position"]
}
- profile-edit?action=EDIT&id=awWo0cH6jw4Ib8fD9Fgi&position=SHOOTING_GUARD
{
"result":"success",
"queries":["action","id","position"]
}
- profile-edit?action=edit&id=a0Xd2wuFh9oGb3aJuv4K&name=Bosh Boshington
{
"result":"success",
"queries":["action","id",'name"]
}
Unsuccessful requests
- profile-edit?action=edit&id=definitelynotaplayerid&name=Bames Jond&position=SHOOTING_GUARD
{
"result":"error_bad_request",
"details":"No item found to edit: No Player found with corresponding ID",
"queries":["name","action","id","position"]
}
- profile-edit?id=definitelynotaplayerid&name=Jond, Bames Jond&position=SHOOTING_GUARD
{
"result":"error_bad_request",
"details":"action keyword must contain the word 'edit' or 'delete'. Any other word will result in an error",
"queries":["id","name","position"]
}
Successful requests
- match-end?id=2&playerWon=lose
{
"result":"success",
"queries":["id","playerWon"]
}
Unsuccessful requests
- match-end?id=1234567890
{
"result":"error_bad_request",
"details":"Error in specifying 'playerWon' variable. Variable must be 'win', 'tie', or 'lose'",
"queries":["id"]
}
- match-end?id=1234567890
{
"result":"error_server",
"details":"Error getting match data from the server: {exception}",
"queries":["id"]
}
Successful requests
1. match-view (Shown here with 3 matches but this number is configurable)
{
"result":"success",
"matches":
[
{match1},
{match2},
{match3}
],
"queries":[]
}
Successful requests
1. queue-view
{
"result":"success",
"PlayerQueue":
[
{
"id":"a0Xd2wuFh9oGb3aJuv4K",
"losses":12,
"name":"Josh Joshington",
"position":"POWER_FORWARD",
"skillLevel":10.0,
"wins":20
}
],
"queries":[]
}
- queue-view?id=a0Xd2wuFh9oGb3aJuv4K
{
"result":"success",
"playerPosition":1,
"queries":["id"]
}
Unsuccessful requests
1. queue-view
{
"result":"error_datastore",
"details":"Datastore Error: {exception}",
"queries":["id"]
}
Successful requests
1. queue-add?id=1234567890
{
"result":"success",
"Message":"Player added to queue",
"newCourtMade":false,
"addedID":"1234567890"
}
- queue-add?id=1
{
"result":"success",
"Message":"Player added to queue",
"newCourtMade":true,
"addedID":"1",
"court":
{
"match":{match1},
"players":
[
{player1},
{player2},
{player3},
{player4},
{player5},
{player6},
{player7},
{player8},
{player9},
{player10}
]
}
}
Unsuccessful requests
- queue-add?id=1234567890 (second time)
{
"result":"error_bad_request",
"details":"Player has already been added to queue.",
"newCourtMade":false,
"queries":["id"]
}
- queue-add?id=incorrectID
{
"result":"error_bad_request",
"details":"Player Not Found: No Player found with corresponding ID",
"newCourtMade":false,
"queries":["id"]
}
Each user in omatch will be assigned a Player class. This class will contain their specific user ID, skill level, W/L record, position, and other necessary information.
Players are assigned to teams in our matchmaking algorithms (described below). The teams class contains information about the average skill of the team itself.
Two teams are assigned to a Match class. The match class keeps track of ongoing games and the outcome of said games. Based on the outcome, the skills will be adjusted accordingly.
The IMatchMaker interface implements the matchmaking method, which will take in a list of players, divide them into teams and return matches based on those teams. Based on the input, the matchmaking algorithm can divide players into any EVEN number of teams. More matchmaking algorithms can be implemented with this interface in the future.
- SimpleMatchMaker - This algorithm does not take into account skill. Rather, it just splits players up 1 by 1 onto separate teams. It then combines teams two by two into matches.
- SortSkillMatchmaker - This algorithm sorts each player based on skill level. Then, it splits players 1 by 1 onto separate teams. Once this is complete, the teams are sorted again based on average skill to ensure more parity. The teams most similar in skill are then paired together, from highest to lowest rank.
- PositionMatchMaker - This algorithm sorts players on skill level, but prioritizes making sure each team has players from each position. First the players are split up into their respective positions, and then split up evenly amongst all teams to minimize the overlap of positions and ensure teams are as balanced as possibles. The remaining players are split up based on skill like in SortSkillMatchmaker.
Skill-Level(SL) is set at 1500 when a player profile is created, and modulated based on their performance in future games. The SkillUpdater interface implements the skillupdater function, which takes in a completed match and updates the skill levels of the players in the match depending if they win or loss. Like with matchmaking, we implemented three algorithms of increasing complexity.
- SimpleSkill - This algorithm substracts 1 point from all players that loss the game and adds 1 point to all players that win the game.
- WLSKill - This algorithm sets the skill level of each player to their W/L ratio.
- EloSkill - This algorithm implements a generalized version of the EloAlgorithm over a teams approach. The expected outcome is determined beforehand, and a team's skilllevel is adjusted depending on how likely or unlikely they were to win a game. For example if a weak-ranked team beats a much higher ranked team, they would see a dramatic increase in their collective skill levels. However, if a highly ranked team beats a team that is much lower ranked then them, there skill levels will only increase by a marginal amount. More information about the ELO algorithm can be found at this link: https://en.wikipedia.org/wiki/Elo_rating_system