- #SCARY MAZE GAME JUMPSCARE HOW TO#
- #SCARY MAZE GAME JUMPSCARE CODE#
Here is a sample of a digital journal designed for Scratch ( source) and here is an example of a printable journal useful for younger coders.Celebrate Halloween any time of year with our scary games! This spooky collection includes ghosts, zombies, ghouls, and all kinds of other monsters. If reflecting in smaller groups or individually, walk around and ask questions to encourage deeper responses and assess for understanding. Debugging exercises and unplugged lesson that reinforces concepts from a projectĬoders can either discuss some of the following prompts with a neighbor, in a small group, as a class, or respond in a physical or digital journal. Getting started sequence and beginning project work An example for incorporating unplugged lessons: Incorporating unplugged lessons in the middle of a multi-day project situates understandings within an actual project however, unplugged lessons can occur before or after projects with the same concepts. List of 100+ unplugged lessons and resources You could start a lesson with a short, unplugged lesson relevant to a project, or use unplugged lessons when coders appear to be struggling with a concept or practice. Unplugged lessons are coding lessons that teach core computational concepts without computers or tablets. In particular, reinforcing a variety of standards, practices, and concepts through the use of unplugged lessons.
#SCARY MAZE GAME JUMPSCARE CODE#
This will run the same code as before however, the forever loop will check the conditions much faster than the “when tilted” event blocks, which makes the Player sprite much fasterĪlthough each project lesson includes suggestions for the amount of class time to spend on a project, BootUp encourages coding facilitators to supplement our project lessons with resources created by others. We need to create a function for the movements and use conditionals (“if” blocks) to check which direction we are tilting. Micro:bit required Why does the Player move so slowly when using the micro:bit? Next we need to show the JumpScare sprite (because we hide it when the green flag is clicked). First the JumpScare sprite needs to receive “jumpscare” and not “jump scare” (spacing is important). Why doesn't the jump scare happen when the player touches the HiddenObject sprite? (Debugging 3) We need to show the HiddenObject sprite, otherwise the Player sprite won’t touch it. Why doesn't the jump scare happen when the player touches the HiddenObject sprite? (Debugging 2) We need to wait until the HiddenObject sprite touches the Player sprite, not the JumpScare sprite. Why doesn't the jump scare happen when the player touches the HiddenObject sprite? (Debugging 1) If the project is a game, could you turn it into a different kind of game?. If the project is not a game, could you turn this project into a game?. How might you use “if” conditional blocks in this project?. How might we add player controls to this project?. What’s something you like about their project that you could add to your project?. What blocks did they use that you didn’t use?. How is this project similar (or different) to something you worked on today?. What are some ways you can expand this project beyond what it can already do?. For example, “look for five minutes,” “look at no more than five other projects,” “find three projects that each do one thing you would like to add to your project,” or “find X number of projects that are similar to the project we are creating.” Note: Coders may need a gentle reminder we are looking at other projects to get ideas for our own project, not to simply play around. Resource: Studio with mazes I created (some are very complicated) Encourage coders to experiment with different numbers, effects, and the pick random number blocks to create their own unique blinking sprite. After a couple of minutes of sharing and discussing their code, use the slides on the quick reference guide (or this example project) to talk through creating a “blink forever” function (explicitly point out we use the broadcast message block because the function will loop forever and therefore My Blocks will never move to the next block). Have coders chat with a neighbor about how they tried to reverse engineer a blinking forever function. After a minute or so, remind coders to think about modularity by using functions to keep the code organized and readable. #SCARY MAZE GAME JUMPSCARE HOW TO#
Give about five minutes to experiment with figuring out how to make a sprite blink forever before comparing algorithms with a neighbor. Ask coders if they can figure out how to make the player’s sprite blink forever (for an extra challenge).
0 kommentar(er)
