+

Cookies on the Business Insider India website

Business Insider India has updated its Privacy and Cookie policy. We use cookies to ensure that we give you the better experience on our website. If you continue without changing your settings, we\'ll assume that you are happy to receive all cookies on the Business Insider India website. However, you can change your cookie setting at any time by clicking on our Cookie Policy at any time. You can also see our Privacy Policy.

Close
HomeQuizzoneWhatsappShare Flash Reads
 

Aaron Rodgers blasted the 'Game of Thrones' finale just a week after appearing as an extra in the epic series

May 22, 2019, 04:05 IST

Advertisement
Twitter / Stephen Watson

Aaron Rodgers was not at all pleased with the final episode of "Game of Thrones."

The Green Bay Packers quarterback was a known fan of the show heading into the final season and even appeared in the penultimate episode of the show as an extra during the destruction of King's Landing - though there was much confusion over where he appeared in the episode.

Read more: Aaron Rodgers made a cameo on 'Game of Thrones,' and fans are wondering 'where's Waldo?'

But Rodgers was furious with the show's finale, a sentiment shared by many fans. Speaking with reporters on Tuesday afternoon, Rodgers ranted against the final episode of the series, pointing out a few major plot points with which he disagreed.

Advertisement

After clarifying that he was neither the man who caught fire nor the archer that many speculated him to be during the fall of King's Landing, Rodgers was asked if he enjoyed the finale.

"No," Rodgers said with disdain. "I love the show, and it was a great 10 years, but no."

You can watch Rodgers rant in full here, or read more about it below.

Rodgers especially took issue with how Bran Stark, or "Bran the Broken," wound up as the ruler of the Six Kingdoms.

"You come down to the end, and Tyrion says the person with the best story is Bran? Who by the way, said three episodes ago that he wasn't Bran Stark anymore?" Rodgers asked. "No. Jon had a better story. Dany had a better story. Arya had a better story. Sansa had a better story. Tyrion had a better story. Vary had a better story. Bronn - lot better story. Jaime better story. Cersei ... probably better stories. Any Baratheon, better story."

Advertisement

Read more: Isaac Hempstead Wright defends the 'Game of Thrones' finale and his character's arc: 'I am thrilled with the way the show ends'

Rodgers said that he believed Dany should have ended up on the throne, before again taking issue with Bran Stark's handling of the final season. Specifically, due to the nature of his powers, it could be argued that he was responsible for the majority of the conflicts that took place during the final three episodes of the season. 

"Bran the Three-Eyed Raven, who's all about the health of the realm, let's think about what he did," Rodgers said. "He basically wanted the throne the whole time? Because he's basically, the one who told the Starks, knowing that they would tell Tyron, knowing that Tyrion would talk to Varys, knowing they would scheme for Dany's death, knowing that would piss her off, which led her to be the Mad Queen."

"So he the entire time set this whole thing up?" Rodgers asked. "And he the whole time says 'Oh no I don't want to be king. But why did I travel all this way to be here?'"

"I love the show, but you know, the writers are also doing Star Wars," Rodgers concluded. "So I think they might have been a little busy this season."

Advertisement

Here's why Drogon destroyed the Iron Throne in the dramatic finale scene - and where he may have gone next

Isaac Hempstead Wright defends the 'Game of Thrones' finale and his character's arc: 'I am thrilled with the way the show ends'

68 details you might have missed on the final season of 'Game of Thrones'

Every important 'Game of Thrones' death, ranked from least to most tragic

NOW WATCH: This stunning visualization breaks down all the ingredients in your favorite processed foods

You are subscribed to notifications!
Looks like you've blocked notifications!
Next Article