Losing fuel by burning mothership does not respect game speed
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
Start by reading Mothership.init, where the timer speed is set to 50, and trace how game speed is stored and applied to timers. Reproduce mothership burning at different game speeds and check that fuel loss follows the selected speed; done when the loss rate adjusts as game speed changes.
Written by the indexing model from the issue text.
Description
If the mothership burns, the fuel that's lost is independent of current game speed.
The speed of the timer in Mothership.init is set exactly once - to 50 (the default game speed).
- Dominant language
- Kotlin
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 16
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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 openbase/planetsudo.engine
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
openbase/planetsudo.engine#108 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 1-2 days Newbie friendliness 35/100
openbase/planetsudo.engine#106 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 22/100
openbase/planetsudo.engine#89 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
openbase/planetsudo.engine#82 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
openbase/planetsudo.engine#81 ·
Maintainers usually reply within 1 day
All issues in openbase/planetsudo.engine
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
software-mansion/enriched-markdown#1033 ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
app
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
LawnchairLauncher/lawnicons#4180 ·
Maintainers usually reply within 1 day
-
Kotlin extra warnings in GeneratedAppGlideModuleImplPossibly taken @bacecek claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 18 days