The document outlines the structure and expectations for a Game Interface Design course in 2013, which includes 20 credits divided into 50% coursework and 50% exam. It highlights the use of Adobe Flash CS5.5 for labs, covers topics like menu design, HUDs, and interaction design, and encourages students to engage in tutorials and prototyping. Contact information for the instructor and resources are also provided.

1. Game Design 2
Lecture 1: Game Interface Design
2013

2. Important Stuff
• 20 credits
• 50% Coursework
• 50% Exam (2 hr)
• Coursework given out around week 5*
• Will be using Adobe Flash CS5.5 for labs.
• http://www.gcugd2.com
• @gcugd2
*probably

3. Who am I?
• CS @ Strathclyde / Games @ Caledonian
• Dare to be Digital
• e-Bug
• Brand Bang! and others...
• david.farrell@gcu.ac.uk
• @unthank
• M615 (Jon’s old desk)

4. Dare to be Digital

5. e-Bug: Platform Game

8. e-Bug Detective Game

13. Game Interface Design?

14. Game Interface?
• Menus
• Hud
• Data (abstracted?)
• Interaction

15. ‘main’ menus

18. in-game menus

21. HUD
Heads Up Display

22. “any transparent display that presents data without requiring
the user to look away from his or her usual viewpoint.”
Wikipedia article on Heads Up Display, http://en.wikipedia.org/wiki/Head-up_display, 2009

27. data communication
and abstraction

36. interaction

39. Design?

40. “Design is the process by which a designer creates a context to
be encountered by a participant, from which meaning emerges.”
Salen and Zimmerman, Rules of Play, page 41, SAGE Publications, 2004

41. These make sense. The design says “push me”.

42. This make sense.
The handle (and all that text) says “pull me”.

43. But what the heck do you do here?
For a bonus point:
Have you seen this design mistake on campus?

44. Is this good design?

45. Is this good design?

46. Design is used to communicate with the player.

47. This game has many many many combos...
...but did anyone learn them?

48. So what next?

49. Lectures
• data visulisation
• communication with the player
• menu design and flow
• semiotics

50. Tutorials
• play games
• find examples of learning outcomes
• discuss how to improve
• practice designing interfaces
• ‘paper’ prototyping

51. Labs
• Learn how to use Adobe Flash CS5.5 to
create interfaces
• Learn ActionScript 3 basics
• Learn how to combine the two to create
script driven interfaces.

52. Contact
• david.farrell@gcu.ac.uk
• http://www.gcugd2.com
• What do you want?
• @gcugd2
• If you want to meet in person:
• M615