Star Wars: What Happened To Lobot After The Empire Strikes Back?
"Star Wars: Episode V – The Empire Strikes Back" introduces numerous heroes, villains, and those in-between to "Star Wars" fans. One of the most notable to make their franchise debut in the feature is the suave Baron Administrator of Bespin's Cloud City, Lando Calrissian (Billy Dee Williams), who allows Han Solo (Harrison Ford) and his allies to seek refuge from the Empire. Flanking him are numerous Bespin guards and a stoic cyborg named Lobot (John Hollis) — one of Lando's longtime associates who uses his cybernetic attachments to carry out various tasks around Cloud City.
Lobot is a key player in Lando's attempt to rescue his friends from the Empire, leading Bespin guards in an effort to evacuate Cloud City and fend off the arriving Imperial stormtroopers. Unfortunately, they're only somewhat successful, with Lando and his friends escaping while Lobot and his companions are captured by the Empire. The regime takes over Bespin, and Lobot is plugged into Cloud City's central processing core to do the Empire's bidding. Thankfully, Lando returns to rescue his old friend and brings him along as part of the Rebel Alliance. In addition to helping out with several Rebel missions, Lobot also leads the charge in removing the Empire's presence from Bespin.
Unsurprisingly, Lobot's post-"Empire Strikes Back" canon story differs greatly from the one many know from the "Star Wars" Legends continuity.
Lobot gets plenty of time to shine in the Star Wars Legends continuity
Like so many underdeveloped original "Star Wars" trilogy minor characters, Lobot gets plenty to do in the non-canon "Star Wars" Legends continuity. In the wake of the Empire's initial occupation of Cloud City, he stays behind and serves under the Imperial Hugo Treece, though he doesn't hold this job long. Ugnaughts overtake Cloud City and damage Lobot's motivational programming capsule, which Lando Calrissian has to fix when he returns to his old home. With that, Lobot joins Lando and his Rebel friends in battling back against the Empire and temporarily liberating Bespin.
He later heads to Tatooine to hunt down the droid EV-9D9 (Mark Hamill), who previously attempted to destroy Cloud City, but Lobot fails to capture him. Following this escapade, Lobot returns to Cloud City, serving under Zorba the Hutt and maintaining his duties once the Empire retakes the planet under Grand Admiral Thrawn's (Lars Mikkelsen) command. Once the Empire is again removed from Bespin, he eventually becomes the Baron Administrator of Cloud City, continues to help Lando and the New Republic on various missions, and witnesses the fabled Yuuzhan Vong War.
Despite being a side character with no dialogue and little to do narratively, Lobot has gotten a lot of mileage throughout the canon and non-canon "Star Wars" universes.