FANDOM


Shoichi Kusanagi (くさなぎ しょういち, Kusanagi Shōichi) is a character appearing in the Yu-Gi-Oh! VRAINS anime. Operating out of a food truck called Café Nagi, which doubles as his and Yusaku's base of operations, Shoichi is an ally of Yusaku Fujiki in his fight against the Knights of Hanoi, with integral knowledge of the LINK VRAINS.

Design

Personality

Shoichi is a rather friendly individual. He's shown to be sympathetic towards Yusaku and hopes he can one day enjoy Dueling again. He also regrets dragging him into the fight against the Knights of Hanoi.

Unlike Yusaku, Shoichi doesn't seem to actively show hatred towards Hanoi.

Abilities

Being the owner of a food truck, Shoichi is a capable cook; he was seen cooking hotdogs.

Like Yusaku, he's a talented hacker. He was able to get information about SOL Technology's activities and helped Yusaku capture Ignis in the latter's Duel Disk. He was also able to figure out that Aoi Zaizen is "Blue Angel".

Biography

History

Shoichi's younger brother was kidnapped by the Knights of Hanoi in the past. At some point, Shoichi and Yusaku began fighting Hanoi.[1]

Yu-Gi-Oh! VRAINS

Shoichi and Yusaku discussed SOL Technology and Hanoi's recent movements. Shoichi told Yusaku about the Data Storm and that it could help Yusaku enjoy Dueling again. He also mentioned SOL was looking for an AI on the run and that they were planning a full scan of LINK VRAINS to find it. Hearing this, Yusaku came up with a plan to capture the AI and use it as a trump card against Hanoi and closed Café Nagi, despite Shoichi protesting that he was expecting customers that night. The two hackers managed to capture Ignis into Yusaku's Duel Disk during an attack from the Knights of Hanoi.[1] Shoichi was surprised when a Data Storm occurred when "Playmaker" challenged a knight. He was worried when Yusaku was sucked into a Data Storm tornado, and was relieved when Yusaku won the Duel.[2]

Shoichi and Yusaku spent the next few days trying to figure out Ignis' programming, but Shoichi struggled to understand the complicated algorithms that Ignis was made out of. He then suggested to come up with a name for the A.I., to which Yusaku decided to name it "ai", a pun on "eye". He was also impressed that the card data Yusaku obtained form the Data Storm was becoming a physical card. Trying to scan footage from "ai's" memories caused the Knights of Hanoi's leader to track them down, however Shoichi shut down Café Nagi's power before they were found.[3] The next day Shoichi gave Yusaku the "Decode Talker" card that had finished materializing before he went to LINk VRAINS to fight a supposed Knight of Hanoi that appeared.[4] When the Knight turned out to be Go Onizuka, a program that prevents Playmaker from logging out was activated by SOL Technology. Shoichi worked on an escape route for Yusaku, but Yusaku refused to use it. After the Duel ended, Shoichi scolded Yusaku for not using the escape route, but also suggested that they could recruit Go for their fight against Hanoi.[5]

Shoichi discovered that the real identity of the famous idol "Blue Angel" is Aoi Zaizen, a classmate of Yusaku. He thought about Yusaku meeting Aoi so they could get closer to Akira Zaizen in order to get more information about SOL Technology regarding his brother and Yusaku's memories, however he also doubted the plan would work because of Yusaku's poor social skills. A few days later, he was shocked when Playmaker and Blue Angel began a Duel before getting interrupted by a customer.[6]

References

  1. 1.0 1.1 Yu-Gi-Oh! VRAINS episode 1: "My Name is Playmaker"
  2. Yu-Gi-Oh! VRAINS episode 2: "Seize the Wind! Storm Access"
  3. Yu-Gi-Oh! VRAINS episode 3: "First Contact"
  4. Yu-Gi-Oh! VRAINS episode 4: "Charisma Duelist Go Onizuka"
  5. Yu-Gi-Oh! VRAINS episode 5: "The Three Count Rings"
  6. Yu-Gi-Oh! VRAINS episode 6: "Idol!! Blue Angel"

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.