Skip to content

Commit d80ef8a

Browse files
[wiki] my first core bot spelling fixes
1 parent b69ff20 commit d80ef8a

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

wiki/my_first_core_bot.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ In this guide (30-minute-ish, please take your time), we'll go through your firs
77
If you haven't created a team & cloned your repo yet, look at & follow the [Getting Started Guide](README) first.
88

99
Before we get started writing code, please run `make` once to run the game, and then have a look at the game that was played in the visualizer. For more details on how to do those things, look at your bots README.
10-
- Watch the game run through entirely once & enjoy seeing your team be killed by the noob default opponent. 😂
10+
- Watch the game from start to finish & enjoy seeing your team be killed by the noob default opponent. 😂
1111
- Have a look at all the different objects in the game and how they differ. Hover with your mouse and look at the tooltip to see what kind of data is associated with each object.
1212
- Can you see the differently colored bars behind the objects? Do you understand what they mean?
1313
- Can you figure out why some units move faster than others? When do units move?
@@ -93,7 +93,7 @@ Let's move the unit to the opponent core and perform an attack action!
9393

9494
To do this, we'll first need a reference to our warrior. The game needs to know which specific unit should perform a certain action, not just that a unit that is a warrior should do a certain thing.
9595

96-
All objects are represented in the library as the `t_obj` struct. A `t_obj` could therefore represent your own or your opponents units, but also your core, a wall, a deposit or even a bomb. By using cmd+click in VSCode, you should be able to navigate to the `bot.h` file and from there to the `core_lib.h` file. Here you can see every struct and function provided to you by the core library, where you should also be able to find the `t_obj` struct. You don't every have to allocate a `t_obj` yourself, as the library already created every object currently in the game for you, you just need to look for it.
96+
All objects are represented in the library as the `t_obj` struct. A `t_obj` could therefore represent your own or your opponents units, but also your core, a wall, a deposit or even a bomb. By using cmd+click in VSCode, you should be able to navigate to the `bot.h` file and from there to the `core_lib.h` file. Here you can see every struct and function provided to you by the core library, where you should also be able to find the `t_obj` struct. You don't ever have to allocate a `t_obj` yourself, as the library already created every object currently in the game for you, you just need to look for it.
9797

9898
To get the `t_obj` struct of the warrior we created, let's have the Core library make us an array of all of our units that we can then loop over. Let's add this new utility function:
9999

0 commit comments

Comments
 (0)