Meeting 13
MC: Yumi
Tomorrow: Emmanuel
We are all working towards a FRIDAY deadline. You can still spend some of your workday finishing projects that need more time, but we need mostly finished work to show to the rest of our program.
What to do if you finish your game/project early;
- Create a soundtrack
- Add sound effects to collisions and events — JFXR or Leshy SFMaker
- Create an intro screen, with the title/credits/controls/backstory/etc
- Create an easter egg level, or bonus level
- Replace static sprites with animated sprites
- Add more graphics and NPCs
- Help someone else with their project (coding, artwork, sound, etc.)
LVL2, if you are done you can start event planning for the LVL1 Graduation Ceremony — the more humorous and weird, the better!
Also, if anyone would like to figure out the 3D printers that showed up, have at it!
Work session
LVL2
Work session
LVL1
HUD
aka: heads-up display, aka status bar
- Create a new layer (on top) and set its parallax property to 0% x 0%
- Make sure ALL sprites and textboxes are placed INSIDE of the viewport
- Give textboxes a descriptive name (for sanity's sake), but if the text content will change depending on events in the game, then you don't need to write anything in the textbox (we'll let the code do it instead)
- Do make sure that textboxes have a font size and color that will make sense
Note that the text that remains the same all of the time is kept in quotations, and then a variable name is added after it.
Fun fact!
In your code, you can just refer to Global variables by name. But for instance variables you have to use this format:
objectName.instanceVariableName
For example:
player.health
Instance variables vs Global variables?
Instance variables are set at the start (or restart) of the layout.
They are also unique to sprites — such as: enemies each having their own health.
Global variables are carried from layout to layout. This is handy for player health, or for game progress.
From my demo:
platform-demo-with-HUD.c3p