So You Want to Record Funny Moments Without Spoiling Yourself
Blind playthroughs are one of those things that sound simple until you actually try to pull them off and end up with forty minutes of someone hitting a wall for three straight minutes. I've done enough of these to know where they fall apart before the upload even hits YouTube. The basic approach is straightforward. You play a game you haven't beaten—or ideally, one you haven't played much at all—without looking up strategies, endings, or anything that would ruin your reactions. The funny moments come from genuine confusion, unexpected physics glitches, or the kind of stupid mistakes that only happen when you don't know what's supposed to happen next. That's the core of it. Here's the part most people skip: recording blind takes more prep than a standard walkthrough video because you can't rewind and plan your commentary. You need your audio chain solid before you press record, not after you've already missed three good moments because your mic was clipping or your game audio drowned out your voice.
I use OBS with a sidechain compression rule set so my voice dips the game audio automatically. Game sound in Man 2 can spike pretty hard during combat sequences, and if you're not ducking it, your viewers are going to turn their volume down and your punchlines get lost. Set your compression threshold around -18dB and a ratio of about 3:1. That's enough to keep things even without making your voice sound like it's coming through a telephone. For actual gameplay, the trick with Man 2 is that the humor comes from player error and environmental chaos, not scripted events. There are no guaranteed funny moments baked into the code. You're mining randomness. My go-to strategy is letting the game run for the first twenty minutes without touching the camera or doing much of anything. Just walk around. See what breaks. The physics in that game have a particular softness to them that makes everything look ridiculous when you're not playing with intent. A character stumbling over nothing is funnier than any cutscene. One thing I learned the hard way: don't play on the hardest difficulty if you're going blind for comedy. I tried it once and spent an hour dead because I kept walking into things I didn't understand. The humor evaporates when you're just suffering. Easy mode keeps the momentum going and lets the accidental comedy surface naturally.
What Actually Makes These Videos Work
The recordings that get views aren't the ones where the game is perfectly hilarious. They're the ones where the creator's reaction feels real. People can spot a forced laugh from a mile away. The best moments are usually when you genuinely have no idea what just happened and your confusion becomes the content. When editing, keep your clips tight. A funny moment is dead after twelve seconds unless something builds on it. I usually cut anything over fifteen seconds unless the situation evolves. Man 2 has some great engine quirks—characters sliding into walls, objects phasing through floors, that kind of thing. Those are your gold. Trim the walking, trim the menu diving, trim the parts where you're figuring out which button does what. A common mistake I see people make is trying to narrate everything as it happens. Don't do that. Your job during the recording is to play. Your job during editing is to find the moments and add context if needed. Recording live commentary while also being genuinely surprised is exhausting and usually sounds worse than post-record commentary. Save your breath.
Get the Full Details
If you're looking for the game itself, Man 2 is available on Steam. It's an indie physics-based title, and I'd recommend grabbing it on sale if the full price gives you pause. This style of content doesn't require the most expensive hardware either. A mid-range GPU from a couple generations back handles it fine. The bottleneck is usually your storage speed, not your graphics card. Make sure your capture drive is an SSD, or you'll be watching your framerates drop during longer sessions. The other realistic problem I ran into is managing file sizes. A single two-hour blind run can easily eat fifty to eighty gigabytes depending on your recording settings. I ended up just recording shorter sessions—forty to fifty minutes max—and compiling from multiple days. It kept the files manageable and actually helped with the content because each session had its own little arc instead of one long blur.
When This Approach Falls Apart
Not every game works for this. If a game is purely narrative-driven with no physical comedy or emergent moments, a blind playthrough will just be a person reading dialogue out loud. That's not funny. It's also not particularly engaging to watch. This method thrives on systems-based games where player input creates unpredictable outcomes. Also, don't expect this to be fast. A polished five-minute clip from a blind run can take six to eight hours of recording to produce. You're essentially paying with time instead of pre-production planning. Factor that in before you commit to a full game run. If you're just starting out, try a short indie title first before tackling something long. Build the recording workflow, nail your audio levels, and get comfortable with the editing rhythm. Then scale up. Most people skip that and burn out on their tenth hour of footage because they didn't have a system yet.
