The Tempest (Puzzleshipping)

The Tempest (Puzzleshipping)

  • WpView
    Reads 152
  • WpVote
    Votes 4
  • WpPart
    Parts 3
WpMetadataReadOngoing9m
WpMetadataNoticeLast published Tue, Oct 8, 2019
Yami, captain of The Tempest, is known across the seas for his fantastic ability to predict shifts in the weather, his skill with a sword, and his firm control of what is one of the most respected ships ever to grace the seas. Above all, he desires to be reunited with the bearer of the Millenium Puzzle, an artifact that his family has guarded for generations. He has been following rumors about where he might be able to find it for the last few years and offering aid to those he encounters along the way... But what will happen when Yami finally tracks it down? *This is a puzzleshipping fanfiction and will focus on the relationship between Yami and Yugi from Yu-Gi-Oh. I do not own Yu-Gi-Oh. This is purely a fan-made contribution to the series. The fan-art featured is not my own!*
All Rights Reserved
#127
puzzleshipping
WpChevronRight
Join the largest storytelling communityGet personalized story recommendations, save your favourites to your library, and comment and vote to grow your community.
Illustration

You may also like

  • Shuffled Deck (Prideshipping)
  • It's Too Hard...
  • Into the light
  • Just Say The Truth (YamixYugi)
  • The Reign of Yugi Muto
  • The Killer School
  • Tarnished Innocence
  • The Dark in my Light [Finished]
  • The Love Of A Mermaid
  • The Spirit of the Mirror

Seto Kaiba and Yami Yugi have an intimate moment during a Dueling rematch where they show each other a side none haven't seen leaving the small Duelist in pain the next morning in class. Confused but having a clue what happened Yugi confronts the spirit of the Millennium Puzzle and gets the answers he wants, offering his help to patch things up between both awkward Duelists. Kaiba doesn't really hate his rival as much as he thinks he does but refuses to see him, will he accept Yugi's help? Or will he be stubborn with his feelings as usual?

More details
WpActionLinkContent Guidelines