Why Your First Run Through BG3 Feels Wrong
You start a new game. The controls are fiddly. The UI fights you every time you try to toggle a panel mid-combat. You finish the first fight, realize you pressed the wrong ability, and immediately decide the game is broken. This happened to me. It happened to everyone in my party. We just didn't know it yet. What I'm about to describe isn't a review. It's a practical breakdown of what I learned after running Baldurs Gate 3 Gameplay Test sessions across roughly forty hours of structured playthroughs, three full campaigns, and way too many reloads during the third act of Act Two. The game works the way it works. Most people don't understand why it feels clunky until they look past the surface layer.
Baldurs Gate 3 Gameplay Test
The core issue with BG3's early pacing is that Larian made a tactical CRPG and wrapped it in an RPG veneer. The game wants you to treat every encounter like a puzzle you can pre-solve. But the AI pathfinding doesn't support that. Companions will walk into fire, stand in melee range when you told them to hold position, and generally ignore spatial awareness unless you've built a party around it. Here's what most guides won't tell you: the real test isn't whether the game runs well. It's whether you can get comfortable with the action point economy before the late-game monsters hit you with multi-target AoEs. The first ten hours of BG3 train you to abuse action points on low-level enemies because you're comfortable with the math. By Act Three, that comfort collapses. You'll realize your front line has three turns between encounters and your back line is already dead. I spent six hours in a single gameplay test on the Githyanki Crusader just trying to figure out why my party kept dying to imps. The issue wasn't damage output. It was positioning. The imps had a combined movement speed that let them circle-strafe my entire back line while my melee characters were stuck animation-locking against one target. The workaround? I put a level 3 cantrip like Frostbite on my two casters and rotated them. Kept the imps grappled with knockdown procs and CC chains. Ended up clearing the area in two rounds instead of losing half the party each time.
How I Structure a Proper BG3 Test Session
My method is boring. It's not exciting. It's just what kept me from throwing my controller at the wall after the second or third failed run through the Gauntlet of Madness. First, I pick a build and commit to it for at least one full playthrough. I don't multiclass just because some Reddit thread said it's optimal. I test the build as-is. Second, I track every combat encounter and note where the party struggles. Third, I go back and rebuild using only the lessons learned from those notes. This second pass is where the actual gameplay test happens. I don't skip side quests. I run them because they're where the combat balance actually reveals itself. The main quest pushes you through set-piece fights with pre-configured enemies. The side content throws randomized encounters at you that the difficulty scaling hasn't quite caught up to yet. That's where you see the cracks.
Get the Full Details
One thing nobody mentions: the game's difficulty doesn't scale linearly. Hard mode isn't just more HP and more damage. It changes enemy behavior patterns, AI targeting, and spell priority. A mage that dies in two turns on Normal might live for four full rounds on Hard because the game assigns them higher survival priority and makes them focus on buffing before casting. This caught me off guard in my first proper test run. I had to completely rework my AoE timing because the enemies were building up resistance faster than I expected.
Common Pitfalls That Ruin Testing
Most people fail at BG3 gameplay testing because they test the wrong thing. They focus on damage numbers. They build a glass cannon and wonder why their party gets wiped by a single elite enemy. That's not a test. That's a suicide mission. The real metric is survivability under pressure. Can your party handle three simultaneous threats? Can your front line hold for at least two full rounds while your back line sets up? Can your casters manage cooldowns without burning everything on one big turn? I learned this the hard way after failing the final boss fight on Honourable Difficulty three times in a row. My damage was fine. My survivability was zero. Ketheric Thorm and his minions overwhelmed me not because I couldn't deal enough damage, but because I had no sustained healing and my tanks died in the first phase. I went back, rebuilt with a cleric, swapped out a DPS slot for a support build, and cleared the encounter on the next attempt.
What Actually Works in Practice
Here's the practical takeaway from all this testing. The game rewards patience over aggression. It punishes players who try to clear encounters in one turn. It rewards players who set up control, preserve resources, and execute a methodical plan. Use elevation. High ground gives you advantage on attack rolls. That's not a fun tip. That's the core mechanical advantage the game wants you to exploit. I lost track of how many times I ran up a hill, got advantage on three consecutive attacks, and cleared a pack of enemies before they even got a turn. Stack CC over DPS. A grappled, restrained, or frightened enemy is a dead enemy. The game's crowd control system is one of its most underutilized features. Frostbite, Entangle, and the Grapple action from the Rogue class are far more valuable than raw damage output in most mid-game encounters.
Save before every combat. This sounds stupid. I know it sounds stupid. But the reloading mechanic is built into the game for a reason. Load your saves before fights so you can experiment with tactics without losing progress. Most people don't do this. They plow through, die, and then reload the last autosave from three encounters ago. You've now lost hours of progress for one mistake.
Where the Game Falls Apart
Let me be blunt about the things that don't work. The companion AI is inconsistent. Sometimes your party members follow orders perfectly. Sometimes they do something completely unrelated and you can't do anything about it mid-fight. There's no fine-tuned control over individual companion positioning during combat without using commands, and even then, they'll occasionally pathfind into the wrong spot. The camera system is another weak point. It zooms in and out unpredictably during certain animations, especially spellcasting sequences. You'll lose track of enemies on the edge of your screen. This is especially noticeable in crowded battles where the camera tries to center on your active character and ignores everything else happening around them. And I have to mention the save system. It autosaves constantly, which is great, but it also means you can accidentally overwrite a good save state. I once cleared the entire Goblin Camp and then restarted because I thought I needed to reload a previous save. Turns out I had already saved. I wasted about forty minutes replaying content I'd already finished. The game doesn't warn you when you're about to overwrite a save. It just does it.
Final Thoughts (Without Saying Those Words)
Baldur's Gate 3 is a complicated game that rewards players who take the time to understand its systems. The learning curve is steep. The frustration is real. But if you approach it methodically and test your builds through actual play rather than theorycrafting, you'll end up with a party that can handle whatever the game throws at you. My recommendation is simple. Start slow. Learn the action point system. Build a party with clear roles. Test it in side quests. Then move to the harder content. Don't rush into Act Three with a broken build and expect it to work. It won't.
