Skip to content

Playtest Recorder & Tagger

Module: Design · Category: LevelDesign · Tool ID: PlaytestRecorderTagger

Records level-design observations as location-anchored event tags during PIE sessions, then provides a review timeline for designer iteration. Persists sessions to JSON on disk. Path-records player position/rotation during PIE. Integrates with UE’s Replay system for full playback. Heatmap visualization for event density.

Screenshot 01 — Hero shot — Tool open during a PIE session with multiple events tagged, viewport showing event markers.


  • Designer-led playtests — tagging combat / pacing / navigation / bug / polish observations as they happen
  • Internal QA pass — recording where players consistently get stuck
  • Replay analysis — recording a playtest and reviewing where to improve
  • Heatmapping event density across a level
  • Don’t expect this for analytics — it’s an editor-time designer tool, not telemetry
  • Don’t use this for video recording — UE’s Movie Render Queue handles that

  1. Open the EQLabs Hub and search for Playtest (or browse to Design → LevelDesign)
  2. Click the tool card
  3. Create a new session (or load an existing one)
  4. Start PIE — tag events as they happen

ActionWhat it does
Session Name inputName for the new session
Create SessionCreates and activates a new session
Sessions listPer-session row: name, map name, start time, duration, event count
Load SessionActivates the selected session
Delete SessionRemoves the session file
FieldWhat it does
Category pickerCombat / Pacing / Navigation / Bug / Polish / Custom
Severity pickerInfo / Warning / Critical
Note inputFree-text observation
Capture Player LocationReads PIE player’s current position
Manual Location XYZManually enter location
Add EventLogs the event with location + category + severity + note
SectionWhat it does
Filter CategoryShow only events of one category
Filter SeverityShow only events of one severity
Events listPer-event row: timestamp, category, severity, note, location

Single-click an event to focus the editor camera at the event location.

ActionWhat it does
Toggle RecordingStarts/stops capturing player position + rotation at intervals
Capture IntervalSample rate (default 0.25s)
Stored as JSONSerialized to disk per session
ActionWhat it does
Start Recording ReplayTriggers UE’s full demo recording
Saved Replays listBrowse, play, delete saved replays
Replay View ModeFree Camera / Follow Player (chosen at playback)
Play Saved ReplayPlays back via UE’s PlayReplay system

Visualizes event density in the editor viewport — colored hot spots based on event clustering.

Screenshot 02 — Event review — Session loaded with 30+ events, filter active showing only Critical severity, viewport showing focus camera at one event.


  1. Click Create Session, give it a name
  2. Optionally toggle Path Recording to capture player movement
  3. Optionally Start Recording Replay for full UE demo
  4. Start PIE
  5. As you play, switch to the editor and tag events: pick category + severity, type a note, click Capture Player Location, click Add Event
  6. Stop PIE — session auto-saves
  1. Load the session from the Session Manager
  2. Switch to Event Review
  3. Filter by category / severity
  4. Click events to focus the viewport at their location
  5. Optionally enable Heatmap Overlay to see event density
  6. Optionally Play Saved Replay to re-watch the session

Export CSV writes the events list as plain text for sharing with the team.


Sessions persist to [Project]/Saved/EQLabs/Playtest/sessions/<sessionname>.json. Replays use UE’s standard demo path.


  • JSON session files — events + path captures
  • UE replay files — when Replay recording is enabled
  • CSV export — events as plain text
  • In-viewport heatmap — toggle visualization

  • Event location must be valid — Capture Player Location requires PIE running; otherwise use Manual Location
  • Replay playback supports two view modes — Free Camera (default UE) and Follow Player (auto-set view target on first non-spectator pawn)
  • Heatmap density is logarithmic — small clusters show faintly, hot spots saturate
  • Sessions accumulate — clean up old session files manually if storage matters

  • Project Doctor Suite (Tech module) — runtime health audit complementary to designer events

Report an issue with this tool

Opens our feedback form in a new tab with the tool name pre-filled.