Voltrons executive producers reveal the real reason why the fan favorite character came back so soon after hed departed.
Voltron: Legendary Defenderseason two ended on a major cliffhanger.
Zarkon seemed defeated and the Paladins raced back to the Castle Ship…. Only to find Shiro was gone.
He wasnt dead just… gone.
In the hiatus between seasons two and three fans speculated what happened to him.
Was he somehow fused with the Black Lion?
Was he really truly dead?
Did he somehow bond with Zarkons Quintessence?
How long would it take before Shiro was brought back?
How would the team deal with his absence?
The opening episodes of the season began to answer that last question.
Keith struggled with taking on the mantle of leader.
The team was in disarray.
They needed someone to pilot Black Lion.
Everyone tried but eventually Keith had to take on responsibility.
Lance moved into Red Lion and Allura into Blue Lion.
Then Shiro came back in episode five.
Why was he brought back so soon?
Even Allura, who was the brand new Paladin, had some of her fire stolen.
Why couldnt have Shiro come back later on, perhaps a season or two down the line?
Executive producer Joaquim Dos Santos has a fairly blunt answer.
We werent allowed to from the executives.
He had to come back.
Thats pretty much it.
We wanted him to be gone for a much longer period of time and we werent allowed to.
Co executive producer Lauren Montgomery adds, Shiros gotta sell toys.
Sometimes we have people we need to like.
But when it comes down to it sometimes we dont get out way.
Like Lauren said, theres a lot of moving parts to an IP this big.
So did they already have the outline of the season planned and it was vetoed?
Had they already written the episodes and had to change them at the last minute?
Its an organic system, things change along the way and you just have to be able to adapt.
Different people chime in.
Different departments chime in.
Theres a lot of moving parts.
Thats kinda how that works.
Read and download the fullDen of Geek Special Editionmagazine here!
