Challenge 3: Why Game Engine Export Falls Outside This Course's Scope — Solution Walkthrough

The answer:

Per this chapter's own material, this course stays focused on
Blender's own single-application workflow — it explicitly doesn't
cover exporting assets into a real-time game engine, among other
genuinely separate, much larger topics.

Why this is a deliberate scope boundary, not an oversight:

Exporting a character into a real-time game engine involves an
entirely separate set of tools, formats, and technical considerations
(engine-specific rigging requirements, real-time performance
constraints, a completely different pipeline) that exist outside
Blender itself. Covering that properly would require its own dedicated
course, not a chapter or two appended onto this one.

Why this matches this chapter's own broader framing:

Per this chapter's own material, this course sets out to deepen
Blender's own internal workflow — sculpting, modifiers, shading,
rigging, physics, compositing — all still within Blender's single
application. Game engine export, render farm setup, and team
production pipelines are named directly as genuinely separate topics,
consistent with keeping this course's own scope honest and clearly
bounded.

WHY THIS WORKS AS AN ANSWER
------------------------------
This exercise checks that game engine export is correctly recognized
as outside this course's own deliberately bounded, single-application
scope, rather than an oversight or a gap that should have been
covered.