Frogger Design 2D

From Scalable Game Design wiki
Jump to: navigation, search
OriginalFroggerGameScreenshot.png
Frogger is a classic arcade style game from 1981 developed by Sega. This design is about a frogger-like game which is a good first game design activity for students with no programming background.


Gameplay

You are a frog. Your task is simple: hop across a busy highway, dodging cars and trucks, until you get the to the edge of a river, where you must keep yourself from drowning by crossing safely to your grotto at the top of the screen by leaping across the backs of turtles and logs. But watch out for snakes and alligators! (Sega, 1980).

Tutorials

Experimental

Lesson Plans

Examples

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 Frogger), agents that move or do other things by themselves (sometimes also called artificial intelligence agents) and completely passive agents acting as props such as the road.
  • identify agent interaction by locating verbs in the game description

Skills

This is the Scalable Game Design starter game. You need no background in programming, AgentSheets or other tools.

Computational Thinking Patterns

  • Absorb: Trucks, turtles, and logs will need to be absorbed (erased) with truck absorber, log absorber, and turtle absorber agents.
  • Collision: Trucks collide with frogs. We will use a simple form of collision to deal with trucks colliding with frogs.
  • Generate: Trucks, turtles, and logs will need to be generated with truck maker, log maker and turtle maker agents.
  • Transport: Logs and turtles transport the frog. This slightly more advanced pattern will be used in part II of the frogger tutorial.

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.

CSTA K–12 Computer Science Standards (L2)

  • Computational Thinking: (CT)
    • Use algorithmic problem solving: students work from game problem statement, design implement and test.
    • Define an algorithm as sequence of instructions.
    • Describe the resulting behavior of an agent following a set of rules.
    • Use abstraction to decompose a problem into sub problems.
  • Collaboration (CL)
    • Collaboratively design, develop, publish, and present products: work in pairs, exchange programs or game artifacts through arcade.
    • Collaborate with peers, experts, and others using collaborative practices such as pair programming, working in project teams, and participating in group active learning activities.
  • Computing Practice & Programming (CPP)
    • Design, develop, publish, and present products: share game with others on arcade.
    • Implement problem solutions using a programming language: looping behavior, conditional statements, logic, expressions, variables, and functions.
  • Community, Global, and Ethical Impacts (CI)
    • Exhibit legal and ethical behaviors when using information and technology and discuss the consequences of misuse: student is aware of copyright concerns and fair use.

Objectives

  • make your first simple but complete game
  • apply design process to identify objects and interactions
  • computational thinking: basic object interaction, stacks, creating object instances, rule based programming, message sending.

Grading Requirements, Assessment, Success Criteria, etc.



External links


International

Versions translated via Google Translate. Notice, these translations are generally not all that great and often include unintended humor. If you find them to be almost usable please let us know and help us to fix them up.