Playing Your Super Mario Maker Levels

You do not need to be a professional designer to learn something useful from game criticism. A critic usually approaches games by analysing, breaking down, and examining existing work: what makes it tick, why it feels good, where it fails, and what other creators might learn from it.

That kind of analysis is interesting for players who want to understand why their favourite games work. But it can also be useful for indie developers, students, and hobbyists who are trying to make something of their own.

Super Mario Maker makes that feedback loop visible. When people build small Mario levels after studying existing Mario design, you can see the lessons move from theory into craft. The result is not imitation. The result is a set of tiny courses that take familiar ideas about safety, escalation, surprise, and restraint, then turn them into something personal.

One of the strongest recurring patterns is the safety net. A level can ask the player to learn a new mechanic, but it should often give them a low-pressure space to understand the idea before using it in a dangerous situation.

In Iglian's levels, the course introduces its core mechanic with room to experiment. A seemingly random enemy wandering around a block turns out to be a preview. The player gets to see how that enemy behaves before the same foe appears in the middle of a trickier section.

That is classic teaching without a tutorial. The level does not stop to explain itself. It lets the player observe, test, and internalize the rule, then asks them to apply it under pressure.

"The Spring's The Thing" from Nick Burnham has a small gag that works because it understands player expectation. The course lures the player down toward a question block. Everything about the setup says there must be something useful inside. Instead, it is just a coin.

That kind of joke is not separate from level design. It depends on how players read space, rewards, and familiar Mario grammar. The laugh comes from the designer knowing what the player will assume, then harmlessly undercutting it.

Mithoswrath's Raccoon Plains pushes that playful hostility further, using invisible blocks and runaway mushrooms to keep the player guessing. It has fun at the player's expense, but the fun works because the surprises are embedded in a readable course language.

Several of the strongest levels are built around a single clear gimmick. Travis builds a course around enemies shot out of cannons, then ramps the idea up beautifully. Drew Fitzpatrick builds around springs on springs, first introducing the timing and physics in a safe space before asking more of the player.

Violet's Gliding Ground Grotto has bouncing platforms that feel like they could belong in an official Mario level. Carlos finds that falling platforms do not fall while the player is bouncing on a spring, then turns that discovery into a full course.

The important part is not just finding a clever interaction. It is introducing the interaction bit by bit, in a forgiving and thoughtful way. A gimmick becomes a level when it can evolve: first a safe demonstration, then a more demanding use, then a version that combines timing, risk, and confidence.

The best thing about these courses is that they clearly borrow lessons from Mario without simply copying Mario. They use ideas like evolving challenges, limited toolsets, safe zones, escalation, and readable surprises. But each course still has its own personality.

That is the practical value of studying existing games. The point is not to trace over a level. The point is to notice the underlying craft. Why does the first version of a challenge feel safe? How many objects does the course really need? When does the player understand the rule? How does the final version make that same rule feel new?

A designer can take those questions into almost any genre. Mario Maker just makes the process unusually clear because the parts are small, the rules are familiar, and the courses are compact enough to reveal the structure quickly.

The same loop works in reverse. A course called Saw Subject changed after player feedback: red bullet bills improved a one-up chase, a spike trap was fixed, a precursor challenge made a note-block leap easier to understand, a flamethrower difficulty spike was smoothed out, and some clutter was removed.

Those are practical edits. They do not change the whole identity of the level. They make the course clearer, fairer, and better paced. That is what useful feedback often does: it finds the places where the idea is good but the communication is rough.

Another course, Pipeflip Airship, uses a larger structural idea. The whole level flips upside down whenever the player goes through a pipe, taking inspiration from a Super Mario Bros. 3 stage where the world changes after passing through a door. That is exactly the kind of borrowing that feels productive: keep the underlying transformation idea, then rebuild it around a new course shape and a new joke at the player's expense.

The larger point is simple. Looking closely at games can make you better at making games, but only if the analysis turns into action. Notice how a game teaches. Notice how it escalates. Notice when it limits its toolset. Notice where it gives the player a safe place to learn, and where it finally asks them to perform.

Then build something small and test whether those observations survive contact with a real player. The player-made Mario Maker levels are valuable because they show that this method has merit. They are fresh and personal, but they are also improved by taking careful note of what came before.