Project 1: Scissors Paper Stone (Part 1)



For our first project we will make our own version of the classic Scissors Paper Stone game. We have split this project into 2 parts to cater to the pace of Rocket's Fundamentals course. See the Course Schedule for when we have assigned each part.

Part 1 works with the technologies we have learnt so far in Fundamentals, and Part 2 adds additional technologies that we learn in subsequent course days.


  1. Create a project directory in your fundamentals code folder to host your projects if you haven't already.

  2. Make a copy of the Fundamentals Starter Code for your Scissors Paper Stone project.


Basic Scissors Paper Stone

Create a basic version of Scissors Paper Stone where the user inputs one of "scissors", "paper", or "stone", the program internally randomly chooses scissors, paper, or stone, and the program outputs whether the user won, the program won, or it's a draw.

Rules: scissors beats paper, paper beats stone, and stone beats scissors. If both parties choose the same object, it's a draw.

Unsure how to start? Try these steps:

  1. Write some pseudo code.

    • What is the input going to be?

    • What should the output be?

    • How will the computer's option be randomly generated?

    • How many different cases are there?

  2. Draw a simple flowchart to help you visualise the overall control flow of the program.

  3. Start small, test while you build and be ready to debug.

    • It's unwise to attempt to build the entire program in one go before testing.

    • Know that the final shape and form of your program will look different from when you are building it.

    • You can write new lines of code within main first, check that the code works as intended, and then "relocate" / refactor your code as a helper function.

    • Utilise console.log() sensibly to check for the right control flow and values.

    • Try to test as frequently as you can, and whenever you make a significant change. It builds confidence that things are working as they should and you will catch bugs as soon as they pop up.

  4. Refactor your code:

    1. Is all of your logic in main()? Can more lines of code be in helper functions?

    2. Are there any unwieldy or long helper functions? Should they be sub-routines which call helper functions instead?

    3. Can any of the logic be streamlined?

Input Validation

Sometimes the user types something other than "scissors", "paper", or "stone" during gameplay. Add input validation to check if what the user types is a valid choice, and if not, kindly let the user know that there are only 3 input options, and ask them to try again.

More Comfortable


Make the output of your game look nice. You can use string '<br>' to create new lines in the output. Your output might look something like this:

The computer chose scissors ✂️.
You chose paper 🗒.

You lose! Bummer.

Now you can type "scissors" "paper" or "stone" to play another round!

Reverse Game

You decide to prank your friends and create an SPS game where the rules are reversed: scissors beat stone, stone beats paper, and paper beats scissors. Create a version where the rules are reversed. The user can choose to try their luck at reversed mode by adding the word "reversed" to their choice. For example: "reversed stone".

Reference Solution

View the reference solution for SPS-Part1 (up till More Comfortable). Please only refer to the reference solution after you have attempted the project. Note that there are many ways to implement the project and the reference solution is only 1 way.

Last updated