FANDOM


Desert Hills is the first track of the Flower Cup in Mario Kart DS. It is a plain desert and is one of the few tracks to have Pokeys. When a racer touches a Pokey, they flip to the side and drop their items. CPU racers sometimes may get hit by a Pokey, when the Pokey continues moving in their direction, continuously flipping them over and slowing them down greatly. It is also the first track to feature Fire Snakes (the second being Grumble Volcano). If you touch a Fire Snake, you spin around. The sand here slows the drivers sharply. It ends with lond, sharp, winding turns.In a similar vein to Airship Fortress, this track is inspired by World 2, Desert Land, in Super Mario Bros. 3 (which is also known as Desert Hill). Missions 2-6 and 4-4 are held in this course. Both missions use Wario. In 2-6, he has to destroy all 5 Pokeys. In 4-4, he has to drive through 7 numbered gates in order. The staff ghost uses R.O.B. in the ROB-LGS.

Mario Kart Wii

Hqdefault

As seen in Mario Kart DS.

This track returns as a retro course in Mario Kart Wii. It has many of the same features as the DS version, such as Pokeys and Fire Snakes. It's the first course in the Leaf Cup.

The two Staff Ghosts use Dry Bones in the Standard Bike S and the Tiny Titan/Rally Romper.

Shortcuts

Before the second turn, use a Mushroom or 2 to cut through the deep sand between the pyramid and the wall. for all games


Glitches

If you hit the hit the left dark terrain right before you touch the water, you will fall through it with no splash. This glitch was fixed in Mario Kart Wii which means this glitch only works in Mario Kart DS.

Previous track:
Luigi's Mansion
Current track:
Desert Hills
Next track:
Delfino Square
Previous track:
GCN Waluigi Stadium
Recently reappeared in:
Mario Kart Wii
Next track:
GBA Bowser Castle 3

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.