Available
Apr 13, 2022 at 8am - Jun 3, 2022 at 11:59pm
This assignment was locked Jun 3, 2022 at 11:59pm.
Lesson 19: Collision Detection
Question of the Day: How can programming help make complicated problems more simple?
Students learn about collision detection on the computer. Working in pairs, they explore how a computer could use sprite location and size properties and math to detect whether two sprites are touching. They then use theisTouching()block to create different effects when sprites collide, and practice using the block to model various interactions.
To earn credit for the lesson, students will submit a screenshot of their bubble 7. The screenshot should show:
The student's code for the level (specifically the conditionals using isTouching() )
The animation it creates
The animation should do what is required in the directions and uses a conditional (show in your screenshot).
For a distinguished score, students have all the requirements above and have:
When the rainbow leaves the screen:
make the unicorn move back and forth using velocityX()
make the unicorn rotate using sprite.rotationSpeed()
Submit a shared link to the animation (see below)
Additionally, since we'll be using animations starting now, please share the link to your project by clicking the share button, copying the link, and pasting it in as a comment for your submission.
10to >8.5 pts
Distinguished• Work correctly uses previously learned concepts, code, or materials not explicitly required in the directions.
• Code executes correctly, with no errors, and correct output.
• Work shows independent thinking.
• Work shows a genuine effort to understand and creatively apply the topic or material.
• Answers (if required) are written in complete sentences.
• Code (if required) is organized and formatted for readability (uses whitespace and indentation to separate elements, appropriate names, etc)
• All sections of the assignment are complete.blank
8.5to >7.5 pts
Proficient• Code executes correctly, with no errors, and correct output. • Work shows student thinking, regardless of “correctness”. • Work shows genuine effort to understand the topic. • Answers (if required) are written in complete sentences. • Code (if required) is formatted for readability (uses whitespace and indentation to separate elements, appropriate names, etc) • All sections of the assignment are complete_4803
7.5to >6.5 pts
Competent• Code executes, possibly with errors, generates an expected output that is close to the correct output. • Work shows an attempt to understand the topic. • Work demonstrates student thinking, but needs expanding or clarification. • Answers (if required) are in fragments or incomplete sentences. • Code (if required) is hard to read • Some sections of the assignment are incomplete._9677
6.5to >5.0 pts
Inadequate• Portions of the code run, but contain many errors or is incomplete.
• The code output is severely incomplete or broken
• No evidence of student thinking.
• Answers are attempts to “fill space” or do not make sense.
• Answers are fragments or incomplete; difficult to read
• Aspects of the task incomplete or missing_9560
5to >0.0 pts
Unacceptable• Code is broken, incorrect, or incomplete, resulting in no output. • Work is missing or plagiarized from another website • More than half the assignment is blank or incomplete • Work has a complete heading_360
0to >0 pts
No Credit• Work must be redone and resubmitted • Work is missing. • More than half the task is blank. • Work is incomprehensible.blank_2
This area will be used by the assessor to leave comments related to this criterion.
pts
/
10 pts
--
This criterion is linked to a Learning OutcomeDescription of criterion