Second session down – lots to talk about! We’re already seeing game visions take form.
If you’re having a hard time getting clarity, try forming a sentence along this template:
For example, “I want to make a rail shooter game about archerfish where the main mechanic is shooting water in Stencyl”. Having a focus helps you make decisions and set your main goal for your game.
Keep in mind, even if your idea doesn’t seem 100% clear right now, it’s still early enough in the program to change it up! As you implement your game, you can discover new paths and unexpected fun and there’s no reason not to take a new opportunity or change ideas as you’re making it. In fact, it’s expected that the game you make won’t be exactly what you thought initially – embrace it!
MDA DESIGN FRAMEWORK
Our very own coordinator Elaine presented the concept of MDA: Mechanics, Dynamics, and Æsthetics. It’s one of the many frameworks we can use to analyze games. It helps give us a common language to talk about our games and other games.
For more information:
→ Jennifer’s presentation on MDA during PGI5
→ Alicia’s presentation on MDA during PGI4
→ Presentation on MDA dring PGI2
→ Une traduction de la source originale cité dans la présentation de Jennifer et d’Alicia.
→ Original source cited in the presentations
We also talked about “paper prototyping”: sketching out your game on paper first, and using props (like quarters and dimes, a stack of playing cards) and diagrams (post-it notes with different outcomes, flowcharts) to try re-creating your game concept on a few sheets of paper. Rather than spending time tackling unknown tasks at the computer, use your paper prototype to make clear what your goals are, and to take inventory of what exactly it is that you even need to code and make art and sound for. Consider your game design and ask yourself: Can I even play this? Is this a fun (or whatever other emotional states you’re trying to trigger) game?
Particularly helpful too if you want a branching narrative, drawing a diagram by hand can help you figure out holes and missing branches quickly.
GAME ENGINES AND INTRO TO PROGRAMMING WITH ELEANOR
For the second part, Julia Perdigueiro, game programmer with indie studio MegaZebra in Montreal, was our mentor this week. She gace us a presentation on game engines and an introduction to programming logic.
For more information:
→ Here is a presentation on variables and logical operators.
JOIN US ON SATURDAY AFTERNOONS AT GAMEPLAY SPACE!!
We encourage you to go online to discuss at our Facebook Groups or on our Slack channels, but there’s still no substitute for face-to-face interactions. Thus we encourage you to meet with us again to ask questions, brainstorm, bug-fix or just for tea and biscuits!
When: Saturdays from January 12 to February 23 2019, inclusively
Time: 14h à 17h
Where: Gameplay Space, 1435 rue Saint-Alexandre, suite 140 (métro Place-des-arts)
- Analyze your game in terms of MDA: What is your core mechanic? What’s your Aesthetic goal? What Dynamics do you think the players will have?
- Get the main input of your game working in your game engine. How will the player play- Dragging the mouse? Typing on the keyboard? Screaming into the mic?
- Make a paper prototype of your gameplay. Use cards, paper, post its, drawing to flesh out level ideas, narrative trees, or point and click options. Get creative, and don’t be shy to show it to other people to see if they understand! Paper prototypes help find problems in your design much faster than if you had to code them all to find them!
- If you hit a wall, it’s okay. Come out to the meetup or contact the group via email, Slack or Facebook. As long as you’re started this week, we can suss out where you may be having problems and adjust, for next week!
Don’t hesitate to send us any questions, ask for feedback, or bounce ideas. You can send us e-mails at email@example.com.