Objective #1: This objective is a short lesson on binary numbers and how they can be used to turn on user LEDs. For more information, you can have students click on "binary" in the Objective Panel to add it to their toolbox and read about binary numbers. To use binary numbers when controlling LEDs, use the prefix 0b. You can also use the same technique to turn on the line sensor LEDs. The only difference is there are five of them instead of eight. Example: leds.ls(0b00110)

Objective #2: This objective shows a truth table for the logical operators OR and AND. You may need to review the table with your students. Students will not start a new file for the program. They can delete all the practice code except the import statements and then add new code below. If a student clicks "Reset", they will get a new problem. There are many ways to meet the goal. Students can use code from Mission 1 to turn on or off each LED individually. They can use binary to turn on or off the LEDs with a single line of code. For the highest score, they need to incorporate the logical operator in the code somewhere, but it is not required. For example: answer = True or False

Objective #3: Just like Objective 2, there are many ways to meet this goal. CodeTrek shows one way, which is to solve the problem on your own, and then write code to turn on/off the LEDs. The hints show another way, with a higher score. It uses a variable for each number and then the bitwise operator. The third hint goes into some detail on how the bitwise operators work. It is optional. The bitwise operators are | (or) and & (and).

Objective #4: This challenge uses hexadecimal numbers. The Hint gives a table of hex numbers. You can use it to convert the numbers to binary and then go from there. If you don't want to do any conversion, your students can use the second Hint, similar to the Hint for Objective #3, and use the hexadecimal numbers to solve the problem and turn on/off the LEDs. This will be the most useful way to do it, since further objectives will have similar challenges. To use hexadecimal numbers when controlling LEDs, use the prefix 0x. Here is a sample code:

a = 0x26
b = 0xD5
leds.user(a | b)

Objective #5: This is one of the harder challenges in the mission pack. One difficulty is getting out from under the table. The activity guide encourages students to have a plan.

Tips for Objective #5: CodeBot can go under the chairs. This could be the easiest way to get out from under the table. You can keep all the codes as hexadecimal; there are a few instructions that mention changing the codes to binary, but that is not necessary. The code for moving CodeBot does perform differently from run to run. If it runs correctly once or twice and then doesn't, that doesn't mean you need to change the code, just keep running it and it will perform correctly again. Try using different camera angles: Universal is good for seeing the entire room, but Rotate and Chase are good for seeing what CodeBot sees. If your students are comfortable with functions, this is a good time to use them. You can define a function for moving the 'bot and another function for unhexing the pumpkin, and pass as a parameter the code above the pumpkin. If students don't want to do a function for unhexing, they can just type the three lines of code needed to unhex the pumpkin, filling in the correct code for the pumpkin. You don't have to go to all four pumpkins. Any three will do. You can even avoid the pumpkin under the table altogether if you want.

Objective #6: The objective can be completed on many different levels. For beginners, they just need to go through the door. The code can be just like the one used to get off the porch (Mission 1 Objective 13). If students take time to munch several snacks, this objective can take a lot of time for trial and error. For a higher score, do the same thing as DoorDash but use a function. For bonus scoring, travel around the kitchen munching on treats (with or without a function).