FANDOM


One night on the Sporum, the thread exoskeleton limbs was Melvin'd, making user Kaleb702 the OP. Striking again in the General Discussion section on 18/3/2011, Kelvin, also known as Melvin II by newer users, is a glitch that removed all of the non-stickied threads in the general discussion section, save a new thread called Everything Got Melvin'd. Some are saying that this glitch could be a new, and much more powerful, reappearance of Melvin.

However, it seems slightly unlikely. Due to its similar nature it was probably a son of Melvin, however it seems to be the most powerful son of them all... even more powerful than his father, who only targeted single threads at a time.

ChronologyEdit

For many months, the great beast of Melvin was asleep. Sometimes his children caused minor glitches and annoyances, but these were perfectly bearable and often a cause for laughter. However on the Eighteenth of March 2011, Kelvin, a son of Melvin far more powerful than any of his other brothers and sisters, eventually struck to 1bring down almost the whole of the General Discussion section.

He destroyed the first page of General Discussion, reducing it to nothing more than the stickies and one glitched thread. Said glitched thread also suffered, being cast upon page over page of rage, undesirable discussions, and page lag. Users panicked, bumping the thread upon thread to fix the glitch, but to no avail. Kelvin had seemingly, taken over General Discussion, leaving nothing but a barren, glitch-filled field of hopeless threads and posts.

One must type Kelvin in dark blue text, so as to reduce the likelihood of his return.

During this short reign of terror, it was decided by the wise Zaroas and Jabba the Hutt that this could be no other than Kelvin, the feared son of Melvin. Jabba had originally called it Melvin II, but Zaroas, in his wisdom of experience, declared that this was the recurrence of an existing glitch, which had been already dubbed Kelvin. However, both agreed that the new glitch was one of the most powerful sons, and not a recurrence of, Melvin.

Why Exactly did He Strike?Edit

This remains a mystery as of now, but will probably reach a solution with the great weapons wielded by the SporeMasters and admins. Now, children, we must wait for another day to tell another story about the terrible glitches that lay in wait around the Sporum. However, as the Admins have virtually all left for the newer pastures of the DarkSporum, it is likely that Kelvin will remain for quite some time, and thus the general discussion shall a dead husk.

If a glitched up box containing the "An error has occurred" message produced by Kelvin is clicked, it will bring you to a nonexistant profile. This nonexistant user has been called 'Bob' or '81054' after the number appearing in the URL bar when you go to this profile. Why exactly this occurs is unknown but it probably relates to the cause of this glitch.

The End of The First Attack and the Beginning of the SecondEdit

The End of the First AttackEdit

The glitch was reversed by 3/19, amidst several threads which were created to (unsuccessfully) try to "bail the section out" of the dreaded Kelvin.

More old GD threads were bumped, the combine weight of so many OPs slammed him into the darkness.

The Beginning of the Second AttackEdit

On 5/1/2011, Kelvin once again struck the Forums. All of the usual symptoms of this glitch were displayed, but luckily, the glitch eventually subsided, as expected approx. seventeen minutes later. Kelvin was been taken care of. [voice=devil]FOR NOW!!![/voice]

Glitches

Royal Glitch House of Midzo
KelvinMidzoMelvinMelviiMortimerWilliam ShatnerRichardSallyAntiSpode
Other, Lesser Glitches
VladmirOlgaMichael JacksonJoséKeithBieberKathyDebbyGregoryLady GaGaMedFascMrs. SophiesWallyKevinDoctor OctagonopusScreebles (glitch)Ghostofillusion (glitch)Yoshi (glitch)

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.