A player battling a droid inStar Wars Jedi: Survivorwas thrown for a loop when the enemy AI seemingly gave up mid-fight. WhileStar Wars Jedi: Survivorhas received praise for its Metroidvania exploration, thrilling combat, and captivating story, a sizable chunk of the player base has experienced debilitating glitches and game crashes that have sullied the experience. Developer Respawn has released a series of update patches to fix the game’s numerous issues.

Commando droids, inStar Warslore, are not the run-of-the-mill cannon fodder droids that can be seen throughout the prequel trilogy of films or animated shows likeClone WarsandRebels. They’re a deadlier batch of autonomous soldiers that have been known to give Republic clone troopers and even Jedi a fair amount of trouble on the battlefield. They’re faster and much nimbler than the average tin can holding a blaster rifle. Like most droids in theStar Warsuniverse,Star Wars Jedi: Survivor’s droids can be troublesome.

RELATED:Star Wars Jedi: Survivor Player Notices Adorable BD-1 Detail

Despite their reputation, a Reddit user by the name of drumeatsleep encountered a commando droid inSurvivorthat, either by way of glitch or simply hilarious happenstance, immediately gave up once it realized what it was up against. The clip shared by drumeatsleep picks up in the heat of battle, as the droid scores a clean strike on Cal Kestis. Cal decisively blocks a follow-up attack before backtracking to regroup. Figuring they needed to tilt the scales in their favor, drumeatsleep powered on the opposing end to turn their lightsaberinto a double-bladed lightsaber. What happens next is pure unintentional video game comedy.

One look at the double-bladed lightsaber was enough to make the usually fearsome commando droid put away its blaster and casually walk away as if nothing had happened. Perhaps the droid realized it wasn’t getting paid enough to deal with double-bladed lightsabers. Or, more realistically, one of theglitches plaguingSurvivorsince its releasecaused the droid to walk away from an intense fight, leaving drumeatsleep wondering what just happened. It’s also possible Cal moved too far away from the droid and that triggered the end of the battle.

Players have been reporting technical problems across all platformssince the release ofStar Wars Jedi: Survivor, from major crashes to frame rate issues. A droid giving up a fight mid-battle is on the lower end of bugs a player can encounter, and certainly one of the more humorous. But it does act as a testament, however small, to the fact that Respawn still has some work left ahead of them.

Star Wars Jedi: Survivoris available now on PC, PS5, and Xbox Series X/S.

MORE:Star Wars Jedi: Survivor May Subtly Hint at a Major Connection to the Obi-Wan Kenobi Show