FANDOM


Rook
Gallery | Relationship | Quotes
Ep003 Rook
Name
Japanese ルーク
Rōmaji Rūku
Personal Information
Gender Male
Characteristics
Duel Monster statistics
Classification
Affiliation SOL Technology
Partner(s) Bishop
King
Knight
Pawn
Queen
Debut
Anime Episode 1
Voice
Japanese Koichi Makishima

Rook (ルーク, Rūku) is a character appearing in the Yu-Gi-Oh! VRAINS anime. He is a higher-up at SOL Technology who communicates via a hologram of a white rook chess piece.[1]

History Edit

Ep003 Akira, Bishop, Knight and Rook

Rook discusses the Duel between Playmarker and the knight of Hanoi with Akira, Knight and Bishop.

Rook was briefly seen during the first conversation between Bishop and Akira Zaizen.[2] A few days later, he, Bishop, Knight and Akira discussed about the incident caused by the duel between Playmarker and Knight of Hanoi. Rook proposed to close down Link VRAINS and to perform some maintenance. Knight added that there were some reckless individuals who appeared and it might result in injuries. Akira said that he didn't think it would be a good idea to shup down Link VRAINS for their company didn't decrease in profits and the Data Storm was confirmation that Cyberse was safe. He added that Ignis was captured by a hacker named "Playmarker". Knight asked Akira about Playmarker's identity, Akira answered that they devoted all their ressource into investgating it. Rook reminded Akira that this was his job as the head of Security Department. Akira said that if they shutdown Links VRAINS and the battle between Playmarker and the knight of Hanoi moved elsewhere, they will be lost the Cyberse world forever and suggested to restrict Link VRAINS and to make a battlefield for Playmarker and The Knights of Hanoi in order to capture Playmarker inside of it. Bishop agreed but warned that they won't accept failure.[3]

ReferencesEdit

Navigation Edit

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.