Taylor Cadwallader
Input Replay Analyzer
Playtesting & Debugging Tool Built in C# WinForms
C# • WinForms • JSON • Tool Development • Input Systems • QA / Playtesting
About the Tool
Problem
Playtesting often produces large amounts of raw input data, but it can be difficult to analyze what the player actually did during a session.
​
Solution
Input Replay Analyzer is a standalone debugging tool that loads recorded input logs, visualizes them on a timeline, and allows developers to replay player input sessions exactly as they occurred.
​
Audience
-
QA testers
-
Designers
-
User researchers
Project Details
Goal: Create a tool for analyzing and replaying player input logs from playtests.
Role: Tool Designer and Developer
Tech: C#, WinForms, JSON
Team Size: Solo
Duration:​ 4 weeks
Year: 2025
Problem the Tool Solves
The Problem
When debugging playtests, designers often rely on:
-
written notes
-
memory
-
incomplete logs
-
Reproducing player behavior can be difficult when the exact sequence of inputs is unknown.
​
Design Goal
Create a tool that allows developers to:
-
inspect player input behavior
-
isolate specific moments in a session
-
reproduce bugs reliably through input replay.
Core Features
Input Log Timeline
The tool loads recorded input logs and displays them on a structured timeline, allowing developers to quickly inspect player actions during a playtest session.
​
Input Replay
A recorded session can be replayed locally using the original timestamps.
This allows developers to reproduce player behavior exactly as it occurred.
​
Useful for:
-
bug reproduction
-
usability debugging
-
behavior analysis
​
Log Filtering and Trimming
Inputs can be filtered or trimmed by:
-
input type
-
time range
This allows developers to isolate specific moments in a session.
​
Exporting Cleaned Logs
Logs can be exported after trimming so specific gameplay moments can be shared with developers.
​
Input Profile System
To support different games, the tool includes a profile system.
​
Profiles define input mappings and are stored as JSON files, allowing the tool to adapt to different control schemes.
​
Focus-Based Input Recording
The tool includes an executable focus check so inputs are only recorded while the target application is active.
Benefits:
-
prevents unrelated input capture
-
improves data accuracy
-
protects user privacy
Development Approach
Why WinForms
The tool was intentionally built outside a game engine to explore standalone tool development and experiment with building debugging utilities using C# and WinForms.
​
Technical Focus
The project involved:
-
input handling
-
log parsing
-
timestamp synchronization
-
JSON-based configuration
-
building UI-driven debugging tools.
Example Workflow
Example Playtest Workflow
-
Assign a game executable
-
Record player input during a playtest
-
Load the recorded log into the tool
-
Inspect the timeline
-
Replay the session to reproduce bugs
Outcome
-
Fully functional input visualization and replay tool
-
Successfully loads and replays playtest input logs
-
Supports multiple input profiles through JSON configuration
Lessons Learned
-
Building tools outside a game engine
-
Input handling and serialization
-
Designing debugging utilities for designers
-
Importance of tools for playtesting iteration