Required to run
Your game HTML
The generated .html file is self-contained. Graph images are embedded. You do not need a question-assets folder beside it.
Composer quick start
From course topics to a working game in seven steps.
Choose concepts and learning-outcome coverage, then configure modes and appearance. The Composer assembles the question bank, checks readiness, and produces a self-contained game.
Before you start
You do not need to edit JavaScript.
Have a rough list of the concepts students should practice. If you want a quick build, use a starter combination and let automatic checkpoint coverage do its job.
- 01
Concepts & scope
Choose General Economics, Microeconomics, or Macroeconomics, then a starter combination or individual concepts. Open a selected card’s Learning outcomes. Standard is the normal starting coverage; Brief selects essentials and Full selects all outcomes. Check or uncheck outcomes for Custom coverage. A combination matching a preset may show that preset name. Some concepts have one coherent outcome, so the presets coincide. Explore the Learning Outcome Coverage guide.
- 02
Game details
Give the game a student-facing title and a file name using lowercase letters, numbers, and hyphens. Review Anonymous gameplay data: collection is OFF by default. Explicitly enable it only if you want the generated game to send anonymous gameplay and interaction telemetry for operational, instructional, and product analytics. This does not transmit your Composer selections and is not research by default. See Privacy and Responsible Telemetry Use for student controls, visibility, and interpretation.
- 03
Modes
Enable the modes that fit your assignment. Availability depends on the chosen content; coverage and difficulty are separate. See the mode guide.
- 04
Checkpoints
Review automatic coverage: easy checkpoint questions at Checkpoint One, medium at Checkpoint Two, and hard at the Final Checkpoint. Optional focus narrows checkpoint coverage without removing ordinary questions.
- 05
Appearance
Choose an official theme, keep its artwork, or replace individual slots with official or custom images.
- 06
Readiness
Resolve blocking coverage issues for your selected modes. Confirm the anonymous data collection ON/OFF status before Generate. Review the estimated package size and detailed counts when useful.
- 07
Generate
Download the ZIP with the self-contained game, composition recipe, manifest, and README. Keep the recipe to reopen the same selections later. Test the game before assigning it.
What to keep
The HTML runs the game. The other files document the build.
Keep for revision
Composition recipe
Import the recipe back into the composer when you want to reopen the same concept and mode selections.
Keep for records
Manifest and README
These describe the generated build. They do not need to be published for the game to work.
Optional telemetry on HTTPS hosts
You can choose to collect anonymous gameplay data when you create a game with the official Mastery Quests Composer. Collection is OFF by default. To send data, the game must be published on a supported HTTPS website. Permission to send data lasts 365 days for each generated game. Collection stops if that permission expires or is withdrawn, or if a player turns it off in their browser. Players can still play and download their game data. Data already received stays subject to the separate 730-day retention policy.
A game opened directly from a file on your computer can be played and can save a CSV, but it cannot send gameplay data to Mastery Quests. Publish the same file on a supported HTTPS website to enable collection while its permission is valid. Your LMS or network may still block data collection, so test the game the way students will open it. Anonymous records cannot confirm who played or reliably link the same player across different websites.
The National Engine uses an older data-collection setup. Check its own notice for details.