Seasonal Weather
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue defines a seasonal weather system and terrain effects but names no files, tests, or entry points. First locate the turn, map-terrain, and unit-movement systems, then clarify the unresolved wetland-to-lake behavior before implementing; done should match the listed seasonal transitions and cold, wet, and dry effects.
Written by the indexing model from the issue text.
Description
Assuming northern hemisphere, temperature decreases as you go north. Temperature oscillates on a sine wave, from turn to turn, to simulate seasonal weather.
Temperatures decrease based on the distance from the coast.
A northern map:
Summer Autumn Winter Spring
Fine Wet Cold Wet
Fine Fine Wet Fine
Dry Fine Fine Fine
A map further north:
Summer Autumn Winter Spring
Fine Cold Cold Cold
Fine Wet Cold Wet
Fine Fine Wet Fine
This can be easily turned upside-down for southern hemisphere maps.
Effects on terrain: All tiles have a base type of terrain, assuming a spring/autumn temperature.
Dry
- Affects Lake, Wetland and Grassland hexes
- Lake -> Wetland, Wetland -> Grassland, Grassland -> Desert
Fine
- The default
Wet
- Affects Arid, Grassland, Wetland and Mountain hexes
- Desert -> Grassland, Grassland -> Wetland, Wetland -> Lake
- Negates the move bonus of roads
Cold
- Lakes freeze - units can now treat a frozen lake as land
- Rivers freeze - units can now cross rivers without a movement penalty
- Grassland, Hill, Forest, and Mountain become snow covered
- Unit morale drops from the cold if not in a structure or not on preferred terrain
- Some units aren't hindered by the cold (no morale loss)
Problems with this system:
- Units that were in a wetland might find themselves in a lake in the following turn
- Dominant language
- C#
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ledpup/StrategyGame
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
ledpup/StrategyGame#57 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ledpup/StrategyGame#56 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ledpup/StrategyGame#55 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ledpup/StrategyGame#54 ·
-
Diplomacy rules Open
Difficulty 5/5 Over a week Newbie friendliness 20/100
ledpup/StrategyGame#53 ·
All issues in ledpup/StrategyGame
Similar issues
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·
-
.NET Flaky Test Testing Tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
getsentry/sentry-dotnet#5617 · 1 comment ·
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Client customer-reported needs-team-attention question Service Attention WebPubSub
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Azure/azure-sdk-for-net#63292 · 3 comments · 1 reaction ·