Video Script: GameEngine E-Learning Module Demonstration

Total Duration: 8-10 minutes
Target: WGU D301 Task 2 - Design-Based Research on Cognitive Load Reduction

Video Script Table

Step	Time	%	Script & Actions (intermixed for pacing)
1. Introduction & Navigation	0:00-1:00	8%	“Welcome to Open Coding Society built on GitHub Pages.” ACTION: Start at login page “GitHub serves as our Learning Management System for all student content.” ACTION: Login as Hop (student user) “Let me show you the navigation that organizes our entire learning experience.” ACTION: Navigate to CSSE → Sprint 4 → Week 13 “This is the OCS GameEngine Guide.” ACTION: Click “OCS GameEngine Guide” link “This module serves 9th-10th grade students in week 13 of their 24-week course.” ACTION: Show infoGraph with 3 topic cards visible “Let’s review the infoGraph and documents that guide the ‘Applying Object-Based Game Mechanics’ experience, designed to reduce cognitive load.”
2. Assessment Structure Preview	1:00-2:15	10%	“Before diving into the tools, let me show you the assessment structure students are working toward.” ACTION: Stay on main guide page, scroll to “Assessment Structure” callout “Students complete 3 Formative Assessments as individual progress checks, followed by 1 Summative Assessment integrating their team work.” ACTION: Point to bullet list showing FA1, FA2, FA3, Summative “Formative 1: Configure foundational objects—background, player, NPC, barrier.” ACTION: Scroll to FA1 section heading “Formative 2: Implement interactions and reactions.” ACTION: Scroll to FA2 section heading “Formative 3: Manage assets and file structure.” ACTION: Scroll to FA3 section heading “The Summative integrates all three into a team project with video demonstration and reflection.” ACTION: Scroll to Summative section, pause briefly “Now let’s see the documentation guides and gamebuilder tools that support this learning progression.”
3. GameEngine Briefing	2:15-3:15	7%	ACTION: Scroll back to top, click “GameEngine Briefing” infoGraph card “The first component is the GameEngine Briefing, which introduces core architecture and mechanics.” ACTION: Scroll through intro content “Students learn about the game loop, object lifecycle, sprite animations, and collision interactions.” ACTION: Point out sprite animation gif “Notice the key points: Game Objects, Game Loop, Properties and Updates, Interactions and Reactions.” ACTION: Highlight key points list “This provides the conceptual foundation before students begin authoring.” ACTION: Show systems thinking diagram “This demonstrates multimedia integration—animated gifs, images, and interactive diagrams reduce cognitive load by providing visual context.”
4. GameBuilder - Authoring View	3:15-4:45	12%	ACTION: Navigate back, click “GameBuilder Visual Interface” infoGraph card “Now we enter GameBuilder, the rapid authoring tool that reduces cognitive load.” ACTION: Show GameBuilder interface “This is where instructional design meets implementation—students configure game objects visually without writing syntax.” ACTION: Open file browser for `/images/gamebuilder/` “Let me demonstrate: I’ll select a background image from our asset library.” ACTION: Select background image, show preview “Now I’ll add a player sprite with animation frames.” ACTION: Add player sprite, configure animation settings “Next, I’ll configure an NPC with speed and behavior properties.” ACTION: Add NPC, adjust properties in UI “Finally, I’ll set up barrier objects.” ACTION: Add barrier objects “Notice how the interface provides immediate visual feedback—this is the authoring view, demonstrating our e-learning development tool.“ ACTION: Pan across configured game scene “The asset library provides multimedia resources students use throughout.”
5. GameBuilder - Code Generation	4:45-5:45	8%	“When students click ‘Generate Code,’ GameBuilder creates structured JavaScript.” ACTION: Click “Generate Code” button “This is the bridge between visual design and code implementation.” ACTION: Show generated `GameLevelCustom.js` file “The generated code shows proper object initialization and imports from our essentials library.” ACTION: Point out imports from essentials/ (Background, Player, NPC, Barrier) “Students can then test immediately using our local development environment.” ACTION: Show terminal, run `make dev` command “The make command rebuilds the site with their new game level.”
6. GameBuilder - Learner View	5:45-6:30	6%	ACTION: Show running game in browser “Here’s the learner outcome—the game running with sprite animations, collision detection, and interactive behaviors.” ACTION: Demonstrate player movement with arrow keys “Students see immediate results from their configuration work.” ACTION: Show NPC interactions and movement “This is the learner view: a functioning game that demonstrates object-based mechanics in action.” ACTION: Trigger collision with barrier “Notice the sprite animations in motion—multimedia demonstration of the visual-to-code-to-runtime pipeline.” ACTION: Point out sprite animation frames cycling “This pipeline keeps cognitive load manageable by providing immediate feedback.”
7. Formative Assessment Connection	6:30-7:15	6%	ACTION: Split screen: GameBuilder + Assessment guide side-by-side “GameBuilder directly supports our three Formative Assessments we previewed earlier.” ACTION: Point to FA1 section “Formative 1 requires configuring the foundational objects we just demonstrated—background, player, NPC, barrier.” ACTION: Point to FA2 section “Formative 2 adds interaction logic and reactions, which students implement using collision callbacks.” ACTION: Point to FA3 section “Formative 3 focuses on asset management and file structure in the repository.” ACTION: Show example GitHub Issue with screenshots “Students document their progress in GitHub Issues with screenshots showing their GameBuilder work and running games.” “This is how the authoring tool connects to assessment tracking—tools become evidence of learning.”
8. Logistics & Submission Guide	7:15-8:30	10%	ACTION: Navigate back, click “Logistics and Submission Guide” infoGraph card “The Logistics guide is the bridge from authoring to assessment workflow.” ACTION: Scroll to Team Repo setup section “Students use GitHub as the LMS and assessment tracking system—version control, team collaboration, and progress documentation all in one unified platform.” ACTION: Scroll to Kanban screenshot “The Kanban board provides team mission control. Notice how cards show task organization with clear assignments.” ACTION: Point to screenshot caption explaining stages “Your video should show similar organization.” ACTION: Scroll to Issue screenshot “This Issue demonstrates good documentation: clear description, progress updates with screenshots, and commit link references.” ACTION: Point to screenshot caption “Students’ Formative Issues should follow this pattern.” ACTION: Scroll to video evidence callout “Notice the video callout: students must capture GameBuilder screenshots, running game evidence, and commit links for their Summative video.” ACTION: Show VSCode Dev Setup section “This unified platform serves both student development and instructor assessment.”
9. Summative Assessment Details	8:30-9:30	9%	ACTION: Navigate back to main guide, scroll to Summative section “The Summative Assessment integrates all three Formative tasks into a team project.” ACTION: Read list of requirements “Students must: integrate individual levels into one game, demonstrate interactions in a video walkthrough, contribute best assets via Pull Request, write a 150-word reflection on applying object-based mechanics, and show complete GitHub documentation.” ACTION: Point to “This summative builds on…” callout “The connection is explicit: FA1 objects become team levels, FA2 interactions are shown in video, FA3 asset management contributes to the shared library.” ACTION: Scroll to Review Criteria “This capstone assessment demonstrates mastery while maintaining professional workflow practices.”
10. Conclusion & Research Goal	9:30-10:00	5%	ACTION: Return to infoGraph view showing all 3 cards “This module demonstrates design-based research on reducing cognitive overload through visual authoring tools.” “GameBuilder serves as the rapid development environment, GitHub provides the LMS infrastructure, and the three Formative assessments scaffold learning toward the Summative integration.” ACTION: Emphasize 3 cards (Briefing, GameBuilder, Logistics) “Students apply object-based programming concepts within a larger system while developing professional workflow practices.” ACTION: Final frame showing Assessment Structure callout “Thank you for reviewing this e-learning module.”

Key Compliance Checkpoints

✅ E-learning development tools demonstrated:

GameBuilder (rapid authoring tool) - Steps 4-6
GitHub (LMS/tracking system) - Steps 1, 8
VSCode (development environment) - Step 8

✅ Functional multimedia integration:

Background images - Step 4
Sprite animations (player, NPC) - Steps 4, 6
Animated gifs in briefing - Step 3
Screenshots for documentation - Step 8

✅ Three Formative Assessments:

FA1: Configure foundational objects - Step 2 (preview), Step 7 (connection)
FA2: Implement interactions - Step 2 (preview), Step 7 (connection)
FA3: Manage assets and files - Step 2 (preview), Step 7 (connection)

✅ Summative Assessment:

Team integration with video, reflection, PR - Step 2 (preview), Step 9 (details)

✅ Learner view + Authoring view:

Authoring: GameBuilder configuration UI - Step 4
Learner: Running game with interactions - Step 6

Pre-Recording Checklist

Speaking Tips

Pacing: Speak slightly slower than normal for clarity
Emphasis: Use phrases like “notice how,” “this demonstrates,” “the key here is”
Academic tone: Balance technical accuracy with accessibility
Tool names: Always use full names first mention (e.g., “GameBuilder, our rapid authoring tool”)
Requirements: Explicitly state when covering requirement areas (e.g., “This demonstrates the multimedia integration requirement”)

Remember: You’re demonstrating BOTH a student learning tool AND an academic research artifact. Show how the design reduces cognitive load while meeting all WGU assessment criteria.