Fandom

Kingdom Hearts Fanon Wiki

Oxide

5,006pages on
this wiki
Add New Page
Talk1 Share
I can't be happy, not while feeling so incomplete.
KexonTalk
This article is in need of more information !
Help improve it by adding in what you know, or look at the request below for specific details.


This article is lacking: Everything save for Story.
Sure, I sense Oxide's prescence, but I can't see anything!
ZaneTalk
This article is in need of an image.
You can help by uploading and adding a picture or two.
Okay, now we need to make a new name for ourselves.
BlankSprite
This article is uncategorized or poorly categorized.

You can improve this page by categorizing it accordingly.

Oxide is the 15th member of Organization XVIII. He worked with the Organization during the Great War and was later assassinated.

OriginEdit

Oxide was originally named Doie (Do-e). He was a brave fighter of the Darkest Rebellion. One day he was ambushed by several Heartless Generals and had his heart taken away. He became a member of the Organization and put away his Blast Blade for later days.

Organization LifeEdit

In the Organizition, he was a powerful warrior who would fight any battle for his kind. He fought in the Great War and killed Grim inside the Cavern of Doom. He was then in the Battle of Sacred Gorge where he fought the 3000 Heartless and conqured them. He then became friends with Izral. Him and Izral went on every mission together. Soon after the War, they had a fight over Ella, and Oxide killed Izral, scaring Ella away. He was taken out of the Organization.

AssassinationEdit

He was cought in the Crystal Cavern two days after he was exiled by Grim's older brother Heatach. They fought. Oxide won but let Heartach go. Two months later Heatach made a sneak attack on Oxide and killed him by snapping his neck.

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.