Design Club - Super Mario Bros: Level 1-1 - How Super Mario Mastered Level Design

Yes, it's rare, but they have. Game maker's toolkit has one on how they solved their open world problem for BotW: - link And at GDC, they talked about their Chemistry engine for BotW: - link - link Game historian has some tidbits of how they made certain design decisions for their successful games Mario Kart: - link Super Mario World: - link Super Mario Bro 3: - link GMT, Snowman, and Extra credit does analysis of how Nintendo designs their Mario levels. - link - link - link - link - ▶ this video Generally, it follows the ramp up and down of the Hero's journey in storytelling. 1. Introduce a new mechanic in a safe area where it's impossible to die. 2. Increase the challenge with the mechanic by adding variations 3. Ramp up challenge even more by combining with previously learned mechanic 4. Have periods of rest inbetween the challenges.

Was thinking the same thing. The Nintendo designers were always so meticulous about the design of the levels, especially what’s visible to a player at any given point. To get a sense for this, watch this video [1] (from 7 years ago) walking through the design of level 1-1 of SMB. It’s crazy what (likely) went into planning the design of each level of the various Mario platformer games. But like OP, this is strictly looking at it from a gameplay perspective, ignoring the impressive technical feet that this is. [1] ▶ this video

Possibly the most famous video game tutorial of all time has got to be World 1-1 from the original Super Mario Bros. ▶ this video And really, most of the later Mario games execute this fairly well, with some (sunny) exceptions here and there. Nintendo is unusually skilled at introducing a new mechanic in a way that feels like organic play, and slowly ramping up the complexity in a way that will leave most players feeling like natural masters by the end of the level, without realizing that the level was leading them by the nose the entire time.

Proper teaching looks less like what most teachers do, and more like what (good) game designers do. • Hide the tutorial for the problem, in the "shape" of the problem, so the student won't even realize they're being taught something. (See e.g. ▶ this video ) • Make the student/player feel a need for a new tool, before the tool is introduced. Have them try (and perhaps fail) to solve the problem without the tool first. (See the "keys and doors" discussion in link ) • For each new concept, present its lesson as a series of spaced-chunk challenges, where each chunk ramps the difficulty up to a climax and then down again to a gentle denouement. Give the learner's mind a chance to feel a sense of mastery over already-understood concepts, not just the continual stress of new challenges. (See link or link ) • Gate problems behind proof of mastery of previous micro-skills, not just in the form of obvious tests, but also in the form of multi-step problems for new knowledge which can't even be approached without also having another prerequisite skill. Ensure that it becomes impossible to "leave behind" a foundational skill—i.e. ensure that the learner will get stuck without the new tool, and so realize they need to backtrack to pick up that tool, rather than flailing uselessly at the next problem. • Meter and visualize progress. Map acquisition of micro-skills directly to some sort of measurement the student can look at (a level number; a tech tree; a skill grid), to feel that they're

> You can definitely feel the 'steering' if you're looking out for it The implicit steering is one of the things that Nintendo is famous for though. At least among game designers: ▶ this video What the video doesn't point out is that if you don't run to the right, the timing of the jump to avoid the Goomba makes you hit that first question mark block by accident.

It's certainly a nice enough script for what it does, and I can see it being useful in some instances, but... a lot of this 'feature tour/tutorial' stuff strikes me as more of an excuse to not worry about ease of use. A good site design should be intuitive in of itself, not something that requires a guided tour to figure out. It's a bit like the modern gaming world to be honest. In the old days, games like Super Mario Bros was designed to teach you through level design, so you'd figure out how things worked without getting a huge info box thrown in your face. Like this: ▶ this video On the other hand, games since got obsessed with tutorials detailing every minute thing about the title, leading to such over the top insanity as this 'help DVD' included with Super Mario Galaxy 2: link These tutorials on sites and in mobile apps remind me all too much of the latter. It's like 'we won't use our product to teach people in a natural way, so we'll put in a guide for complete dummies instead'.