That's a spicy meatball

* APIUtils additions
* Socket and web server listen on dedicated ports (see denoland/deno socket issue created by ZombieB1309 on GitHub)
* Coach and Server created automatically (untested)
* Profile content functions split into 'managers'
* Progression temporary implementation
* Settings placed into profile content manager
* Relationships and messages return temporary empty array
* Socket targets defined, message delivery to target, exec returned (goes unused for now)

src/routes/match/player.ts

@@ -3,6 +3,7 @@ import { APIUtils, NoBody } from "../../apiutils.ts";
 import express from "express";
 import Matchmaking from "../../data/live/base.ts";
 import Presence from "../../data/live/presence.ts";
+import { AuthType } from "../../data/users.ts";
 
 export const route = APIUtils.createRouter('/player');
 
@@ -17,6 +18,7 @@ const LoginSchema = z.object({
 route.router.post('/login',
 
     APIUtils.Authentication,
+    APIUtils.AuthenticationType(AuthType.Game),
     express.urlencoded({extended: true}),
     APIUtils.validateRequestBody(LoginSchema),