Adding Bombs to the Grid

To begin implementing bombs in our Minesweeper game, we'll first update our Globals.h file with some new variables. These additions will help us manage bomb-related events and configure the game's difficulty:

1. UserEvents::BOMB_PLACED: This new event type will be dispatched whenever a bomb is placed within a cell. This will allow other cells to keep track of how many bombs are in adjacent cells, which we'll use later to display the correct number.
2. Config::BOMB_COUNT: This variable will control how many bombs are placed in the grid. By adjusting this number, we can easily change the difficulty of the game - more bombs generally mean a more challenging experience for the player.
3. Config::BOMB_IMAGE: This string specifies the file name of the icon we want to render in cells that contain a bomb. By defining this in our global configuration, we can easily change the bomb image across our entire game if needed.

1// Globals.h
2
3// ...
4
5namespace UserEvents{
6  // ...
7  inline Uint32 BOMB_PLACED =
8    SDL_RegisterEvents(1);
9}
10
11namespace Config{
12  inline constexpr int BOMB_COUNT{6};
13  // ...
14
15  // Asset Paths
16  inline const std::string BOMB_IMAGE{
17    "Bomb.png"};
18  // ...
19}
20
21// ...

To implement bomb placement in our grid, we'll update our MinesweeperGrid class with a new PlaceBombs() function. This function will be responsible for randomly selecting cells and placing bombs in them.

Here's how the PlaceBombs() function will work:

1. We'll create a loop that continues until we've placed the required number of bombs (specified by Config::BOMB_COUNT).
2. In each iteration, we'll select a random index from our Children vector, which contains all the cells in our grid.
3. We'll call a new PlaceBomb() function (which we'll add to our MinesweeperCell class later) on the randomly selected cell.
4. If PlaceBomb() returns true, indicating a successful bomb placement, we'll decrement our counter of bombs to place.
5. If PlaceBomb() returns false, indicating the selected cell already contains a bomb, we'll continue the loop to try placing the bomb in a different random cell.

This approach ensures that we place the correct number of bombs, and that no cell contains more than one bomb.

1// Minesweeper/Grid.h
2#pragma once
3#include "Globals.h"
4#include "Minesweeper/Cell.h"
5#include "Engine/Random.h" 
6
7class MinesweeperGrid {
8// ...
9
10private:
11  void PlaceBombs(){
12    int BombsToPlace{Config::BOMB_COUNT};
13    while (BombsToPlace > 0) {
14      const size_t RandomIndex{
15        Engine::Random::Int(
16          0, Children.size() - 1
17        )};
18      if (Children[RandomIndex].PlaceBomb()) {
19        --BombsToPlace;
20      }
21    }
22  }
23
24  std::vector<MinesweeperCell> Children;
25};

We'll call PlaceBombs() at the end of the MinesweeperGrid constructor.

1// Minesweeper/Grid.h
2
3// ...
4
5class MinesweeperGrid {
6public:
7  MinesweeperGrid(int x, int y){
8    // ...
9    PlaceBombs();
10  }
11  
12  // ...
13};

Now that we've implemented bomb placement in our grid, we need to update our MinesweeperCell class to handle bombs. We'll make the following changes:

1. Add a new PlaceBomb() function that returns a bool. This function will be called by MinesweeperGrid when attempting to place a bomb in the cell.
2. Add a hasBomb member variable to keep track of whether the cell contains a bomb.
3. Create a GetHasBomb() getter function to allow other parts of our program to check if a cell contains a bomb without directly accessing the hasBomb variable.

Let's update our header file with these three declarations:

1// Minesweeper/Cell.h
2
3// ...
4
5class MinesweeperCell : public Engine::Button {
6public:
7  // ...
8  bool PlaceBomb();
9
10  [[nodiscard]]
11  bool GetHasBomb() const{ return hasBomb; }
12  // ...
13
14private:
15  bool hasBomb{false};
16  // ...
17};

Over in our MinesweeperCell.cpp file, we'll implement the PlaceBomb() function. If the cell already has a bomb, we'll immediately return false, prompting the PlaceBombs() loop back in MinesweeperGrid to choose another cell.

Otherwise, we'll update our hasBomb member variable, report that a bomb has been placed, and return true to inform MinesweeperGrid that a bomb was successfully placed:

1// Minesweeper/Cell.cpp
2
3// ...
4
5bool MinesweeperCell::PlaceBomb(){
6  if (hasBomb) return false;
7  hasBomb = true;
8  ReportEvent(UserEvents::BOMB_PLACED);
9  return true;
10}
11
12// ...

We'll also update our HandleEvent() function to react to bomb placement events.

For now, we'll just log that a bomb was placed, but in future parts, we'll use this to update the count of adjacent bombs for neighboring cells.

1// Minesweeper/Cell.cpp
2
3// ...
4
5void MinesweeperCell::HandleEvent(
6  const SDL_Event& E){
7  if (E.type == UserEvents::CELL_CLEARED) {
8    // TODO
9    std::cout << "A Cell Was Cleared\n";
10  } else if (E.type ==
11    UserEvents::BOMB_PLACED) {
12    // TODO
13    std::cout << "A Bomb was Placed\n";
14  }
15  Button::HandleEvent(E);
16}
17
18// ...

We can now run our program and verify everything is connected correctly by looking at our terminal output. Every time a bomb is placed in a cell, every cell will react to the event, so we should see a long list of logs:

1A Bomb was Placed
2A Bomb was Placed
3A Bomb was Placed
4...

Naturally, we'll replace this logging with more meaningful reactions later.

Rendering Bomb Images

Finally, lets update our program to render the bomb images in the appropriate cells. We'll add a BombImage member variable:

1// Minesweeper/Cell.h
2#pragma once
3#include "Engine/Button.h"
4#include "Engine/Image.h"
5
6class MinesweeperCell : public Engine::Button {
7 // ...
8
9private:
10  Engine::Image BombImage;
11};

Over in our constructor, we'll initialize it. Our Engine::Image class needs to know the position (x and y) and size (w and h) we want the image to be rendered on the surface. It also needs to know the location of the image file. We'll pass all of this information to its constructor:

1// Minesweeper/Cell.cpp
2
3// ...
4
5MinesweeperCell::MinesweeperCell(
6  int x, int y, int w, int h, int Row, int Col)
7  : Button{x, y, w, h}, Row{Row}, Col{Col},
8    BombImage{
9      x, y, w, h,
10      Config::BOMB_IMAGE}{};
11
12// ...

Finally, we update the Render() method of our MinesweeperCell. If the player has cleared the cell and the cell contains a bomb, we render the image:

1// Minesweeper/Cell.cpp
2
3// ...
4
5void MinesweeperCell::Render(
6  SDL_Surface* Surface){
7  Button::Render(Surface);
8  if (isCleared && hasBomb) {
9    BombImage.Render(Surface);
10  }
11}

If we run our game and clear cells, we should now eventually find a bomb:

Development Helpers

To make future development easier, it would be helpful to know where the bombs are without having to find them by clearing cells. In our Globals.h file, we created a preprocessor definition called SHOW_DEBUG_HELPERS.

We can use this preprocessor definition in our MinesweeperCell::Render() method to display bombs in all cells during development, regardless of whether they've been cleared:

1// Minesweeper/Cell.cpp
2
3// ...
4
5void MinesweeperCell::Render(
6  SDL_Surface* Surface){
7  Button::Render(Surface);
8  if (isCleared && hasBomb) {
9    BombImage.Render(Surface);
10  }
11#ifdef SHOW_DEBUG_HELPERS
12  else if (hasBomb) {
13    BombImage.Render(Surface);
14  }
15#endif
16}

When our preprocessor definition is enabled, we will be able to see bombs without clearing cells, which will make future development more convenient:

To enable these debug helpers, ensure the SHOW_DEBUG_HELPERS macro is defined in your Globals.h file. To disable them, simply comment out or remove the #define SHOW_DEBUG_HELPERS line:

1// Globals.h
2
3// #define SHOW_DEBUG_HELPERS 
4
5// ...

Complete Code

Complete versions of the files we changed in this part are available below

Globals.h (Edited)

Minesweeper/Grid.h (Edited)

Minesweeper/Cell.h (Edited)

Minesweeper/Cell.cpp (Edited)

Files not listed above have not been changed since the previous section.

Summary

In this part of our Minesweeper tutorial, we've made significant progress in implementing one of the core elements of the game: bombs. We are now:

1. Implementing a system for randomly placing bombs in the grid.
2. Updating cells to track whether they contain a bomb.
3. Rendering bomb images when cells are cleared.
4. Adding a debug helper to visualize bomb placement during development.

In the next part of our tutorial, we'll build upon this foundation to implement the ability for cleared cells to display the number of bombs in neighboring cells. This feature is essential for providing players with the information they need to deduce the location of bombs and clear the grid safely.

We'll modify our cell class to keep track of neighboring bombs, update this count when bombs are placed, and display the count when a cell is cleared. This will involve working with events, updating our rendering logic, and introducing new graphical elements to represent the numbers.