1
0

Use "loadGame" instead of "createGame" on ws connection

Signed-off-by: James Ketrenos <james_eikona@ketrenos.com>
This commit is contained in:
James Ketrenos 2022-03-01 13:19:23 -08:00
parent 4be68a39f1
commit 35c6033ae5

View File

@ -2498,19 +2498,19 @@ const ping = (session) => {
session.keepAlive = setTimeout(() => { ping(session); }, 2500); session.keepAlive = setTimeout(() => { ping(session); }, 2500);
} }
router.ws("/ws/:id", (ws, req) => { router.ws("/ws/:id", async (ws, req) => {
const { id } = req.params; const { id } = req.params;
console.log(`WebSocket connect from game ${id}`); console.log(`WebSocket connect from game ${id}`);
let game; const game = await loadGame(id);
if (!(id in games)) { if (!game) {
game = createGame(id); console.error(`Unable to load/create new game for WS request.`);
} else { return;
game = games[id];
} }
const session = getSession(game, req.session); const session = getSession(game, req.session);
if (session) { if (session) {
console.log(`WebSocket connected for ${session.name ? session.name : "Unnamed"}`); console.log(`WebSocket connected for ${session.name ? session.name : "Unnamed"}`);
session.ws = ws; session.ws = ws;