Skip to content

Commit 496c709

Browse files
john-b-yangjohn-b-yang
committed
Respond to feedback
1 parent 7e030e3 commit 496c709

6 files changed

Lines changed: 37 additions & 120 deletions

File tree

‎configs/battlecode.yaml‎

Lines changed: 3 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -13,30 +13,9 @@ prompts:
1313
You are a software developer ({{player_id}}) competing in a coding game called BattleCode.
1414
Battlecode 25 throws you into a real-time strategy showdown where your Python bot pilots a team of specialized robots—Soldiers, Moppers, Splashers—alongside towers that spawn units or generate resources.
1515
Your mission: paint over 70% of the map (or eliminate the enemy) by coordinating cleanups, area cover, and tower-building through tight bytecode budgets and clever unit synergy.
16-
- Round: {{round}}/{{rounds}}
17-
- Goal: Improve your bot, win the next round.
16+
17+
The game is played in {{rounds}} rounds. For every round, you (and your competitor) edit program code that controls your bot. This is round {{round}}.
18+
After you and your competitor finish editing your codebases, the game is run automatically.
1819
1920
Your task: improve the bot in `src/mysubmission`, located in {{working_dir}}.
2021
{{working_dir}} is your codebase, which contains both your bot and supporting assets.
21-
22-
The details of the game are fully available within this codebase.
23-
- `docs/`: Game documentation
24-
- `logs/`: Past rounds and outcomes
25-
- `trajs/`: History of your edits
26-
- and a lot more. It's up to you to explore and utilize these resources.
27-
28-
⚠️ You won't remember past rounds.
29-
So if you want to carry knowledge forward — leave tools, notes, or strategies in the codebase.
30-
Good documentation means you (and others) can pick up right where you left off.
31-
32-
If you'd hate to repeat a step next round, encode it now — as a script, a note, or a tool.
33-
34-
Improve the bot however you like — experiment, document, iterate. Some ideas:
35-
- Build analysis tools
36-
- Create bot variants to test
37-
- Track strategies across rounds
38-
How you choose to evolve and document is up to you. Good luck!
39-
40-
<important>
41-
When you are finished making changes, issue the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
42-
</important>

‎configs/battlesnake.yaml‎

Lines changed: 3 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -17,30 +17,9 @@ prompts:
1717
You are a software developer ({{player_id}}) competing in a coding game called BattleSnake.
1818
Your bot (`main.py`) controls a snake on a grid-based board.
1919
Snakes collect food, avoid collisions, and try to outlast their opponents.
20-
- Round: {{round}}/{{rounds}}
21-
- Goal: Improve your bot, win the next round.
20+
21+
The game is played in {{rounds}} rounds. For every round, you (and your competitor) edit program code that controls your bot. This is round {{round}}.
22+
After you and your competitor finish editing your codebases, the game is run automatically.
2223
2324
Your task: improve the bot in `main.py`, located in {{working_dir}}.
2425
{{working_dir}} is your codebase, which contains both your bot and supporting assets.
25-
26-
The details of the game are fully available within this codebase.
27-
- `docs/`: Game documentation
28-
- `logs/`: Past rounds and outcomes
29-
- `trajs/`: History of your edits
30-
- and a lot more. It's up to you to explore and utilize these resources.
31-
32-
⚠️ You won't remember past rounds.
33-
So if you want to carry knowledge forward — leave tools, notes, or strategies in the codebase.
34-
Good documentation means you (and others) can pick up right where you left off.
35-
36-
If you'd hate to repeat a step next round, encode it now — as a script, a note, or a tool.
37-
38-
Improve the bot however you like — experiment, document, iterate. Some ideas:
39-
- Build analysis tools
40-
- Create bot variants to test
41-
- Track strategies across rounds
42-
How you choose to evolve and document is up to you. Good luck!
43-
44-
<important>
45-
When you are finished making changes, issue the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
46-
</important>

‎configs/corewar.yaml‎

Lines changed: 3 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -13,30 +13,9 @@ prompts:
1313
You are a software developer ({{player_id}}) competing in a coding game called CoreWar.
1414
CoreWar is a programming battle where you write "warriors" in an assembly-like language called Redcode to compete within a virtual machine (MARS), aiming to eliminate your rivals by making their code self-terminate.
1515
Victory comes from crafting clever tactics—replicators, scanners, bombers—that exploit memory layout and instruction timing to control the core.
16-
- Round: {{round}}/{{rounds}}
17-
- Goal: Improve your bot, win the next round.
16+
17+
The game is played in {{rounds}} rounds. For every round, you (and your competitor) edit program code that controls your bot. This is round {{round}}.
18+
After you and your competitor finish editing your codebases, the game is run automatically.
1819
1920
Your task: improve the bot in `warriors/warrior.red`, located in {{working_dir}}.
2021
{{working_dir}} is your codebase, which contains both your bot and supporting assets.
21-
22-
The details of the game are fully available within this codebase.
23-
- `docs/`: Game documentation
24-
- `logs/`: Past rounds and outcomes
25-
- `trajs/`: History of your edits
26-
- and a lot more. It's up to you to explore and utilize these resources.
27-
28-
⚠️ You won't remember past rounds.
29-
So if you want to carry knowledge forward — leave tools, notes, or strategies in the codebase.
30-
Good documentation means you (and others) can pick up right where you left off.
31-
32-
If you'd hate to repeat a step next round, encode it now — as a script, a note, or a tool.
33-
34-
Improve the bot however you like — experiment, document, iterate. Some ideas:
35-
- Build analysis tools
36-
- Create bot variants to test
37-
- Track strategies across rounds
38-
How you choose to evolve and document is up to you. Good luck!
39-
40-
<important>
41-
When you are finished making changes, issue the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
42-
</important>

‎configs/mini/default.yaml‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,28 @@ agent:
1717
Failure to follow these rules will cause your response to be rejected.
1818
instance_template: |
1919
{{game_description}}
20+
21+
The details of the game are fully available within this codebase.
22+
- `docs/`: Game documentation
23+
- `logs/`: Past rounds and outcomes
24+
- `trajs/`: History of your edits
25+
- and a lot more. It's up to you to explore and utilize these resources.
26+
27+
⚠️ You won't remember past rounds.
28+
So if you want to carry knowledge forward — leave tools, notes, or strategies in the codebase.
29+
Good documentation means you (and others) can pick up right where you left off.
30+
31+
If you'd hate to repeat a step next round, encode it now — as a script, a note, or a tool.
32+
33+
Improve the bot however you like — experiment, document, iterate. Some ideas:
34+
- Build analysis tools
35+
- Create bot variants to test
36+
- Track strategies across rounds
37+
How you choose to evolve and document is up to you. Good luck!
38+
39+
<important>
40+
When you are finished making changes, issue the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
41+
</important>
2042
========================================================
2143
You can execute bash commands and edit files to implement the necessary changes.
2244

‎configs/robocode.yaml‎

Lines changed: 3 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -24,30 +24,9 @@ prompts:
2424
You are a software developer ({{player_id}}) competing in a coding game called RoboCode.
2525
Robocode (Tank Royale) is a programming game where your code is the tank: each turn your bot sends intents—speed plus body/gun/radar turn rates and firepower—based on the game state it perceives via radar.
2626
Your program decides how to move, aim, and fire in a deterministic, turn-based arena to outlast other bots.
27-
- Round: {{round}}/{{rounds}}
28-
- Goal: Improve your bot, win the next round.
27+
28+
The game is played in {{rounds}} rounds. For every round, you (and your competitor) edit program code that controls your bot. This is round {{round}}.
29+
After you and your competitor finish editing your codebases, the game is run automatically.
2930
3031
Your task: improve the bot in `robots/custom/`, located in {{working_dir}}.
3132
{{working_dir}} is your codebase, which contains both your bot and supporting assets.
32-
33-
The details of the game are fully available within this codebase.
34-
- `docs/`: Game documentation
35-
- `logs/`: Past rounds and outcomes
36-
- `trajs/`: History of your edits
37-
- and a lot more. It's up to you to explore and utilize these resources.
38-
39-
⚠️ You won't remember past rounds.
40-
So if you want to carry knowledge forward — leave tools, notes, or strategies in the codebase.
41-
Good documentation means you (and others) can pick up right where you left off.
42-
43-
If you'd hate to repeat a step next round, encode it now — as a script, a note, or a tool.
44-
45-
Improve the bot however you like — experiment, document, iterate. Some ideas:
46-
- Build analysis tools
47-
- Create bot variants to test
48-
- Track strategies across rounds
49-
How you choose to evolve and document is up to you. Good luck!
50-
51-
<important>
52-
When you are finished making changes, issue the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
53-
</important>

‎configs/robotrumble.yaml‎

Lines changed: 3 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -11,30 +11,9 @@ prompts:
1111
You are a software developer ({{player_id}}) competing in a coding game called RobotRumble.
1212
RobotRumble is a turn-based coding battle where you program a team of robots in Python to move, attack, and outmaneuver your opponent on a grid.
1313
Every decision is driven by your code, and victory comes from crafting logic that positions robots smartly, times attacks well, and adapts over the 100-turn match.
14-
- Round: {{round}}/{{rounds}}
15-
- Goal: Improve your bot, win the next round.
14+
15+
The game is played in {{rounds}} rounds. For every round, you (and your competitor) edit program code that controls your bot. This is round {{round}}.
16+
After you and your competitor finish editing your codebases, the game is run automatically.
1617
1718
Your task: improve the bot in `robot.py`, located in {{working_dir}}.
1819
{{working_dir}} is your codebase, which contains both your bot and supporting assets.
19-
20-
The details of the game are fully available within this codebase.
21-
- `docs/`: Game documentation
22-
- `logs/`: Past rounds and outcomes
23-
- `trajs/`: History of your edits
24-
- and a lot more. It's up to you to explore and utilize these resources.
25-
26-
⚠️ You won't remember past rounds.
27-
So if you want to carry knowledge forward — leave tools, notes, or strategies in the codebase.
28-
Good documentation means you (and others) can pick up right where you left off.
29-
30-
If you'd hate to repeat a step next round, encode it now — as a script, a note, or a tool.
31-
32-
Improve the bot however you like — experiment, document, iterate. Some ideas:
33-
- Build analysis tools
34-
- Create bot variants to test
35-
- Track strategies across rounds
36-
How you choose to evolve and document is up to you. Good luck!
37-
38-
<important>
39-
When you are finished making changes, issue the following command: `echo COMPLETE_TASK_AND_SUBMIT_FINAL_OUTPUT`.
40-
</important>

0 commit comments

Comments
 (0)