-
Choose a theme for your game! In the demo, we picked an 80s theme: 80s questions, 80s sound and an 80s aesthetic. You can choose any subject for your theme, though, so be creative!
-
Use key events to listen for the letters that your players will type.
-
Display the following on the page:
-
Press any key to get started!
-
Wins: (# of times user guessed the word correctly).
-
If the word is
madonna, display it like this when the game starts:_ _ _ _ _ _ _. -
As the user guesses the correct letters, reveal them:
m a d o _ _ a.
-
-
Number of Guesses Remaining: (# of guesses remaining for the user).
-
Letters Already Guessed: (Letters the user has guessed, displayed like
L Z Y H). -
After the user wins/loses the game should automatically choose another word and make the user play it.
- Play a sound or song when the user guesses their word correctly, like in our demo.
- Write some stylish CSS rules to make a design that fits your game's theme.
- HARD MODE: Organize your game code as an object, except for the key events to get the letter guessed. This will be a challenge if you haven't coded with JavaScript before, but we encourage anyone already familiar with the language to try this out.
- Save your whole game and its properties in an object.
- Save any of your game's functions as methods, and call them underneath your object declaration using event listeners.
- Don't forget to place your global variables and functions above your object.
- Remember: global variables, then objects, then calls.
- Definitely talk with a TA or your instructor if you get tripped up during this challenge.
-
IMPORTANT: Whichever assignment you choose, code your game one piece at a time! Code all of your apps one piece at a time. Always code one piece at a time!
-
Pseudocode your program and break the app down into tiny, manageable fragments. This will make the coding process much less frustrating and a veritable Mach number faster. Otherwise, you'll be chipping away at a giant chunk of abstraction for way too many hours.
- The ability to solve a large problem by treating it as a set of smaller ones is the hallmark of a strong programmer. Best start adapting this into your development routine now, to better prepare for your more complex future projects.
- Remember:
- Split the whole program into many distinct, pseudocoded problems.
- Focus on one of the smaller problems and solve it.
- Only when you solve one problem should you then move onto your next problem.
-
When you encounter bugs (and we all do),
console.logwill become your best friend. Regularly check your console to make sure your app is spitting out the right values.- As a more advanced—but more powerful—alternative, feel free to experiment with the Chrome DevTools Debugger.
-
Try your best to deliver a 'working/playable game' by the end of the deadline. If you're not making progress with Word Guess, switch gears to the Psychic game. Contact your TA/Instructor if you're not making progress after 2 hours. We're here to help!
-
Substance over style! Submitting a working game matters more that making a broken app that at least looks pretty. We're focusing on game mechanics, not just on the look and feel of your app.
-
That said, coding a functional app that also looks pretty would be impressive.
-
Always commit your work and back it up with GitHub pushes. You don't want to lose hours of your work because you didn't push it to GitHub every half hour or so.
- Commit often.
-
Turn in anything you have! Even if you don't finish, we still want to see what you were able to accomplish in the time we gave you. This will help us know what concepts we could help you with, as well as what topics we should focus on in the coming lectures.
- Please submit both the deployed Github.io link to your homework AND the link to the Github Repository!
Attempt to complete homework assignment as described in instructions. If unable to complete certain portions, please pseudocode these portions to describe what remains to be completed. Adding a README.md as well as adding this homework to your portfolio are required as well and more information can be found below.
Add a README.md to your repository describing the project. Here are some resources for creating your README.md. Here are some resources to help you along the way:
After completing the homework please add the piece to your portfolio. Make sure to add a link to your updated portfolio in the comments section of your homework so the TAs can easily ensure you completed this step when they are grading the assignment. To receive an 'A' on any assignment, you must link to it from your portfolio.
If you have any questions about this project or the material we have covered, please post them in the community channels in slack so that your fellow developers can help you! If you're still having trouble, you can come to office hours for assistance from your instructor and TAs.
Good Luck!