Board Games
How to play Mastermind
Deduce a hidden color code from exact and partial feedback.
QUICK ANSWER
How do you play Mastermind?
The codebreaker places one full guess; the codemaker returns exact-position and correct-color feedback without identifying individual pegs. Resolve the full result of that action before the next player begins. Continue in order while keeping pieces, scores, resources, or progress visible. Solve within the permitted rows, or the codemaker wins if every guess is used.
Jump to the step-by-step rules ↓EDITOR'S TABLE NOTES
Is Mastermind a good fit for your group?
This game works especially well for players who enjoy visible choices, turn-by-turn planning, and learning around a shared table; the listed 2-player range and 10–20 min playing time should also fit the group. Before setting up, decide whether that matches the experience your group wants today.
Rules version covered here
This guide explains the standard beginner version. Component names, board layouts, and special powers can change between editions, so the instructions packaged with your copy settle edition-specific questions. For Mastermind, pay particular attention to the stated setup and ending condition below.
QUICK VIDEO GUIDE
Learn Mastermind in under a minute
About this video
This original mini lesson covers what you need, setup, normal play, the winning condition, and one beginner tip. Continue below for the complete written guide.
INTERACTIVE LEARN-TO-PLAY
Practice Mastermind before the first round
Walk through the setup, try a sample turn, and get a quick answer when play stalls.
The codemaker secretly sets the agreed number of colored pegs behind the shield.
Confirm the starting player, turn direction, and the exact ending condition for Mastermind.
Playable example turn
Step 1 of 4
The codebreaker places one full guess; the codemaker returns exact-position and correct-color feedback without identifying individual pegs.
What should we do now?
Start with this action: The codebreaker places one full guess; the codemaker returns exact-position and correct-color feedback without identifying individual pegs.
Scoring and winning
Solve within the permitted rows, or the codemaker wins if every guess is used.
Common dispute to prevent
Assuming a feedback peg corresponds to the peg directly beside it; feedback is unordered. Agree on any edition-specific variation before the first turn.
The objective
Your goal is to deduce a hidden color code from exact and partial feedback. Before play begins, make sure every player can explain how the game ends and what determines the winner. That one check prevents many mid-game disagreements.
What you need
A Mastermind set. Lay out every required item before teaching the rules. If pieces, cards, controllers, or play space are missing, resolve that before the practice turn.
How to set up
- The codemaker secretly sets the agreed number of colored pegs behind the shield.
- Confirm the starting player, turn direction, and the exact ending condition for Mastermind.
Setup check: Ask one player who did not arrange the game to compare the table, field, or screen with these steps. A fresh look often catches an incorrect starting position.
How to play: step by step
- The codebreaker places one full guess; the codemaker returns exact-position and correct-color feedback without identifying individual pegs.
- Resolve the full result of that action before the next player begins.
- Continue in order while keeping pieces, scores, resources, or progress visible.
- Solve within the permitted rows, or the codemaker wins if every guess is used.
Example first round
A useful first-round walkthrough for Mastermind begins this way: The codebreaker places one full guess; the codemaker returns exact-position and correct-color feedback without identifying individual pegs. Next, resolve the full result of that action before the next player begins. Continue in normal turn order until the ending condition applies: solve within the permitted rows, or the codemaker wins if every guess is used.
How scoring and winning work
- The result is determined by the guide's stated objective: Deduce a hidden color code from exact and partial feedback.
- The final step explains when play stops: Solve within the permitted rows, or the codemaker wins if every guess is used.
- For the most common rules question, use this clarification consistently: That depends on the chosen rules; decide before the code is created.
Useful variations
- For a first teaching game, play one open practice round and explain the reason for each legal move.
- For a shorter session, announce a stopping time before starting; 10–20 min is the normal planning range for Mastermind.
- When playing with beginners, demonstrate this strategy before scoring begins: Change only a few variables between guesses so the new feedback can be compared logically.
Beginner strategies
- Change only a few variables between guesses so the new feedback can be compared logically.
- After each round, identify which decision created the strongest position and test that lesson in the next game.
Choose one of these ideas for the first game instead of trying to remember every strategy at once. Afterward, identify one decision that changed the result and one move you would test next time.
Common mistakes to avoid
- Assuming a feedback peg corresponds to the peg directly beside it; feedback is unordered.
- Mixing rules from another edition or a familiar house version without telling the other players.
If an illegal move is discovered, pause and agree on the least disruptive correction. For casual play, consistency and a shared understanding matter more than reconstructing many turns.
Frequently asked questions
Are repeated colors allowed?
That depends on the chosen rules; decide before the code is created.
What is the best way to teach Mastermind?
Explain the objective, demonstrate one normal turn, and let everyone try a no-pressure practice turn before scoring.
Related board games guides
Official instructions for your edition or the game publisher’s current documentation take priority over this summary. If you spot a factual error or an important edition difference, please tell us.
Report a correction →