Skip to content

Commit b627c95

Browse files
john-b-yangjohn-b-yang
committed
Add prompts for remaining games
1 parent c74d869 commit b627c95

4 files changed

Lines changed: 128 additions & 0 deletions

File tree

‎configs/battlecode.yaml‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,3 +8,35 @@ players:
88
name: p1
99
- agent: dummy
1010
name: p2
11+
prompts:
12+
game_description: |
13+
You are a software developer ({{player_id}}) competing in a coding game called BattleCode.
14+
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.
15+
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.
18+
19+
Your task: improve the bot in `src/mysubmission`, located in {{working_dir}}.
20+
{{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/corewar.yaml‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,3 +8,35 @@ players:
88
name: p1
99
- agent: dummy
1010
name: p2
11+
prompts:
12+
game_description: |
13+
You are a software developer ({{player_id}}) competing in a coding game called CoreWar.
14+
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.
15+
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.
18+
19+
Your task: improve the bot in `warriors/warrior.red`, located in {{working_dir}}.
20+
{{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/robocode.yaml‎

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,3 +19,35 @@ players:
1919
name: p1
2020
- agent: dummy
2121
name: p2
22+
prompts:
23+
game_description: |
24+
You are a software developer ({{player_id}}) competing in a coding game called RoboCode.
25+
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.
26+
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.
29+
30+
Your task: improve the bot in `robots/custom/`, located in {{working_dir}}.
31+
{{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: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,3 +6,35 @@ players:
66
name: p1
77
- agent: dummy
88
name: p2
9+
prompts:
10+
game_description: |
11+
You are a software developer ({{player_id}}) competing in a coding game called RobotRumble.
12+
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.
13+
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.
16+
17+
Your task: improve the bot in `robot.py`, located in {{working_dir}}.
18+
{{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)