<?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 Thomas Theux on Medium]]></title>
        <description><![CDATA[Stories by Thomas Theux on Medium]]></description>
        <link>https://medium.com/@thomas_1379?source=rss-9600798b4f3d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pwqsr4NOfVmjBPHRgdmyeQ@2x.jpeg</url>
            <title>Stories by Thomas Theux on Medium</title>
            <link>https://medium.com/@thomas_1379?source=rss-9600798b4f3d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 02:20:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thomas_1379/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[How to re-invent character progression [part 2]]]></title>
            <link>https://medium.com/@thomas_1379/how-to-re-invent-character-progression-4f1a3ec24df7?source=rss-9600798b4f3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4f1a3ec24df7</guid>
            <category><![CDATA[ux-framework]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[gamedev]]></category>
            <category><![CDATA[player-experience]]></category>
            <dc:creator><![CDATA[Thomas Theux]]></dc:creator>
            <pubDate>Wed, 07 Aug 2019 15:17:55 GMT</pubDate>
            <atom:updated>2019-08-07T15:18:59.069Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*33ZANcxfLMftVkLGN1phlA.png" /></figure><h4>or The TAO Framework</h4><p><em>This is [part 2] of the series </em><a href="https://medium.com/p/5e0b508cfe74/"><strong><em>Designing a game for literally only 2 people?</em></strong></a></p><p>When you think about character progression or level-up systems in RPGs you most probably think about this basic concept:</p><p>You kill enemies. You gain XP. Enough experience yields a level. One level gives you points. These can then be invested in your character to improve stats or learn skills.</p><p>These concepts work great, but they are quite old already. I think it’s time for game designers to start thinking more creatively.</p><p>That’s why I thought of a system to come up with new ideas for character progression: the <strong>TAO Framework</strong>.</p><h3>What is the TAO Framework?</h3><p>The <strong>TAO Framework</strong> is a framework where we break down a complete character progression system (CPS) into single stages and try to come up with new ideas for every stage while also analyzing existing systems for benchmarking.</p><p>Now every system can be broken down into these three stages:</p><p>Trigger ➞ Action ➞ Outcome</p><p>The <strong>Trigger</strong> defines what needs to happen before the player can actually improve their character. It’s like a requirement.</p><p>The <strong>Action</strong> consists of the main interaction with the system. What does the player do to actively improve their character?</p><p>The <strong>Outcome</strong> is what the actual result looks like. Think of it as the reward for the character.</p><h3>What does it look like?</h3><p>Let’s look at an actual example of an existing system: <strong>Diablo III</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tGSSurUmUeLDEnXtuJV0KA.png" /></figure><p>We have started a new game with the Wizard class and already leveled our character up to level 5.</p><h4>The Trigger</h4><p>We continue killing some monsters to gain more XP. Once we have gathered 9,000 experience points, we reach level 6. This is where we unlock the <em>Charged Blast</em> rune. The rune is a modifier to our basic skill <em>Magic Missile</em>.</p><h4>The Action</h4><p>We can now go into our character’s skill menu where we can choose the modifier we want to use with our <em>Magic Missile</em> skill. We assign the newly unlocked <em>Charged Blast</em> rune.</p><h4>The Outcome</h4><p>The rune improves our <em>Magic Missile</em> skill by 325% in weapon damage which we can also see and feel in battle.</p><p>So we have a <strong>Trigger</strong>, an <strong>Action</strong>, and an <strong>Outcome </strong>➜ Level up, assign the rune, feel the improvement.</p><h3>Let’s develop a new concept!</h3><p>Now that we have analyzed a system and have a small benchmark we can try and come up with our own concept with the help of the TAO Framework and the <a href="https://medium.com/@thomas_1379/a-ux-method-for-crafting-game-mechanics-48dba2a0a433">OASIS Method</a>.</p><h4>Where to start?</h4><p>I like to start at the end and think about the <strong>Outcome</strong> first. That way we know our goal and what we want the result to look like. Think about what you want your character to progress in.</p><p>This can be anything from classic stats (e.g. <em>damage</em> or <em>attack speed</em>) to more exploratorive improvements (e.g. a worm that barely <em>crawls</em> but learns new ways to traverse, like <em>flying</em>, <em>swimming</em>, or <em>walking</em>).</p><h4>Defining an Outcome</h4><p>As mentioned above I’ll start with the result.</p><p>I want the players to improve their hero in a few basic things. This means, they can improve very classic stats like</p><ul><li><strong><em>HP +10%,</em></strong> or</li><li><strong><em>Crit Hit Chance +2%</em></strong></li></ul><p>but also a little more unconventional stuff like</p><ul><li><strong><em>Respawn Time -2s,</em></strong> or</li><li><strong><em>+100 Gold every 1000th step</em></strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y623HSyXyGfcB58doYQdPQ.png" /><figcaption>This is a collection of 24 different stats the players will be able to use</figcaption></figure><h4>Creating a Trigger</h4><p>Next, we need a <strong>Trigger</strong> that lays the foundation for the main interaction. So let’s brainstorm a few requirements.</p><p>Here’s a list of Triggers I found in other games or came up with:</p><ul><li>Gaining a level</li><li>Collecting stat points</li><li>Killing special enemies (e.g. bosses or from side quests)</li><li>Finding rare items/treasures/loot</li><li>Solving quests</li><li>Gathering gems/runes/stones/..</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*f7BUgKWpikbtCdF5g_IrYg.png" /><figcaption>A few of the ideas I brainstormed</figcaption></figure><p>These Triggers now initiate the whole character progression process. Without these, it’s not possible for players to improve their hero.</p><h4>Defining an Action</h4><p>And finally we need an <strong>Action</strong> that defines our core interaction to improve our character.</p><p>For this part of the framework the <a href="https://medium.com/@thomas_1379/a-ux-method-for-crafting-game-mechanics-48dba2a0a433">OASIS Method</a> always helped a great deal.</p><blockquote>The method basically consists of steps to come up with new ideas by <strong>outlining</strong> your situation, <strong>analysing</strong> the basic problem, finding other <strong>scenarios</strong> with the same problem, figuring out their <strong>interaction</strong> and then transferring the <strong>solution</strong> to your own problem.</blockquote><p>After creating wireframes from the ideas, I made small prototypes with <a href="https://www.adobe.com/products/xd.html">Adobe XD</a>, tested them, and eventually picked one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*q3oilYeiogjoPm_Y_J7EAA.gif" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FeA9VkJkToG2JJsO-yb-8g.gif" /></figure><p><em>These are only some of the prototypes I created and tested. You can find all of them in this article: </em><a href="https://medium.com/@thomas_1379/a-ux-method-for-crafting-game-mechanics-48dba2a0a433"><em>The OASIS Method</em></a></p><p>And this is the idea I decided to go with. It’s a collect-and-link concept where players can bind gems to fixed equipment (you‘ll always have the same equipment) if the linking process is successful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*-ZqdzJ4KRT3L_IdMJyy4CQ.gif" /><figcaption>The “Linking” prototype I eventually decided on</figcaption></figure><h4>Bringing it all together</h4><p>Now let’s sew together all 3 pieces of the framework to get one big concept:</p><ol><li>The <strong>Trigger</strong>: slay enemies who then will drop <em>Ghosts</em> that have different attributes</li><li>The <strong>Action</strong>: Go to the next Blacksmith (I call them <em>Necromancer </em>in my game) and link the <em>Ghosts</em> with your equipment</li><li>The <strong>Outcome</strong>: This then improves your character with the attributes of the linked <em>Ghosts</em></li></ol><h3>That’s it, that’s all</h3><p>And there you have it. With this framework we came up with a new concept for character progression.</p><p>Now this concept seems like it’s more on the side of traditional character progression (since linking something to your hero’s equipment isn’t that new) but with a little tweak (since you always have the same equipment but continuously improve it with <em>Ghosts</em>).</p><h4>The UX perspective</h4><p>If we take a look at the player/user experience this is an important tweak because of 3 reasons:</p><ol><li>We give the players kind of the same mechanics they already know<br>➞ This helps them <strong>adopt the concept</strong> faster</li><li>We add a little bit of newness (with the fixed equipment)<br>➞ So it doesn’t feel like other RPGs</li><li>But we have a bigger change in how we deliver it to players (with the <em>Ghosts</em> that players can link whenever they want and also easily exchange)<br>➞ This gives a major (perceived) <strong>boost to the feeling of newness</strong></li></ol><p>So this concept should feel kind of innovative to players because of the tweak even though we only changed a few things.</p><p>This is part 2 of a series called <a href="https://medium.com/@thomas_1379/designing-a-game-for-literally-only-2-people-part-1-5e0b508cfe74"><strong>Designing a game for literally only 2 people?</strong></a><strong> </strong>Other parts include:</p><ul><li>a fluid <strong>character stats </strong>system [part 3]</li><li>a dynamic <strong>reputation </strong>system [part 4]</li><li>a simple <strong>skill board</strong> system [part 5]</li><li>a flexible <strong>character class</strong> system [part 6]</li></ul><p>I will explain every system in detail with a special focus on user/player experience. So stay tuned 📻</p><p>—</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4f1a3ec24df7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Designing a game for literally only 2 people? [part 1]]]></title>
            <link>https://medium.com/@thomas_1379/designing-a-game-for-literally-only-2-people-part-1-5e0b508cfe74?source=rss-9600798b4f3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e0b508cfe74</guid>
            <category><![CDATA[gamedev]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[friends]]></category>
            <category><![CDATA[xp]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Thomas Theux]]></dc:creator>
            <pubDate>Sat, 06 Jul 2019 09:31:18 GMT</pubDate>
            <atom:updated>2019-08-08T08:28:08.311Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L-buaqU4F-NDHmCjp5xVdw.png" /></figure><h4><em>or</em> The story of a game for two best friends</h4><h4>An introduction</h4><p>Developing a game is like going on a journey without having a map. Without knowing where you’ll end up. Not knowing where you’re actually going.</p><p>At least that’s what it always felt like to me.</p><p>I was developing early prototypes. Testing them with a lot of players. Getting their feedback. And having a meltdown after every test session, wanting to kill the project right away.</p><h4>The problem</h4><p>The reason was simple: I always wanted to implement every feedback, direction, or idea. I wanted to make players happy. All of them.</p><p>The problem: I didn’t have a clear vision. Didn’t have a target group. Always wanted to please <strong>all</strong> players. Being afraid of people hating me for not implementing their feature or idea.</p><h4>My solution</h4><p>Screw all that, I’m focusing on <strong>one</strong> target group. And this group consists of 2 people. One of them is me. The other? My best friend. And that’s it.</p><p>So I decided to come up with a game idea we both like, develop a first prototype, and implement every feature and idea we’re having.</p><p>Making it <strong>our</strong> game!</p><h4>Making it more concrete</h4><p>Let’s get to it. What’s the game? What are the ideas? What are we building?</p><p>It’s a <strong>local co-op fantasy action RPG</strong>. And here’s the first prototype:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*NLBozVUwOhtbwB_zcwVS7g.gif" /><figcaption>A short prototype of <strong><em>Techno Hunter</em></strong></figcaption></figure><p>The game features the following components:</p><ul><li>an equipment-based <a href="https://medium.com/@thomas_1379/designing-a-game-for-literally-only-2-people-part-1-5e0b508cfe74"><strong>character progression</strong> [part 2]</a></li><li>a fluid <strong>character stats </strong>system [part 3]</li><li>a dynamic <strong>reputation </strong>system [part 4]</li><li>a simple <strong>skill board</strong> system [part 5]</li><li>a flexible <strong>character class</strong> system [part 6]</li></ul><p>I will explain every system in detail with a special focus on user/player experience. So stay tuned 📻</p><p>—</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e0b508cfe74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A UX method for crafting game mechanics]]></title>
            <link>https://medium.com/@thomas_1379/a-ux-method-for-crafting-game-mechanics-48dba2a0a433?source=rss-9600798b4f3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/48dba2a0a433</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[ux-method]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[player-experience]]></category>
            <category><![CDATA[gamedev]]></category>
            <dc:creator><![CDATA[Thomas Theux]]></dc:creator>
            <pubDate>Fri, 21 Jun 2019 13:57:17 GMT</pubDate>
            <atom:updated>2022-02-17T14:12:39.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eoIKZxKe6XPCaeBXntAkcQ.png" /></figure><h4>or The OASIS Method</h4><p>On my mission to combine UX and Game Design, I’ve come up with a method that has roots in UX Design but can perfectly be applied for creating and developing new game mechanics.</p><p>A few days ago I was trying to develop a framework for character progression.</p><p>At some point I reached the point where I didn’t exactly know how to think up new interactions and game mechanics for equipping your character in an RPG.</p><p>That’s when I came up with this method that is basically a tweak of the <em>Put to other uses</em> part of the <a href="https://en.wikipedia.org/wiki/S.C.A.M.P.E.R">S.C.A.M.P.E.R method</a> and shall help game designers create new concepts.</p><h3>The Method</h3><p>Let me show you the basic structure of the OASIS Method:</p><h4>O — Outline</h4><p>First we need to outline our scenario, problem, or situation.</p><h4><strong>A</strong> — Abstraction</h4><p>Next we analyse the situation by abstracting the situation to the bare minimum.</p><h4><strong>S</strong> — Scenarios</h4><p>We then try to find other scenarios where the analyzed breakdown also applies.</p><h4><strong>I</strong> — Interaction</h4><p>After that we try to define the scenario’s core interaction.</p><h4><strong>S</strong> — Solution</h4><p>And finally we retransfer the interaction back to our initial outline to get to a solution.</p><h3>Applying the Method (an example)</h3><p>To better understand how to use the method, I’ll explain it with the example I mentioned above: coming up with concepts for equipping a character in an RPG.</p><p>I like to phrase the problems I’m trying to solve as <a href="https://toolkit.mozilla.org/method/how-might-we/">how might we</a> questions. This way we have an open question for our situation.</p><p>In my scenario the question looked like this:<br><em>How might we design a new character progression experience for RPG players?</em></p><p>Now let’s apply the method:</p><h4>Outline</h4><p>First, I outlined my situation in a short sentence that made clear what the method should solve:<br><em>We need a character equipment mechanics that is different to those in other games.</em></p><h4>Abstraction</h4><p>If we take a look at the classic game loop for equipment, it looks like this:</p><ul><li>player kills enemies</li><li>enemies drop equipment (like armor or weapons)</li><li>player picks them up</li><li>player can equip them in the character UI</li><li>player gets stronger</li></ul><p>This means players have an inventory with many items. They can then put them in slots of their character where usually only one of a kind can be equipped (one helmet, one pair of boots, etc..).</p><p>After describing the main problem I tried to abstract it as much as I could to get the most generic breakdown:<br><em>Many different items (quantity 1–50) where always one is active / being used but can be exchanged with the other ones.</em></p><h4>Scenarios</h4><p>Now that I have a generic breakdown of the problem I can search for other areas with the same breakdown. I found the following scenarios:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2nAfYFrsAYbu-7_WFOjyNA.png" /><figcaption>Dropdown in the Desktop &amp; Screen Saver settings</figcaption></figure><p><strong>A dropdown menu</strong><br>A simple dropdown where one is always selected and active but the user can change it anytime he wants by opening a list of options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H86yaH-EmdtczHFd4JkgkQ.png" /><figcaption>Spotify playlist</figcaption></figure><p><strong>Spotify playlists</strong><br>Doubleclick to start a song. Automatically play the next song when this one is over.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3mJWjb7POAkNBVC7" /><figcaption>Photo by <a href="https://unsplash.com/@fikrirasyid?utm_source=medium&amp;utm_medium=referral">Fikri Rasyid</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Supermarket cash register<br></strong>Consumer puts their goods on the conveyor belt which are then being moved from left to right to scan them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y7pd3ekPv3cpcBlXlKHM2g.png" /><figcaption>MacOS folder structure (icons view)</figcaption></figure><p><strong>Folder structure</strong><br>The icons view in a folder structure on your computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1bhFc6OzJa95O2Fh" /><figcaption>Photo by <a href="https://unsplash.com/@slavmetal?utm_source=medium&amp;utm_medium=referral">Max Max</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>Bartering</strong><br>Bartering people that exchange one good with another one</p><h4>Interaction</h4><p>Now that we have found a few scenarios where we can get ideas from, we need to identify the specific interaction of this situation. It’s best to describe the core interaction as generic as possible, this makes transfering easier later.</p><p><strong>Dropdown<br></strong>Click to open, select from list, click to confirm</p><p><strong>Spotify playlist<br></strong>Start by clicking an item, automatically activate next one after the first is done</p><p><strong>Supermarket<br></strong>Move items one by one from one side to the other</p><p><strong>Folder structure</strong><br>Grid with only one item active that you can select by navigating and clicking</p><p><strong>Bartering</strong><br>You have one item that you exchange with another person‘s while holding always only one item at a time</p><h4>Solution</h4><p>Now that we have figured out our interactions from other situations that share the same basic problem, we can transfer them back to our scenario and come up with solutions.</p><p><em>(I found that some of my concepts were pretty similar, so I simply combined them)</em></p><p><strong>1 List View</strong><br>The list view is a very classic equipment system that combines the interactions of the <strong><em>dropdown menu</em></strong> (click to get a list with options to choose from) and the <strong><em>folder structure</em></strong> (having a grid view and selecting one option).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*EgVV6YQoYTk6IwxHLS85Ow.gif" /><figcaption>1 List View</figcaption></figure><p><strong>2 Stack</strong><br>The stack concept is an semi-automated equipment system. Players collect equipment and add them to a stack. After the equipped item wears out, the next item will automatically be equipped. It is derived from the <strong><em>Spotify playlist</em></strong> interaction (select one item to start, automatically activate next).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FDm0fRf2BlKGgniXXE0tgw.gif" /><figcaption>2 Stack</figcaption></figure><p><strong>3 One by one</strong><br>The ony by one concept is derived from the <strong><em>bartering</em></strong> interaction where you can always carry only one item at a time but are able to exchange it. Here you see your currently equipped item (yellow highlight) and the dropped one lying around in the level for the player to pick up and exchange.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YZEOxsA0-tJ3ahe-0ABe1g.png" /><figcaption>3 One by one</figcaption></figure><p><strong>4 Horizontal swiping</strong><br>Another concept I came up with is the horizontal swiping one. This concepts works with the <strong><em>supermarket</em></strong> interactions: bringing things from one side to the other by swiping.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*FoMUqglp9DOi_HdM8DR71g.gif" /><figcaption>4 Horizontal swiping</figcaption></figure><p>The interactions and concepts triggered another idea that I wanted to explore:</p><p><strong>5 Diamond linking<br></strong>This one is a little different than the others since you’re not collecting equipment but single diamonds with different abilities. First you loot them from enemies then you go to a blacksmith that links them in your accessories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*uFEQCtoMFpGkOBqo8cyqCQ.gif" /><figcaption>5 Diamond linking</figcaption></figure><h3>Conclusion</h3><p>And so I eventually had 5 different solutions that dervied from 5 different scenarios with the same basic problem. Not every solution was directly linked to one of the scenarios but it triggered other ideas.</p><p>In this case the method worked and gave me 5 solutions. There might be other cases where the method needs to be tweaked a little or doesn’t work at all —But the basic method should always work.</p><p>Go <strong>be creative</strong> and craft <strong>awesome games 🎉</strong></p><p>—</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48dba2a0a433" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Game Design is easy]]></title>
            <link>https://medium.com/@thomas_1379/game-design-is-easy-2f8150a82734?source=rss-9600798b4f3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/2f8150a82734</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[playtesting]]></category>
            <category><![CDATA[user-eperience]]></category>
            <category><![CDATA[gamedev]]></category>
            <category><![CDATA[player-experience]]></category>
            <dc:creator><![CDATA[Thomas Theux]]></dc:creator>
            <pubDate>Thu, 04 Apr 2019 16:01:19 GMT</pubDate>
            <atom:updated>2019-04-04T16:01:19.218Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ETxJOElRipWH-CKlY5L6Tw.png" /></figure><h4>A guide to crafting skill trees</h4><p>Okay to be fair: game design is not easy at all, I just needed a provocative title.</p><p>Let’s get right to it. This article talks about developing the perfect skill tree for your game and how you get there with just a little bit of groundwork. And the best way to talk about it is to give a real life example. Let’s go!</p><p><em>(you can skip to the very end if you’re only interested in the main takeaways)</em></p><p>Imagine mixing Battle Royale gameplay with Action RPG fighting and add a skill tree concept where players can develop their character.<br>And that‘s what <strong>Feierabend Heroes</strong> (working title)<strong> </strong>is: a local competitive party game with chaotic fighting until the last hero is standing.</p><p>Now imagine a massive skill tree where unlimited character builds can be developed and everyone has their unique hero. That’s what I had in mind when I started creating the game. And this was the first draft of the tree:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TC38EGkWlc451BD6jcO8AA.png" /><figcaption>The initial skill tree design for Feierabend Heroes</figcaption></figure><p>It wasn’t too bad. I liked the direction and still loved the idea, so I kept going.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*amfXLdT9H9P43sFT9j7xkw.gif" /><figcaption>A few of many more drafts</figcaption></figure><p>After the first design was done, I implemented it in Unity to give it a first go and playtest it with a few people. I’ll make it quick: they hated it! <strong>But why?</strong></p><p>The skill tree needed to work with only one fourth of the screen since it was a local multiplayer game → splitscreen with up to 4 players.</p><p>If you take a look at this screenshot you might guess what some of the issues could’ve been. But let me explain in detail what happened and how you can avoid these problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PzcCa92X0zciXvFHHT2RTw.png" /><figcaption>What could’ve been the problem here 🤔</figcaption></figure><p>Let us take a look at the attributes of the game again:<br>• fast-paced<br>• short rounds<br>• chaotic fighting<br>• time-limited (120 seconds per round)<br>• surprise enemy encounters</p><p>Now let’s take a look at the attributes of the skill tree design:<br>• many different options<br>• lots of visual details<br>• a bunch of detailed information for each skill<br>• many attributes and skills that can be improved</p><p>Do you feel it? The attributes of the design did not match the characteristics of the game <strong>at all</strong>! And that is why the first test failed.</p><blockquote><strong>💬 Takeaway: </strong><em>List your game’s characteristics and find concepts that match these attributes — and don’t lie to yourself.</em></blockquote><p>Okay, back to the drawing board.</p><p>.. is what I should have done. I believed in the concept though so I only iterated on the layout rather than going back to rethink the whole concept.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FOojI1XikRrBkZLYscbuhw.png" /><figcaption>Some of the new layouts of version 2</figcaption></figure><p>So I simply tried to reduce the amount of options players have. I started with <strong>32</strong> abilities and skills that also had dependencies and reduced them to <strong>11</strong>.</p><p>I didn’t want to get rid of the stats sheet though. I wanted it to be in the game and thought it’d help players, so I brought it in again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eIkXlzjN3FPBkrfLk9i5Sw.png" /><figcaption>Reduced design with a stats sheet</figcaption></figure><p>Since the game should run on consoles it had to work in an environment where players sit around 2–3 meters away from the screen.</p><h3><em>⚠️ Experiment </em>⚠️</h3><p>Let’s do the test: move about 2 steps away from your computer (or phone) and take a look at this screenshot. Can you still read it?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HPNoCdRgIsePpd1HupJk4g.png" /><figcaption>The second TV test with a “reduced” design</figcaption></figure><p>Okay you can come back now 😅</p><blockquote>💬 Takeaway: Test in real environments! If you design games for consoles then plug your computer to a TV. If you design for forklift displays, go get yourself a forklift and test it there!</blockquote><p>So I improved readibility with bigger gaps, larger font sizes, and eventually removed the stats sheet since the need for it just wasn’t there and it took up a lot of space I really needed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jM-9VD1JB-aKaBtsbpi2aw.png" /><figcaption>The fifth TV test I conducted with the new layouts</figcaption></figure><p>After testing these designs I still got feedback, that it’s too much, people were not reading the texts, the information was not close to the icons etc..</p><p>By the way: I already spent more than 50 hours designing and redesigning the skill tree over and over again. So I was already kinda suffering from tunnel vision 😅</p><p>It was embarassing. The feedback I got. I should have known it. All of it!</p><p>I’m currently working as a Senior <strong>User Experience Designer</strong> and have a few years of experience with developing proper software concepts. But let me tell you, it’s different with games. Is what I thought. In fact, Game Design can be very similar.</p><p><strong>Game Design is not that different to Application Design.</strong><br><em>(even though they seem different)</em></p><blockquote>💬 Takeaway: When it comes to UI design for games, try applying the 10 usability heuristics (see link below) that help to solve basic design problems.</blockquote><blockquote>💬 Takeaway: Try applying design thinking methods to game design and vice versa — they can complement each other.</blockquote><p><a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 Usability Heuristics for User Interface Design</a></p><p>Okay, alright. Back to the very beginning. I stopped implementing every single idea and quick-fix in Unity and started creating basic layouts in <a href="https://www.sketch.com/">Sketch</a>.</p><p>I created a ton of different versions, iterated on them, kicked some of them out, merged concepts and tested the ones I thought make sense.</p><p>Here are some of the concepts I came up with:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*UWrbtbPCmbS_6oBICgqCaQ.gif" /><figcaption>The <strong>Out-of-the-box</strong> concept</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*zzxN9oTxe-eghLtOwqCc9g.gif" /><figcaption>The <strong>Expand-and-collapse</strong> concept</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*2qNpmWOJc69YhTfHLkmL4g.gif" /><figcaption>The <strong>Folders</strong> concept</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*6xvXCaxMQPmGi4q7MU5diA.gif" /><figcaption>The <strong>Cards</strong> concept</figcaption></figure><p>After a bunch of surveys, questionnaires, and tests with players I had 2 finalists that I wanted to implement and do an <a href="https://en.wikipedia.org/wiki/A/B_testing">A/B Testing</a> session.</p><blockquote>💬 Takeaway: Quickly drafting these layouts, animating them with <a href="https://www.adobe.com/products/xd.html">Adobe XD</a>, and testing them was the best way to come up with final concepts for the skill tree.</blockquote><p>And so, these are the latest concepts that I planned on implementing in Unity:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FyTmcdl1rCm0%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DyTmcdl1rCm0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FyTmcdl1rCm0%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/7ce753356cc46fff650c8dac4e6def23/href">https://medium.com/media/7ce753356cc46fff650c8dac4e6def23/href</a></iframe><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FCItlwRhjeME%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DCItlwRhjeME&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FCItlwRhjeME%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/812a4553c781942d1749b556e441a049/href">https://medium.com/media/812a4553c781942d1749b556e441a049/href</a></iframe><p>I only needed to implement them in Unity now. I asked my friends and we picked a date for the tests. Now I had a deadline. And it was in 2 weeks.</p><p>So I started with the <strong>List</strong> design, backed up the project, and exported a build for the test. After that I immediately started with the <strong>Card</strong> design and finished it just one day before the deadline.</p><p>😅 Phew, enough time to test and bugfix before the big playtests.</p><blockquote>💬 Takeaway: Have a deadline and plan properly, even if you’re working solo. I use <a href="https://trello.com/">Trello</a> to organize my tasks and work with one week <a href="https://www.atlassian.com/agile/scrum/sprints">sprints</a> to get my stuff done.</blockquote><blockquote>💬 Takeaway: Don’t set deadlines that are too far in the future, you won’t get work done. Keep <a href="https://en.wikipedia.org/wiki/Parkinson%27s_law">Parkinson’s Law</a> in mind: “work expands so as to fill the time available for its completion”.</blockquote><p>Now, I scheduled 2 playtests with 2 different groups. They both should test the <strong>List</strong> concept vs the <strong>Cards</strong> concept and give feedback regarding the experience. The plan was to let the players decide which one of them they liked best and eventually should made it into the game.</p><p>Now which do you think won? You’ve probably got your favorite in mind 😉</p><p>The result was <strong>50:50</strong>.. Yikes!</p><p>Since this whole concepting, prototyping, and testing phase took me more than 80 hours I decided to move on and focus on other important tasks. I integrated both concepts and made it an option for the players to choose in the match settings (I might take one out in the future).</p><blockquote>💬 Takeaway: If you have a target/player group you’re designing your game for, it makes decisions way easier! Don not make the mistake of not having your players in mind! This is similar to creating <a href="https://www.nngroup.com/articles/persona/">personas</a> in classic application design.</blockquote><p>And so ends the journey. The skill tree chapter is closed. For now.<br><em>(if you want to find out more about </em><strong><em>Feierabend Heroes</em></strong><em>, check this </em><a href="https://feierabend-crew.com/feierabend-heroes.html"><em>page</em></a><em>)</em></p><h3>What to take from this journey</h3><p>I’ll make it short, because the story was long enough:</p><ul><li>Write down your game’s <strong>attributes</strong> and develop concepts that match these</li><li>Test in <strong>real</strong> <strong>environments</strong>, e.g. get a TV when developing for consoles</li><li><strong>Get familiar</strong> with the <a href="https://www.nngroup.com/articles/ten-usability-heuristics/">10 usability heuristics</a> that help shape your designs</li><li><strong>Try out</strong> <a href="https://www.interaction-design.org/literature/article/5-stages-in-the-design-thinking-process">design thinking</a> methods and see if you can work with them</li><li>Prototype your ideas <strong>as cheap and early as possible</strong>, try tools like <a href="https://www.invisionapp.com/studio">InVision Studio</a> or <a href="https://www.adobe.com/products/xd.html">Adobe XD</a> (which are free)</li><li>Set a freaking <strong>deadline</strong>! (read about <a href="https://en.wikipedia.org/wiki/Parkinson&#39;s_law">Parkinson’s Law</a>)</li><li><strong>Organize</strong> yourself! (use tools like <a href="https://trello.com/">Trello</a> or <a href="https://asana.com/">Asana</a> — all free)</li><li>And <strong>get stuff done</strong>! (go with the <a href="https://www.atlassian.com/agile/scrum/sprints">sprint method</a>)</li></ul><p>Go <strong>be creative</strong> and craft <strong>awesome games 🎉</strong></p><p>—</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2f8150a82734" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[We Need New Level-Up Systems]]></title>
            <link>https://medium.com/@thomas_1379/we-need-new-level-up-systems-3efbb544ea15?source=rss-9600798b4f3d------2</link>
            <guid isPermaLink="false">https://medium.com/p/3efbb544ea15</guid>
            <category><![CDATA[level-up]]></category>
            <category><![CDATA[gamedev]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[player-experience]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Thomas Theux]]></dc:creator>
            <pubDate>Mon, 04 Feb 2019 12:50:34 GMT</pubDate>
            <atom:updated>2019-02-04T12:50:34.150Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8oML5EWRjCk774n79KjUg.png" /></figure><h4>An impulse to start thinking differently</h4><blockquote>Only keep reading if you’re a game developer or interested in game development️️!</blockquote><h3>Why do we love level-up systems in games?</h3><p>A quick answer would be that it’s simply satisfying to see our character learn new skills and bash monsters with these newly acquired abilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AoC0pA8ZIFX-Ivi0aZOK6A.jpeg" /></figure><p>But what is it really that fascinates us, that keeps us motivated to advance on skill trees or grind to level up?</p><h3>What’s the current status?</h3><p>Let‘s first have a look at the three main systems that emerged over time and have made it into a ton of games nowadays:</p><ul><li><strong>Level-based</strong> progression (aka EXP progress bars)</li><li><strong>Activity-based</strong> progression (aka Elder Scrolls style)</li><li><strong>Free-form</strong> advancement (aka Skill Trees)</li></ul><h4>Level-based progression</h4><p>A level-based progression system is simply a progress bar that indicates the <em>current level</em> of a character and constantly increases through gaining EXP.</p><p>When leveling up your character gets better by improving stats like health, strength, or defense. Additionally characters learn new skills (depending on the game).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jmJd1J1ohiDAz_ythy7zIw.png" /><figcaption>Level-Based Progression</figcaption></figure><p>Popular games using this system:<br>• The original <strong>Pokémon</strong> franchise<br>• <strong>Diablo III</strong><br>• <strong>Octopath Traveler</strong></p><p>—</p><h4>Activity-based progression</h4><p>Action-based progression improves the character’s stats whenever specific actions are performed by the player. This can include jumping, running, fighting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Up5MoaUdf4_-zTKF3yFShQ.png" /><figcaption>Activity-Based Progression</figcaption></figure><p>Popular games using this system:<br>• The <strong>Elder Scrolls</strong> franchise<br>• The <strong>Grandia</strong> franchise</p><h4>Free-form advancement</h4><p>Another big level-up system that is also known as <em>skill tree </em>has gained popularity over the last few years. Your character advances on a skill board by spending points to learn abilities and improve your character’s stats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVSUCUPxj3JyhcDhjzcz0A.png" /><figcaption>Free-form Advancement</figcaption></figure><p>Popular games using this system:<br>• The <strong>Far Cry</strong> franchise<br>• <strong>Fortnite</strong><br>• <strong>God of War</strong></p><p>—</p><p>A great number of games also utilize <strong>hybrids</strong> where skill trees and progress bars are combined and complement each other.</p><h3>What’s the problem with these systems?</h3><p>In general level-up systems are a great idea — so what is it now that sucks?</p><p><em>(I won’t go into scientific details, simply because I’m not a scientist..)</em></p><p><strong>☠️ Overuse kills the excitement<br></strong>Way too many games nowadays use a skill system where it’s not really needed. Just to add an <em>experience</em> for the players and because it’s <em>a trend </em>without really thinking about their core mechanics and if a level-up system makes sense.</p><p><strong>😐 Most level-up systems are boring<br></strong>One reason of these systems being boring is due to the <strong>Overuse</strong> issue: they exist just for the sake of it, so game developers don’t put much thought into it and simply add skill fields like <strong>Increase HP</strong> or <strong>Defense+</strong>.</p><p><strong>⏳ The systems are outdated<br></strong>This is more of a time-goes-by problem: player’s have been seeing these systems for years now and unfortunately they have only evolved so much. I’m not saying that time is always a killer argument but at some point we need innovation (not to be confused with <em>invention</em>) and need to evolve.</p><h3>So, how can we solve these problems?</h3><p>First of all we need to think what exactly it is we’re trying to achieve with a level-up system and what we want to convey with it.</p><p>Simply put: <strong>What’s the purpose?<br></strong><em>“What do you mean? It’s for character development!”</em></p><p>Sure it is, but that’s just the superficial answer that doesn’t go very deep. Think about what it is you want your players to think, to feel, to achieve.</p><p>Now, if we dissect the initial question <em>“Why do we love level-up systems?”</em> we can identify a few factors that might influence the answer. Let’s see:</p><h4>Level-up systems give us satisfaction</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x_NNGJYHEElUnNEq17qobA.png" /><figcaption><strong>Assassin’s Creed Origin</strong>’s skill tree</figcaption></figure><p>In the beginning players have many choices on where or how to improve:<br>“Shall I start with this skill or that one?”, “Should I complete this mission to improve this stat or the other one?”, “Do I want to go with this longsword by killing melee or should I go with that awesome new bow?”. Having <strong>all these possibilities</strong> is what makes us happy and excited for the system.</p><p>Further into the game we transition from this initial excitement to a satisfaction over mastering the skills, abilities and stats. We have decided to go down selected paths we want to excel in. We have tried newly acquired skills and are happy (or not) with the decisions we made.</p><p>At the end we see our character become this <strong>enormous beast</strong>. A Level 89 hunter with arcane skills that one-hits everything. We get satisfaction by seeing our level number, the fully fletched skill tree or the damage we deal.</p><h4>The hunger for more</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*guhHzhqaC1MtyNGTVm1sJA.gif" /><figcaption>Trying your new skill in <strong>God of War</strong></figcaption></figure><p>As soon as we get our first level-up, better stats, next skill — <strong>we are hooked</strong>!</p><p>Players want to get excited about what they will get. It’s like an award: a gift they worked (hard) for and now get to use it. If the player finally reaches level 10 and we (game devs) promised a new skill, we better deliver! There’s nothing more frustrating than to work hard for something and not get any rewards for it.</p><p>So, make Players excited for your skill system! If your skill tree consists of <strong>HP increases</strong> or <strong>improving</strong> <strong>healing potions</strong> no one will care.. Rather give them skills they can test or level-ups that grant access to new areas.</p><h4>Let’s try new approaches</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*LTa2yqZG6TpQjCieo14BNQ.gif" /><figcaption>Marking tasks done in <strong>Things 3</strong></figcaption></figure><p>Coming back to how we can solve these problems and fulfill the player’s needs, l<strong>et’s try something:</strong> let us transfer the aforementioned problems and needs into a different context.</p><p>What if we wanted to satisfy the same needs for a user that is using a to-do list app on their smartphone? What would satisfaction mean in this specific use case? Is it writing new to-dos, setting due dates to tasks, or having many big lists? Maybe. But the most satisfying feeling is to mark them done! Seeing the list shrink as you complete tasks. That little check mark ✅</p><p>Now, let’stry to abstract this concept of satisfaction to a minimum:<br>a list with things that minimizes when you do stuff.</p><p>Next, transfer this concept back to your game and put it in context. It could be a list of bosses to kill. After every boss you receive the skill that this boss inherited or unlocking areas with bonuses that lets the player feel satisfaction.</p><p>I’m not saying the idea of having a <em>boss list</em> is good — it’s merely an example of how to approach solving problems in a different way.</p><p>Be creative, think outside the box. It’s not that hard! 🙂</p><h4>The basic concept</h4><p>The structure and method on how to approach creating new stuff is simple:</p><ul><li><strong>Define your problem</strong> or the problem of your players</li><li><strong>Extract the needs</strong> from these problems</li><li><strong>Put</strong> the problem and the needs <strong>in other contexts</strong></li><li><strong>Think about a solution</strong> for the problems in this context</li><li><strong>Break it down</strong> to a minimum</li><li><strong>Transfer it</strong> to your game</li><li><strong>Expand it</strong> to create new ideas</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jOP0nnJyZRx4yl4A52ZZzw.png" /><figcaption><a href="https://www.giantrobot.media/stories/2017/12/11/post-it-show">The Post-It Show</a></figcaption></figure><p>This concept can also be defined as <strong>diverge, remixe, converge</strong>:<br>You take a look at all the possibilities on how to solve a problem especially in other areas (like apps) and open your mind: <strong>diverge</strong>.<br>Combine every idea you have with each other to come up with new ideas and innovations: <strong>remix</strong>.<br>Bring those new ideas back to your game by sorting out and adapting it for your game: <strong>converge</strong>.</p><p>I dare to say that this method can be used for anything! Try developing new game mechanics, designs, levels, character types, stories, heck even genres!</p><h3>What to take from this</h3><p>After all the blabbering and theory it’s time to summarize and put that information to good use!</p><ol><li>Instead of just adding a level-up system, try thinking about <strong>what you want to achive</strong> with it in the first place.</li><li>Do you really need it or can you make your players happy with different / new mechanics? Feed the <strong>player’s needs</strong>!</li><li>Try thinking outside the box with the <strong>diverge, remix, converge </strong>concept.</li></ol><p>Go <strong>be creative</strong> and craft <strong>awesome games 🎉</strong></p><p>—</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3efbb544ea15" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>