I have no clue where this Barrier haki headcanon creeped in.
Just looking at how the two fights were shown - Kizaru being angry & capturing 500 pirates to vent his frustrations after failing to best Rayleigh v. casually kicking Snakeman Luffy out of the Island.
It's very clear which fight was the more tougher one.
damn kizaru should not be so hyped for this chapter, he has not a very nice portrayal.
btw there is no way we can scale based on this fight, cause neither luffy and kizaru are interested in defeating the other: luffy only wants to stall him while they regroup to escape, kizaru wants to complete the mission (as it is shown by the fact that he immediately goes after vegapunk after kicking luffy)
both of them are not going all out in my opinion, cause they have things to protect.
the robot gonna cause loooooot of damage to the navy
2-Kizaru is no doubt superior to Snakeman, even if Snakeman had used ACoC. Those ACoC attacks are useless if they cannot reach Kizaru, who just embarrassed Luffy in speed and blitzed him.
Yonkoturds crying about adv CoC when Kizaru is using literally no haki, meanwhile Yonko is in full haki and his 2nd strongest form?
And still got 1 knocked out by casual attack he did vs x-Drake
I have to repeat that I absolutely love Kizaru's fighting style, very visually pleasing.
From this round of Kizaru vs Luffy, I can infer two things:
1- That kick Base Luffy gave Kizaru was definitely AdCoC.
2-Kizaru is no doubt superior to Snakeman, even if Snakeman had used ACoC. Those ACoC attacks are useless if they cannot reach Kizaru, who just embarrassed Luffy in speed and blitzed him.
Luffy will likely use his toon hax to keep up with Kizaru here.
The comparision i drew was for speed. Rayleigh actually stalemated Kizaru in close quarters meanwhile Snakeman's attacks all got palmed away. And Ray ain't even a Fs user for all we know.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.