I liked Star Wars Jedi: Survivor a lot. I’ve written about how it improved on Fallen Order in all the right ways, especially in its character development, and the major plot twist left my jaw on the floor. But there was one particular part of the game that felt vastly different by design, and I didn’t like it at all. Spoilers ahead, obviously.

After finally getting a salvageable compass that can lead your group to Tanalorr, everybody is thrilled. We get a nice scene where the team celebrates together, but things go sour the next day when it’s revealed that Bode is a traitor. He shoots Master Cordova, steals the compass, and escapes, with a distraught Cal giving chase. Bode reveals he is a former Jedi and knocks Cal out. You’re prompted to respawn, and when you do, you begin playing as Cere Junda, defending the Hidden Path’s archives from the Empire, who were called there by Bode.

Related: Star Wars Jedi: Survivor Doesn’t Trust You With Its Biggest Battles

That’s all fine. I, like many others, gasped when it was revealed I’d be playing as Cere, and I was excited to see what abilities her character would have. But the gameplay of this section was intolerably boring. The combat is mostly repelling waves of Stormtroopers, but it has almost no challenge - Cere is incredibly powerful. In fact, she’s overpowered. She takes out giant crowds with no problem, and while this could have played into the Jedi power fantasy, I found myself feeling nothing. Every combat section was far too long, and I felt like I was just waiting for it to be over so I could move to the next thing, which would hopefully be more interesting.

Cere Junda stands in her rebuilt Jedi archives on Jedha in Star Wars Jedi: Survivor.

But the next thing wasn’t more interesting. You use your force powers to make some explosive balls roll and bounce off a cliff edge, making some walkers explode, but it is neither intuitive nor difficult enough to make it exciting. You just force pull a ball and watch it blow up your enemies. Then there’s some rudimentary platforming and you’re back to fighting waves of Stormtroopers, in very easy combat, for, again, way too long. Eventually you destroy their access point and go back to the archives to retrieve the contact codes for the Hidden Path, where you encounter your boss fight - Darth Vader.

I didn’t really have issues with this boss fight, though Editor-In-Chief Stacey Henley highlighted that the game constantly interrupts itself here with cutscenes, making the encounter far less engrossing. That didn’t bother me as much, but I was severely underwhelmed by the whole thing. The poor pacing of the sections before had taken me out of the game that I had previously been completely sucked into, so that by the time I got to Vader, I was ready for the whole thing to be over. I just wanted to go back to Cal Kestis, which is a testament to how enjoyable the main storyline is, but also a reflection of this particular segment’s flaws. Fighting Darth Vader and almost winning should have made me feel like a god, but instead I was bored.

Vader throwing debris at Cere in Star Wars Jedi: Survivor

It’s a shame, because the emotional beats were on the money in this scene. I was entirely taken by Cal’s grief as he chased Bode, screaming his name as he followed him. When Bode used the force for the first time, I gasped. Darth Vader’s reveal should have given me the same reaction, but the game got in its own way by padding the sequence unnecessarily. It’s a small flaw in the grand scheme of the game, but it still disappointed me.

Next: PlayStation Exclusives Just Don't Excite Me Anymore