Faculty demonstration
The Mastery Quests Faculty Template shows the full adaptive structure in a neutral build, making it easier to distinguish the reusable learning engine from the custom art, audio, story, and disciplinary identity added later.
Local-only demonstration: The Faculty Template asks only for a display name. It does not transmit gameplay telemetry. Progress and preferences remain in the player's browser.
Why the template exists
A finished Mastery Quest can look highly customized, but the instructional structure underneath remains portable. The template gives faculty a clean starting point and a working reference when something needs to be changed.
The template demonstrates
A developed game adds
What faculty change
Replace the questions, tags, objectives, calculations, feedback, and boss pools.
Revise titles, guides, room language, remediation text, and mastery-report labels.
Add a course theme, backgrounds, characters, artifacts, icons, and collection branding.
Use optional ambient, battle, boss, and completion audio with player-controlled sound.
What stays intact
Faculty can redesign most visible content. Core IDs, state variables, adaptive functions, mode rules, telemetry fields, and completion logic should be changed only when the engine itself is intentionally being revised.
Question content, labels, story text, media paths, colors, guides, bosses, and artifacts.
Question IDs, tags, objective mappings, pool names, room thresholds, and hub storage keys.
Adaptive selection, progression, remediation, scoring, completion, persistence, and telemetry.
Recommended path
Complete a short run, miss questions intentionally, and inspect the mastery report.
Notice which elements belong to the engine and which were added for the course world.
Work from a local copy and retain a clean original for comparison.
Audit answer logic, duplicates, IDs, tags, objective coverage, and repair connections.
Test correct paths, missed-answer paths, timers, bosses, saving, scoring, and reporting.