Using Open Game Data to Understand Game-Based Learning
summary
Field Day publishes Headlines and High Water telemetry to the Open Game Data Project and uses Jupyter notebooks to analyze thousands of plays per week. Logs show most classroom sessions last ~30 minutes while finishers take >1 hour (≈3 sessions), many players drop after level one, and failures cluster around time gating and low-attribute locks. Telemetry exposes balance issues (weak research stat uptake, endurance-heavy finishers), usable snippet quality flags, and concrete fixes — more gating tweaks and UI changes reduce soft‑locks and improve progression.
AI-written summary · about
chapters (9)
- 0:00Introduction to session
- 5:26About Open Game Data
- 14:37Game demo: Headlines and High Water
- 32:53Design goals and data analysis
- 59:47Player behavior and game balance
- 1:10:28Player categorization and clustering
- 1:21:45Assessment and learning outcomes
- 1:34:00Player engagement and UX
- 1:58:37Wrap-up and next steps
related talks
51mOptimising Games for a Complex World
06mUnderstanding Player Patterns by Combining Knowledge-Based Data Abstraction with Interactive ...
53mBalancing gameplay of aRPG using player behavioral patterns
52mOptimising your game AFTER it ships
39mBehind the Game: Strategies for Building the Tech That Powers Today’s Top Titles.
21mIncreasing retention with live game services
24mThe Data Driven Advantage: Optimizing VR Games with Analytics
52mLet's Talk About LiveOps