imgd 2900 digital game design i class 12: thursday 12.08

IMGD 2900Digital Game Design I

Class 12: Thursday 12.08

Official class evaluation

Playtesting Round 1

Beadwalkers vs HambingersColored Blocks vs Pearl Etched SpearsDynamic New Algorithms vs Team IshmaelTeam Rocket vs Team Swag CheckTeam Sauce vs Tempest SerenadeTeam Subtlety vs Stormriders

Post-test questions

What is the goal of the game?Was anything confusing or difficult?

Is there any info that would have been good to know before starting?

What did you like? Dislike?How would you describe this game to

someone who has never played it?

Write down the answers.

Playtesting Round 2

Beadwalkers vs StormridersColored Blocks vs Tempest SerenadeDynamic New Algorithms vs Swag CheckHambingers vs Team SubtletyPearl Etched Spears vs Team SauceTeam Ishmael vs Team Rocket

Post-test questions

What is the goal of the game?Was anything confusing or difficult?

Is there any info that would have been good to know before starting?

What did you like? Dislike?How would you describe this game to

someone who has never played it?

Write down the answers.

Some games

Assignment 13Refine and polish your abstract game

Refine and polish your gameComplete your box artJournal as you design and codePost your game before noon MondayBring completed game to class

General requirements

1. The game must have a title.

2. The game must be for one player.

3. Sound effects and/or musicmust be used.

General requirements

4. If custom audio is used, no recognizable speech or singing in any language is permitted.

Custom audio must be open source or in the public domain, with all sources fully documented as comments in your main .js file.

General requirements

4. Final submission must run without crashes or error messages.

5. Must use the current version of Perlenspiel, including the latest .html and .js template files (available on the Download page).

General requirements

6. Must follow The Rules to the letter. Review The Rules on the course Web site to be sure you understand them.

Submitted .html and .js files will be inspected for conformance. Grades of violators will suffer.

General requirements

7. Must be entirely self-documenting. No out-of-game instructions or explanations should be necessary to play the final game.

Quality matters

Your final submission should be functionally complete, stable and polished enough to add to your professional portfolio.

Games in the public domain that follow The Rules will be considered for posting on the Perlenspiel Web site.

1. Grid cannot exceed 16 beads ineither dimension at any time.

2. No glyphs allowed in any beads. 3. Only white, black or shades of gray can be used in the grid, background or status line.

Design RestrictionsPick any three

Design RestrictionsPick any three

4. The game uses either the mouse (no wheel) or WASD/arrows/space bar for all user input.

5. No intelligible words, initials, labels or numbers in any language can appear anywhere, except for the game’s title in the status line.

Beads may be used only as game elements,never as picture elements.

Objective 1:Refine and polish your game

Remove all error messages.

Don’t rely on in-class testing alone!

Show the game to lots of people, especially when you think it’s “done.”

Aim for a showcase piece!

Objective 2:Complete your box art

Must be completely originalGame title or (preferably) logoName of team and all team membersOne-sentence tagline 480 x 480 .png file (named box.png) See Assignment 13 Web page for detailed installation steps

Objective 3:Journal as you design/code

Document your creative processIdeas, code fragments, sketchesJournals will be inspected

Objective 4:Post your completed game before noon next Monday

Your link must point to the box artThe box art must point to the gameMake sure it actually runs!

Objective 5:Bring completed game toMonday’s class

Use flash drivesKeep a backupMake sure both team members

bring a copy to class!

Questions?

Next class:Monday 12.10