Import the Secret Tomb and the last-era boss kinds (v1.696)

Abierto
#3,274 8 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
backend, game-dev

Línea de trabajo

Start with the inventory at research/investigations/later-sources-3247/v1696-inventory.md to see which MOB_SECRET_* and MOB_LAST_* kinds and RN_SECRET_TOMB_DUNGEON_TOP/BOTTOM region shells are listed. The open work is working out the terrain mapping from those shells to the region ids that hold their terrain, and deciding the level cap above 140. Done means the Secret Tomb is built behind its flag with its kinds placed, the cap decision is recorded, and the flag-off build behaves as before. Get the design settled in the thread before writing code.

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

Descripción

area: server enhancement priority: critical status: gated

Per-area import from the #3247 inventory (owner 2026-11-12: every new map and monster will be imported).

Evidence: research/investigations/later-sources-3247/v1696-inventory.md. MOB_SECRET_* and MOB_LAST_* kinds run levels 150-190 in the v1.696 client, and RN_SECRET_TOMB_DUNGEON_TOP/BOTTOM exist as region shells whose terrain lives under other region ids. Both the terrain mapping and a level-cap decision past 140 are this import's first work.

Done when: the Secret Tomb is built behind its flag with its kinds placed, the cap decision recorded, and the flag-off build is unchanged.

Ungate when: owner decides

Lenguaje dominante
Go
Estrellas
97
Forks
61
Merge medio
4 h 14 min
PR fusionados (30 d)
913

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 opensro-dev/opensro

Todos los issues de opensro-dev/opensro

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.