FANDOM


The invasion of Gobbo Valley by Baron Dante and his Dantinis set the pretext for Croc: Legend of the Gobbos.

HistoryEdit

Baron Dante 1 had watched, for a long time, the Gobbos living in peace and harmony, not just in Gobbo Valley, but all over the Gobbo Archipelago. He decided that for once, the Gobbos should suffer. Eventually, he and his army of Dantinins traversed the length between Castle Island and Forest Island.

The InvasionEdit

Baron Dante 1 and his Dantinis quickly took over Gobbo Valley. The Gobbos were no match for the Dantinis, and because the Gobbos had never encountered anything like the invasion in their long history, they were ill-prepared. Almost 9 in every 10 Gobbo was captured and imprisoned. Some Gobbos managed to take cover in time, hiding in calved-out tree trunks.

King Rufus, Croc and a few Gobbos managed to flee from the invading Dantinis, but they were soon trapped. The Gobbos were swiftly caught, and King Rufus led Croc away to a Beany Gong. Beany The Bird appeared and took Croc away, just as Baron Dante 1 himself caught King Rufus, who was locked away in his castle back on Castle Island.

Effects of the InvasionEdit

It was not just the Gobbos in Gobbo Valley that suffered. Creatures from all over the Gobbo Archipelago were subject to Baron Dante 1's magical powers, and were transformed into evil beings loyal to Baron Dante 1.

The Dantinis took control of the islands, guarding the evil beings and the Gobbos.

On the GobbosEdit

The Gobbos were a very social species, and were distraught by the fact that they were separated from each other for a prolonged amount of time.

LegacyEdit

The invasion set Croc up to rescue the Gobbos, rescue King Rufus and defeat the Dantinis and Baron Dante 1.

Gobbo TimelineEdit

When Croc AppearsInvasion of Gobbo ValleyCroc: Legend of the GobbosCroc 2Beyond

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.