An offline, learning game where players design a satellite, check it can launch, operate it in orbit, and read evidence-based results
Beginners learn subsystems one by one and assume a higher-spec part always helps.
Building and flying a satellite costs money and carries risk, so students rarely try it.
Without the reason behind a failure, learners cannot work out what to change.
Better camera → more data → more storage → more downlink → more power.
Budget, launcher mass, battery energy, onboard storage and downlink rate.
You can only observe during access windows and transmit during ground contact.
Mission Creator, Spacecraft Builder, Flight Readiness, Operations, Debrief, Redesign.
Simple deterministic equations; every blocked action states its reason.
Five mission presets and A/B redesign: change one part and measure the result.
How mission goals become engineering requirements.
Power and data budgets, payload trade-offs, operations.
Class demos, trade-off exercises, assessed mission runs.
Gives students early practice in systems engineering, the same requirement → design → validation → operations → trade-study cycle real teams use.
The missions stand for coastal, forest, polar-ice, communications and environmental monitoring teams that rely on satellite data.
Test mission ideas with no hardware cost or risk. Runs offline, so it works in low-connectivity classrooms.
Deterministic, repeatable runs teach cause and effect: change one thing, measure, explain.
Game engine, one project, Compatibility renderer
Mission config, catalog validation, orbit planner, step engine, evaluator
Component catalogs, mission presets, orbit windows
Scenes for Mission Control, Creator, Builder, Readiness, Operations, Debrief
Earth, orbit and spacecraft scenes (illustrative)
Battery, storage, event log, playback, readable failure reasons
Version control, public repository
Godot Web (HTML5) export hosted online
Verified offline desktop build; browser export planned
Codex, Antigravity, and ChatGPT
The challenge brief: mission goals, design trade-offs and a playable loop.
Sample 1U mass rule used in Flight Readiness: M_total < 1.33 kg.
Requirement → design → validation flow behind our Mission Creator.
Model for concurrent subsystem trade studies and A/B redesign.
Conceptual reference for orbit and contact planning.
Collection of 3D models, textures, and images from inside NASA.