FANDOM



IntroductionEdit

Kintoki has raided the city to search for Gin, but a few leaders question why he is obsessing over one man.

PlotEdit

Faced with a possible threat to his illusion, Kintoki brutally crushes Tama only to have Gintoki show up before he can finish her off. Instead of taking him down right then and there however, Gintoki prioritises saving her and so runs off to Gengai after tearing his nuts and bolts out, a weakened Tama taking the chance to capture a glimpse of a crying Gintoki. In response to this though, Kintoki uses what has happened to Tama to villainise him.

As such Gintoki finds his friends after his head while he hides out at Gengai’s place, Gengai having believed him after he showed up with Tama, and resolves alongside Sadaharu to take Kintoki down. Gengai realising that he had failed to give Kintoki the ability to do just that and that he must be stopped. While everyone is on the lookout for him though, messing about all the same, Otae has further doubts about Kintoki. Knowing that if something like this had happened the leader of the Yorozuya would plunge head first into it without a word. Gintoki showing up just as she finishes this and charging through on Sadaharu.

This however had been a ploy to lure their attention away as he makes his way alone across the rooftops, but even so the likes of Tsukuyo, Sacchan, and Kyuubei had not been fooled and refuse to back down. If anything fighting over who gets to take him down which Gintoki takes advantage of to try to sneak away. This of course fails and he soon finds himself up against all three of them unarmed, but through pure chance he saves all three of them by reenacting significant scenes. In turn breaking Kintoki’s illusion over them and leading to them choosing to stand in Kintoki’s way when he shows up.

CharactersEdit

TriviaEdit

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.