Faculty resources

Build, adapt, and deploy a mastery-centered learning game.

Download the guides, templates, code starters, and validation tools needed to use an existing collection or create a discipline-specific Mastery Quest.

Start with the demonstration

Preview the minimal faculty template before editing the files. It shows the complete engine without the artwork, audio, story, or course-specific identity of a fully developed game.

Explore the Faculty Template

Start here

Understand and implement the platform

Overview guide

Faculty Game Overview Guide

Understand the learning model, game modes, adaptive behavior, student experience, and the relationship between practice, repair, bridge work, and mastery reporting.

Download Guide

Implementation guide

Faculty Implementation Guide

Plan a course deployment, introduce the games to students, select the appropriate modes, and make responsible instructional and privacy choices.

Download Guide

Instructions and checklist

Student Instructions and Faculty Customization Checklist

Provide student-facing directions while reviewing the faculty steps required before launch.

Download Checklist

Featured resource

Mastery Quests Faculty Template

The template is a complete but deliberately minimal implementation of the adaptive engine. Faculty can inspect the structure, play every mode, and compare it with a finished collection before beginning a build.

Already included

Five modes, adaptive selection, repair and bridge logic, checkpoints, boss encounters, progress saving, achievements, and mastery reporting.

Faculty customize

Questions, learning-objective tags, titles, instructional text, theme, artwork, audio, guides, bosses, artifacts, and collection identity.

Suggested workflow

  1. 1 Play the minimal demonstration
  2. 2 Review a developed game collection
  3. 3 Download the template and guides
  4. 4 Replace content in the marked zones
  5. 5 Validate and simulate every mode

Build and customize

Question-pool and collection tools

Hub template

Mastery Quests Multi-Game Hub Template

Create a single landing hub for multiple games, mission status, shared progress, achievements, and collection navigation.

Download Hub

Question builder

Faculty Question Bank Helper

Follow the required question structure and prepare main, boss, repair, bridge, and legendary pools with consistent IDs and tags.

Download Helper

AI prompt template

Example Question Generation Prompt

Use a detailed starter prompt to help an AI system build structured question banks across difficulty levels, distribute learning-objective coverage, apply the required ID ranges, and audit answer logic and choice length.

Download Prompt

Question structure reference

Example Question Architecture

Review the recommended authored-question object, including IDs, answer choices, objective tags, skill fields, common-error tracking, feedback, and optional images. Use it as the structural reference when creating or reviewing question banks.

Download Architecture

Code starter

JavaScript Question Pool Starter

Use a clean JavaScript structure for external question banks and consistent pool naming.

Download Code

Guide

Using External JavaScript Question Pools

Separate question content from the game file, connect scripts correctly, and avoid common loading and path errors.

Download Guide

Validate

Check a question bank before deployment

Spreadsheet tool

Faculty Question Bank Validator

Review item structure, missing fields, duplicate IDs, answer keys, objective tags, and other common defects before the question pools are placed into a live game.

Download Validator

Before deployment

Tell students what the game records.

The Faculty Template does not transmit gameplay data. Some published course games use an instructor-configured telemetry workflow that sends identifiable gameplay records to a spreadsheet. Faculty interested in adding telemetry should not copy an existing endpoint. Contact the creator for implementation guidance and review institutional privacy, records, and research requirements before deployment.