Landscape generation - tweak land type placement distances
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Start by locating the landscape-generation options, the code that places land types relative to water, mountains, and cliffs, and the configuration-loading path. Check existing tests or add focused coverage for configured distance limits and clamping; done means the supported distances can be configured within reasonable bounds and affect placement as intended.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the solution you'd like
Instead of having fixed distances for the different land generation options (near water / far from water / on mountains / far from mountains and arround cliffs), allow the distances to be set via config file (clamped to some reasonable values). For example, "Near Water" option currently marks all tiles up to 25 tiles away from the water. It could be changed to be anywhere from 1 to 30-50 tiles away (could be a common setting for near water and far from water so they don't clash). UI options for these settings can be optional or could be placed in the landscape generation window.
Describe alternatives you've considered
It would be better to store these settings on a per scenario basis, but that requires new save format. A per scenario basis would allow finer control depending on how the scenario author designs the scenario. Maybe he wants to make a desert map with grass only near water, or he wants sand only near water for 1-2 tiles to have beaches. etc.
Additional context
Scenarios save only the option for the land type, not the actual distance it applies to, so this tweaking option won't affect existing save games. Scenarios with "only generate random landscape on game starts" could result in different looking maps due to new settings but would not make them incompatible.
Once new save format is added, these options can be used as default values when creating a new scenario.
- Lenguaje dominante
- C++
- Estrellas
- 1.9k
- Forks
- 221
- Merge medio
- 1 d 37 min
- PR fusionados (30 d)
- 1
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de OpenLoco/OpenLoco
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 92/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Todos los issues de OpenLoco/OpenLoco
Issues similares
-
Code: Performance
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
CrimsonCrossBunker/Cataclysm-Cleanwater-Bomb#1167 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
meshcore-dev/MeshCore#3760 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
deepseek-ai/DeepGEMM-Ascend#29 ·
Los mantenedores suelen responder en 1 día
-
ci Windows
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
aethersdr/AetherSDR#7003 · 1 comentario ·
Los mantenedores suelen responder en 1 día