Big Picture

Now that you have come up with a design for your video game today is the day in which we create it.

Here are some big picture ideas:
​Design ideas become technological outcomes through the selection of tools, techniques and processes.
As developers create games, their design decisions influence how users interact with the outcome and affect its performance, usability and engagement.

Lesson 1: Create Pixel Art Assets

Learning Intention
  • Develop pixel art assets that support the purpose, audience, and visual style of a game.
  • Use appropriate digital tools and techniques to create game graphics.
Success Criteria
  • I can create a player character, collectible item, obstacle, and background.
  • I can apply pixel art conventions such as clear shapes, colour consistency, and readability.
  • I can explain how my design choices support the target audience.
  • I use appropriate tools and file management practices when creating assets.
Today: Create Assets that support a fit-for purpose game prototype
Do Now: Review your Week 1 design work, (5 Minutes)
Answer the following:
* What is the purpose of your game?
* Who is our target Audience?
* What style of pixel art best suits your audience?

Task 1: Create Core Assets (45 Minutes)

Create the following pixel art assets:

- Player Character (2 Frames for walking)
- Coin (could spin start with single frame)
- Obstacle or enemy
- Background

Optional
- Extra collectable
- Power up
- Additional Scenery

Task 2 Design Reflection (5 Minutes

For each asset explain:
Why did you choose these colours?
Why did you choose this design?
How does this support your target audience?

Lesson 2: Build Scratch Prototype

Learning Intention
  • Develop a working game prototype by integrating pixel art assets and Scratch programming techniques.
  • Use structured processes to create an interactive technological outcome.
Success Criteria
  • I can create player movement controls.
  • I can implement a coin collection system.
  • I can create a score system that functions correctly.
  • I can integrate my pixel art assets into the game.
  • I can identify and fix simple errors during testing.
Do Now (5 minutes):
Create a new scratch game
Click the orange publish button
​Share it to your one note.

​Don't worry any future changes will be automagically updated

Task 1: Build Basic Functionality

​Core Features✅ Character movement
✅ Coin collection
✅ Score variable
✅ Obstacle interaction
✅ Win or lose condition
Students may use a provided guide for:
  • Arrow key movement
  • Collision detection
  • Coin collection
  • Scoring

Guide: to Importing Sprites from Pixilart.com to Scratch

1.) Make sure the background is transparent
Click File then Export/Download
3.) Change the Export settings to 10x and Download all frames
Picture
4.) Rename the file to something meaningful
Pick one picture and Upload the Sprite
Upload any further Costumes.

​These are further animations

Task 2: Performance Check (5 Minutes)

Test your prototype

Check:
  • Does movement work smoothly?
  • Does scoring work correctly?
  • Do assets display properly?
  • Are there any bugs?

Is there a feature that still needs improvement?

Lesson 3: Playtesting and Refinement

Learning Intention
  • Test a technological outcome and use feedback to improve functionality, usability, and engagement.
  • Document design decisions and refinements made during development.
Success Criteria
  • I can provide constructive feedback on another student's game.
  • I can analyse feedback about function, engagement, asset quality, performance, and usability.
  • I can make improvements based on evidence from playtesting.
  • I can document changes and explain why they were made.
  • I can evaluate how design decisions influence the player's experience.

Do Now (5 minutes)
​Before testing, predict:
One thing users will like.
​One thing users may struggle with.

Task 1: Peer Playtest (20 Minutes)

Swap games with another student

Complete the feedback sheet:
​Function
  • Did the game work correctly?
  • Were there any bugs?
Engagement
  • Was the game enjoyable?
  • Would you play again?
Asset Quality
  • Were the graphics easy to recognise?
  • Did they suit the game?
Performance
  • Did the game run smoothly?
  • Were there delays or problems?
Usability
  • Were controls easy to learn?
  • Were instructions clear?

Task 2: Analyze feedback (15 Minutes)

Identify:
  • One Strength
  • One Weakness
  • One Improvement

​Complete the development log below

Task 3: Refine Prototype (20 minutes)

​Implement improvements based on feedback.
Possible improvements:
  • Fix bugs
  • Adjust movement
  • Improve graphics
  • Increase challenge
  • Improve instructions