Breaking Down Gwendolyn vs The Band of Barren Hearts
I've spent more time than I care to admit grinding through this particular sequence in what most people just call Gwendolyn Vs The Band Of Barren Hearts Monster 1, and the core issue most people run into is that nobody really talks about the timing windows on the second phase transition. The setup is straightforward enough on paper. You control Gwendolyn in a top-down survival encounter against waves of enemies led by the main monster from The Band of Barren Hearts. The catch is that the monster has multiple phases, and the damage scaling between them isn't consistent unless you know what triggers each transition. The first phase is relatively forgiving. The monster telegraphs its attacks with a brief wind-up animation. You have roughly 0.8 seconds between when the sprite starts glowing and when the attack connects. That window is enough to dodge if you're paying attention, but it's also enough that a lot of people walk away thinking the fight is easy and then get wrecked when phase two hits.
Phase two happens when the monster's health drops below 60 percent. This is where the common problem lies. The enemy stops telegraphing its primary attacks and starts mixing in a fast dash strike that covers significantly more ground than the earlier move set. I wasted about three hours on this phase before I realized the dash strike always comes after a three-second lull following any failed attack. If you respect that pause instead of pressing forward immediately after you land a hit, you can bait the dash and punish it. Works every time.
Build recommendations that actually matter
Most guides online push you toward maxing out raw damage early. That's not wrong, but it's incomplete. Gwendolyn's speed stat scales her dodge animation recovery, which means stacking even a moderate amount of movement speed lets you close the gap after dodging rather than waiting for a recovery frame that feels too long at higher difficulty tiers. The sweet spot I ended up settling on was roughly a 50-30-20 split between damage, speed, and endurance. Going all-in on any single stat creates a bottleneck. Early game I tried max speed with minimal defense and got caught one-shot by a phase three attack I didn't even see coming. The endurance buffer kept me alive for the mistakes you're going to make regardless of how much practice you've had.
Get the Full Details
The edge case nobody mentions
There's a specific scenario where this fight becomes nearly impossible if you don't adjust your approach. When the monster spawns additional smaller enemies during phase three, most players try to kite everything around the arena. That works fine until you hit the later rounds where the spawn rate increases and the arena boundaries start cutting off your escape routes. The workaround is simpler than it sounds. Stop running. Position yourself near a corner with one flank covered and let the smaller enemies cluster. Gwendolyn's area attack hits hard enough to clear them in one or two swings, and the main monster's pathfinding gets slightly sluggish when navigating tight spaces between units. I dropped my run time from about twelve minutes to under five by making this change, and I actually stopped dying to the corner trap that took me eight tries to figure out.
Where this breaks down
The fight has a hard difficulty spike at the third phase transition that no amount of build optimization fully smooths over. The attack patterns become genuinely random within a set of predefined options, which means muscle memory stops working reliably. If you've been playing on easier settings, the jump to the final phase can feel unfair because the game doesn't warn you that the rules change at that point. There's also a known issue with frame rate drops on older hardware during heavy spawn sequences. The game wasn't optimized well for concurrent entity rendering, and you'll notice input lag that makes dodging considerably harder. Running the game at a locked 30 FPS instead of letting it scale to your monitor's refresh rate actually reduces that input delay in practice, which is the opposite of what most people would assume. If you find yourself stuck, taking a break and coming back with a fresh perspective usually helps more than grinding the same pattern repeatedly. This fight rewards pattern recognition, not repetition, and that distinction matters more than most players realize.
Where to get it
You can find this content on the standard distribution platforms. It's available through the usual indie game storefronts and the dedicated community hub. No special setup or patched version needed beyond the latest update, which fixed the spawn timing bug that was causing unnecessary deaths in phase two a while back. Grab it, read through the controls once, and go in knowing that the first few attempts are supposed to be rough. The fight isn't designed to be won on the first try, and anyone who tells you otherwise probably hasn't actually played it past the opening wave.
