This page is being redesigned for the 2023 school year and is being constantly updated.
Be sure to REFRESH this page daily so that you are seeing the latest updates.
Follow the directions on this page. However, if you get stuck and/or something doesn't make sense, contact your teacher immediately.
The Dodger Game Extension Project is a special THREE WEEK PROJECT* that is intended to be an extension of the Dodger Game Starter Project. It is designed to accomplish several things:
TWP: Introduce students to how a game extension project fits into the THREE WEEK PROJECT process.
PJ: Reinforce the idea of maintaining a PROGRAMMING JOURNAL to properly document the iterative design process.
Version Numbering: Reinforce proper version numbering. Introduce how to do versioning when you are not starting from scratch. Reinforce how to use a VERSION SCHEDULE TABLE to organize and keep track of project builds.
PREP WORK: Build on the idea of the importance of properly completing the PREP portion of a project - even when you are already starting with a "working" game.
While the "training wheels" are off for this project, I suggest you still rely heavily on the following sites as you work through this project:
For the most part, you will work on your own. There will be very little instruction from your teacher.
Now is the time to show off what you have learned this school year.
(* Usually, we allocate 15 school days to complete the project. However, due to other external factors, the actual project my be slightly more (or slightly less) than 15 school days).
The general criteria for grading will be based on the following:
How well a student properly PREPARES and PLANS OUT the entire project before attempting the first build.
How well the student honestly REFLECTS, ASSESSES, and makes appropriate ADJUSTMENTS (as necessary) to the project build.
The quality of final ARTIFACT. This will be assessed in the following ways:
The UX (User Experience) of the finished product (does the program actually work, etc.)
How well the student follows good programming conventions when writing the code (whitespace, indentation, comments, naming conventions, user-created functions, organization/structure, etc.).
How well the student incorporates NEW coding structures that demonstrate learning and growth as a programmer. (i.e., don't show me what you already know how to do. Show me that you can learn and incorporate new ideas).
This THREE-WEEK project can be broken up into FIVE main chunks:
Project Proposal
Project Planning
Iterative Project Development (building, testing, and continually making small improvements/adjustments)
Final Project Submission
Evaluation, Feedback, and Reflection
While we generally do these in order, there is overlap between the last four chunks. For example, we are constantly reflecting on the project from the very first day (via our programming journal) and there are Reflection elements built in to the Iterative Project Development . . . that, in turn, can cause us to go back and refine our original plan.
Creating your "builds" for this project should be a very interactive and flexible process.
A detailed breakdown of what you should be completing each day of the project can be found on the Three Week Project Schedule page.
The Dodger Game Extension is a project to EXTEND the DODGER GAME STARTER project. In this extension, you are going to add enhancements and your own personalization to the original Dodger Game starter in order to make this a more polished game.
What you change is entirely up to you. You can change the theme, sprite or background graphics. You can add a scoreboard. You can add levels. You can add anything you like to make this a better game . . .
. . . but you must also include at least one new programming structure that you have never used before. I'd suggest reading through the p5play elements at the GameLab Game Tutorials site to give you some ideas.
Below are some of the extensions that other students have attempted over the years. (Note: many of the samples shown below are still in draft form. They are not the final version of the extension. These are just provided to give you some ideas on how you could extend the Dodger Game Starter project.)
It's Raining Cats and Dogs (JB, Class of '22)
Space Game (NB, Class of '24)
Star Navigator (MC, Class of '24)
Space Dodger (AD, Class of '24)
Barrier Run (HN, Class of '24)
Cake Defense (ST, Class of '24)
Catch the Star (CW, Class of '21)
Air Fighter (AW, Class of '24)
Dodger Racer (GY, Class of '24)
Galactic Dodger (RS, Class of '24)
[Hidden]
The Project Proposal can be chunked into TWO main steps:
Determine the Scope of your Project
What do you plan to build (a new project or are you extending another project)?
How much time do you have to build it?
Create your Project Proposal (ONE-PAGER)
You have three-weeks to build this project.
Your first task is to figure out what you can realistically complete in your three-week time-frame. Your plan should have your finishing your project ON the last day. Not before. Not later.
Don't take on too much work. Don't take on too little work. Try to find the "Goldilocks" amount. Your final grade is based less on WHERE you finish and more on the JOURNEY you took to get there. Specifically, did you keep iterating and improving your project over the entire three week project cycle?
Keep this in mind as you plan out your project.
A typical ONE-PAGER for a classic 2D arcade-style game should contain all the important facts about the project you intend to build. Typically, it should contain the following:
State the overall objective of game (how do you win? // how do you level up?)
An explanation of how the game functions:
How do you play?
What is the role of the user?
Do you control a character/avatar?
Do you use the mouse/keyboard?
How do you level up?
Sketches of various modes of game play (splash screen, game play, levels, boss, game over, etc.). All games are different so what you sketch will depend on YOUR game. Your sketch(es) should make it clear to a stranger what you expect your final game will look like AND what the experience will be like. On each sketch, you should:
identify all the sprites/variables you plan to use
identify the naming convention(s) you plan to use for sprites/variables/functions
detail the expected behavior(s) of your sprites (do they animate, move, fade-in, etc.). Be as detailed as possible.
identify whether or not there will be a scoreboard (or some kind of user feedback) on the screen? What information does it show?
Make a copy of the Dodger Game Extension: ONE PAGER document.
Keep the document PRIVATE but give your teacher COMMENTING rights. You can't earn any points for your work if I can't see your work.
The formatting of the ONE-PAGER document is entirely up to you. Arrange your page in a way that best communicates your information. Use use solid visual communication and design strategies. If you use photos/images, be sure all your detail can be seen/read.
Finally, seek help if you have any questions or you are having any trouble completing this assignment.
When you are sure you have completed all the requirements for the ONE-PAGER, go to the ONE PAGER section of the CSD Class Projects: Submission Forms page to submit your digital document for approval.
[Hidden]
Once your ONE-PAGER IS approved, you can start earning points on the rest of your project.
Your first big assessment will be on the quality of the PLANNING you do before you start your build.
To get your project started off on the right footing, you need a solid plan for the next three weeks.
If you plan well, the rest of your project usually runs smoothly. If you plan poorly, you will likely encounter a lot of frustration while trying to build and complete your project.
The Project Planning can be chunked into FOUR main steps:
Establish and set up your Programming Journal (PJ)
Complete the Daily Entry section of Your Programming Journal (one entry completed for each day of the project).
Complete the Version Schedule (VS) in your Programming Journal (this should be completed prior to starting your first build).
Complete the "Prep" section of your Programming Journal (this should be done prior to starting your first build).
Note: be aware that you cannot make up any of your planning work after you begin your build. Once you've started your build, you have moved beyond the PLANNING phase (and beyond the ability to earn any more points for this portion of your project). Therefore, be sure you have completed all your planning steps before you begin working on any portion of your digital build.
Your programming journal is where you will document your project scope, your project planning and prep work, AND where you will keep a record of your daily reflections about your work/progress throughout the project cycle.
As soon as you get access to your PJ, your should complete your COVER PAGE.
Make a copy of the Dodger Game Extension: Programming Journal.
The directions for completing each section of the PJ are embedded in the PJ itself.
Talk to your teacher if you have any questions about any of the sections.
In order to make your document available for periodic checkups (as well as your final submission), you are going to SUBMIT your document NOW. Don't worry, you can keep on making edits to your document after you submit.
Before submitting, be sure to keep the document PRIVATE but give your teacher COMMENTING rights. You can't earn any points for your work if your teacher can't see your work.
Go to the Programming Journal section of the Class Projects: Submission Forms page to digitally submit your work.
Now that you have submitted the URL for your PJ, it's time to begin your DJE (Daily Journal Entries) and completing your PREP work (all the pages before the DJE begin: everything from the COVER SHEET to the FUNCTION TABLE).
Follow the instructions on the Daily Class Announcements and the TWP Project Schedule page as necessary.
[Hidden]
[Hidden]
Use the FORM below to submit the most recent WORKING draft build of your project for peer review. Use the SPREADSHEET to check and make sure everything is submitted properly.
All DUE DATES / DEADLINES should be posted in the Daily Class Announcements.
Dodger Game Extension: Peer Evaluation Prep: Submission Form
Peer Evaluation Prep: Spreadsheet.
As always, the class will be split into groups for the RESPONDER portion of the Peer Evaluations. You are responsible for completing a peer evaluation for each member of your group.
Follow the instructions below:
(NOTE: Links will not be active until the day we complete the peer evaluation activity)
Find your group using the spreadsheet from the last step (NOTE: the submission form will not be formatted into groups until the day we complete the RESPONDER activity. Check the Daily Class Announcements for full details.)
Review the work of each person in your group.
Use the Peer Evaluation: RESPONDER Submission Form to conduct a peer evaluation for EACH MEMBER OF YOUR GROUP (even if they didn't submit anything for review). Follow the directions on the form. It will walk you through all the steps.
Check the Peer Evaluation: RESPONDER: Spreadsheet to make sure all your evaluations have been properly submitted.
As soon as you receive your peer evaluations from the RESPONDER activity, you can begin the ARTIST portion of the Peer Evaluation process.
Follow these steps:
Use the spreadsheet from the last step to review your feedback. Note: when it's time to complete this activity, the spreadsheet will be re-sorted by ARTIST so you can find your peer evaluations more easily (See the Daily Class Announcements for full details).
When you are finished with your review, navigate to Google Classroom.
Go to the CLASSWORK section.
Find the DODGER GAME EXTENSION topic.
Open the Peer Evaluation: Artist assignment and follow the instructions on the document. Note: the document will not post in Google Classroom until it is time to complete this assignment. See the Daily Class Announcements for full details.
[Hidden]
[Hidden]
[Hidden]
Make a copy of the DGE Project: Final Reflection Worksheet.
Follow the directions on the document and complete your form.
Be sure to check the Daily Class Announcements for specific DUE DATES and DEADLINES for this assignment.
Follow the directions in the Final Reflection section of the CSD: Class Projects: Submission Forms page to submit your work.
[Hidden]