What:

• Implement full usage of BeatKhana-API for the WebPanel.

Why:

To make setting up the overlay quicker.

Current setup path:

- Asked if: 1V1 or Battle Royale (If BR is picked, BeatKhana cannot be used currently)
- Asked if BeatKhana tournament or local (User decides).

If BeatKhana is used:

- Confirmation of tournament-style and that BeatKhana is used.

- Enters User1 and User2 info.
- Enters "Round X"
- Enters BeatKhana tournament ID
- Select a map-pool from the tournament (through API)
- Proceeds to WebPanel to control scoreline and Pick&Ban

If local:

- Confirmation of tournament-style and that BeatKhana is not used.


1V1:

- Enter User1 Info
- Enter User2 info.
- Enter "Round X"
- User is asked to upload map-pool(s)
- Select a map-pool from the uploaded map-pool(s)
- Proceeds to WebPanel to control scoreline and Pick&Ban


BR:

From here the user clicks "Configure",
- Input a complete list of usernames for all users. *1
- Input a complete list of ScoreSaber IDs. (In the same order, as the usernames, so the ID belongs to the username) *1
- Input a complete list of Twitch-usernames. (Same as above) *1
- Proceeds to WebPanel to control player-scores + spectated user.

*1 Example

Using a BeatKhana-implementation removes the need for the WebPanel-user to manually:

- Set user info
- Enter what round it is
- Upload map-pools

Using a BeatKhana-implementation will add automation for those things + add make it so the WebPanel-user simply can select a match from a drop-down window, which then will auto-setup with the following data from BeatKhana:

- Needed user info
- The current round
- Map-pool played in that match/round.

How:

The user will be required to have a tournament created on the BeatKhana website, have it public, show participants, have a bracket generated + have map-pools created, named (Round 1, Round 2, LR1, LR2 etc.) and public.

This information will be fetched through the BeatKhana-API, where we simply ask the API to for the following:

Assuming the user picks a BeatKhana-setup, the setup-would look like this:

- Asked if: 1V1 or Battle Royale (User picks the style of tournament)
- Asked if BeatKhana tournament or local (User picks BeatKhana)
- Asked for their BeatKhana tournament ID (The numeric value in the URL when on the specific tournament-page)

If 1V1:
- Asked to pick a match. (Dropdown example: "Cerret-gustav, Round 1", "Cerret-Garsh, Round 2", and so on)
- Proceeds to WebPanel to control scoreline and Pick&Ban

If BR:
- Adds the complete participants list to the control-panel. (BeatKhana-name, ScoreSaberID and TwitchName)
- Proceeds to WebPanel to control player-scores + spectated user.

What:

• Implementing multi-match handling.

Why:

Because right now, the backend is horribly set up, and only allows for one ongoing match, which can cause problems for multiple on-going matches.

How:

The backend will be rewritten to handle arrays, where current matches will be stored:

{
	"matches": [{
		"1": {
			"matchid": "1",
			"players": ["76561198086326146", "76561198086326146"],
			"coordinator": "Hawk",
			"round": "1",
			"currentMap": "Unpleasant Sonata",
			"currentMapHash": "6423F3A3429D503FA97A1C5282155436D12A9366",
			"currentMapDiff": "Easy"
		},
		"2": {
			"matchid": "2",
			"players": ["76561198086326146", "76561198086326146"],
			"coordinator": "Hawk",
			"round": "3",
			"currentMap": "Unpleasant Sonata",
			"currentMapHash": "6423F3A3429D503FA97A1C5282155436D12A9366",
			"currentMapDiff": "Easy"
		}
	}]
}

and so on.

This will allow for multiple matches to be ran at the same time, without coordinators interfering with eachother and the auto-map function.

ETA: No idea, a bit pressed on time because of life.

Why:
While testing the BR Overlay with 32 people, the Relay Server seized up, and stopped providing information.

This prevented the BR Overlay from updating, giving a live score.

How will it be fixed?:

• 1V1 and BR Overlay will have the TA overlay-connection webpacked and bundled, removing the need to send scores through the relay server.

The relay server will still be relevant, as it's used to communicate between WebPanel, P&B, setting the 1V1 overlay info(Username, image, current map and so on).

ETA: 9th of October, 2022