Team Chimeritos

Robby Bailey	rbailey@hmc.edu
Ken Dye	kdye@hmc.edu
Colleen Hamilton	chamilto@cs.hmc.edu

Game Concept

Game Design
    Risk Factors
        Pre-implemented features to reduce risk
    Use Cases
    Preliminary Design Document
    Final Design Document

Game Implementation
    UML Class Diagram
    User Guide
    Primary Critters
    Forces Needed
    Demo of In-Game Forces

SKATE OR FAIL FINAL EXE

Game Concept

The game is a side-scroller with the player as a student at Harvey Mudd. The object of the game is to get their room to their test (or class, or meeting, etc.) in another part of campus. The player will have control of forwards and backwards movement, as well as the ability to jump, duck, and climb in order to avoid obstacles. Obstacles could include stairs, gardeners/lawnmowers, local plant life, fellow students, jumping skateboarders, unicyclists, and teachers. Different levels start off at different dorms, ending in different locations. As level difficulty increases, the distance from one point to the other gets longer, and the obstacles become more numerous. The hardest level would be perhaps to get from Linde to Olin. The score is based on the time taken to complete the level. Perhaps have a best times scoreboard. Maybe as a bonus level, have a destination off-campus?

Game Design for SKATE or FAIL

SKATE or FAIL concept site

Risk factors:

Physics
Graphics

Identified features of Pop that will decrease risk

Side-scrolling backgrounds
"Gravity" can stick player to "ground"
Collision detection
Built-in Forces (gravity, drag, etc)
Level rewind (see end of Ball World)
Input detection for mouse and keyboard
AI for badguys
Frame-rendering timer
Player object
Enemy objects
Neutral objects
Sprite animations
Various kinds of movement (see Spacewar: car movement, scooter, etc)
Restricted area for movement to occur within
Multiple backgrounds for use in different levels
Status bar for info such as score, time, health, etc
Auto-advancing at correct location in movement plane

Use Cases

Word Document

HTML Document

Preliminary Design Document

Word Document

HTML Document

Final Design Document

Word Document

HTML Document

Game Implementation for SKATE or FAIL

UML Class Diagram

Download UML.bmp

User Guide

Word Document

HTML Document

Primary Critters

Skater

Attributes: position, velocity
Appearance: skater boy. When skater hits an obstacle, he is frozen temporarily, because he has “fallen”
User Controls: right arrow is turn right, left arrow is turn left, up arrow is speed up, down arrow is slow down.
Forces affecting: none
AI: none
Collision behavior: the skater falls if he runs into teachers or students. If he hits a building, he bounces off.

Teachers

Attributes: position, velocity
Appearance: big, fast, and smart
User Controls: none
Forces affecting: none
AI: move around randomly, move toward skater when skater is close to them
Collision behavior: when the skater hits a teacher, he falls. When teachers hit buildings they bounce off.

Students

Attributes: position, velocity
Appearance: small, fast, and dumb
User Controls: none
Forces affecting: none
AI: walk randomly along walkways, move slightly away from skater when he is close to them
Collision behavior: when the skater hits a student, he falls. When students hit buildings they bounce off.

Buildings

Attributes: position, size
Appearance: similar to buildings on campus
User Controls: none
Forces affecting: none
AI: none
Collision behavior: when anything hits the buildings, they bounce off.

back to top

Forces needed

cForceObjectSeek

Teachers seek out the skateboarder using cForceObjectSeek (included in POP framework), and so do students, but to a lesser extent.

Demo of In-Game Forces

Download ForceDemo.exe

Sprites

Download sprites.bmp