Move world generation hardcoded constants to config.yaml #56
Labels
No labels
Blocked
Duplicate
MoSCoW/Could Have
MoSCoW/Must Have
MoSCoW/Should Have
Points/1
Points/13
Points/2
Points/21
Points/3
Points/5
Points/8
Priority/Backlog
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
State/Completed
State/In progress
State/In review
State/Paused
State/Unverified
State/Verified
State/Wont Do
Type/Bug
Type/Epic
Type/Feature
Type/Legendary
Type/Task
Type/Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
#26 Epic: Configurable world generation parameters
aethyr/Aethyr
Reference: aethyr/Aethyr#56
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Metadata
refactor(worldgen): make world generation parameters configurable via config.yamlfeature/m3-v11-worldgen-configBackground
RESOLUTION_METRES,MAX_TILES, lat/lon ranges, and thread counts are hard-coded constants. There are no config.yaml entries for world generation.Expected Behavior
ServerConfigkeys override constants:world_resolution_metres,world_max_tiles,world_lat_range,world_lon_range,world_max_download_threads,world_max_process_threads.Acceptance Criteria
ServerConfigwith fallback to constantsconfig.yamlincludes new keys with defaults matching current constantsSubtasks
conf/config.yamlWorldCoverGeneratorconstructor to read fromServerConfigbundle exec rake unit, fix any errorsDefinition of Done
This issue is complete when all subtasks are done, commit created on the specified branch, PR submitted and merged.