Extensibility (NxN board, multiple players) in LLD - System Design Guide

Problem Statement

Hardcoding a fixed board size and a fixed number of players makes the game rigid. When you want to change the board size or add more players, you must rewrite large parts of the code, causing bugs and slowing development.

Solution

Design the game logic to accept any board size and any number of players as parameters. Use flexible data structures and loops that adapt to these parameters, so the game can easily scale without code changes.

Architecture

Game Engine

(Game Logic)

→Board Manager

↓

Input

Handler

This diagram shows the game engine coordinating between a flexible NxN board manager and a player manager that supports multiple players. Inputs flow into the game engine, which updates board and player states accordingly.

Trade-offs

✓ Pros

→

Allows easy changes to board size without rewriting core logic.

→

Supports any number of players, enabling new game modes.

→

Improves code maintainability by separating concerns.

→

Facilitates testing different configurations quickly.

✗ Cons

→

More complex code due to abstraction layers.

→

Slight performance overhead from dynamic data structures.

→

Requires careful design to handle edge cases for large boards or many players.

Use when the game needs to support variable board sizes (e.g., 3x3 to 10x10) and multiple players (more than 2), or when future extensions are expected.

Avoid if the game is simple, fixed-size (e.g., always 3x3), and single-player only, where added complexity is unnecessary.

Real World Examples

Google

Google's Tic-Tac-Toe demo supports variable board sizes and multiple players to demonstrate flexible game design.

Discord

Discord bots for games like Connect Four allow users to customize board size and player count dynamically.

Amazon

Amazon's Alexa games support multiple players and variable board sizes to enhance user engagement.

Code Example

The before code fixes the board size to 3x3 and supports only two players. The after code accepts any board size and a list of players, updating the current player in a round-robin fashion. This makes the game flexible and extensible.

LLD

### Before: Fixed 3x3 board and 2 players
class Game:
    def __init__(self):
        self.board = [[None]*3 for _ in range(3)]
        self.players = ['X', 'O']
        self.current_player = 0

    def make_move(self, row, col):
        if self.board[row][col] is None:
            self.board[row][col] = self.players[self.current_player]
            self.current_player = 1 - self.current_player

### After: Extensible NxN board and multiple players
class Game:
    def __init__(self, size=3, players=None):
        if players is None:
            players = ['X', 'O']
        self.size = size
        self.board = [[None]*size for _ in range(size)]
        self.players = players
        self.current_player = 0

    def make_move(self, row, col):
        if 0 <= row < self.size and 0 <= col < self.size:
            if self.board[row][col] is None:
                self.board[row][col] = self.players[self.current_player]
                self.current_player = (self.current_player + 1) % len(self.players)

Alternatives

Fixed-size board with hardcoded players

Board size and player count are constants in code, no flexibility.

Use when: Choose when the game requirements are simple and unlikely to change.

Plugin-based extensibility

Game logic loads external plugins to add new board types or player rules dynamically.

Use when: Choose when you want third-party developers to extend the game without modifying core code.

Summary

Hardcoding board size and player count limits game flexibility and increases maintenance.

Designing for extensibility allows easy changes to board size and player number without rewriting code.

Extensible design improves maintainability and supports future game feature expansions.

Practice

1. What is the main benefit of designing a game system with an NxN board and support for multiple players?

easy

A. It allows the game to be easily extended to different board sizes and more players without major code changes.

B. It limits the game to only two players and a fixed board size.

C. It makes the game run faster by using fixed-size arrays only.

D. It removes the need for input validation.

Solution

1. Step 1: Understand extensibility in game design

   Extensibility means the system can grow or change easily without rewriting code.

2. Step 2: Apply extensibility to NxN board and multiple players

   Using flexible data structures and modular code allows changing board size and player count easily.

3. Final Answer:

   It allows the game to be easily extended to different board sizes and more players without major code changes. -> Option A

4. Quick Check:

   Extensibility = Easy growth [OK]

Hint: Extensibility means easy to add features later [OK]

Common Mistakes:

• Thinking fixed size is more extensible
• Ignoring input validation importance
• Assuming extensibility means faster code

2. Which of the following code snippets correctly initializes a flexible NxN board in Python for any given size n?

easy

A. board = [[0]*n]*n

B. board = [[0 for _ in range(n)] for _ in range(n)]

C. board = [0]*n

D. board = [0 for _ in range(n)]

Solution

1. Step 1: Understand list initialization for 2D board

   Using list comprehension creates independent inner lists for each row.

2. Step 2: Compare options for correct 2D board creation

   board = [[0 for _ in range(n)] for _ in range(n)] creates a list of lists with separate inner lists, avoiding shared references.

3. Final Answer:

   board = [[0 for _ in range(n)] for _ in range(n)] -> Option B

4. Quick Check:

   Independent rows = board = [[0 for _ in range(n)] for _ in range(n)] [OK]

Hint: Use nested list comprehensions for independent 2D lists [OK]

Common Mistakes:

• Using [[0]*n]*n causes shared inner lists
• Initializing only 1D list for 2D board
• Confusing list multiplication with comprehension

3. Given a game system supporting multiple players, what will be the output of this Python snippet?

players = ['Alice', 'Bob', 'Carol']
turns = 5
for i in range(turns):
    current = players[i % len(players)]
    print(current)

medium

A. Bob Carol Alice Bob Carol

B. Alice Bob Carol Carol Carol

C. Alice Alice Alice Alice Alice

D. Alice Bob Carol Alice Bob

Solution

1. Step 1: Understand modulo for cycling players

   The modulo operator cycles index through player list length (3).

2. Step 2: Trace each iteration's player

   i=0 -> Alice, i=1 -> Bob, i=2 -> Carol, i=3 -> Alice, i=4 -> Bob.

3. Final Answer:

   Alice Bob Carol Alice Bob -> Option D

4. Quick Check:

   Modulo cycles players = Alice Bob Carol Alice Bob [OK]

Hint: Use modulo to cycle through players repeatedly [OK]

Common Mistakes:

• Not using modulo causes index errors
• Assuming players list is longer than turns
• Confusing player order in output

4. Identify the bug in this code snippet for initializing a variable-sized board and multiple players:

def setup_game(n, players):
    board = [[None]*n]*n
    for p in players:
        print(f"Player: {p}")
    return board

setup_game(3, ['A', 'B'])

medium

A. The board rows are references to the same list, causing shared updates.

B. The players list is not printed correctly.

C. The function does not return anything.

D. The board size is fixed to 3 regardless of input.

Solution

1. Step 1: Analyze board initialization

   Using [[None]*n]*n creates rows that reference the same list object.

2. Step 2: Understand impact of shared references

   Changing one cell affects all rows because they share the same inner list.

3. Final Answer:

   The board rows are references to the same list, causing shared updates. -> Option A

4. Quick Check:

   Shared inner lists cause bugs = The board rows are references to the same list, causing shared updates. [OK]

Hint: Avoid list multiplication for nested lists [OK]

Common Mistakes:

• Ignoring shared reference problem
• Thinking players print is incorrect
• Assuming function returns nothing

5. You are designing a turn-based game with an NxN board and support for multiple players. Which design approach best supports easy extensibility for future features like variable board sizes, more players, and custom rules?

hard

A. Write all game logic in one large function for simplicity.

B. Use fixed-size arrays and hardcoded player count with separate functions for each board size.

C. Use flexible data structures (lists/dictionaries), modular functions, and validate inputs dynamically.

D. Use global variables for board and players to avoid passing parameters.

Solution

1. Step 1: Identify extensibility requirements

   Extensibility needs flexible data structures and modular code to adapt easily.

2. Step 2: Evaluate design options

   Use flexible data structures (lists/dictionaries), modular functions, and validate inputs dynamically. uses lists/dictionaries and modular functions with input validation, supporting future changes well.

3. Final Answer:

   Use flexible data structures (lists/dictionaries), modular functions, and validate inputs dynamically. -> Option C

4. Quick Check:

   Modular + flexible data = extensible design [OK]

Hint: Modular code + flexible data = easy extensibility [OK]

Common Mistakes:

• Using fixed sizes limits future changes
• Writing monolithic functions reduces flexibility
• Using globals causes maintenance issues