Change mines to damage and burn agents instead of instantly killing them
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 24/100
Research direction
The issue names no files or tests. Start by finding where the engine handles an agent picking up a mine and where that pickup currently kills the agent. The change is to apply partial damage, then a lingering burn that another team agent can extinguish. Balance values are not settled, and the issue depends on #10, so confirm scope with maintainers before coding. Done means a damage-and-burn path with tests for the damage, burn and extinguish cases.
Written by the indexing model from the issue text.
Description
Instead of instantly killing the agent picking up a mine, they should instantly suffer 50% damage (value is up to balancing) and keep burning after the explosion. While burning, an agent slowly looses energy until the fire is 'put out' by another team agent.
The lingering fire damage could depend on the number of agents a team has, to make up for the number of agent that are available for putting out the fire.
In addition to Issue #10 nearby agents could suffer max 25% damage without burning. Again, final values would depend on balancing.
- 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
openbase/planetsudo.engine#107 ·
Maintainers usually reply within 1 day
-
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
All issues in openbase/planetsudo.engine
Similar issues
-
area/kotlin
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
dafonton77-tech/Cadreenf#11 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Hy4ri/hermes-mobile#1647 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
supabase-community/supabase-kt#1429 ·
Maintainers usually reply within 5 days