Jump to content

Tutorial Failure: Difference between revisions

deleted last example -- a separate player's guide is not an in-game tutorial; added subheads, added a fictional example
No edit summary
(deleted last example -- a separate player's guide is not an in-game tutorial; added subheads, added a fictional example)
Line 1:
{{trope}}
{{quote|"It's not that hard. You just have to use abilities they won't discuss and techniques they haven't entirely taught you via controls they never quite explain." |'''[[Penny Arcade|Tycho Brahe]]''', on ''[[The Witcher 2: Assassins of Kings]]''}}
|'''[[Penny Arcade|Tycho Brahe]]''', on ''[[The Witcher 2: Assassins of Kings]]''}}
 
[[Video Game Tutorial|Video game tutorials]] are meant to quickly and easily improve the player's comprehension of the game he or she is playing. Ideally, they should explain everything the player needs to know to play the game without hand-holding. They should be succinct and easy to follow. But what happens when a tutorial fails to do its job?
Line 7 ⟶ 8:
 
This trope is for those tutorials which do a completely inadequate job of what they're supposed to do—the kind that leave the player frustrated that they can't perform that seemingly-simple move, or wrap their heads around a gameplay system which seems straightforward. Either this tutorial contains misleading or false information or fails to mention some vital aspect of gameplay. Perhaps it's because of a [[Blind Idiot Translation]]; perhaps it's because the game swamps the player with [[Info Dump|mounds of text]] right out of the gate and expects them to remember everything immediately; or, maybe, the tutorial tries to simplify a complex game mechanic into a "rule of thumb" which ends up being more of a hindrance than a help. Perhaps the tutorial gives advice that is no longer valid after a game patch. Whatever the case, this tutorial just doesn't work. Think of this as a tutorial-induced [[Guide Dang It]]. Related to [[Manual Misprint]]. If an important gameplay element ought to be in the tutorial but is not, that might result in a [[Noob Bridge]].
{{examples}}
 
{{examples}}
== Real Life Examples ==
* In the original release of ''[[Dungeon Lords]]'', the tutorial told the player about a great number of features that '''were not in the game.''' Later patches added some features and removed references to the ones that never materialized.
* When the player does enough damage to the first boss enemy in ''[[Fable]]'', the boss falls to the ground and starts writhing in agony. At this point, the [[Voice with an Internet Connection|Guild Master]] tells the player that the boss "is near death. A few more hits should finish her off!" In fact, the boss is already defeated and this is her death animation. Hitting her while she is writhing on the ground does absolutely nothing.
Line 38 ⟶ 40:
** There's also the fact that Paradox seldom bothers to update the tutorials to reflect their endless expansion packs, most of which alter gameplay more than enough to make the tutorials useless.
* One of the loading screen hints in ''[[Neverwinter Nights 2]]'' says some classes multiclass better than others. This is correct and sound advice. What is wrong is that it follows this by giving the Monk as an example of a class that doesn't, which is completely wrong. It says Monks gain lots of abilities at high levels, which is true but these abilities are all terrible while the abilities they gain at low levels are useful for a melee class or divine caster.
 
* The player's guide (a short free publication guiding players on how to make characters that fit a campaign both thematically and background wise) for the ''[[Pathfinder]]'' Adventure Path ''Iron Gods'' recommends that good "favored enemy choices include construct, humanoid (android), humanoid (human), undead, and even plant". Problem is reading the description of Androids will tell you "Androids count as both Humanoids and Constructs for effects that target creature type", which means taking favored enemy against just Androids is a terrible idea since Favored Enemy (Construct) is strictly better and doesn't stack.
== Fictional Examples ==
=== Live Action TV ===
* It's hard to be certain, but it appears that the unreleased [[Augmented Reality]] game at the heart of the South Korean series ''[[Memories of the Alhambra]]'' -- despite its groundbreaking design and programming -- offers what could at best be called an "inadequate" tutorial upon initially entering it. (If it's even a tutorial at all!) It takes main character Jin-woo an entire night (dusk to dawn) and dozens of attempts to finally beat the boss and level up for the first time. Some of that was certainly due to Jin-woo's arrogance and stubborn refusal to listen to the friends/employees who were acting as his [[Mission Control]], but judging from the bits of game interface we see, he gets almost no welcome, almost no explanation, and very terse and uninformative instructions as to what to do next.
 
{{reflist}}
Cookies help us deliver our services. By using our services, you agree to our use of cookies.