Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Free-for-all battles for 3 to 8 players

Abierto
  • ¿Algo no está bien?
#21 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
javascript, nextjs, nodejs
Área
api, backend, distributed-systems

Línea de trabajo

Read backend/server.js to understand the existing one-on-one battle state and identify the runner and problem loader to reuse; then plan a separate lobby module with its own state and socket events. Validate join, start, submission tie ordering, disconnect/rejoin, and host-leaving behavior with socket tests and a recorded run using at least four browsers. Done means npm test and node scripts/check-boundary.js pass, with a short Judge0 request-rate note for an eight-player round.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

enhancement help wanted

Battles are strictly one on one. A free-for-all lobby for 3 to 8 players, all on the same problem, with live standings, is a great format for friend groups, classrooms and streams.

Design

  • Create a lobby, share a link, start when the host is ready.
  • Every player gets the same problem and timer. Standings rank by tests passed, then by time of the submission that reached that count.
  • Live standings show each player's pass count and status, never their code during the round.
  • When the round ends, everyone can see everyone's final code, as in one-on-one battles.
  • Unranked by default. Ranked support can come later and needs its own rating design, so leave it out of scope.

Engineering notes

  • One-on-one battle state in backend/server.js assumes exactly two players in many places. Do not add if (players.length > 2) branches to that code. Build lobbies as a separate module with its own state and socket events, reusing the runner and problem loader.
  • Players dropping and rejoining mid-round must keep their code and position.
  • Submission spam must be rate limited per player, since a lobby multiplies Judge0 load.

Definition of done

  • A recorded run with at least 4 browsers, including one disconnect and rejoin.
  • Socket tests for join, start, submit ordering ties, disconnect and the host leaving.
  • A short load note: Judge0 requests per minute for an 8-player round.
  • npm test and node scripts/check-boundary.js pass.

Large feature: please comment with a short plan before starting.

Lenguaje dominante
JavaScript
Estrellas
0
Forks
2
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de sennaicodes/codearena

Todos los issues de sennaicodes/codearena

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.