FSEM131
Pre Lab 1
Light-bot
Before next class, Sept 7, 2018, do the following pre-lab exercise.
  1. Read all the instructions below.
  2. Search on the web how to take a screenshot of your computer screen--or better an area of your screen--so as to save the capture as an image file (extension .png preferably)
  3. In a web browser, visit http://coweb.cc.gatech.edu/ice-gt/1835
    to access the game Lightbot 2.0.
    If you are experiencing issues getting the game to run, make sure you have Adobe Flash Player installed or try again using the Firefox web browser.
  4. Tinker with the game, press any button you find. Turn off the annoying music.
  5. Try to complete the six Basics levels.
  6. Take a screenshot of the last level, you solved, call it FirstNameLastNameInitial_prelab1.png. Send the picture to me as an email attachment efourquet@cs.colgate.edu before our Friday class.

Description

Computers have to be told everything. Today, you are in control of a special robot: Light-bot who is in charge of turning on the lights around the factory. Light-bot has lost its program, and you must tell it what to do. Your task is to tell the robot how to navigate to the blue tiles and to turn on the lights there.

The simple commands available are:

Move forward
Turn right
Turn left
Jump (up or down)
Turn on the light
plus Teleport
and Function call

These commands can be issued by clicking them into the 'Main Method' section of the interface, where they form a list of instructions that the Light-bot will follow slavishly. The commands can also be selected by clicking. Explore the game interface.

When you have set the instructions, the RUN button start the Light-bot. If all of the blue squares have been lit by the end of your program, you will proceed to the next level.

This is a fun little puzzle game, which I want you to play before the first lab session. Think about the strategies you use when your first attempt at a level does not succeed. How do you approach the puzzle considering the functionality of the game interface so as to effectively refine your instructions and reach a solution? Does it connect to what we did Wednesday in class?

When you edit the sequence of steps you are actually doing the mysterious activity that programmers call debugging.

Hint