<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Léo Lesêtre on Medium]]></title>
        <description><![CDATA[Stories by Léo Lesêtre on Medium]]></description>
        <link>https://medium.com/@leolesetre?source=rss-104a172a987d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*LYmegWdQT05qaWzWESFdyA.jpeg</url>
            <title>Stories by Léo Lesêtre on Medium</title>
            <link>https://medium.com/@leolesetre?source=rss-104a172a987d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:19:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@leolesetre/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Good Ideas make for Bad Designers — (Part 3 of 3)]]></title>
            <link>https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-3-of-3-42b9aeaf45fe?source=rss-104a172a987d------2</link>
            <guid isPermaLink="false">https://medium.com/p/42b9aeaf45fe</guid>
            <category><![CDATA[game-industry]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Léo Lesêtre]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 22:13:55 GMT</pubDate>
            <atom:updated>2023-10-01T22:13:55.864Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iyLVfvApyQNbHP56Kj4G7g.png" /></figure><h3>Good Ideas make for Bad Designers — (Part 3 of 3)</h3><h4>A love letter to the team and to heist movies (it’s related, I promise).</h4><p>Game development is highly collaborative and requires the work of many people. As the industry grows, it is no longer rare to see flagship projects combining the efforts of thousands of people. Despite this, we still have a tendency to see those creations as the work of just one or a few persons.</p><p>I’ve already discussed why I think this perception is both false and harmful to the people in the industry (in <a href="https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-1-or-3-1a94fdbcf12e"><strong>part 1</strong></a> and <a href="https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-2-of-3-58ad72f98556"><strong>part 2</strong></a><strong>)</strong>. And while I think neglecting people’s contribution is a big problem, overestimating the contribution of a few, no matter how skilled and experienced they might be, is just as problematic.</p><p>And it often ends up being bad for the game and the player experience as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*oZ9NhnsWONYhleNG.gif" /><figcaption>Fine idea. Bad execution.</figcaption></figure><h3>Stories about lone geniuses do not end well.</h3><p>As I previously explained,<strong><em> Warren Spector</em></strong> is often considered the father of <em>Immersive Sim</em> genre, just like <strong><em>Peter Molyneux</em></strong> is considered the father of <em>God Games</em>. Similarly, <strong><em>Cliff Bleszinski</em></strong>, while not considered its father, is recognized for the immense influence he had on the shooter genre due to his work on the <strong><em>Unreal</em></strong> and <strong><em>Gears of War</em></strong> series.</p><p>I take the time to reinstate those facts because despite being seen as living legends in their respective domains, they also have another point in common: Their latest additions to those very genres were all massive failures.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/530/0*1XPeVR8GVngY7vyd.jpg" /></figure><p><strong><em>Godus </em></strong>is a god game developed by 22Cans, a studio founded by <strong><em>Peter Molyneux</em></strong>. Initially teased by <strong><em>Molyneux </em></strong>himself as “<em>the ultimate god game</em>”, the project launched to disastrous reviews from players and critics alike. In <a href="https://kotaku.com/why-peter-molyneuxs-godus-is-such-a-disaster-1685539932">this extensive article</a>, <strong><em>Kotaku</em></strong> journalist <strong><em>Nathan Grayson</em></strong> talked with the designer and many members of the team and cites a lack of communication and a rebuttal of feedback provided both by players and the team as a reason for the project’s failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*tLhc_e9IGBaTFNut" /></figure><p><strong>Underworld Ascendent</strong> is an <em>Immersive Sim</em> game greenlit on <strong><em>Kickstarter</em></strong>, led by several industry veterans, among which <strong><em>Warren Spector</em></strong> has been one of the most celebrated. But despite those obviously talented people’s presence on the project, it has, for lack of kinder words, <a href="https://www.pcgamer.com/after-over-a-year-of-necessary-improvements-underworld-ascendant-still-isnt-fun-to-play/#:~:text=It%20had%20the%20experience.,a%20shocking%20number%20of%20bugs.">been a mess</a> (with all due love and respect). While we have no specific insights into how development went, the game’s bizarre decisions and lack of clarity in its features seem to indicate that it didn’t benefit from much room to receive feedback and iterate on its many problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*GsSzycppe3I88XPL.gif" /></figure><p><strong><em>LawBreakers </em></strong>is the latest and final creation of the studio <strong><em>Boss Key Production</em></strong> before it closed its doors in 2018. The studio was co-founded by <strong><em>Cliff Bleszinski </em></strong>and developed the game as a shooter game designed to offer a more gritty and realistic competitor on the hero shooter market. Despite being quite aggressively marketed by <strong><em>Cliff </em></strong>himself during its development, the game wasn’t met with the expected success, leading to the retirement of <strong><em>Cliff </em></strong>from the game industry and the closure of the studio.</p><p>While many still consider the game good if quite generic, it didn’t convince the majority of players. And while I do not have any insights on the development on this project, I can’t help but wonder in what measure the project leaders were ready to acknowledge problems, regarding statements made after the game failure claiming <a href="https://www.shacknews.com/article/135060/cliff-bleszinski-lawbreakers-news">the players rooted for the game to fail</a>, or that it was <a href="https://www.vg247.com/lawbreakers-failed-woke-says-cliff-bleszinski">too progressist to succeed</a> (???).</p><p>So what’s happening here? If the success of those games relied exclusively on the genius of those designers and the quality of their ideas, they should have worked here as well, right? Well, those games have another thing in common, I believe: they were all promoted for the personalities they were the product of rather than for their process, teams, or proven concepts. Ignoring problems is about the only truly unforgiving mistake you can make in this industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*-nDK9xK7Ik0rjBT5" /></figure><h3>As many heroes as there are stories.</h3><p>In his video <strong><em>Bloodborne is Genius, and here’s why</em></strong>, <strong><em>HBomberGuy </em></strong>talks about the gameplay improvements between <strong><em>Dark Souls</em></strong> and <strong><em>Bloodborne</em></strong>. And <a href="https://youtu.be/AC3OuLU5XCw?t=1900">when talking about a specific point</a>, he describes how he envisions the creative process, saying: “<em>Can you imagine being in the room when Hidetaka Miyazaki was looking at playtest footage from the previous games and coming up with the concept for Bloodborne, and he was like — take out the shields</em>”. In the video (which is otherwise fantastic, and you should watch it), this is just a way to illustrate a point. But it depicts the identification of the problem and the proposition made to solve it, all made by one man: Game Director Hidetaka Miyazaki. It also imagines the solution as instantly functional without requiring tests, iterations, and adjustments.</p><p>And this is indeed how we often imagine game creations. This falls in the <a href="https://en.wikipedia.org/wiki/Availability_heuristic"><em>availability heuristic</em></a>, I believe. When we imagine creation, the famous faces and names we associate with it are the first to come to mind. And so we imagine those people being responsible for the most decisive inputs of the project. But like any other bias, just because it comes intuitively doesn’t mean that we shouldn’t challenge this intuition or that this is an accurate representation.</p><p>Directors are responsible for defining the vision for the game and its global direction, but because of this, they have to be aware of the design, the art direction, the engine limitations, testers’ availability, budget, time, and so much more. Simply put, they just do not have the time or mind resources to micro-manage each design problem. And it’s fine because it’s not their role. On the other hand, testers, designers, and other specialized roles can focus entirely on their tasks; therefore, they are, in fact, often the ones coming up with the solutions. But they are not the ones we tend to think about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*klpbhdV0JCZnaXEn" /></figure><p>And this can go pretty far. I’ve heard people argue that <strong><em>Dark Souls 2</em></strong> shouldn’t be considered as part of the <strong><em>Dark Souls</em></strong> series because <strong><em>Hidetaka Miyazaki</em></strong> did not direct it, and some even went as far as to say it shouldn’t be played for this exact reason. Dismissing in the process the work of the many people who gave all they had to the game as nothing more than worthless.</p><p>One of the more accurate and insightful talks I’ve seen on this process is a <strong><em>GDC </em></strong>conference given by different members of <strong><em>Santa Monica Studio</em></strong> on their work on the latest <strong><em>God of War</em></strong> games. In <a href="https://www.youtube.com/watch?v=aIb-Lt7WX_s&amp;ab_channel=GDC">his conference</a>, Game Director <strong><em>Cory Barlog</em></strong> describes his own job as “<em>pitching and doubting</em>”, and explains how he defined the direction he wanted to take the game in. You can then see how the <a href="https://www.youtube.com/watch?v=hE5tWF-Ou2k&amp;ab_channel=GDC">combat designers</a>, <a href="https://www.youtube.com/watch?v=eSB29qx6sWw&amp;ab_channel=GDC">level designers</a>, <a href="https://www.youtube.com/watch?v=ARBNHvxiwiU&amp;ab_channel=GDC">animators</a>, and others, had to work together to make those ideas work. <a href="https://www.youtube.com/watch?v=kX8Jn3XPoWQ&amp;ab_channel=GDC">This conference</a> by <strong><em>Jason McDonald</em></strong>, Lead Gameplay Designer on the project, is particularly explicit on how challenging those ideas were and how the team had to iterate and rethink their approach to find a working formula.</p><p>This is also echoed by <strong><em>Warren Spector</em></strong>. In his <a href="https://youtu.be/tffX3VljTtI?t=2046">GDC speech</a>, he also talks about the importance of the team, saying of the team leads on <strong><em>Deus Ex</em></strong>: “<em>Those guys do not get enough credits for the creative aspects of the game, and the fact that we shipped at all</em>”. He says <strong><em>Deus Ex</em></strong> was based on the idea of both <em>Immersive Simulation</em> and <em>Shared Authorship</em> as a collaboration between developers and players. But this idea of Shared Authorship also goes for the team, as he explains that the project evolved directly because of the persons involved: “<em>Why did things change? Well, we had new people join the team; they had new ideas</em>”. He explains how his work was more about driving the direction the different teams and individuals worked toward and balancing their different inputs.</p><p><strong><em>Warren Spector </em></strong>has been one of the most outspoken people in the industry about this, in a 2001 <a href="https://www.ign.com/articles/2001/11/12/deus-ex-2">interview with IGN</a>, he famously declared: “<em>There’s a tendency among the press to attribute the creation of a game to a single person</em>”. As the article proceeds to credit him as sole creator of both <strong><em>Thief</em></strong>, and <strong><em>Deus Ex</em></strong>… in order to prove his point, I assume.</p><p>This shared vision and direction is something he experienced firsthand as Producer on <strong><em>Thief </em></strong>when he asked the teams to change the game to make a viable alternative to sneaking, and they refused because it went against the direction of the game. And he says: “<em>For this game, I believe they were right to tell me no</em>”.</p><p>One of my lead designers once described the process of iterating on the game as diamond polishing. It is just a shiny rock until you remove imperfections and smooth its edges, one face at a time, so only the best parts remain. And this takes many people with many skills, not just those who own the mines.</p><p><em>Also, just like ideas, </em><a href="https://thecuriouseconomist.com/are-diamonds-really-that-scarce/"><em>diamonds are not that rare</em></a><em> or special</em>,<em> in fact. Their value and rarity have been artificially inflated by companies to make fortunes out of the work of people barely paid for it. <br>But isn’t it a compelling metaphor?</em></p><p>And it might be what’s missing here, right? A compelling narrative. <br>What’s the lesson here? No one is a genius; you will inevitably fail and need to ask for help because success is never entirely in your hands. It depends on the team, on the time and budget you have, and somehow on luck, too. <br>This just doesn’t make for a great story.</p><p>Or does it?</p><p>Because there’s a type of story that is at least as celebrated as the ones about lone geniuses. One that shares many similarities with what we’ve discussed so far and still manages to be inspiring and move people. And I’m now going to argue that this is the type of narrative we should aspire to (as well as trying to justify spending so much time consuming those stories).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/0*QRrSfZVFjIj09neG" /></figure><h3>This was a Heist story all along.</h3><p>I might not be able to kill this myth outright, but I can propose another narrative to try and replace it! So I’m now gonna argue that stories such as the <strong><em>Ocean’s Eleven</em></strong>, <strong><em>La Casa de Papel</em></strong>, <strong><em>Mission Impossible</em></strong>, or the <strong><em>Fast and Furious</em></strong> series all give interesting lessons for how we should think about game development.</p><p><em>Side note — You might be arguing that </em><strong><em>Mission Impossible</em></strong><em> or </em><strong><em>Fast and Furious</em></strong><em> movies are not heist movies, as they are not about heists, and it’s okay, but you’re wrong.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*UpUC1q-5_w6mZOt9" /></figure><h4>1. It’s about the team</h4><p>The first step of all good heist movies is about one thing: Bringing together the right team for the right job.</p><p>We do not just follow one lone wolf who doesn’t need anyone and can solve every situation; instead, we follow a diverse cast of characters who all have different skills and have to rely on each other to survive and succeed.</p><p>And you might note that even in heist movies, among all those different characters, the leading one is often still the archetype of a genius who comes up with the plan. And while it’s sometimes true, yes, those stories still have some major differences.</p><p>The first one is the plan is often decided or at least challenged by the team; they all have a role to play in it, and it is their combined skill and trust for each other abilities that bring success.</p><p>And the reason why the team and the trust they put in one another is so important is the second difference:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*o17odqG4bmkYtdsR" /></figure><h4>2. The plan always fails</h4><p>Failure, unpredictability, and overcoming challenges are a part of every good heist.</p><p>Improvisation, compromises, relying on each other expertise to identify new options as the problems arise, one after another. You won’t have the time nor the resources to make the plan work as it is without changes, so there’s only one way to go about it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*_HgzBgz5I-2GoqdK" /></figure><h4>3. Grab what you can before time runs out</h4><p>There is no such thing as a perfect heist. Just like there is no such thing as a perfect design or a perfect game. You set an objective for your team, and you make the most of the time and budget you have to bring the project to as much quality as possible until it is released.</p><p>If you set your expectations on only releasing a “perfect” project, one that matches exactly the ideas you had for it, you’ll never release anything, or worse, you’ll be forced to release something in a stage that is far from complete. And there is simply no going back from that.</p><p>So keep what you need, cut what is slowing you down, and make sure you move forward.</p><h3>Conclusion</h3><p>It’s been a long journey (way too long — I’m sorry, I swear I tried), and at the end of it all, I want to remember and leave you with this:</p><p>Anyone can have ideas. Not just designers. And it is not the job of the designer to have ideas. <br>A good designer sees those ideas as what they are: tools. To solve problems. Facing the problems and failures posed by those ideas does not make us bad designers; it is what makes us designers.</p><p>Because in the end, it’s not about being a lone genius, and it’s not about being better than the others or being the one whose idea works. In the end, only one thing matters…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/550/0*GdWD63QwVP6iSjHg" /></figure><p><a href="https://docs.google.com/document/d/1i11u0Dc9cPSDVUylaq1b7pYk7NU0xQ9O2qoNnIHIWCE/edit?usp=sharing"><strong>Credits here</strong></a><strong> <br></strong><em>(because of course, and like everything, I couldn’t have done this without the work and help of many other people)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=42b9aeaf45fe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Ideas make for Bad Designers — (Part 2 of 3)]]></title>
            <link>https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-2-of-3-58ad72f98556?source=rss-104a172a987d------2</link>
            <guid isPermaLink="false">https://medium.com/p/58ad72f98556</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[game-industry]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[game-design]]></category>
            <dc:creator><![CDATA[Léo Lesêtre]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 22:13:07 GMT</pubDate>
            <atom:updated>2023-10-01T22:14:17.572Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XTmFqiPFF2z7WiRisfxtYw.png" /></figure><h3>Good Ideas make for Bad Designers — (Part 2 of 3)</h3><h4>A love letter to people who pointed out my mistakes and helped me get better.</h4><p><em>Game designer</em>, or simply <em>designer</em>, is not an easy job to explain. For how many times I’ve tried to explain it to my parents and their friends, I know it is a way more abstract activity than Artist, Programmer, or even Producer. I usually describe it as “defining the rules of the game, the way the different systems should behave and interact, in order to create the intended experience for the player”. Sooo clearly, it doesn’t dispel all questions.</p><p>And so I get why you could try to reduce it to “imagining games” or “having ideas for games”. But as we explored in <a href="https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-1-or-3-1a94fdbcf12e"><strong>part 1</strong></a>, there is little base in reality, if any, to support the belief that the role of designers is to have ideas or that successful projects are based on good ideas.</p><p>And we could stop here, but I argue that we should actively challenge this perception. We should not settle for this oversimplified version of reality because this perception shapes more than just how we explain design. It shapes what aspiring designers expect, what we expect from them, and how we perceive the role of all the other actors of the industry as well.</p><h3>Failing to live up to the story.</h3><p>Remember when I said becoming a game designer, things never clicked how I hoped they would? Well, here’s the part I haven’t told you about:</p><p>This made me terrified.</p><p>For months, I refused to ask for help, to show my work early for fear of being judged. For fear of being uncovered as a fraud. What would they think of me if they realized my ideas didn’t work? That I sometimes had no ideas? This led to catastrophically bad decisions, terrible designs, and those mistakes being more exposed and visible than ever as a result, which fed into the negativity cycle of doubting myself and my abilities.</p><p>Hopefully, it eventually got better. My design began to work as I hoped it would. On the first try, sometimes. My mistakes were smaller and easier to address. So what happened? I got used to it? I got more experienced? None of that.</p><p>No, what changed is I got help. I was lucky enough to be a part of one of the most amazing teams I have ever worked with, and they realized that I needed help even when I myself would not admit to it. And they provided that help without any judgment. They showed me the way by showing me their work and asking me for feedback. I realized that even designers with almost ten years of experience still made mistakes and benefited from feedback and help. And so I slowly started to heal from these toxic beliefs I used to hold.</p><p>And I know I’m not the only one who has experienced this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*FcMaM7WlDA1pdcQl" /></figure><h3>This story is bad for everyone.</h3><p>Stories and myths we believe and repeat are not just that. They inform a vision of reality that is easier to grasp, less complex than the real thing, and often more satisfying and compelling in its structure. Because of this, they become easy and convenient reference points about a topic, a historical event, a concept, or anything else.</p><p>This, however, can become problematic when the myth becomes the only or the most dominant reference point for people who do not know the reality and haven’t experienced it for themselves. At this point, the story actively clashes with the reality it is about, as it shapes people’s expectations and actions based on what they<em> believe</em> to be an accurate representation of reality.</p><p>And from my own experience and many testimonies I heard, I am convinced this myth is doing exactly that. It is informing an inaccurate representation of what game development looks like, reinforcing counterproductive behaviors and practices and unfair expectations, impacting everyone, from designers, to the team, to the industry as a whole and the project itself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*a5dov4LFtTMdKstV" /></figure><h4>Bad for designers</h4><p>You might think this story is actually very comforting and ego-boosting for designers. After all, they’re the heroes in this story; they’re the people being looked up to, the ones getting credited for the success of the game.</p><p>But no matter how flattering it might sound, I want to argue that <em>having good ideas</em> is a very unfair and discouraging standard to hold or to be held against. It is most often seen as an innate quality and highly dependent on luck. It is not something you can train or gain control over. And when we only judge the idea, it is as much a judgment of the person having the idea as it is of the idea itself. The fact it is a compelling narrative might make it even more destructive to young designers.</p><p>In <a href="https://www.hachettebookgroup.com/titles/timothy-d-wilson/redirect/9780316051903/"><em>Redirect: Changing the Stories We Live By</em></a>, psychologist <strong><em>Timothy D. Wilson</em></strong><em> </em>highlights how we shape our actions to preserve the narratives we tell about ourselves. And how when we fail to meet those criteria, we feel like we don’t live up to who we thought to be. <a href="https://psycnet.apa.org/record/1982-26799-001">Studies he and his team conducted</a> show when met with failures, students who attribute success to innate qualities like intelligence tend to think that they are simply not intelligent enough to succeed and are then more likely to give up and drop out.</p><p>If the success of the experience relies solely on the idea, then if it doesn’t work, it means it was based on a bad idea. If it was based on a bad idea, then I had a bad idea, and I am not as good a designer as I thought. If I’m not a good designer, I’ll never have good ideas, and I have no place here.</p><p>I’m still drawn to this idea even today; I still doubt myself when I propose something and hear someone else instantly demonstrate how flawed it is and make a perfectly viable counter-proposition. But now, I fight back against this feeling. Because I know that every time someone shows me a mistake I made, I become a better designer as a result. Because, and that’s the real important lesson here, having ideas is NOT my job. My job is to fix problems.</p><p>The true job of a designer is about problem-solving. Good Ideas make for Bad designers because you only progress and get better when you face challenges and work to solve them. You become a designer when the idea fails and succeed when you MAKE it work. Not because it naturally works.</p><p>Also, remember when I said the myth of the lone genius was not unique to games or design and existed in science and other domains also? Well, <a href="https://www.nobelprize.org/martin-chalfie-npii-canada/">it’s destructive here, too</a>, it seems.</p><p>And if this perception of creation puts a lot of pressure on the shoulders of designers, it also deprives this credit of all the other members of the team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/0*vJAJXXcWbiKrmRwr.gif" /></figure><h4>Bad for the team</h4><p>Ideas are uncollaborative by nature. A plan, a design, a solution, all those things can be crafted by many people. But when we speak about ideas, we mean the first impulsion someone got, a proposition just one individual made. And so, when we praise the idea, we praise this individual contribution only.</p><p>It turns creation into a zero-sum game. If two or more people propose ideas and one works, then it means this person and only this person solved the problem. This is a heavily egotistical and self-centered approach to what is supposed to be a team activity. It makes us less likely to accept feedback and propositions from other team members because we don’t want to feel useless, and worse, it often makes us happy to see other people’s ideas fail because it makes us feel useful and justified.</p><p>But none of that is true. Providing the feedback that will help identify the issue, participating in the discussion, proposing solutions, implementing it, and testing it to see if it actually solves the problem, why should we celebrate one of those steps above all else? Well, because this is how we (most often) envision creation.</p><p>But even among all the jobs undermined by the belief that their success relies solely on ideas, one is the most criminally underestimated: the role of the testers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/0*7HHwsrAcUFwRYMz1.gif" /></figure><h4>Bad for testers, especially</h4><p>A recurrent element among all the success stories we’ve looked at is how the turning point in developing all those projects always comes with acknowledging the project’s problems. Recognizing and working toward fixing those mistakes is demonstrably what made those projects work, not the initial idea they were based on. And that’s why it is so unfair that the people whose job it is to identify and point out those problems are the ones whose jobs are seen as the less valuable.</p><p>I remember reading many articles when I was trying to get into the game industry about QA Testing being an entry-level job toward becoming a <em>real</em> game designer (strangely enough, I also remember many articles saying the same about level design). Today, I feel like it is much more understood that level design, game design, and other specialties are simply different disciplines, each with their own set of skills and challenges. But the same cannot be said for QA testing yet. I still occasionally stumble across “inspirational” stories of QA Testers being so good at their job that they’re promoted to Designers.</p><p>The thing is, most QA Testers I’ve worked with indeed expected to move on to another job at some point. And I can’t blame them, seeing <a href="https://kotaku.com/quality-assured-what-it-s-really-like-to-play-games-fo-1720053842">how they’re being treated</a> and seen as expandables in most companies. I’ve worked at companies whose entire test team was comprised of interns (even the team lead), and others where we simply didn’t have any testers (so I can really appreciate the value a good tester brings to a team, believe me). And what’s making my blood boil is looking at all the stories we’ve mentioned so far: they are always the unsung heroes. Not only do they get no credit for their input to the game, but they get most of the blame and hate from the players whenever something goes wrong.</p><p>In every story, the turning point that made the game a success didn’t come with the genius lead of the director or the inventive ideas of a designer. No, it always came with feedback highlighting the issues to be addressed. And of all the team members, the testers are the most likely to identify those problems. They know the game better than anyone else but have a distant enough vision to avoid most of the biases designers have for their own work. Whether they are playtesters or QA testers, their feedback demonstrably impacts the game and its direction. And it’s a shame that the role is not more credited, paid, and recognized for its value.</p><p>Because it leads to invaluable people being exploited and burnt out to the point of leaving the industry, which is both unfair and a loss for them, the team, and the project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*b-ypC9yqp9JJQ4hK" /></figure><h4>Bad for the industry</h4><p>Finally, and this seems almost too obvious to say at this point, but when we only praise the people at the top and neglect to mention the people working under them, we praise and present a portrait of what a “good designer” looks like that is incredibly narrow. We reinforce the biases that make people of a certain gender/race/else more likely to get management jobs by only celebrating people who match those criteria as responsible for the success of their projects. Representing the whole industry only by the 1% that sits at the top.</p><p>The game industry is already lacking a lot of diversity <a href="https://www.youtube.com/watch?v=Xz6NyOaP5xg&amp;t=1s&amp;ab_channel=PeopleMakeGames">in more ways</a> than one. And while this is clearly not solely responsible for this, it doesn’t do anything to make it better either. And I want to clarify that this doesn&#39;t say anything about whether the people we praise are skilled and if they are indeed giving all they have to the project. I’m not saying those people do not deserve to be praised and recognized for their work.</p><p>But by only crediting those few people, neglecting all other persons and factors contributing to success, we miss how necessary they are to reproduce this success. We evaluate a project&#39;s potential based only on who is leading it and not who are building it.<br>And this isn’t good for anyone because those people we praise are, in fact, as fallible as anyone else.</p><p>I am now convinced this belief is unhealthy and leads to unhealthy expectations and practices that make the work of everyone more unnecessarily difficult.</p><p>But even if you do not care for workers, for unfair expectations, uncredited and undervalued work, and all you care about is the game itself, this, is still a problem. This is still something to be concerned about because of the amount of control and trust we put in the hands of people who ultimately cannot make the success of a project on their own.</p><p>And this is what I intend to demonstrate in <a href="https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-3-of-3-42b9aeaf45fe"><strong>part 3</strong></a>. Why this is also ultimately bad for the game itself, and thus, for the players as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58ad72f98556" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Good Ideas make for Bad Designers — (Part 1 or 3)]]></title>
            <link>https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-1-or-3-1a94fdbcf12e?source=rss-104a172a987d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a94fdbcf12e</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[game-industry]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Léo Lesêtre]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 22:12:21 GMT</pubDate>
            <atom:updated>2023-10-01T22:13:33.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VVgbIv4ts9XjDeRXHBfVLg.png" /></figure><h3>Good Ideas make for Bad Designers — (Part 1 or 3)</h3><h4>A love letter to mistakes.</h4><p>A few years ago, when testing a prototype made during a jam by a group of coworkers, I noted the game was cool but had some pacing issues. One of the programmers then noted that he wished they had a designer on the team. To which another instantly interjected, «I don’t see why; we had a lot of ideas by ourselves.»</p><p>Okay, so, first of all, ouch, obviously. Surely designers do more for a project than just having ideas and writing them down into documents that no one wants to read, right? …right?</p><p>This perception of the designer&#39;s role (having ideas) is quite common, even among aspiring and young designers. As a matter of fact, it is one I have held for years. One that made my job more difficult every time I did. And yet, I still happen to be drawn to it, to doubt myself and others around me based on this belief. So I’m writing this to convince myself. Convince myself that this belief is indeed false, misguided, and counterproductive. And if I’m lucky, this might convince a few people who might need to hear it, too.</p><p>In this writing, I’ll discuss my experience as a Game Designer, but I believe this applies to all forms of design and creation more generally. Ideas are a part of every creative activity and are commonly perceived as complementary to execution. And it is most generally accepted that execution is the most determinant part of every creation.</p><p>And yet, the notion of <em>good</em> and <em>bad ideas</em> and their role in design is still as present as ever. So why do we still believe this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/533/0*CTC86iw6E6flkuev" /></figure><h3>Every story needs a hero.</h3><p>Games are great (very controversial statement, I know). When we play a game, especially one that moves us, one that makes us want to become a designer ourselves even, we see the final product, the destination. We do not see the challenges, changes, compromises, and failures that happened during the execution. The best experiences feel complete, polished, and made of organically connected systems and features. Everything is as it should be, and you wouldn’t want it any other way. You couldn’t even imagine it any differently, in fact.</p><p>So it makes sense to see the final product as the embodiment of an idea, as the final form of a concept that was as organically connected. But I think there is another reason for this belief: Those games are often presented as the materialization of one man’s genius plan. <br>And honestly, it is a compelling narrative.</p><p><strong>Miyamoto</strong>, <strong>Miyazaki</strong>, <strong>Kojima</strong>, <strong>Spector</strong>, <strong>Notch</strong>, <strong>Ueda</strong>, <strong>Bleszinski</strong>, <strong>Molyneux</strong>… we all have different references, but I&#39;m sure you&#39;re familiar with at least some of those names, if not all. They’re often celebrated as geniuses, superstars, or both. The one person who defines a game, imagines it, and whose ideas can make or break a project. They are role models for aspiring designers.</p><p>Although those people&#39;s titles are more often Game Director, or Creative Director than Designer, design is indeed at least part of their job, and it is how we see it anyway. We see them as the people who pitch, who have <em>THE ideas</em>, who envision what the game should be about and how it should be. We see the game as the materialization of their vision and their vision only.</p><p>Of course, this is not unique to games; the lone genius archetype is a <a href="https://www.bbc.com/future/article/20120316-the-myth-of-the-lone-genius">common and celebrated trope</a> in science and in popular media: Leonardo Da Vinci, Albert Einstein, Thomas Edison, Sherlock Holmes, Tony Stark, Rick Sanchez… fictitious or not, they set an example for what skilled persons look and act like.<br>- <em>This might become problematic later.</em></p><p>And that’s for this exact reason that it might come as a shock to some to learn that it’s entirely bullshit :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*Kl2Wz8gh7ahEu2V5" /></figure><h3>This story is bullshit.</h3><p>During my many years as a game designer, even during my three years as lead game designer, I never had ideas so great that they worked on the first try. I never came up with concepts that had exactly the impact I thought they’d have. Things never clicked as I thought they would.</p><p>Even more revealing, the most successful gameplays I’ve worked on are generally the ones I had fewer ideas for, the ones that had the most input from other team members, designers, as well as programmers, artists, and testers alike.</p><p>But maybe that’s just me, right? Maybe I’m not the best designer; maybe I’m the odd one out here. Again, ouch, but it’s an entirely fair point to make. But if it is all about the subject and not execution… how do we explain <strong><em>Supersonic Acrobatic Rocket-Powered Battle-Cars</em></strong>?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/0*J8-eLohmgv_JdkT4" /></figure><h4>SARPBC vs. Rocket League</h4><p>If I were to ask you if “A soccer game with cars” is a good idea, most people today would answer yes, I’m sure, because <strong><em>Rocket League</em></strong> exists and exposed to the world how fun it can be. But it wasn’t always the case.</p><p>Sometime in 2009, <strong><em>SARPBC</em></strong> (I’m not saying the name in its entirety again), a game based on the exact same idea released and was met with… not that much positive attention. <em>Gamespot, </em>in <a href="https://www.gamespot.com/reviews/supersonic-acrobatic-rocket-powered-battle-cars-re/1900-6228858/">their review</a> of the game, gave it a 6/10 and declared: “<em>Playing soccer with cars isn’t all that fun</em>”.</p><p>Of course, it became clear six years later that the problem wasn’t the idea of playing soccer with cars but its execution, when <em>Gamespot</em> would <a href="https://www.gamespot.com/reviews/rocket-league-review/1900-6416186/">then report</a> “<em>the promising concept of combining two wonderful things — cars and soccer — is equally magnificent in execution</em>” and give <em>Rocket League</em><strong> </strong>a 9/10.</p><p>Oh, and just so we’re clear that it is indeed the exact same idea being executed on both attempts, <strong><em>Psyonix</em></strong>, the studio behind <strong><em>Rocket League</em></strong>, is also responsible for <strong><em>SARPBC</em></strong> six years earlier. They executed the idea, failed, learned from their mistakes, and tried again, this time to great success.</p><p>Okay, so this doesn’t seem to be just me. Execution is indeed a big part of it. But this is the work of an entire team; maybe the idea wasn’t as well formed the first time they tried. And the studio doesn’t have any genius superstar at its head, so this doesn’t say anything about the famous designers we cited earlier. Yet.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FjYt9DcbJ0X1VOiKbmW%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FjYt9DcbJ0X1VOiKbmW%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FjYt9DcbJ0X1VOiKbmW%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="183" frameborder="0" scrolling="no"><a href="https://medium.com/media/36312889ba4764361a459f529a85df1a/href">https://medium.com/media/36312889ba4764361a459f529a85df1a/href</a></iframe><h4>Warren Spector and Deus Ex</h4><p><strong><em>Warren Spector</em></strong> is often considered the father of <strong><em>Immersive Sim</em></strong> games. A genre that is, without a doubt, my favorite. No need then to say how highly I regard the work of <strong><em>Mr. Spector</em></strong>, especially for the game that pushed the genre to where it is today: <strong><em>Deus Ex</em></strong>.</p><p><strong><em>Immersive Simulation</em></strong> is a genre centered entirely around player agency, and <strong><em>Deus Ex</em></strong> is the game that first drafted the current formula combining gameplays for Sneaking, Shooting, or Talking your way through most situations the game throws at you (as well as box stacking, a whole lot of box stacking).</p><p>The combination of gameplay and systems in the game is something <strong><em>Warren Spector</em></strong> seemingly always believed in, and yet he makes no secret about the fact that it took several iterations to bring the game to where it is now. He talked extensively about the process of bringing the game to life at a <a href="https://youtu.be/tffX3VljTtI">GDC Conference</a> he gave in 2017.</p><p>“<em>By September, we were done. Except we weren’t. The game was not good enough; it wasn’t ready to ship. […] We brought real people to play the game; I call this particular milestone the </em><strong><em>wow those missions suck</em></strong><em> milestone. We had a lot of work to do.”</em></p><p>He really hammers this point, saying:<br>“<em>Be open to change. Anybody who tells you that when you get off pre-production, you’ve got a script and nothing changes has never made a game, right?</em>”</p><p>The team remained focused on their objectives and the ideas the game was based on but used it as a compass and not as strict guidelines. The designer says of the final product: <em>“Three years later, here it was! Every single detail had changed, but in spirit, it was exactly the game I was hoping to make.”</em></p><p>Yet again, it was a work that took many iterations to make the idea it was based on viable and satisfying to engage with. But video games are demanding productions; they require an entire team, a serious budget, and operate on tight planning. So obviously, compromises have to be made, and with several people participating in the game creation, the final product naturally reflects those different points of view even slightly. What about designers who work alone? What about board game designers?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*UOLzt31r4Q366okI" /></figure><h4><em>Donald X. Vaccarino</em> and Dominion</h4><p>Apart from the artists who often join the project, usually after the game is already proven to work, board game designers often work alone on their project. Therefore, the success of their game must surely reflect the quality of their ideas.</p><p>And talking about success, even among board game designers, <strong><em>Donald X. Vaccarino</em></strong> is an anomaly. He designed two games, <strong><em>Kingdom Builder</em></strong> and <strong><em>Dominion</em></strong>, both of which received the highly regarded <a href="https://www.spiel-des-jahres.de/en/"><em>Spiele Des Jahres</em></a> price (for best game of the year), and the latter of which did nothing less than summon the entire deck-building genre into existence.</p><p>Released in 2008, <strong><em>Dominion </em></strong>is minimalist, has depth, and entirely relies on its deck-building mechanic: using card effects to obtain new cards, thus gaining new options, to obtain more cards again, and this each turn. This bite-size complexity addition to the game as it goes on is so brilliant and self-contained that it has appeared in <a href="https://boardgamegeek.com/boardgamemechanic/2664/deck-bag-and-pool-building/linkeditems/boardgamemechanic">hundreds if not thousands</a> of other games since its release. The fact that no one seemingly thought of it before its inception and it has since been declined and used in so many games surely means the designer had this brilliant idea of a mechanic as it is. True lightning in a bottle.</p><p>This is exactly what <strong><em>Gabe Barett</em></strong> tries to find out in his book <a href="https://www.kickstarter.com/projects/gabebarrett/board-game-design-advice-2nd-edition"><em>Board Game Design Advice from the Best in the World</em></a>. In the interview with <strong><em>Mr. Vaccarino</em></strong>, he opens with this simple question: What is the favorite mistake the designer ever made?<br>And predictably, the answer is… Dominion… wait, what?</p><p>So apparently, while designing a game called <strong><em>Spirit Warriors II</em></strong>, he imagined a combat system in which a deck of cards represented each hero&#39;s actions. He iterated on the system, wanting the heroes to get better with time. So he changed it so that when the heroes leveled up, they could add better cards to their decks. However, playtests showed the game was too slow and complex for the players to enjoy, but the leveling part was fun. So that’s the only part he kept and reworked it into the game we know today as <strong><em>Dominion</em></strong>.</p><p>So not only was the initial idea not that brilliant or special, it wasn’t even… fun. Again, what turned it into the amazing experience we know and love today was making a mistake, having people test it, acknowledging it, and working to fix it and make it the best it could be.</p><p>Ultimately, this seems to be the real connection between all those games rather than the type of idea they’re based on.</p><h3>Ideas are easy.</h3><p>And it makes sense when we think about it. Because that’s what ideas are; they’re goals, destinations we ought to reach, objectives we set for ourselves and the game, but they do say nothing about how to get there. They’re very basic and vague concepts, and they only lead to what can be described as first drafts. And to quote <strong><em>Ernest Hemingway</em></strong>: “<em>The first draft of anything is shit.</em>”</p><p><strong><em>Ernest Hemingway</em></strong> might not have been a game designer (that we know of), but he‘s not the only one to express this opinion. Just to throw more authoritative arguments, <strong><em>Jamey Stegmaier</em></strong>, designer of <strong><em>Scythe</em></strong> and <strong><em>Viticulture</em></strong>, said (still in <a href="https://www.kickstarter.com/projects/gabebarrett/board-game-design-advice-2nd-edition"><em>Board Game Design Advice</em></a><strong><em> </em></strong>): “<em>Don’t consider a game designed until you’ve playtested and iterated dozens of times. […] I thought that “designing a game” was thinking of an idea, writing out the rules, [and] creating a prototype […] I wish I had realized that the real work in designing a game is what follows that first prototype.</em>”</p><p>To circle back around, during the conference, <strong><em>Warren Spector</em></strong> declared about having to shelve his initial ideas for <strong><em>Deus Ex</em></strong> that “<em>Ideas are easy. Anybody that tells you that ideas are hard or you should hold on to your ideas because they’re so amazing and valuable is kinda nuts.</em>”</p><p>Ideas are tools; they can be helpful by giving the designer and the team a direction they’re working toward, but they carry no intrinsic values on their own. Some ideas will inevitably be easier to turn into functional products than others, but the goal is never to have the idea work! It is to create the intended experience for the players, no matter how, no matter based on what ideas. Ideas are expendables; they’re just insights for potential solutions that <em>might </em>work and <em>might</em> have the expected effect. It makes no sense to value them more than the final experience, to give them more attention than the problems they come with.</p><p>It’s based on those reasons and looking at those examples, among others, that I am today absolutely convinced that this story is indeed nothing more than a myth. That a designer&#39;s role is not to have ideas and that ideas are not responsible for the success of a project.</p><p>And it doesn’t surprise me this much, to be perfectly honest. Myths are everywhere, in all parts of our lives, and especially around activities that summon the kind of passion and fantasies games do. As we said, they make for good stories. And they can still carry meaning, lessons, and useful insights.</p><p>But not this myth, unfortunately. I am convinced this belief is actually harmful. Harmful to designers, the other team members, the project, and even the industry and all the people who are a part of it. <br>And I’ll explain more specifically why in <a href="https://leolesetre.medium.com/good-ideas-make-for-bad-designers-part-2-of-3-58ad72f98556"><strong>part 2</strong></a> of this essay.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a94fdbcf12e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ico, disruptive game design, and experiences that live forever.]]></title>
            <link>https://leolesetre.medium.com/ico-disruptive-game-design-and-experiences-that-live-forever-59db0f2a9cf3?source=rss-104a172a987d------2</link>
            <guid isPermaLink="false">https://medium.com/p/59db0f2a9cf3</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[video-game-industry]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[live-games]]></category>
            <category><![CDATA[game-design]]></category>
            <dc:creator><![CDATA[Léo Lesêtre]]></dc:creator>
            <pubDate>Mon, 19 Dec 2022 05:01:47 GMT</pubDate>
            <atom:updated>2023-01-08T14:24:12.567Z</atom:updated>
            <content:encoded><![CDATA[<p>100 updates later. Why we enjoy games, why we stop, and how live game design might bring us back.</p><p><em>This writing is not a review of ICO, but it still describes the plot in its entirety. It also talks about some plot points of Shadow of the Colossus and The Last Guardian — spoiler warning.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0PSpV62sqoEkwH2C40Szsg.jpeg" /><figcaption>ICO cover art — Fumito Ueda</figcaption></figure><p>Some games just stay with you. You don’t simply turn off the game and move on when the credits roll: they change you, and they change the way you see other games, forever. And once you’ve encountered them, you become restless for being able to experience this feeling again.</p><p>This is the story of the game that changed me, changed my entire view of games, what they could be, and made me want to become a game designer in the first place. This is also the story of how I now try to bring this feeling back as well on the games I work on.</p><p><em>Ico</em> was this game for me. <em>Ico</em> is about being locked together in a castle and trying to find a way out. But escaping seems impossible. The game opens in the densest, deepest, and darkest of forests, and takes what seems like hours to reach the fortress by horse, then by boat, and finally by foot. When you finally enter the castle, as imposing as one can be, you’re then sealed inside an urn, and the game locks the door behind you without looking back. Even the game&#39;s very first moments make no secret about the fact that there is no such thing as a way back. Not unchanged.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FLpILyt0uzWk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DLpILyt0uzWk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FLpILyt0uzWk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8e10af7e2c79036d1f0589d79e0b2137/href">https://medium.com/media/8e10af7e2c79036d1f0589d79e0b2137/href</a></iframe><p>Another thing the game is very direct about is…</p><h4>Games are conversations</h4><p>From pen and paper and tabletop games to their evolution as text-based adventure games to their modern incarnations, at its core, the basic relationship between player and game has remained the same: the game presents the player with a situation it describes with clues of what can be done and how. The player then proposes an answer to the situation, before the game describes the consequences of this action. Video games no longer require a game master to express themselves or even a text-based interface; the situations and consequences simply appear on the screen. But the challenge at the heart of the relationship is still the same. For the player, it is understanding what the game expects and responding accordingly. And for the game, it is to give enough indications and to be clear to the player about what happens and why. Because despite all games being conversations, players and games do not speak the same language.</p><p>Few games, however, are as transparently conversations as the ones from <em>Team Ico</em>. Silent conversations; apart from the occasional narration, those games rarely have dialogs or even text at all. But they are, unequivocally, conversations. Like gods descending from their pedestals and disguising themselves as humans, those games inhabit their own world; they hide among players. They mascarade as characters you interact with and talk to, and when you do, they answer back to you, but in their own language.</p><p>Despite the game being named <em>Ico</em>: the name of the boy you play as; <em>Yorda</em> is the real avatar of the game. She’s your companion for the game, a young girl trapped in a cage of her own. After managing to free her, you try and talk to her, but you speak different languages. Dialogs are subtitled and display cuneiform symbols, highlighting the fact that you don’t understand each other, yet. Understanding <em>Ico </em>is understanding <em>Yorda</em> and learning to trust each other.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5OuJF4ojNPVeaP7ahccLdw.jpeg" /><figcaption>Yorda early character design concepts — <em>Team Ico</em></figcaption></figure><blockquote>“Kids are playing everywhere, all the time, and often playing games we do not quite understand. They play and learn at a ferocious rate. We see the statistics on how many words kids absorb in a day […] Many believe this shows language is built into the brain and that there’s something in our wiring that guides us inexorably toward language.”<br>- Raph Koster</blockquote><p>Game designer<em> Raph Koster</em> speaks about this relationship between game and player in his book <em>A Theory of Fun</em>. A topic he analyses through his experience working on games like <em>Ultima Online</em>, <em>Star Wars Galaxies</em>, and <em>Everquest II</em>, or even watching his own children play and learn new games. He describes evolution as the player identifies and decodes the patterns of the game, like kids learning to identify new words and their meaning as they encounter them.</p><blockquote>“Games are puzzles, they are about cognition, and learning to analyse patterns.”</blockquote><p>But first conversations are hard; the first few words you say to another are critical and often run the risk of being clumsy and leading to misunderstanding. You know what you want to say, but you need to say it in a way that will speak to your interlocutor so it resonates with what they told you before. And when it fails, your attention wanders, you stop listening, and words fade into the background noise of the room.</p><p><em>Ico </em>is often described as a “weird” game and<em> </em>walks a difficult line; its<em> </em>sharpest shard of poetry is also its less friendly aspect. Its characters do not react like systems: they behave like, well, like people, kids even. Even when you precisely know what you’re supposed to do and you do everything you can to execute it, characters take time to understand, to react, to move. The<em> </em>animation absolutely sells it too. The hazardous climbing of the chain, the light stumble when you grab <em>Yorda</em>’s hand and start running without warning, the exhausted fall of their heads when you finally find a bench on which you can rest and save your progression. It all feels so real and alive.</p><p>But at times, this lack of direct control over what you’re trying to achieve can feel like you’re sitting next to the person holding the controller telling them what to do. And this can be one of the most frustrating experiences ever. Engaging with a new game is always a risk: you can never be sure that you’re gonna get enjoyment out of the efforts you’re putting in through what is arguably the most demanding part of the experience, the initial learning gap.</p><p>You need to work together to survive and escape, but working together is only possible when you understand each other. Like <em>Yorda</em>, the game won’t simply give you the answer and tell you what you’re supposed to do, not in your own language, at least; that’s a journey you have to take for yourself, and when I first experienced the game myself at the time, I couldn’t. Maybe I was too young to understand. Surely I wasn’t paying enough attention. Signs and words faded, and I got submerged by the noise.</p><blockquote>“When we meet noise, and fail to see a pattern in it, we get frustrated, and give up. […] Noise is any pattern we don’t understand.”</blockquote><p>I sealed <em>Ico</em> back in its box, locked the door behind it without looking back, and left it on the shelf for the next eight years.</p><h3>Holding On</h3><p>Being left alone doesn’t initially seem like it would be a struggle in <em>Ico</em>. The boy<em> </em>has all of the capacities that make a video game character able to survive on his own. He can run, jump, climb, and of course, fight. The one thing he cannot do is open the doors of the fortress. That is an ability only <em>Yorda</em> possesses; this is, after all, her world, not yours. The castle recognizes her as a part of itself. She was born within those walls, but you are a stranger here. Navigating the corridors, solving the puzzles of the different rooms, fighting, none of it is particularly difficult, but you need to do it together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*R-VhHyrpeRz1rMNg-LsTag.jpeg" /><figcaption>Ico move set concept document — Team Ico</figcaption></figure><p>The shadows guarding the castle cannot kill you, and they don’t even attempt to; they merely push you to the side to get to your companion and take her away. Apart from the occasional lethal falls, this is the only way to really get a game over, to get separated from one another. You’re locked together, and you have no other option but to both escape.</p><p>That is the reason why the most unique and important of <em>Ico</em>’s abilities is to call <em>Yorda</em> and hold her hand when she’s close. Once you’ve experienced this loss, <em>R1 </em>gets carved into your right index, and it feels like your skin gets torn off when you have to let go of the button and of her hand. Even just entering a room where <em>Yorda</em> cannot follow fills you with dread as it is taking the risk of attracting shadows, and you’ll count every second until you’re back together. That is what makes the game so compelling, caring for those characters as you discover and get closer to them. This isn’t an easy experience to grasp, but this is the part of the game that is still unmatched to this day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JrVV2iMOyu_8sz6ZiICbpw.jpeg" /><figcaption>Ico hand-holding feature design documents — Team Ico</figcaption></figure><blockquote>“Noise is any pattern we don’t understand.<br>But once we see a pattern, we delight in tracing and seeing it reoccur.”</blockquote><p>This is where the idea of enjoyment of the game, of “<em>fun</em>”, depending on and even resulting from the comprehension of the game, comes from. The pleasure of the experience comes from the decoding of its patterns and its <em>language</em>, resulting in a progressive gain of mastery over it. And this is not a groundbreaking idea either.</p><blockquote>“Fun is the emotional response to learning.” <br>– Chris Crawford</blockquote><p>Ten years after its original writing, <em>Raph Koster</em> goes back to <em>A Theory of Fun</em> and summarizes the original lessons as such, as he proceeds to cite many psychologists, philosophers, and designers who came to the same conclusion.</p><blockquote>“The idea was, games are systems built to help us learn patterns. And fun is a neurochemical reward to encourage us keep trying.<br>This was not a new idea.”</blockquote><p>This is where the magic of <em>Ico</em> lies, this rhythm, this synergy between the characters, how they don’t react like systems, but like humans, imperfectly, and so you have to pay attention, look for signs and learn to work with the game. But it feels so much more rewarding to be able to seamlessly converse with the game, to achieve what you want, together. It creates a beautiful dialog, poetry that carries the entire experience; at times, it feels like a dance, player, and game, in perfect harmony, progressing alongside one another.</p><p>It took eight years, and also being locked inside during a thunderstorm with nothing but my old PS2 and the game, for me to be able to finally get over my initial struggle and experience the true potential of the game. But once I did, I couldn’t let go of it anymore. I felt so wrong about misjudging the game on my first attempt that I decided right there and then to become a game designer myself to explore the types of experiences games could create. I devoured the game content until I ultimately reached the ending and the point upon which the game left me wanting more, despite having nothing more to learn from it.</p><h3>Drifting apart</h3><p>Games of <em>Team Ico </em>are rarely remembered for how they end; they’re remembered for how they play. Those games understand that this is about the journey, about the process of learning, getting better, and progressing. They know that once arrived, there is nothing left to be said. All those games end, with some form of separation, between the player and the game’s avatar. A rupture of the link between the two which is all too relevant at the end of those stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*j3W54sgxj3G9jkHkOwBt5g.jpeg" /><figcaption>Ico separation scene concept document — Team Ico</figcaption></figure><p><em>Ico</em> is no exception, of course. At the moment when you finally see the land on the other side of the bridge, after spending so much time making your way out of the castle together, when you believe there could be a way back… everything is ripped away from you. You’re separated, definitively separated. <em>Yorda</em> is turned to stone. And though you can still escape, you’re left to wander the final levels of the game on your own. Leaving a part of you forever trapped within the walls of the castle. Never to be freed.</p><p>It’s a feeling that, like a lot of players, I know too well. It is inevitable, with every game I love, there’s inescapably a drift. You fall in love with a game, you play it, and get better at it, so much that you inevitably reach a point where the game has nothing new to offer to challenge you, or you don’t feel like you can get any better at it anymore.</p><blockquote>“Noise is any pattern we don’t understand. But once we see a pattern, we delight in tracing and seeing it reoccur. […] But you’ll only play until you master the pattern.”</blockquote><p>Just like not understanding the language of the game will deprive you of enjoying it; so will knowing it so well you already know what to answer without having to think about it.<br>Because at the core…</p><h4>Games are about making choices</h4><p>Analyzing, thinking, doubting, and trying, are fundamental components of the enjoyment of the experience. All this is lost when you know the game so well that there is no doubt left about what choices to make in which situation and what the <em>correct</em> answer is. <em>Dominant strategies</em>, or <em>Meta</em>, describe those models of optimal decisions identified and used by competitive players of a game. Developers of competitive games often try to disrupt those dominant strategies when they become predominant among players. Because games are more interesting when they’re not simply about applying a pre-determined series of choices, but when the player has to think about the decisions they’re making.</p><p>In the field of decision-making, psychologist and economist <em>Daniel Kahneman</em> advanced the idea that the human brain makes choices using two systems: <em>Fast</em> and <em>Slow</em>.</p><p><em>Slow </em>is conscious and<em> </em>approaches problems that are unusual and require careful thought; it is, as the name implies, a process that requires a lot of time and energy. It comes from intense focus where the world outside the task at hand seems to fade to maximize learning and efficiency on a specific activity.<br><em>Fast </em>is unconscious<em> </em>and<em> </em>responsible for intuition and comes up with quick but often imperfect responses for routine situations we’re used to. It is the source of our assumptions, right or wrong. It is the reason for our cognitive biases and stereotypical views. It works to reduce the situations and choices it encounters to simple and predictive systems to come up with easy right or wrong answers.</p><p>The two systems are not entirely separated, of course, and they have to work together.<em> Fast </em>can do a lot of things by itself; walking or driving are some of the activities we can do entirely without thinking about it. Some types of games are almost exclusively played in <em>Fast</em> state as well. FPS, Fighting, or Racing games, for example, are mostly based on twitch reflexes and instinctive reactions. Actively thinking about whether to shoot or when to dodge in those games would mean wasting precious seconds we cannot afford to waste. This is not to say that this is a bad thing; knowing where to aim, when to shoot, when to slow down to take a sharp turn, or when to block and how to counter, it all feels great.</p><p><em>Fast</em> can walk, run, jump, and fight. The one thing it cannot do is open doors to new, unusual situations or difficult choices. That is an ability only <em>Slow</em> possesses. Even in those games, some situations require cautious thinking about what to do and how to do it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*Fa3mYabFtN4mWGxr4zOq5Q.png" /><figcaption>Yorda being captured by shadows concept document — Team Ico</figcaption></figure><p>And I would argue those can be the most powerful moments the games can offer. The <em>mind game</em>, as it is sometimes referred to, happens when a player deliberately does something that goes contrary to what the intuitive (or <em>Fast</em>) response is in a situation. A player makes their way behind enemy lines but doesn’t shoot an opponent in his range to lure the entire enemy team into a false sense of security and wait for the perfect timing to take them all out; a player repeats the exact same move three times in a row in a fighting game to prey on their opponent expectation that no one would take such a risk so many times; there are many examples of this. And they make for incredibly memorable moments.</p><p>But just like <em>Slow</em> is still required, although less frequently in <em>Fast</em> games; it would be wrong to assume that only action-based games are played in <em>Fast</em> state. In his studies, <em>Daniel Kahneman</em> describes chess grandmasters observed planning their next moves in <em>Fast</em> state, when they meet board patterns they’ve encountered enough times before. We analyze and become better at identifying patterns in all the games we play. Pattern recognition is improved and perfected each time we practice an activity; it is the process of learning and getting better at it. Eventually, after enough practice, we can do it entirely on autopilot. And we barely, if ever, need to think about it again.</p><p>Deep enough competitive games like chess are virtually immortal because new patterns are based on opponents’ behavior and, thus, theoretically infinite. And still, we can only get so good at any game. Every time we get better, less potential for improvements remains, and thus, getting even better is every time a slower process. Eventually, we feel like we are not evolving anymore, like we’re not learning and not getting better anymore.</p><p>We keep applying the same quick responses to the same situations and stop coming up with new and different reactions; we stop thinking about it, and do it entirely on autopilot. <br>Games die in this state. Once we’re able to play without thinking about the game, something is irremediably lost. We stop listening to the game, we already know everything the game has to say. We apply the same method again and again, it stops being <em>play</em>, and it becomes a tedious process, at best a boring experience, at worst, <em>work</em>.</p><blockquote>“But you’ll only play until you master the pattern. Once you’ve mastered it — or realized you can’t get any better — the games becomes boring. […] Game makers are fighting a losing battle againt the human brain.”</blockquote><p>This is why, I believe, the most enjoyable moments with a game come from the intrinsic feeling of increased mastery, of actively getting better. And we’re only able to get better as we still have things to learn and explore. Thus, learning is a necessary component of “<em>fun</em>”. Just like <em>Raph Koster</em> describing his children moving on from tic-tac-toe after all games end in draws because they know all the possible actions and outcomes, after reaching a certain point, all plays of any game inevitably turn into <em>grinding</em>. A slow, repetitive process whose outcome is predictable and unchanged.</p><p>This happens even to games we love, we inevitably split apart eventually because our brain is programmed to do so.</p><p>Moving on and playing new games isn’t a bad thing, of course, and it can feel petty to only stick with the kind of experiences you know, but some games just stay with you, and you can’t help but go back.</p><p>Even after <em>Yorda</em> is turned to stone and you end up at the deepest point you’ve ever been, you go back. You can’t help but go back. You just can’t let go of this feeling. You can no longer save your progress but you don’t really need to; you find ways to unlock doors on your own, there are no enemies, no feeling of tension, of uncertainty, the only thing left is the hope that you might be reunited ultimately.<br>Still, you go back.</p><h3>Going back</h3><p>After completing <em>Ico</em>, you can play it again in some kind of “game+” mode. What it does is, this time, the dialogs of <em>Yorda</em> are translated. The subtitles no longer display weird symbols but appear in the language of the player. The dialogs do not reveal any particularly useful information, nor do they majorly recontextualize any part of the game. Most of it you can more or less guess during your first play-through. What it does is acknowledge how the characters changed during the first play-through, and the fact they now understand each other. But what it also means is you have nothing more to learn; there is no mystery left, no unspoken part left to explore. There is nothing left to say. The game is still here, and you can still play it, but it’s not the same thing anymore; you start to look for a similar experience elsewhere, look at similar titles, mods, and expansions, for something the original game can simply no longer provide because you know it too well.</p><p>One of my design teachers used to compare it to drug addiction: “You always keep looking for this one first shot that you’ll never reach again, but still you pump your veins with more and more poison searching for it.”</p><p>This is an all too familiar feeling. And this is not limited to games, or to me either. It sometimes feels like current culture is almost entirely fueled by nostalgia. New trilogies, remasters, remakes, selling not just additions to something we loved, but the endearing promise that we can experience this thing we loved for the first time again. The same thing, just different enough.</p><p>I do not want to do that here. I don’t want to make grandiose claims that game design is the magic word that can wipe your memory clean so you can replay your favorite game with no previous recollection of it.</p><p>But as a game designer, I wonder, what if there was a way to unlearn what we’ve learned? To move the players back down the progression curve, extend the progression curve so that they have new things to learn. Disrupt their automatism, and force them to take it <em>Slow </em>again, to make them think about the choices and questions the game asks, to listen once again.</p><p>Time has passed since <em>Ico</em>, since I rediscovered it, and it convinced me to change my career plan to become a game designer. I have been doing this for some time now and specialized in Live Game Design, which is to say I do not create new games, I create expansions and additional content for existing games. To keep them alive for players who keep going back, players who, like me, cannot let go. At the time of writing these lines, I have worked on nearly a hundred live releases and DLCs, and I’ve started to notice, well… recurring patterns.</p><p>This is what I want to talk about. Experiences I’ve had with games, expansions, what worked, what didn’t, and how it impacted the players and their experience. Ultimately, and most importantly, how pattern disruption sometimes seems to be able to bring the players back.</p><h4>Unexpected consequences</h4><p>Fire beats plant, plant beats water, and water beats… one of the three. Everyone knows that. That’s one of the most basic and unchallenged trinity in the history of gaming as it makes for easy-to-grasp tactical and strategic decisions on the part of the player. Mobile game <em>Dungeon Monsters </em>uses this trinity and the team composition of <em>Pokemon</em> and combines it with old-school dungeon-crawler and quick turn-based combat<em>.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FWhqS2SYJ8MQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DWhqS2SYJ8MQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FWhqS2SYJ8MQ%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9f1ffe20cc84653d7cc40cdfd1e0b7cc/href">https://medium.com/media/9f1ffe20cc84653d7cc40cdfd1e0b7cc/href</a></iframe><p>The game is fairly intuitive, and it doesn’t take long for players to understand that the best way to complete a dungeon is to constitute a team of monsters of the dominant element against the creatures they’re gonna face in this particular dungeon. The challenge over time resides more in obtaining and training the creatures the player requires for each dungeon, and the choices and strategy, while still present, take on a secondary role.</p><p>The game saw the addition of much content after its initial release. We designed a lot of new monsters and new dungeons, increasing in difficulty, becoming longer and more maze-like. But we didn’t change previously introduced rules and, in particular, not the well-known element trinity. This all changed, however, with <em>Athena’s Garden</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/526/1*IAM0dHiloruHY843cu57XA.jpeg" /><figcaption>Athena’s Garden dungeon cover.</figcaption></figure><p>Added one year after the game&#39;s initial release, <em>Athena’s Garden</em> was a dungeon of a new kind. Every time they were the target of an attack, enemy creatures’ element would change to become dominant against the monster which attacked them. Constitute a team of water monsters, attack the enemy fire creatures, and you’re now facing plant types creatures that will wreck your team the next time they attack.</p><p>This not only forces the player to have a team composed of all the different types to face all situations but also means every attack now has the potential for devastating consequences down the line. Attacking an enemy is no longer a simple question of “which enemy do you want to deal damages to?” but you now also have to consider “which type do you want this enemy to be when it will be attacking you?”.</p><p>The dungeon was the most difficult we ever released. Even while designing and iterating on it, it remains the only dungeon I never managed to complete myself. It was simply too mean and asked too much. The change of rule was a significant cognitive load increase and a serious spike in difficulty. I was worried that we might have pushed things too far this time. <br>And then…</p><blockquote>“Out he goes. Cold. Athena next. One critical damage hit. Massive. She hits me back. Even bigger. My healer is two charges away. Chip. Chip. Big hit Massive hit. She clobbers me again with a God-fearing smack. I’m not dead. I’m down to a slither of life. The team strikes out. Unbelievable hit, 20,000 and she’s still there, but only just. I’ve got one more. <strong>It’s got to count.”</strong></blockquote><p>This is an excerpt of the 456 words long review left by a player after finally completing <em>Athena’s garden</em>. Players were telling the stories of their experiences with the dungeon, their successes, as much as their failures; they were definitely paying attention and thinking about what they were doing. This update saw a lot more praise and overall a lot more reaction than any other before it, despite being a significant peak in difficulty.</p><p>Through, honestly, complete random experimentations at the time, we managed to recapture the initial excitement of the game, especially among the most experienced players. But this came at a cost; as I said, this event is probably the hardest, meanest, most complicated, and heavy in cognitive charge of the entire game. To experienced players, it was a challenge they were ready and happy to take on. But for less experienced players, this was a piece of content that was simply inaccessible.</p><p>Adding new rules or complexifying existing ones can easily result in increased difficulty and cognitive load, but I do believe it is not the only way to achieve this.</p><h4>Cutting to the essential</h4><p>If I ask you to think about nearly 20 years old <em>MMO</em> games that are still up and running today, still being updated and receiving new content regularly, you probably think about <em>World of Warcraft</em>, maybe <em>Eve Online</em>, or… <em>Dofus</em> if you’re one of the cool kids.</p><p><em>Howrse</em> is among those great-old-ones, gods from a previous world having survived in ours, whose existence is not always known, but whose cult is still very much alive. In the current environment of games, <em>Howrse</em> is an anomaly. It is technically part of the <em>Ubisoft</em> portfolio, by far the oldest live game in it, but it doesn’t feel like it. It is one of those web-browser-based games that came and went around the year 2000. Except… <em>Howrse</em> never went anywhere. It didn’t change platform, or model, it remains where it has always been, unwavering, for the last 17 years.</p><p><em>Howrse</em> is a game about, well… horses. It is an <em>MMO</em> in the most direct sense of the word, a persistent world with a massive amount of players having almost complete control over its economy, resources, and evolution. The reason you almost certainly never heard of it is it is not a <em>mmoRPG</em>, it is a Management Simulation Sandbox where players buy, sell, train, and breed horses. Contrary to what its overly cute aesthetics would suggest, it is a ruthless and cutthroat player-controlled economy about making profits and driving your competitors off business.</p><p>This game is an endless source of fascination to me.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmE3tLoGUgnI%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmE3tLoGUgnI&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmE3tLoGUgnI%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/61f3ab84eb65ff779f58f4e7ef573d45/href">https://medium.com/media/61f3ab84eb65ff779f58f4e7ef573d45/href</a></iframe><p>The game owes this longevity, among other things, to continuous live support, in the form of new content, balancing patches, and temporary events, presenting the players with new activities and gameplay mechanics they can take part in for special rewards and items for a limited time before the event is removed and internally reworked, fine-tuned, and readjusted, before its next iteration.</p><p>One of the events, which was originally very well received by the community, grew more and more ignored through each iteration. Players became more used to it and grew tired of it until it eventually granted a complete rework.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DP9VmecQ15QHq87awAZXPA.png" /><figcaption>Original Event UI</figcaption></figure><p>The <em>Plant even</em>t had players gathered seeds and the resources to farm and harvest them in order to craft different items, and seeds of higher levels, they then repeated the cycle with the seeds of higher levels and so on, until they got to the items they wanted. In total, with all seeds and variations, resources to grow the plants, and collect them, the players had to jungle many different resources, and commit a lot of time and efforts to get what they wanted.</p><p>In its last iteration, the feature was ranked fairly low by players, pointing to tedious gameplay and low returns on investment for their efforts. A decision was made to rework the feature entirely. The design team decided to keep the main theme and idea of harvesting resources to craft items, but to cut a lot of the parts players were complaining about to only focus on the core experience: The choices of what items players wanted to craft.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AwwIwI9CtCEcPvieluUjlQ.jpeg" /><figcaption>New Event UI</figcaption></figure><p>In the reworked edition, players collect one and only resources. On the same principle as <em>2048 </em>puzzle game, fusing two resources of the same level result in a resource of a higher level. Players now have to fuse resources of different levels to craft the items they want. The trick is, their inventory is limited to 9 slots, and the most valuable item requires two level 8 resources to be combined. This means players have to choose between obtaining many low-level items quickly or holding their resources for higher-level items later. Thus restraining their ability to fill their inventory and gather more resources until they could craft the desired items. This faces the player with some difficult decisions, but apart from this, the complexity of the feature was reduced to a minimum.</p><p>The new version was an instant hit, ranking #1 most appreciated players feature, and showing signs of engagement by the players rarely matched. The feature was iterated on again and soon occupied #1, #2, and #3 favorite features across the different iterations. Noted by the players was the simplicity of interacting with the feature, and the fact the choice they had to make was the central point. The core of the gameplay was demanding players to evaluate their options, carefully think about what they wanted, and then offered little resistance in execution, but the fact the feature required players to make difficult choices was enough to create tension and to have players feel engaged.</p><p>This kind of tough choices and difficult resource management actually works really well in other genres as well.</p><h4>Changing the rules</h4><blockquote>“Wounded villagers are as good as dead. Worse in fact, because they still require food.”</blockquote><p>This is one of the first and most recurrent pieces of advice I’d been given about how to play <em>Northgard</em>. A game about Viking clans at war against one another and the environment for the control of an unexplored island. Winters in <em>Northgard</em> are harsh, and the players quickly learn they need to optimize their colony production in order to survive. Villagers are critical during the year as they produce all the resources the player needs. But when the first snows fall, they consume more food and firewood than they can gather, and so a villager wounded by a wolf — producing even less — is a dead weight for the clan. And so, no matter how harsh this can seem to outside observers, this is why players who are very familiar with the game have developed an automatic response to try and get rid of wounded units as soon as they can.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmDN8PHOYnKc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmDN8PHOYnKc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmDN8PHOYnKc%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/78caf1e77c9e0d9ad91b8989e89e8a7f/href">https://medium.com/media/78caf1e77c9e0d9ad91b8989e89e8a7f/href</a></iframe><p>Or at least it was, until we introduced the 13th clan of the game: the clan of the Rat. A clan entirely built on the idea of making players play with wounded units rather than around them. The clan of <em>Dodsvagr</em>, as it is more formally referred to, starts with only wounded villagers, which can then be healed by the Shamans of the clan. But the player can at any moment increase the units’ production at the cost of their entire population&#39;s health. But the more the clan population is hurt, the quicker new units are generated to compensate. And so, the player has to make good use of wounded units and treat health as an entirely new resource to manage in their strategy in order to bring the clan to its full potential: A relentless army of workers swarming the land with wounded but numerous units.</p><p>It is one of the most unforgiving and punitive clans during the first few plays because it is so counterintuitive to what players spent hours learning with every other clans. But after players understood how the clan could be played, and they started to master it, it received one of the most positive receptions of any clan. And this is because it was so unique and so different from the others. Players couldn’t rely on automatic responses they had learned about wounded units and had to consciously, and <em>slowly,</em> think about the choices they were making again.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSFjDGU4ATiw%3Fstart%3D1%26feature%3Doembed%26start%3D1&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSFjDGU4ATiw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSFjDGU4ATiw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/36ad17ef17cc9b848651dba4b221281d/href">https://medium.com/media/36ad17ef17cc9b848651dba4b221281d/href</a></iframe><p>Like <em>Athena’s Gardens</em> before it, this new content asked of the players to go back and learn new fundamentals than the ones they had previously learned. It was a significant increase in difficulty for the players, but got a particularly good reception from players that knew the game the most. And if you’ve stuck with this writing until this point, you probably understand by now that, to me, it is precisely because they forced the players to basically learn the game again, that they’ve got such positive reactions.</p><p>I’ve been able to identify those patterns in various games I’ve worked on, and they were the starting point for this reflection. But it is not my intention to claim that I am the first one to encounter those or that they are limited to my games, and I think we can already observe similar effects in much more well-known games.</p><h4>Closing doors, opening windows</h4><p><em>Dark Souls</em> creative director <em>Hidetaka Miyazaki</em> cited <em>Ico</em> as a major inspiration and even the reason he even decided to make games in the first place (this game seems to do that with a lot of people). But where <em>Ico</em> was a quiet and slow conversation, <em>Dark Souls</em> is more akin to trying to get out of police control by screaming that you know your rights. In the middle of a shoutout. While a dog is biting your leg.</p><p>But despite this barely noticeable difference, <em>Dark Souls </em>inherits its deliberateness from <em>Ico</em>, animations are detailed, actions are slow, and crafted to look alive rather than to facilitate the player’s intention. Enjoyment from both games comes from decoding and mastering the game despite their apparent unfriendliness.</p><p>It is from this interaction that a common sentiment emerged among players:</p><blockquote>“The <strong>real</strong> Dark Souls starts here.”</blockquote><p>This sentiment exists within all games of the Soulsborn series (similar games from studio <em>FromSoftware</em>) and is often used to describe difficulty peaks when playing the game, particularly punitive and difficult, at a moment when the player hasn’t mastered the game yet. When the character you play still feels weak enough that defeating the enemies and situations the game throws at you feels like <em>epic victories</em>:<em> </em>Success against all odds,<em> </em>snatched from the jaws of defeat just one or two hits away from death.</p><p>But like all things, no matter how mean or unfair the game and situations seem, the human brain is designed to decode and grow past them. Soon, <em>Fast</em> kicks in, and a boss that seemed like an impossible opponent just becomes a set of intuitive inputs and predictable timings. In his video essay, <em>Bloodborne is Genius</em>, youtuber <em>Hbomberguy</em> describes learning <em>Dark Souls </em>in a way that echoes the evolution from system <em>Slow</em> to <em>Fast.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FAC3OuLU5XCw%3Fstart%3D643%26feature%3Doembed%26start%3D643&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DAC3OuLU5XCw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FAC3OuLU5XCw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9afb3483dcc8b967cd3c54bb308a2ad9/href">https://medium.com/media/9afb3483dcc8b967cd3c54bb308a2ad9/href</a></iframe><blockquote>«The soulsgame get into you, inside your head. […] You stop doing the maths about how quickly your attack goes off, and trying to figure out an opening to move, and you start to just know the right time. Because all this stuff is so deep inside your head that <strong>you don’t even have to think about it</strong>, it becomes like an instinct.»</blockquote><p>Mastering the game is part of the experience and is a desirable outcome, of course. But once the player knows the game well enough, has memorized every patterns, every levels, this sense of fear, tension, and uncertainty, which is the core of <em>Dark Souls</em> ambiance and experience, is lost. Contrary to <em>Ico</em>, <em>Dark Souls</em> can be played several times and has some ways to renew the experience. There are different types of weapons and classes to try and master. But the enemies, the levels, the optimal paths, all this knowledge remains from one run to the next, as they still remain the same. And players who’ve reached this point keep seeking this pain again.</p><p><em>Scholar of the First Sin</em>, like <em>Daughter of Ash</em>, are additional content that attempts to bring the <em>real</em> <em>Dark Souls</em> back for players who’ve grown past it. Those expansions, one official and released by the developers of the game themselves, the other, modded in by players, similarly approach this search. They break patterns. Shuffle things around. And disrupt introduced rules.</p><p>Levels contain monsters that originally never ventured here, paths are closed, others are opened, forcing the player to find new routes, new ways to achieve what they previously knew how to do. It brings back the sensation of uncertainty and of being lost. The player has to be alert again, to think, to listen.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_sGpKWwxbAE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_sGpKWwxbAE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_sGpKWwxbAE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/945ab24f380160340e0512ffab4f1265/href">https://medium.com/media/945ab24f380160340e0512ffab4f1265/href</a></iframe><p>In his essay <em>The beautiful Pain of Daughter of Ash</em>, <em>Jacob Geller</em> talks about his experience with the expansion.</p><blockquote>«Dark Souls demands patience, and pattern recognition. […] I’ve run out of save slots on my PS3 and my PC, I’ve messed with the game sequencing, I’ve made Lordran look like a joke. […] <br>I thought I was good at this game, but Daughters of Ash dragged me right back to reality. I had to rewire my brain in so many ways […], <br><strong>the real dark souls starts here</strong>.»</blockquote><p>Once again, and at the cost of a significant increase in difficulty, those additions seem to be able to bring the player back to this place where uncertainty, doubt, progress, and thus, fun, live.</p><h3>Moving on</h3><p>At the very end of <em>Ico</em> you can make your way up to the top of the castle again, find <em>Yorda</em>. But she is still petrified, and she’s surrounded by shadows. In a somewhat dark twist, it is revealed in this instance that the shadows that have been chasing you during the entire game come from the same urns you escaped from at the beginning of the game. They are the ones that didn’t get away.</p><p>Shadows of its siblings are the ultimate downfall of <em>Ico</em>. Both in and outside of the game, they are oblivion that absorbed a lot of what remained from it and tainted its legacy. The most destructive of those shadows may be the one of its younger sibling, for lack of a less obvious pun. Gathering more success than <em>Ico</em> could ever dream of getting, <em>Shadow of the Colossus</em> — the following game of <em>Team Ico</em> — relayed <em>Ico</em> to the spot of the lesser game. Where <em>SotC</em> spawned many imitations and homages, and even got an entire remake made for PS4, <em>Ico</em> remained, just <em>Ico</em>.<br>I was finally able to experience <em>The Last Guardian</em> after many years of wait, and found many of the qualities of <em>Ico</em> in <em>Journey</em>, but there will never be another <em>Ico</em>. And I am left trying to find ways to go back and experience the same game again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WSHGZqnmcafLeDAmr5GxxQ.jpeg" /><figcaption>Shadow of the Colossus design document — Team Ico</figcaption></figure><p>To be clear, I’m not saying <em>Ico</em> would have been a better game if it had a dozen DLCs and live support; I don’t think that’s true. But this type of experience is rare enough that you won’t encounter new ones often. And nowadays, developers seem eager to capitalize on their game success, and offer more and longer support than they ever had before. And in this context I think we should strive to think about how to make the most out of those types of additions, to build upon, and extend the potential of the game itself as much as possible.</p><p>Although all types of additional content will hypothetically create novelty and renew the play experience for the players, not all additional contents are equal. Just adding more and more levels to a game until it reaches thousands of levels is what some mobile games do. And it technically works! It keeps players occupied, but it requires a constant stream of new stuff to be relevant because the player mash their way through this new content so fast, and it rarely leads to particularly memorable experiences for the players. On the other hand, adding entirely new and different gameplay to learn will surely create a new learning curve for the player to engage in. But they also represent the risk of striving too far away from what the players enjoy about the game by presenting something radically different. They also often are of a lesser quality because they are not part of the main gameplay, and thus cannot see the same level of investment and polish from the developers.</p><p>I think there are better ways of doing this. Both for developers who cannot afford to add 20 new levels to their game each week or create entirely new and separate features; and for players who expect meaningful and challenging addition to the games they love. The ideal addition is one that let players engage with the same gameplay they fell in love with, but from a different angle, with different rules, or variations, enough that they can discover and get better at it again.</p><p>This doesn’t seem limited to certain games, players, models, or platforms. I’ve worked on very different projects through the years, and I’ve never encountered a project where the idea of disrupting players&#39; previous knowledge and automatism seemed impossible. As fun comes partly from the intrinsic reward of learning and getting better at all games; disruptive design seems to be applicable to every type of game.</p><p>It is my sincere belief that breaking patterns the player learned and pushing the player to learn and make difficult choices again can be among the best experiences we can offer. I would argue it even has the chance to be stronger than the initial discovery of the game, as it is one made with the assurance that the player already enjoys the overall experience; the player knows the efforts they put in will be rewarded, for they know they enjoy the experience of mastering the game already. And they can engage with this new content without this sense of risk.</p><p>Ultimately, the important thing is not to be hard but to make the player think. Making decisions seem challenging to solve, for as long as possible, until the player&#39;s mind inevitably finds a way, then an optimal way, and finally knows the paths with their eyes closed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*96dIxN1bTtJx_b-ImG1Z8Q.png" /><figcaption>Ico first level design document, also the last level of the game — Team Ico</figcaption></figure><p>In the final moments of <em>Ico</em>, with no way to bring Yorda back, the only thing you can do, is to confront the reason she is gone. Fight the dark queen, destroy the castle, end it, turn everything to ashes. After you’ve succeeded but the fight left you unconscious, she eventually wakes up, but even then, there is no way back. Not for her. You can exist outside of those walls, but she cannot. In the last moments of the game, as credits roll, music swings, and the castle crumbles, she carries you to a boat, and pushes you back to the outside world. Only your journey goes on beyond the game, hers is the game.</p><p>Only in the very last seconds of the game, in a post-credit scene after you‘ve landed on a shore, is it revealed that a part of her has survived and has managed to escape. And she will remain with you, forever. The game lets you, even for just an instant, go back, and I hope to one day be able to do that for players myself, to help those experiences live forever. Because some games just stay with you, and you can’t help but to go back.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=59db0f2a9cf3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spider-Man vs. Miles Morales — A game design study]]></title>
            <link>https://leolesetre.medium.com/spider-man-vs-miles-morales-a-game-design-study-c63223272c92?source=rss-104a172a987d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c63223272c92</guid>
            <category><![CDATA[spider-man-miles-morales]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[spider-man]]></category>
            <dc:creator><![CDATA[Léo Lesêtre]]></dc:creator>
            <pubDate>Sat, 19 Jun 2021 09:03:09 GMT</pubDate>
            <atom:updated>2022-03-18T12:35:01.759Z</atom:updated>
            <content:encoded><![CDATA[<h3>Spider-Man vs. Miles Morales — How removing features can improve a game.</h3><h4>How to efficiently build upon existing game systems</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q7ge0ZbhKF3NHFV_V_C0Zg.jpeg" /></figure><p>A little while ago, I talked about <em>Marvel’s Spider-Man </em>game qualities and flaws regarding the principle of skills transversality. <a href="https://leolesetre.medium.com/spider-man-vs-arkham-knight-a-game-design-study-7eb7a02bec46">You can read about it here</a>.</p><p>This new opus centers on the character of Miles Morales and takes the game in <strong>new directions, fixing most of the issues I discussed regarding the first one but still has room to grow and perfect.</strong></p><h3>A new Spider-Man</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FPlsZcNzfW6vQYBL1FS%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FPlsZcNzfW6vQYBL1FS%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FPlsZcNzfW6vQYBL1FS%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="181" frameborder="0" scrolling="no"><a href="https://medium.com/media/9df8ba5918fa00bdaaaba1b3b77a151b/href">https://medium.com/media/9df8ba5918fa00bdaaaba1b3b77a151b/href</a></iframe><p>Released at the end of last year, <em>Marvel’s Spider-Man: Miles Morales</em> doesn’t stray too far away from the original formula. Swinging around New York is as easy and satisfying as ever, combat is reactive and impactful, and a cast of colorful characters drives an interesting story.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*vGQBVakC8V0NPvt4kHCQtg.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*d90x4XiF2ZCjp-BLFMdHiQ.gif" /><figcaption><strong>Marvel’s Spider-Man</strong> (left) vs. <strong>Marvel’s Spider-Man: Miles Morales</strong> (right)</figcaption></figure><p>But more than a simple rinse and repeat copy, Miles Morales brings a significant new addition to the mix: <strong>venom powers</strong>.</p><h3>Better in every way</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FhW4pOhW4dK7JI7hFno%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FhW4pOhW4dK7JI7hFno%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FhW4pOhW4dK7JI7hFno%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="181" frameborder="0" scrolling="no"><a href="https://medium.com/media/b30581131f0284fd21ae8b06f204c3e9/href">https://medium.com/media/b30581131f0284fd21ae8b06f204c3e9/href</a></iframe><p>Back in <em>Marvel’s Spider-Man</em>, I felt disappointed that the game didn’t do much with electricity. Well, I can’t complain now!<br>The <strong>venom powers</strong> are new electric abilities unlockable early in the game and trigger using accumulated energy.</p><p><strong>This addition can seem trivial on the surface but is cleverly used to deepen every major gameplay.</strong></p><h4>From navigation</h4><p>Swinging around the city, Miles can use the new <strong>Venom Dash</strong> to regain momentum mid-air in a double-jump manner up to 3 times in a row.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*2AsmucLpmyCT4hMYqxF9FQ.gif" /><figcaption>Use the<strong> Venom Dash</strong> to regain momentum and reach your destination faster.</figcaption></figure><h4>To combat situations</h4><p>Many new venom attacks can be used in combat to regain the advantage or to get out of a bad situation quickly, such as the <strong>Venom Smash,</strong> which stuns all surrounding enemies, or the <strong>Venom Jump,</strong> which throws all close enemies in the air.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*frNusEG-dX-lLzjBANqCSw.gif" /><figcaption><strong>Venom Punch</strong> in action.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*8bkO3A_qg01FzXJ4O-QiKg.gif" /><figcaption>Using the <strong>Venom Jump</strong> and <strong>Venom Smash</strong> can quickly turn the situation to your advantage.</figcaption></figure><h4>To puzzle solving</h4><p><strong>The most significant improvement of <em>Marvel’s Spider-Man: Miles Morales</em> by far is the new puzzle system.</strong> The previous opus used a mini-game of electronic circuit remapping. Miles can now use his <strong>electric web-shooters</strong> to connect generators and close circuits to unlock doors and activate electric devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*zURk56nXEBRQiCJy-44eFw.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*RaQIbkO7FRSzgDzyDtfRQQ.gif" /><figcaption><strong>Spider-Man</strong> puzzle mini-game (left) vs. <strong>Spider-Man: Miles</strong> <strong>Morales</strong> new puzzle situations (right)</figcaption></figure><p>In addition to removing the puzzle mini-game from the previous opus, the game also reduced Spider-Man gadgets from<strong> 8 </strong>to only <strong>4</strong>. <strong>All this results in a more consistent and focused experience relying on a recurrent set of controls and abilities without the additional cost of complexity.</strong> Furthermore, this demonstrates a better implementation of what I previously called <strong>Skill transversality: </strong>The idea that secondary gameplay relying on variations of the main one enriches and rewards the player&#39;s engagement by developing skills useful outside of those situations.</p><p>But I feel it could have been pushed even further by fully exploiting those new interactions.</p><h3>But not yet perfect</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Ffjy4y5z5si4A0uOjsM%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Ffjy4y5z5si4A0uOjsM%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Ffjy4y5z5si4A0uOjsM%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="183" frameborder="0" scrolling="no"><a href="https://medium.com/media/daa5b27d6ed7ff88d2d7fc5587dab0a2/href">https://medium.com/media/daa5b27d6ed7ff88d2d7fc5587dab0a2/href</a></iframe><p>New York City is filled with interesting challenges and situations, but unfortunately, only a few rely on the environment outside of particular and rare elements. In addition to this, the interaction with those elements also relies on specific gadgets and mechanics, leading to a few unfortunate side effects.</p><h4>A mindless genius</h4><p>A good opportunity for implementing puzzles as an alternative to brute force is the traps that Miles can use. In Lab challenges, you can use a specific gadget, the <strong>remote mine</strong>, to trap<strong> fuse boxes</strong> and eliminate closeby enemies. It is an interesting interaction, but it entirely relies on enemies standing close to bombs you can activate by simply pressing a button, and it doesn’t make me feel smart for it.</p><p>The same could have been achieved using the same kind of electric connection used for opening doors. <strong>You could find conductors around the area to connect a generator to the fuse box, effectively using the reflection and observation skills you learned to turn your environment into a weapon.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ldWyYHRJoenUZ66WLr5CGg.gif" /><figcaption>You can turn this fuse box into a bomb just by pressing a button.</figcaption></figure><p>From here, why stop at fuse boxes. If you could direct electricity toward metallic or electronic items, this could lead to various situations depending on what is present in the level and what you decide to connect. Trap doors or stairs on the enemy’s path, an alarm button that the enemies will go to if they detect you, or really, anything else.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*RaQIbkO7FRSzgDzyDtfRQQ.gif" /><figcaption>It is indeed very satisfying to use your environment to your advantage.</figcaption></figure><h4>An empty city</h4><p>Another problem I have with this game is how beautiful but empty the environment can feel at times. The different events and challenges often resolve similarly and quickly dry off, the number and type of enemies being the most significant variable in most situations. In contrast, the environment in which it takes place often adds relatively few things, if any, in comparison.</p><p><strong>Having players look for an electricity source and connecting it to trap enemies would inherently bring new and various challenges to each area </strong>(while remaining optional). Thus, allowing for more distinct and memorable levels and environments. Finally, this would also eliminate one more gadget, alleviate the cognitive load, and remove the need to go through a menu to switch between fighting and using gadgets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*IWj-gJnRbYE9vz9sGTrOaQ.gif" /><figcaption>This one is gonna hurt…</figcaption></figure><p>I focused on the electric puzzles here, but I think the same kind of intertwined interactions could also deepen with other secondary gameplay, such as swinging through the city or Miles&#39;s ability to move objects along a rail to solve specific situations.</p><p>Despite those complaints, this is not to say that <strong>the game is not one of the best in some areas</strong>.</p><h3>Credit where credit is due</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FMY5rGzA72Jt4GZAZDC%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FMY5rGzA72Jt4GZAZDC%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FMY5rGzA72Jt4GZAZDC%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="181" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ef190eddf37f1c8a34a54d2a8e206ba/href">https://medium.com/media/3ef190eddf37f1c8a34a54d2a8e206ba/href</a></iframe><p>While this article intends to study <em>Marvel’s Spider-Man: Miles Morales</em> from a game design perspective, it would be disingenuous not to mention what the game does for accessibility and positive representation.</p><h4>Accessibility options</h4><p><em>Insomniac Games </em>made a big effort with <em>Miles Morales</em> to address the most common accessibility issues. From control assistance and input setting to audio and visual cues, this game gives a wide spectrum of options and customizations to ensure as many players as possible can enjoy it. And that’s worth praising.</p><h4>Positive representation</h4><p>Not only does this allow players with disabilities or just less-experienced players to have fun, but the game also includes characters with disabilities as an active part of the story, at the image of <em>Hailey Cooper</em>, a hard-of-hearing artist who speaks with Miles in sign language.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/1*3yI3zixd8AIv8YbCKc5ilg.gif" /><figcaption><strong>Hailey Cooper</strong> in Marvel’s Spider-Man: Miles Morales</figcaption></figure><p>Centered around the character of Miles, the game ceases on the opportunity to explore themes related to the Afro-Latino community and how it affects the world around its characters. This gives its characters a more personal and believable touch, reflecting on real-world events such as the <em>Black Lives Matter</em> movement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9zeQP67Pvjx-Oy0XjXsmTw.jpeg" /><figcaption>Screenshot for Marvel’s Spider-Man: Miles Morales</figcaption></figure><h3>TL;DR</h3><p><em>Marvel’s Spider-Man: Miles Morales</em> is an excellent game that I had a lot of fun with but left me wanting more in some areas. If you are yourself trying to add new content to an existing game or formula, keep this in mind:</p><ul><li><strong>Add few new features to avoid adding complexity and making existing systems less accessible to newcomers.</strong></li><li><strong>Have those new features interact with as much of the existing content and systems as possible to add depth to all of them.</strong></li><li><strong>Just because you want to add new content doesn’t mean you can not remove as well, if this makes for a more focused and consistent experience.</strong></li><li><strong>Try to build the skills and features of secondary gameplays into the main experience to reward players for their mastery in those areas.</strong></li></ul><h3>Post-credit scene</h3><p>With a new <em>Marvel’s Spider-Man </em>currently in development, I will again see you when it comes out. Hopefully, praising a more organic and permissive approach to game situations.</p><p>In the meantime, if you’re interested in a closer look at the balance of depth vs. complexity and the principle of elegance in games, <a href="https://leolesetre.medium.com/what-makes-a-game-system-elegant-5c73b4e9b50e">you can read more about it here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c63223272c92" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What makes a game system elegant?]]></title>
            <link>https://leolesetre.medium.com/what-makes-a-game-system-elegant-5c73b4e9b50e?source=rss-104a172a987d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c73b4e9b50e</guid>
            <category><![CDATA[board-game-design]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[video-games-industry]]></category>
            <category><![CDATA[games]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Léo Lesêtre]]></dc:creator>
            <pubDate>Wed, 03 Feb 2021 17:48:10 GMT</pubDate>
            <atom:updated>2022-03-18T12:29:43.474Z</atom:updated>
            <content:encoded><![CDATA[<h4>Moreover, how to achieve it.</h4><h3>Elegance?</h3><p>You might have heard before someone talking about a game system being <strong>elegant</strong>. Yet, there is currently no consensus over a specific definition nor a method to achieve it or improve it among game designers.</p><p>So I will try my best in this essay to define the way I interpret and work with elegance, confronting it with opinions of experienced and influential game designers along the way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_eAsY2TIai4Gi7uzGKNO-Q.png" /></figure><h4>What designers say</h4><p>For most designers, the definition lies in the relation between simplicity and complexity co-existing within a game or a system:</p><blockquote>I’ve grown weary of games with many rules and/or many ways to earn VP´s. So, now I tend to design simple,<strong> elegant</strong> games.<br>- Rüdiger Dorn</blockquote><blockquote>We call simple systems that perform robustly in complex situations <strong>elegant</strong>. <strong>Elegance</strong> is one of the most desirable qualities in any game, because it means you have a game that is simple to learn and understand, but is full of interesting emergent complexity.<br>- Jesse Schell</blockquote><blockquote>The term “<strong>elegance</strong>” is often used to describe such games as I mention, but I prefer the word “simplexity,” by which I mean having the most complex and interesting interactions and outcomes which result from the simplest rules.<br>- Alf Seegert</blockquote><h4>What games are elegant</h4><p>Despite the definition of elegance differing, most seem to agree on which games express it and why:</p><figure><img alt="Ticket to Ride (by Alan R. Moon) box" src="https://cdn-images-1.medium.com/max/1024/1*VWXlBi8j5e1tlXZPn8s3uw.png" /><figcaption>Ticket to Ride (by Alan R. Moon) box</figcaption></figure><h4>Ticket to Ride</h4><p><em>Ticket to Ride</em> is a competitive game in which players collect cards of different colors and spend them to build railroads to connect cities across the country.</p><blockquote>[About Ticket to Ride] The one action per person per turn system is super <strong>elegant</strong>. It makes the game really easy to learn, but the game still allows for satisfying amounts of planning and strategy<br>-Darwin Kastle</blockquote><blockquote>Alan R. Moon’s Ticket to Ride is a game design masterpiece. […] Learning the rules is a snap because the game is so <strong>elegantly</strong> designed. It does a lot with very few rules. Players enjoy clear frameworks, not confusing ones.<br>- Paul Dennen</blockquote><blockquote>Settlers of Catan, Ticket to Ride, Carcassonne. All great, popular, and <strong>elegantly</strong> designed games which should give new designers something to aim for.<br>- Richard Breese</blockquote><figure><img alt="Carcassonne (by Klaus-Jürgen Wrede) box" src="https://cdn-images-1.medium.com/max/800/1*zmOz-8On67WVNOQcg5MasA.png" /><figcaption>Carcassonne (by Klaus-Jürgen Wrede) box</figcaption></figure><h4>Carcassonne</h4><p><em>Carcassonne</em> is a competitive game where players build a map tile by tile, creating roads, cities, and territories, winning points when they complete constructions.</p><blockquote><strong>Carcassonne</strong> is a great example of the <strong>elegance </strong>of simplicity.<br>- Alan R. Moon</blockquote><blockquote><strong>Carcassonne</strong> because of its<strong> elegance </strong>— less rules and a certain kind of “game depth.<br>- Rüdiger Dorn</blockquote><p>So by crossing all those information and for this essay, I will consider elegance as the embodiment of “<em>Easy to learn, hard to master</em>,” or “<em>Less is more</em>.” The idea of offering the maximal amount of depth for the minimal cost in complexity.</p><figure><img alt="Schema on the relationship between elegance, depth, and complexity" src="https://cdn-images-1.medium.com/max/1024/1*wN5w-_sR7rKdaiUA2rcGig.png" /></figure><blockquote>And while <strong>elegance </strong>can seem somewhat ineffable and hard to capture, you can easily <strong>rate the elegance </strong>of a given game element by counting the number of purposes it has.<br>- Jesse Schell</blockquote><p>Let’s see it in context.</p><h3>How did they achieve it?</h3><p>Board games are especially prone to elegance. Not as an exercise of style, but because they often need it to survive. When designing video games, you can afford to have limitless elements, content, visual cues, and hidden balancing systems. Not with physical games though, the player is the game, and every component is expensive to produce.</p><p>One genre has seen a lot of evolution and iteration upon a similar system: <strong>deck-building card games</strong>.</p><h4><strong><em>Dominion</em></strong></h4><p>In <strong>2008</strong>, <strong><em>Donald X. Vaccarino</em></strong> designed the game that defined the genre of deck-building: <strong><em>Dominion</em></strong>. It became an instant classic with its simple mechanics and tough decisions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-RQemelqAI9gCudORiplw@2x.jpeg" /></figure><p>The principle is quite simple: You start with a set of base cards from which you will draw each turn. Those cards will then let you improve your deck by buying new, more powerful cards or removing the less useful ones.<br>But, to win, you have to stuff your deck with victory cards, which are useless when drawn. So the more victory cards you own (the closer to victory you are), the less efficient your deck becomes—an elegant, well-balanced system in itself.</p><h4><strong><em>Valley of the Kings</em></strong></h4><p><strong>5 years</strong> later, designer <strong><em>Tom Cleaver</em></strong> took a twist on the system and made it even more minimalist with <strong><em>Valley of the Kings</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*upZZZt16kGcV2Nq3ntgybw@2x.jpeg" /></figure><p>Like<em> Dominion, Valley of the Kings</em> presents you with cards you will use to buy better cards and get rid of those you do not need. However, to win, rather than having to stuff your deck with useless cards, you have to get rid of your best ones.</p><p>The amount of points you get depends on the value of the cards placed in your tomb. This creates even more dreadful choices as the more useful a card is, the more you gain from removing it from your deck. The game also gets rid of coin cards. Instead, the value of discarded cards constitutes the currency you use to buy new ones.</p><p><strong>The game keeps all the choices and options from <em>Dominion </em>while having overall less different components.</strong></p><h4><strong><em>War Chest</em></strong></h4><p>Finally, in <strong>2018</strong> designers <strong><em>Trevor Benjamin</em></strong> and <strong><em>David Thompson</em></strong> increased the options you could use the components for in <strong><em>War Chest</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nt0ppNGx-z0n7cbvJSS9cA.png" /></figure><p><em>War Chest</em> slightly differs from the previous two examples as it plays with chips drawn from a bag, placed on a board like chess pieces.</p><p>All chips represent a type of unit. When you draw one, you can discard it to play a similar unit from the board. But you can also place it or upgrade a unit on the board, or even discard it to purchase new chips. However, creating and upgrading units require you to remove the chip from your bag. Thus the more useful a unit is, the less you will be able to play it often.</p><p><strong>The game unifies all components, opening up the options of the player.</strong></p><h3>Why it matters?</h3><p>In an era of increasingly powerful technology and video games, it is easy to fix a problem by adding things. Nevertheless, we should not forget to design by removing or re-design efficient functional systems from the start. Because elegance is not just a demonstration of style, it effectively makes games easier to learn, teach, and reduce cognitive load during play.</p><blockquote>In game design, I refer to this as <strong>ELEGANCE</strong>. The best games, longest lasting games have few rules, and few special cases, and achieve their replay through the core puzzle to solve. If you find yourself adding a rule to patch a rule, you may need to go back and redesign.<br>- Raph Koster</blockquote><p>This also makes them more accessible to all type of players, which increase their audience and the number of players who can enjoy them.</p><blockquote>Most “classic games” are considered to be masterpieces of <strong>elegance</strong>.<br>- Jesse Schell</blockquote><p>The hard question is, how to know what to remove, what to keep, and when a component is non-essential to your game?</p><h3>How to achieve elegance?</h3><h4>Remove elements and rules.</h4><p>As seen with the evolution from <em>Dominion </em>to <em>Valley of the Kings, </em>much clever design comes to removing inessential elements or fusing them to give more importance and depth to the essential ones.</p><blockquote>For me, the art of game design is all about the <strong>elegance</strong> of simplicity. I try to take everything out of a game that can be taken out, leaving just enough to make the game fun and challenging.<br>- Alan R. Moon</blockquote><h4>Increase options and interactions</h4><p>Like with the evolution from <em>Dominion </em>to <em>War Chest</em>, another approach is to unify different components and leave the players to decide how he wants to play them to increase his options.</p><h4>Use context to imply behaviors.</h4><p>Finally, another way to make systems simple to grasp despite their potential complexity is to make them more organic by giving them a narrative explanation in the game context.</p><p>A perfect example of elegance is the <strong>wagon system</strong> in <strong><em>Team Fortress 2</em></strong> (or in <strong><em>Overwatch</em></strong>). The game has one team pushing a wagon to the other end of the map while the other team stops them. Simple enough.<br> The twist is that the first team’s spawn point is the starting point of the wagon, the one for the second team is its destination point.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4HHsAT1iauLk8dYf5TJRUg.png" /><figcaption>As one team gets closer to victory, it becomes increasingly easier for the opponent team to make a comeback.</figcaption></figure><p>This naturally and effortlessly creates a <strong>negative feedback loop</strong>: a situation where the closer you are to victory, the more punitive mistakes become. As when you die, you have to walk all the way back from your spawn point. Thus creating twists and epic saves mere seconds before defeat.</p><p><strong>Players expect this behavior because it makes sense in the narrative context of the game.</strong></p><h3>TL;DR</h3><p><strong>An elegant system:</strong></p><ul><li>Is functional</li><li>Adds depth to the game</li><li>Despite relative simplicity</li></ul><p><strong>It adds value to a game because:</strong></p><ul><li>It makes the overall game more accessible.</li><li>It reduces the cognitive load during play.</li></ul><p><strong>To achieve it, consider:</strong></p><ul><li>Removing rules and fusing elements.</li><li>Adding interactions and choices.</li><li>Using context to make rules intuitive.</li></ul><p>Thanks for reading!<br>Did you ever encounter a game or a system you found elegant? Please share them in the comments :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c73b4e9b50e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Spider-Man vs. Arkham Knight — a game design study]]></title>
            <link>https://leolesetre.medium.com/spider-man-vs-arkham-knight-a-game-design-study-7eb7a02bec46?source=rss-104a172a987d------2</link>
            <guid isPermaLink="false">https://medium.com/p/7eb7a02bec46</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[batman]]></category>
            <category><![CDATA[spider-man]]></category>
            <category><![CDATA[zelda]]></category>
            <dc:creator><![CDATA[Léo Lesêtre]]></dc:creator>
            <pubDate>Wed, 18 Mar 2020 10:11:04 GMT</pubDate>
            <atom:updated>2020-12-12T17:26:03.325Z</atom:updated>
            <content:encoded><![CDATA[<h3>Spider-Man vs. Arkham Knight — a game design study</h3><h4>How to design compelling secondary gameplays</h4><p><strong>It appears the discussion of <em>Marvel</em> vs. <em>DC</em> is everywhere these days. Movies, series, everything but comic books, and yes, even games!</strong></p><p><em>Insomniac Games </em>released in 2018, its new <em>Marvel’s Spider-Man </em>game, taking much inspiration from another major superhero-themed game: <em>Batman: Arkham Knight </em>by<em> Rocksteady Studios</em>. Playing both those games made me understand a fundamental lesson about secondary gameplay design.</p><h3>Opposition in similarities</h3><p>Both games portray a comic book <strong>superhero</strong> and present a <strong>heavily scripted storyline</strong> the player experiences through an <strong>open-world city—this</strong> open-area flourishing with different <strong>activities revolving around different gameplays</strong>.</p><p>Namely: Sneaking, Navigating, Fighting, Searching, Collecting stuff, taking pictures of lovely monuments, and <strong>Solving puzzles</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*z6CFwydU-PY2U13DtE8G3w.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*O9ydjQjJwz3TfI331PshOQ.gif" /><figcaption>Batman: Arkham Knight (on the left) and Marvel’s Spider-Man (on the right)</figcaption></figure><p><strong>However, very much like cuisine, ingredients are essential, but the recipe defines the final product.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*kQcXufXoK2UnTliUliHOIA.gif" /><figcaption>Sometimes you get unexpected results even from a familiar formula.</figcaption></figure><p>And the recipe here couldn’t be more different, particularly when it comes to this last piece: <strong>puzzle</strong>.</p><h3>Dark Knight vs. Friendly Neighbor</h3><p>Let’s start by taking a look at each game approach to puzzle design.</p><h4>Batman: Arkham Knight</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*o0vqGXNeIg8DDh95cih4iw.gif" /><figcaption>Batman: Arkham Knight title screen</figcaption></figure><p>In <em>Batman: Arkham Knight</em>, the city of Gotham cripples with puzzles. Installed here (very fittingly) by the Riddler to test out the reflection skills of the player.</p><p>At least, this is what appears on the surface. But <strong>most “puzzles” really consist of knowing how to use the different gadgets and moves at your disposal</strong>.</p><p>Not to say that <em>Arkham Knight </em>puzzles never require the player to think and find a specific pattern to overcome a problem. However, the most significant friction comes from knowing which tool to use and how to use it, learning it along the way if necessary.</p><p><strong>In that sense, many situations are at the crossroad between puzzles and tutorials.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*tca1ZD2WWgm1ahS0BH-ChA.gif" /><figcaption>Batman: Arkham Knight puzzle gameplay</figcaption></figure><p>In the <em>Batman: Arkham</em> series, the puzzles play organically and seemingly in the global experience. Some may require you to press a button or enter into a building to start; still, there is no strict cut between the exploration and the puzzle sequence. In both cases, you have the same abilities and controls as in the rest of the game.</p><h4>Marvel’s Spider-Man</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*KjV9KXxuvYrc8a8CZUMMYw.gif" /><figcaption>Marvel’s Spider-Man title screen</figcaption></figure><p>At the other end of the spectrum, lab stations are scattered around New York City, waiting to be reprogrammed and repaired by Spider-Man.</p><p>However,<strong> in sharp opposition to the <em>Arkham</em> games, <em>Spider-Man</em>’s puzzles play very straightforward</strong>.</p><p>Puzzle sequences are entirely different gameplays: Different cameras, separate commands, specific capacities. <strong>It is the textbook definition of a “mini-game</strong>”: a completely different game, with its own set of rules and restrictions, crammed into another bigger game.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/1*o_g-QXgNyZ0T8CBqhTdEqw.gif" /><figcaption>Marvel’s Spider-Man puzzle gameplay</figcaption></figure><h4>In short</h4><h4>Batman: Arkham Knight puzzles</h4><ul><li><strong>Camera</strong>: Similar to open-world exploration</li><li><strong>Control</strong>: Similar</li><li><strong>Capacities</strong>: Similar</li></ul><h4>Marvel’s Spider-Man puzzles</h4><ul><li><strong>Camera</strong>: 2D fixed</li><li><strong>Controls</strong>: Unique control set</li><li><strong>Capacities</strong>: Specific ability to place, remove, and rotate pieces</li></ul><p>And form this comparison, it is undeniable that the<strong> <em>Batman: Arkham Knight</em> approach feels more immersive, more rewarding, and overall more like solving situations</strong>. While you indeed feel smart when addressing a situation as Batman, Spider-Man’s trials are more like a chore, like something you have to do before you can go back to the “real” game. <br><strong>But why?</strong></p><h3>The secret of Batman: Skills transversality</h3><p>What I refer to as <strong>skill transversality</strong> is the idea that the primary and secondary gameplays share at least some of their controls and abilities. Meaning that <strong>investing time in secondary activities will result in valuable learning to enrich your possibilities in other situations</strong>.</p><p><strong>The skills you gain through one particular side activity can be useful outside of those specific circumstances.</strong></p><p>That’s how <em>Batman: Arkham Knight</em> builds a more organic, more immersive approach to puzzle situations. In Gotham, every puzzle is an experimentation chamber, provoking you into using your abilities in a certain way.</p><p>Being required to quickly throw five shurikens using the auto-aim to press five buttons at once can seem pretty random at first. But this turns out pretty useful when you encounter five enemies running at you in a later fight. There are plenty of examples like this in the game.</p><h3>But with great powers comes great complexity.</h3><p><em>Batman: Arkham Knight</em>’s approach is very efficient, indeed, but is not without flaws. Because in building a wide variety of situations, the game enters another type of problem: <strong>Feature creep</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gqN9iQSN3D5NJ1eEobBw2Q.jpeg" /><figcaption>the different gadgets available in Batman: Arkham Knight</figcaption></figure><p>The dark knight inventory adds up to twelve different devices, each requiring a specific input combination. This situation results in a mere impossibility for the player to fully exploit all capabilities at his disposal. This being almost impossible in a moment of stress.</p><p>Enter a third game that’s also an open-world with stealth, combat, exploration, collection, and of course, puzzle: <em>The legend of Zelda: Breath of the wild</em>.</p><p><strong>That’s right! To the question “which one is better, <em>DC</em> or <em>Marvel</em>?” the answer is, and always was: “<em>Zelda</em>”!</strong></p><h3>The Hero of Puzzles</h3><p><em>The Legend of Zelda: Breath of the wild</em> masterfully creates more than <strong>100 thoughtful situations</strong>, all based on only <strong>four abilities</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ab1zQQTeK-R8Gs6eTjJbbg.jpeg" /><figcaption>The runes (powers) of The Legend of Zelda: Breath of the wild</figcaption></figure><p><strong>You can achieve an unbelievable amount of things in Hyrule, with few capacities</strong>: create a bomb, move metal items, freeze an object in time, and create an ice pillar out of water. That’s it.</p><p>Even more impressive, many puzzles in <em>Zelda: BOTR</em> have more than just one solution. <strong>Not only succeeding at puzzle shrines teach you about your abilities, but exploring the rest of the game also provides you with alternative ways to overcome those puzzles.</strong></p><p>Almost every situation in the game is open to any approach, rather than locked in combat, stealth, or puzzle sets. <strong>Once you know how to use your abilities, taking on an enemy camp by delivering precise attacks, dropping rocks in a physics-puzzle manner, or sneaking around in the shadows, is up to you!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/435/1*uqjj1ktTgGM8gPqqKt3Omw.gif" /><figcaption>There are many ways to raid a goblin camp — Blowing it up is one of them.</figcaption></figure><p>That is fine and all, but we all know <em>Zelda</em> games are on another level. Is it possible to achieve this with any game? Well, there’s only one way to find out, and that’s trying!</p><h3>How to achieve this?</h3><p>How could we change <em>Marvel’s Spider-Man</em> approach to make it more like <br><em>The Legend of Zelda: Breath of the Wild</em>?</p><h4>1. Add interactions, remove features</h4><p><em>Spider-Man</em> puzzles often revolve around directing electricity from a power source to the desired device by rewiring an electrical panel, with limited blocs. <em>Breath of the Wild</em> has a puzzle with a very similar premise but which plays out very differently.</p><p><strong>In Hyrule, just like in New York, you’re faced with an incomplete network and a limited set of pieces to fix it</strong>. Only the circuit is on the floor, and you have to move around metal items physically. <em>Fujibayashi</em>’s team didn’t develop a new feature, but rather a further interaction between existing ones: Metal items conduct electricity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/1*VpOZ8w2m_dLQ27hxDdKO9Q.jpeg" /><figcaption>Shrine puzzle revolving around an electric grid in The Legend of Zelda: Breath of the Wild</figcaption></figure><p>Now the existing functionality of moving metal items around has a lot more depth and applications to it, without any additional complexity.</p><p>Thanks to this interaction, you can even skip some steps using metal weapons from your inventory to close the circuit — one of those sweet multi-solution puzzles I mentioned earlier.</p><p><strong>So, what if, instead of creating an entirely new game, you could achieve the same objective using the web Spider-Man shoots by making it conduct electricity?<br></strong>What if the player had to build a tridimensional network of electrical web around the space, with a limited amount of links, connecting conductive objects to keep the current flowing?</p><h4>2. Build the secondary loop into the main one</h4><p>For side activities to be compelling, they should enrich the primary experience.</p><p><strong>Now that Spidey’s web is conducting electricity, we could use this to build a more thoughtful approach to another gameplay: let’s say combat.</strong></p><p>Luckily for us, there’s already an interaction between electricity and enemies in the game: Foes are stunned when hit by lightning. This effect can come from a particular gadget: the electric web or from being in contact with electrified objects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/1*LSJxy-l3hbrYeXeDg3WMKw.gif" /><figcaption>Drop an electric meter onto a bunch of enemies to stun them for a few seconds</figcaption></figure><p>From here, it’s not too crazy to imagine that you could connect those electric meters to floor panels or door handles. Twisting elements that the enemies are likely to enter in contact with for a shocking surprise.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*G4iFTZMTS4UIcwAuHV7SrQ.gif" /><figcaption>The game lays out plans for a lot of fun interactions with electricity but falls short of their potential</figcaption></figure><h3>TL;DR</h3><ul><li><strong>No matter what secondary gameplay you are designing, always remember the features that already exist in the main gameplay.</strong></li><li><strong>Ask yourself how adding interactions to those might result in the gameplays and challenges you want to create.</strong></li><li><strong>Think about those new interactions. How could you use them to add depth to the global experience?</strong></li></ul><h3>Post-credit scene</h3><p>With <em>Marvel’s Spider-Man </em>being more than likely to get a sequel sooner or later, I give you Rendez-Vous when it happens. To see if, and how, <em>Insomniac Games</em> builds upon the solid, yet the imperfect, structure of the first one. Hopefully, in the area of secondary gameplays as well.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7eb7a02bec46" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>