RICH Summative Task
Worth 30% of your Final Mark

Proposal: Due Tues. Dec. 10 by the end of class
Weekly Reports: Due Dec. 13, Dec.20, Jan 10, Jan 17
Weekly Reports are due even if you are away. No late reports will be evaluated.


RST is due :

Period 1 - at the end of Exam Time on January 23
Period 3 - at the end of Exam Time on January 27
You will have from 9:00 a.m. - 11:30 a.m. to work.

Extra time is available during Morning Open Lab Times or at Lunch


If you complete and submit your project early you do not need to come in during the exam time.

All work for the RST must be completed in the classroom.
USB drives and google drive will be blocked, and file downloads will be monitored.
Save everything to the N:Drive only.

You may not bring in printed/written code from home!
You may not have your phone out at any time during the RST

When you are ready to post to your Google Drive ask to have it unblocked.

Remember: This is your RST and you must show me what you have learned.
You only get 3 free questions per week so use them wisely. To get help complete the Help Request Form. I will answer your questions asap but it may not be until the next class. Work on some other part well you are waiting.
Any additional assistance from me will result in a lower evaluation mark.

RST Mark Breakdown /100

Proposal /4
Weekly Reports /16
Final Product /80

Note: Final Product includes website, evaluations, and program

 

 

Design a gamemaker game of your choice with at least 3 Levels. Games must be unique, so have your choice approved by me before completing your proposal.

For the coding portion of the mark the following Levels apply
Level 4 - 90% or greater code
Level 3 - 70% - 89% code
Level 2 - 50% - 69% code
Level 1
- less than 50% code

At least 50% of the graphics must be created by you.
Every variable/object must be named correctly.
All code must be documented. (Even drag and drop code)

Requirements


- at least 3 levels
- each level must have a different objective

- a character that moves in a variety of directions and has different sprites
- allow three lives and conclude on the elimination of the third

- be able to collect a 'treasure' or reach a point that will give bonus points
- include sound effects and music
- include a health bar
- grant an additional life on arriving at a certain score/objective
- have a win/lose/next level screen
- have a high score screen
- have a new/unique splash screen
- have a 'Help Screen' that explains how to play the game and the objective
- all screens must be modified and match your game

 

 

 

 

RST - What is on your Website


Proposal

Proposal (Due Tuesday, December 10 before the end of class)

Weekly Evaluation

Weekly Reports (Due Dec. 14, Dec.20, Jan 10, Jan 17)

You must submit a report for each week of the RST.
These are due even if you are away.
No exceptions! No extensions!
Not submitted will result in an Evaluation of 0. Do not throw away these easy marks.
Google Drive will be unblocked 15 min before the end of class
Weekly reports may also be completed at home. (Due by the end of the Day)

Explain exactly what you did, do NOT just say "I worked on my Game". I want specific details. It may be in point form, but must list everything you did.

Weekly Evaluation marks will be based on:

- the report
- class work for the week
- problem solving skills
- progress on your project

RST - Final Website Submissions

Updated game 'scenario

This should explain any changes you made to your proposal and why!

Game Play Video

Screen shots of rooms, objects, etc.

Files
.gm81 and .exe


RST - What is Printed and Handed In

Evaluations from Others

Peer evaluation sheets will be printed and available at the front of the room
(2 - ICS2O students and 2 - people not taking programming, must test your game)

Complete 2 Evaluations
The person you do them for will submit.

Complete Rubric

Rubric (with questions answered and evaluations circled)