RVA #GGJ15 Keynote Talk - From Consumer to Creator: Making Games
•
1 recomendación•1,267 vistas
The document provides tips for aspiring game developers, based on the author Catt Small's experience making games. Some of the key tips include: start with planning and prototyping before coding; focus on the core mechanics first before polish or extras; it's okay to pivot ideas if something isn't working; everyone needs help so don't be afraid to ask questions; and the goal is to make games that provide memorable experiences for players, not necessarily "fun" experiences. The overall message is to keep practicing, learn from failures and others, and don't give up on your game idea.
Recomendados
Más contenido relacionado
Similar a RVA #GGJ15 Keynote Talk - From Consumer to Creator: Making Games
Similar a RVA #GGJ15 Keynote Talk - From Consumer to Creator: Making Games (20)
Más de Catt Small
Más de Catt Small (8)
Último
Último (20)
RVA #GGJ15 Keynote Talk - From Consumer to Creator: Making Games
- 2. @cattsmall I’m Catt Small. I like video games A LOT!
- 3. @cattsmall@cattsmall ● Game developer (solo, Brooklyn Gamery, Buttered Toast Studios) ● Teacher & event organizer (The Code Liberation Foundation) ● Product Designer (SoundCloud) ● Illustrator, student, etc. About me:
- 4. @cattsmall@cattsmall Played games as a kid
- 5. @cattsmall@cattsmall Made dress up dolls
- 7. @cattsmall@cattsmall Made game jam games
- 9. @cattsmall@cattsmall At the beginning, game dev was a mystery
- 10. @cattsmall@cattsmall Is this it??? Game Dev Story, Kairosoft
- 12. @cattsmall@cattsmall I knew nothing about making games
- 13. @cattsmall@cattsmall Kirby, © Nintendo I was the artist
- 14. @cattsmall@cattsmall We had huge aspirations
- 15. @cattsmall@cattsmall Our game was pretty bad...
- 16. @cattsmall@cattsmall But we made SOMETHING, & that ROCKED.
- 17. @cattsmall@cattsmall What I learned: YOLO, just do it.
- 18. @cattsmall@cattsmall The next year, I took a break from GGJ to improve my skills.
- 19. @cattsmall@cattsmall Went to more jams & hackathons Prism Shell Hexapong Teledoor
- 21. @cattsmall@cattsmall What I learned: Polished games come from a lot of practice.
- 22. @cattsmall@cattsmall What I learned: It’s okay to fail if you learn from that failure.
- 24. @cattsmall@cattsmall I knew more about making games
- 25. @cattsmall@cattsmall We made a finished game!
- 26. @cattsmall@cattsmall It didn’t win any awards.
- 27. @cattsmall@cattsmall But it got a lot of positive responses.
- 31. @cattsmall@cattsmall What I learned: Jamming is about self- improvement, not winning.
- 32. @cattsmall@cattsmall What I learned: Keep working on your game if you think it has potential.
- 33. @cattsmall@cattsmall What I learned: Advocate for yourself and you’ll get heard.
- 34. @cattsmall Other tips for you!
- 35. @cattsmall@cattsmall Games are made of several things... most of the time.
- 36. @cattsmall@cattsmall ● Characters: beings with which player(s) interact ● Mechanics/Rules: systems that determine how player(s) interact with the game ● Goal: what the player(s) must do to finish the game ● Story: narrative driving the game’s goal & rules What makes up most games:
- 37. @cattsmall@cattsmall You don’t need all (or any) of these.
- 38. @cattsmall@cattsmall Not a programmer? You can do other important things.
- 39. @cattsmall@cattsmall ● Sound design (SFX, music) ● Art (characters, level, menus) ● Game design (levels, systems, logic) ● Writing (story, menus, instructions) Some other roles:
- 40. @cattsmall@cattsmall There is something for everyone.
- 41. @cattsmall@cattsmall ● Game art: www.opengameart.org ● Sound effects: www.grsites.com/archive/sounds ● Sound effects and music: www.freesound.org Free resources:
- 42. @cattsmall@cattsmall Remember to make a plan.
- 43. @cattsmall@cattsmall Try not to jump right into code.
- 46. @cattsmall@cattsmall This will help you stay on track.
- 47. @cattsmall@cattsmall We are now living in the era of accessible game development.
- 48. @cattsmall@cattsmall GameMaker Studio GameMaker Studio, Yoyo Games. image credit: gamedevelopment.tutsplus.com
- 50. @cattsmall@cattsmall Unity Unity Engine, Unity Technologies
- 52. @cattsmall@cattsmall And more! Twine, Scratch, Stencyl, RPGMaker, openFrameworks, Processing...
- 53. @cattsmall@cattsmall Pick whatever gets the job done.
- 54. @cattsmall@cattsmall Dream big, but start small.
- 55. @cattsmall@cattsmall Make the important parts work
- 57. @cattsmall@cattsmall Put the fancy stuff in when you can.
- 58. @cattsmall@cattsmall If something isn’t working, pivot ASAP.
- 59. @cattsmall@cattsmall Don’t waste 3/4 of the jam getting a feature to work.
- 61. @cattsmall@cattsmall No one should judge you for needing help.
- 62. @cattsmall@cattsmall Everyone does this! Google is your best friend.
- 64. @cattsmall@cattsmall If you can, playtest your game.
- 67. @cattsmall@cattsmall You only need FIVE PEOPLE.- "A mathematical model of the finding of usability problems"
- 70. @cattsmall@cattsmall If you stay awake for too long, your code will suck.
- 71. @cattsmall@cattsmall Remember that games don’t have to be “fun”.
- 73. @cattsmall@cattsmall Joy Rayman Legends, © Frictional Games
- 75. @cattsmall@cattsmall Excitement Prism Shell, © Brooklyn Gamery
- 78. @cattsmall@cattsmall Don’t leave if your game doesn’t get 100% finished.
- 79. @cattsmall@cattsmall Stay and learn from what others make.
- 80. @cattsmall@cattsmall In summary: ● Put the polish in later. ● You don’t have to be a programmer! ● Ask for help and test your game. ● Listen to your body and sleep as needed. ● Games don’t need to be fun, but should convey memorable experiences. ● Don’t give up – push through & learn!
- 82. @cattsmall@cattsmall Thank you! Think of questions later? Tweet @cattsmall Email catt@cattsmall.com