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

Hide the duplicate Exits line in the player

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

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
full-stack

Línea de trabajo

Start with packages/engine/src/describe.ts and packages/engine/src/types.ts to see how the exits message becomes an OutputBlock, then read apps/web/src/components/transcript.ts and packages/cli/src/commands/play.ts for rendering behavior. Check packages/engine/src/playtime.ts and section 4 of docs/architecture.md as well. Done when the player hides the exits block, lexvm play still prints it, tests cover both behaviors, and estimates for both packs are unchanged.

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

Descripción

area: engine area: web priority: low type: feature

Context

The default room description ends with a system line listing the exits ("Exits: north, cellar." from the exits message in packages/engine/src/describe.ts). The player also shows the exits as chips in the dock, so every room description lists them twice. lexvm play and other front ends without chips still need the line.

Scope

  • Engine: make the exits block identifiable, for example a dedicated output block kind or a marker on the system block. This is an additive change to the output type, not to the pack format; document it in docs/architecture.md section 4.
  • Player: do not render that block in the transcript; exit chips stay as they are.
  • lexvm play keeps printing it.
  • The play-time estimate ignores the block, as it ignores system blocks today.

Acceptance criteria

  • Room descriptions in the player no longer show the "Exits" or "Ausgänge" line.
  • lexvm play still prints it.
  • An engine test asserts that the block is identifiable; a player test asserts that it is not rendered.
  • Play-time estimates of both packs are unchanged.

References

  • packages/engine/src/describe.ts
  • packages/engine/src/types.ts (OutputBlock)
  • packages/engine/src/playtime.ts
  • apps/web/src/components/transcript.ts
  • packages/cli/src/commands/play.ts
Lenguaje dominante
TypeScript
Estrellas
0
Forks
0
Merge medio
28 min
PR fusionados (30 d)
2

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 nullthrone/lexvm

Todos los issues de nullthrone/lexvm

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.