Epic: every newer area, monster, NPC and pet from v1.696, the ISRO-R DB and the opensro zip

Abierto
#3,264 0 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
5/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go, typescript

Línea de trabajo

This is an umbrella epic with no comments and no assignee, linking eight child issues and one pull request (#3250). Do not start here: pick one child that is small and named, such as the inventory step in #3251, and read its own thread. The epic is done only when every child issue is closed.

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

Descripción

area: client area: server enhancement priority: critical

Owner ask, 2026-11-12: bring in every newer area, monster, NPC and pet the later sources hold.

Sources:

  • v1.696 client: a later native client, pinned in #3250, so its content is native.
  • ISRO-R DB: fills in what the v1.696 client lacks.
  • v2.355 export: always read through the pinned, optional opensro zip. Its content is port-only behind flags.

Children:

  • #3249 / PR #3250: v1.696 mall avatars
  • #3254: the opensro zip (avatars first; the packer then carries the files #3262 and #3263 need)
  • #3262: pets of every kind from v1.696 and the zip
  • #3246: Alexandria monsters from the client alone
  • #1800: the 91-99 tomb and temple content in the VSRO data
  • #3247 / #3251: inventory of v1.696's maps and monsters. The client is now on the workstation (inputs/sro_1696, pins in #3250), so #3251 is unblocked.
  • #3252: ISRO-R late areas (Jupiter, Arabia, GOD era, temples, instances)
  • #3263: the v2.355 export's areas, monsters and NPCs

Order:

  1. Inventory: #3251 and #3263's first step.
  2. One import PR per area. Native sources come before the zip, so a zip area never shadows a native one.
  3. Every import reports what it took and what it skipped.
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.