Sokoban Design

Sokoban is a classic puzzle game created in 1980 by Hiroyuki Imabayashi and later published by Thinking Rabbit in 1982. This design is about a Sokoban-like game and it is a good second game design activity for students who have already completed the Frogger tutorials.

Tutorials

 * Sokoban tutorial part 1: user controlled warehouse keeper and pushable crates
 * Sokoban tutorial part 2: destinations, crate counters, step counters, and level complete

Lesson Plans

 * Sokoban Lesson Plans
 * Pamela Birx, Columbia Middle School, Aurora: Monday, Wednesday, Friday 50 minutes each x 2 weeks

Examples

 * Scalable Game Design Arcade Sokobans

Design
Follow the gamelet design process:
 * Identify game objects, called agents, by locating nouns in the game description
 * Categorize agents into user controlled agents (hint the game is called Sokoban), agents that move or do other things by themselves (sometimes also called artificial intelligence agents) and completely passible agents acting as props such as the floor of the maze.
 * Identify agent interaction by locating verbs in the game description

Skills
This is another Scalable Game Design starter game. You need no background in programming, AgentSheets or other tools, although it is helpful to have completed the Frogger design tutorials.

Computational Thinking Patterns

 * Polling: Crates are pushed on destinations. We can use polling to determine when all of the destinations have a crate over them.
 * Push: The warehouse keeper pushes boxes around the maze to reach the destinations and solve the puzzle.

Standards
ISTE National Educational Technology Standards:
 * Creativity and	Innovation. design and implementation of a game, create originals works: creating artwork and game levels
 * Critical	Thinking,	Problem	Solving,	and	Decision	Making. Plan	and	manage	activities to	develop	a	solution	or	complete	a	project: follow game design process.
 * Technology	Operations	and	Concepts. understand	and	use	technology	systems: use authoring tool, organized project folder; troubleshoot	systems	and	applications: run, test and debug program.

Objectives

 * Make your second simple but complete game
 * Apply design process to identify objects and interactions
 * computational thinking: basic object interaction, creating object instances, rule based programming, and message sending.

Grading Requirements, Assessment, Success Criteria, etc.

 * Mark Shouldice's success criteria sheet: updated 6/12/2013 ([[Media:Sokoban eval sheet v3.doc|Word file]]) ([[Media:Sokoban eval sheet v3.pdf|PDF file]])

Requirements

 * Game Design Course requirement
 * Summer Institute requirement for teachers