Newly added stations do not generate gold for trains already on their segment when placing them
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- game-dev
Research direction
No file or specific test is named. Start by locating the train gold-generation and station-placement logic, then add a regression test for a train already on a segment when a city is placed. Done means that train generates gold when it reaches the new station, while existing behavior for other trains remains intact.
Written by the indexing model from the issue text.
Description
Description
When a station is added on a segment, the trains already on that segment will not generate gold.
The trains not on that segment when the city is placed will still generate gold when passing through this station. This is limited to trains already present on the segment when placing the city
To reproduce
- Place one city and one factory with enough place between both for a new city
- Wait for a train to spawn
- Add a city in front of the train - it will not generate gold when the train goes through it
Expected behavior
The new station should generate gold.
Desktop
- OS: MacOS
- Browser: Chrome
- Version: 34
Additional information
Not a huge deal, but this creates some confusion.
Especially visible in early game, when gold matters most.
Change should be relatively straight-forward and touch only 1 file (+tests).
Assignment
- I'd like to be assigned to this issue and work on it myself
- Dominant language
- TypeScript
- Stars
- 2.7k
- Forks
- 1.4k
- Avg merge
- 16h 28m
- Merged PRs (30d)
- 332
Contributor guide
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 openfrontio/OpenFrontIO
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openfrontio/OpenFrontIO#5562 · 1 comment ·
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openfrontio/OpenFrontIO#5558 · 1 comment ·
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openfrontio/OpenFrontIO#5556 · 1 comment ·
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openfrontio/OpenFrontIO#5500 · 1 comment ·
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openfrontio/OpenFrontIO#5476 · 1 comment ·
All issues in openfrontio/OpenFrontIO
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·