{"id":5309,"date":"2015-08-14T09:00:18","date_gmt":"2015-08-14T15:00:18","guid":{"rendered":"http:\/\/minkhollow.ca\/beckerblog\/?p=5309"},"modified":"2015-08-14T08:30:35","modified_gmt":"2015-08-14T14:30:35","slug":"where-is-the-line-between-good-instructions-and-hand-holding","status":"publish","type":"post","link":"https:\/\/minkhollow.ca\/beckerblog\/2015\/08\/14\/where-is-the-line-between-good-instructions-and-hand-holding\/","title":{"rendered":"Where is the line between good instructions and hand-holding?"},"content":{"rendered":"Approximate Reading Time: <\/span> 2<\/span> minutes<\/span><\/span>

\"\"<\/a>One of the great things about games is their potential for delivering just-in-time instruction.<\/p>\n

Most games require some sort of user assistance,\u00a0whether it be instructions, in-game tutorials, or a help system. Many games\u00a0integrate help and tutorial information into the gameplay as much as possible. As designers, how can we know when it is\u00a0is too much? At what point does a design start to keep a player from feeling autonomous because it\u2019s too helpful?<\/p>\n

I think the answer to this is going to be different for entertainment games than for serious games, and there is probably variation even within serious games. Games that try to change your attitude, for example, will likely need to be much more cautious about forcing people to spend time in a tutorial than a game trying to teach math. It also depends a great deal on the complexity of the game as well as the complexity of the subject matter.<\/p>\n

Personally, I think people should have access to tutorials and other help but there is very little they should be forced<\/em> to do.<\/p>\n

A game like Machinarium<\/a> has a very short intro tutorial that gets you started. I think it is very well designed. Its \u201chelp\u201d pages are incredibly cryptic, on purpose, in keeping with the whole spirit of the game. You even have to do a mini-challenge before you can look at the help pages.<\/p>\n

\"SplashA few years ago, we were asked to design a game<\/a> to teach concepts in machine learning to middle schoolers. This one presented a huge challenge – there is nothing insightful about watching a machine while it\u2019s learning\u00a0and\u00a0without an idea of how the machine is\u00a0doing what it\u2019s doing, you really can\u2019t get any idea of what this is all about – all you see is that the machine (or program) just gets better at what it does. Also, machine learning is not part of any normal middle school curriculum.
\nIt\u2019s a fairly advanced topic, for good reason: it assumes a fair bit of background in probability, statistics, and CS. Our approach was to design\u00a0a game where the player is the one who is asked to learn the way a machine does. The player is to create a program for a probe to be launched to Europa. It was not designed to be easy, but the intent was to give kids a feel for how machine learning works, without all the math and CS (a tall order). The publisher kept asking us to make it easier. They wanted us to add all kinds of hints and pop-ups telling players what to do next and we got into a lot of trouble for resisting. \"viper2\"Making a game easier rarely makes it more fun, and providing the right kind of help in a game can be as difficult as designing the game in the first place. In the end we created a fairly substantial \u2018manual\u2019 that players could access whenever they wanted. We had offered to do far more (video tutorials, lesson plans, etc.) but the publisher didn\u2019t want to pay for them. The game is good, but it doesn’t stand alone. The help we created is also good, but insufficient.\u00a0Good games aren’t cheap.<\/p>\n