Of Legends Gameplay Highlights Blind Playthrough

How to Actually Capture Highlights During a Blind Run Without Losing Your Mind

Blind playthroughs are the only way to properly document first-impression content. You don't know what's coming, so your reactions are genuine. That's what viewers want. The problem is most people fail at the recording side because they try to pre-plan clips that don't exist yet. I record everything continuously with OBS. Set it to 1080p at 60fps with a bitrate around 12000 kbps. That produces files large enough that quality stays solid but not so massive that your drive fills up after three hours. I use an NVMe SSD specifically for temporary recordings and offload after each session. A standard 50-minute run comes out to roughly 6-8 GB at those settings. The mistake everyone makes is relying on a hotkey-based instant replay buffer. It sounds logical. When something good happens, you press a key and the last five minutes get saved. In practice, the buffer size is almost always set too low. Five minutes isn't enough when a boss reveal in Of Legends unfolds slowly over a whole cinematic sequence. I ended up with fragmented clips missing the actual payoff moments because I didn't leave enough buffer headroom. I switched to recording everything raw and then trimming afterward. It's slower upfront but dramatically faster in post because you're not hunting through dozens of partial clips.

Here's the workflow I actually use. Record the entire blind run without stopping. Don't pause, don't cut, don't self-edit while playing. Let the game play. After the session ends, open the footage in a video editor. DaVinci Resolve works fine for this. Use its source monitor to scan through and mark in and out points for every highlight. The keyboard shortcuts for marking are what keep this tolerable. In and out takes about half a second each once you have muscle memory. From a two-hour recording, I can pull out fifteen to twenty highlight segments in roughly twenty minutes. That includes creating basic titles and simple cuts. One thing that catches people off guard: make sure your in-game UI is clean before you start recording. Turn off minimap details, disable damage numbers if they clutter the frame, and skip any tutorial popups that can appear. A blind playthrough naturally triggers tutorials, and those popups ruin highlight pacing. I learned this the hard way during a mid-boss encounter where a system prompt took up half the screen right during the most exciting phase of the fight. I had to crop and reframe that entire segment in post, which took longer than the highlight itself was worth. Audio mixing matters more than people expect. Game audio and mic commentary need separate tracks. OBS lets you set that up in Advanced Audio Properties. You want game audio on Track 1 and your mic on Track 2 so you can balance them independently in editing. There's nothing worse than watching a highlight where your voice is either completely inaudible or so loud it drowns out the game sounds. I aim for game audio at zero decibels and my mic around minus twelve decibels. Adjust from there depending on how much I talk during a particular clip.

Export settings for the highlights themselves are different from your recording settings. Drop the bitrate to 8000 kbps for the final export. Viewers aren't sitting there analyzing individual frames. 8000 kbps at 1080p60 looks nearly identical to 12000 kbps on YouTube's compression pipeline, but your final file will be about thirty percent smaller. That matters when you're uploading and someone's waiting for a download. There are real limitations to this approach. Continuous recording burns through storage fast. If you're doing multiple blind runs across different game systems or modes, you'll need to manage your disk space actively. I typically work in three-hour blocks and clear old footage after each block. The other issue is that a blind playthrough by definition doesn't let you re-grind specific moments. If you miss an interesting interaction because you weren't looking in the right direction, it's gone. You can't go back. That's the tradeoff for authenticity. Some viewers will complain about missing certain encounters. You can't fix that without sacrificing the blind aspect entirely. If your hardware can't handle real-time recording and editing comfortably, the process slows down considerably. You'd be looking at maybe forty-five minutes of post time for a two-hour run instead of twenty. Factor that into your schedule. This method works if you have a decent GPU and at least sixteen gigabytes of RAM. Anything less and Resolve will struggle with playback scrubbing through long timelines.

The simplest advice is probably the most ignored one: label your raw recording files with dates and session numbers immediately after you finish. "RAW_Session03_20250614.mp4" tells you exactly what you're looking at. "Recording1_Final_v2_Real.mp4" does not. I spent an entire evening trying to find a specific clip from a three-session marathon because I'd named everything generically. Twenty minutes wasted. Don't make that mistake.