Objectives #1-5: These objectives introduce students to the CodeSpace environment. The activity guide has specific instructions to help with meeting the goals of individual objectives.

Objectives #6-7: These objectives introduce students to CodeBot's motors and LEDs. Students will click on the parts in the 3D simulator.

Objective #8: This is the first time a student must create a new file. It must have the name spelled exactly the same as what is in the goal. The goal will be met by turning on 3 LEDs, the 0, 4 and 7. They can get a higher score by turning on more than 3. The answers to the activity guide questions are in CodeTrek.

Objective #9: Students continue to use the same file for this objective. Students will not delete any code, just add to it. CodeTrek shows the code only for the required LEDs to turn on. If students did more, they should keep the code. It doesn't have to match perfectly. Also, the speeds of the motors in the added code don't have to be exactly the same as CodeTrek. The validator is only checking to see if the 'bot is rotated. However, students will move the 'bot A LOT during this mission pack, so they should practice all the different ways to move it. You can have students submit their ActionBot code for this objective if you want to check how they are doing.

Objective #10: Students create a new file for this objective. It does not have to be the same name as the one in the instructions. The challenge is to move CodeBot so it tags at least four spiders. The spiders can be tagged in any order. Students get a higher score for tagging all six spiders, but it is not required. Students can also get a higher score for speed. Important note: CodeBot doesn't move exactly the same way every time the code is run. If someone's code looks good but the program run is a little off, just reset the scene and run it again.

Helpful tips for Objective #10: Try different camera angles to find the one most useful to you. The easiest way to get three spiders is to back up, then move forward, since three spiders are in a row. Work at getting one spider at a time, adjusting the sleep and/or motor speed a little at a time. A student may have to run the code a few times, since it runs a little differently each time. Slower speeds have a little more consistency, so if someone struggles, have them go slower at first.

Objective #11: This objective does not use any programming. Students use the universal camera to explore the front porch and locate the envelope. They click on the envelope to meet the goal. The envelope is on the rocking chair.

Objective #12: The answer to the activity guide question is in the message from the envelope. This objective uses the CodeBot speaker to put rats to sleep. Make sure the speaker is enabled or you will not hear the notes as they play. The notes for the melody are given in the note. The code for the rats doesn't have to be complicated. The code for the first rat is given in CodeTrek. Students can follow the pattern for each additional rat, looking for the notes in the dictionary on lines 6-9. The boss rat must hear his melody two times. Don't forget the silence in between. Reset the scene each time you run the code to see the rats disappear. If your students have programming experience or want to try a shorter solution, they can use the hints. Two more ways to play the melodies are given, and each level of complexity will give the student bonus points.

Objective #13: This challenge is fairly straightforward: drive the 'bot through the hole in the door. CodeBot doesn't need to rotate or anything, just drive straight. A faster time gives a higher score. Students should remember to reset the scene each time they run their code. Don't forget to enable the motors!