This document discusses how game developers can use data collection tools to improve their games. It provides examples of how data collection can help with troubleshooting design problems, performance testing, detecting usage patterns, and adjusting difficulty levels. The document also outlines the key elements of rational game design, which uses quantifiable data to balance challenge and fun. It recommends collecting a variety of usage data, looking for patterns, modifying game elements, and repeating the process in an ongoing feedback loop to craft the ideal player experience. Finally, it promotes the tools on id.net for tracking user registrations, engagement, and implementing achievements/leaderboards to further incentivize player participation.

1. id.net for Game
Developers
TOOLS TO ENGINEER FUN AND INCREASE CONVERSIONS

2. Why Collect Data in a Game?
o Troubleshooting design problems
o Detecting pattern changes
o Performance testing
o A/B testing design changes
o Understanding users
o Learning how to best sell products
o Adjusting difficultly to boost fun

3. Case Study: Troubleshooting
18% Player loss from preload time to game play

4. Case Study: Performance Testing
2% Performance gain in a 30 day period

5. Case Study: Detecting patterns
A clear pattern showing increased registration ratio

6. Case Study: Increasing Fun Levels
Increase in user retention at the
30 minute mark by 1% over a
10 day span

7. Case Study: Difficultly Adjustments

8. Case Study: Map Deaths

9. Overview of Rational Game Design
Rational development is a way of objectively
creating an experience using quantifiable data.
The data determines the precarious balance
between rage and boredom. To achieve this,
elements are manipulated to perfect the player
experience.

10. Number of Elements vs Difficultly

11. Game Elements
• Dynamics (big picture)
• Constraints
• Narrative
• Progression
• Mechanics (drive action)
• Movements
• Rewards
• Competition
• Components
• Achievements
• High scores
• Quests
• Avatars

12. The Ultimate Goal of Rational Design
Crafting the ideal
experience

13. Implementing Rational Design with
Feedback Loops
1. Measure actions by collecting data
2. Search for evidence by find patterns in the data
3. Locate the elements that can be modified to change the action
4. Measure the results
5. Rinse and Repeat

14. Tools Available
Track.id.net
Registrations vs plays
Game comparison (admins)
Unique players and Engagement
Browser distribution
OS distribution
Custom events
id.net features
Achievements
High scores
Avatars
Points
Game screenshots
External tools
Google Analytics
Loggly
Datacracker
Excel or Google Docs

15. Tips for Collecting Data
• Schedule a regular time to adjust tracking code
• Use multiple sources where possible
• Discuss the results with someone
• Find a consistent time or place to log data in game
• Plan enough time to measure patterns and results
• Have data collection in and tested before QA

16. Reaching Goals
• Collect as much data as useful
• Look for patterns
• Modify elements
• Measure results and repeat
• Use id.net social features to reward players
and incentivize ecosystem growth
• Achievements
• high scores
• avatars
• point awards
• game screenshots
• profile views, forum views
• Implement elements strategically to drive actions
• Bonuses and gifts
• Items, unlockables
• quests, challenges, competition

17. What are your questions?
Ideas, comments, feedback