<?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 Luigi Minniti on Medium]]></title>
        <description><![CDATA[Stories by Luigi Minniti on Medium]]></description>
        <link>https://medium.com/@scaps?source=rss-4263bee5b0e3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RdoEKzgZJ4OT1qqrrUQc_Q.jpeg</url>
            <title>Stories by Luigi Minniti on Medium</title>
            <link>https://medium.com/@scaps?source=rss-4263bee5b0e3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:15:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@scaps/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[Getting started towards my dream job: a personal story]]></title>
            <link>https://medium.com/@scaps/getting-started-towards-my-dream-job-a-personal-story-7bb772a9f895?source=rss-4263bee5b0e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bb772a9f895</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[video-game-music]]></category>
            <dc:creator><![CDATA[Luigi Minniti]]></dc:creator>
            <pubDate>Fri, 20 Jan 2023 10:41:54 GMT</pubDate>
            <atom:updated>2023-01-20T10:41:54.364Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ldHbmThUwwQ30YIHklOhPA.png" /></figure><p>I’ve been into video games since my childhood, and I’ve always wanted my professional life to circle around them. Up until now I’ve developed a couple of simple arcade games and worked as a sound designer for them since my other life-time passion is music.</p><p>A <em>video game sound designer</em> is one of the most crucial figures in the developing of a video game, considering they’re going to be the ones responsible for creating immersive audio experiences for players so that they can enjoy the mood the game’s intended to give to the fullest. That’s what I’m aiming to be in the future: <strong>that’s my</strong> <strong>dream job.</strong></p><p>That’s why I started looking at the basics of Unity, in the specific creating a simple game mechanic needed for a project that I started working on in the last couple days. I can’t share any details about it for now, but more information will come in the future!</p><p>Certainly at this point most people are going to say:</p><blockquote>“ Wait, aren’t game developing and sound design two completely different things?! “</blockquote><p>Not at all!</p><p>Knowing the process of game development, from concept to launch, is <strong>crucial</strong> for sound designers. This understanding allows them to better collaborate with the game development team and create audio that fits seamlessly into the overall game design.</p><p>An example is understanding how game physics and interactivity between game objects works. This knowledge allows them to create more <strong>realistic and immersive</strong> audio experiences, such as dynamic sound effects that respond to player interactions!</p><p>Understanding the technical aspects of audio integration is also important for sound designers. This includes knowledge of different audio formats, compression techniques, and how to properly implement audio into a game engine.</p><p>So basically this article is the story of the sound library that doesn’t exist (yet), in order to be able to understand basic game and sound design all by myself which is a common thing to do in the indie game scene.</p><p>One of the most striking examples is <a href="https://it.wikipedia.org/wiki/Toby_Fox"><strong>Toby Fox</strong></a>, who created the groundbreaking title <a href="https://undertale.com/"><strong>Undertale</strong></a><strong> </strong>all by themselves. The game features some amazing tracks that do justice to the intense emotions that you’re supposed to feel through the whole experience, and I’m convinced this is not only because the tracks were created by a talented composer but also because this one had a wider vision of the project. After all the success that came from their efforts Toby Fox recently worked as a composer on a couple of songs for the latest Pokémon titles, starting from the indie scene to being involved in a triple A title.</p><p>In conclusion, the road to our dream job has to be <strong>paved by ourselves</strong>, also taking into consideration some <strong>detours</strong> that are going to eventually make the difference in the long run.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bb772a9f895" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Use SpriteKit in Your iOS Arcade Game]]></title>
            <link>https://medium.com/better-programming/how-to-make-your-arcade-ios-game-using-spritekit-and-gameplaykit-make-it-spritey-547a871b690f?source=rss-4263bee5b0e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/547a871b690f</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[ios-app-development]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Luigi Minniti]]></dc:creator>
            <pubDate>Tue, 12 Apr 2022 08:23:25 GMT</pubDate>
            <atom:updated>2022-04-14T08:54:13.516Z</atom:updated>
            <content:encoded><![CDATA[<h4>Make it spritey</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z_5Cni1LA0I7ID_kqVNdgw.png" /></figure><p>Have you ever wanted to create your Arcade Game on a mobile Apple Platform? Then join me in this journey where you’re going to reinforce your understanding of the most used frameworks in the <em>Apple Game Development</em> environment. That’s right, I’m talking about SpriteKit and GameplayKit!<br>This article in particular is going to be<em> focused on SpriteKit.</em></p><p>It’s Luigi here, and today I’m going to show you how I made Fugu, a simple game where you’ll play as a pufferfish that has to avoid touching some bad sea horses and dodge the bubbles they throw at you. The commands are pretty simple, consisting in moving your finger on the screen to move the pufferfish accordingly. Every time you’re damaged by a bubble the pufferfish’s dimensions will increase, also giving a visual cue of the hits you can still take (three hits and you’re done), while getting in contact with an enemy will send you straight to the game over screen. You have a score that increases as time goes, so the more you can resist the enemy’s attacks the better your score will be. Here’s how the game looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*zyIg8JJBMts9Eti7qOrQ4A.gif" /><figcaption><em>A quick gameplay from Fugu</em></figcaption></figure><p>It’s important to know that this won’t be a tutorial starting from scratch, so you’re going to need some SpriteKit basics to better understand what’s going to be covered in the next paragraphs. Don’t worry though, it’s easier than it looks!</p><p>Be sure to check its<strong> </strong>GitHub repository so you can have a look at the whole project while I’m explaining it.</p><p><a href="https://github.com/Decoyman24/Fugu-Pufferblast">GitHub - Decoyman24/Fugu-Pufferblast: An iOS arcade game I made with SpriteKit during a Game Jam.</a></p><p>There’s also an External TestFlight link for trying out the game before it’s released to the App Store (which is going to happen very soon). Make sure to open this link from an iOS device!</p><p><a href="https://testflight.apple.com/join/R7NjDRs0">Join the Fugu: Pufferblaster beta</a></p><p>Since there’s a lot to talk about SpriteKit and how it works and I don’t want to have you reading boring stuff all day, we’ll keep it simple only covering only the parts of the code that can be harsh to understand!</p><p>First of all, we need to understand the entire flow of the GameScene (the actual part where the gameplay happens) and how SpriteKit handles some events such as inputs from the user or constraints given by us.</p><p>There are in fact some GameScene-specific functions that we can use to make the magic happen.</p><p>We’re talking about the update, touchesBegan/touchesMoved/touchesEnded, didMove(to), didBegin and didEnd functions.</p><p>Some of these functions depend on the physics’ part of SpriteKit, and we’ll cover them later.</p><p>Let’s start with the most important ones for now.</p><h3>The didMove(to) function</h3><p>The didMove(to) function of the GameScene is basically what happens when you <strong>move to</strong> the gameplay scene.</p><p>You want to put in here any element that needs to be rendered, along with their properties, or start playing the background music.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/5d5bae0910aecbede32fd19ddf7709a6/href">https://medium.com/media/5d5bae0910aecbede32fd19ddf7709a6/href</a></iframe><p>Here you can also define some properties of the GameScene itself, like showing debug stats (FPS, currently rendered nodes), setting if the physics bodies are going to be displayed and more.</p><p>In this project, we’re going to use the didMove(to) for the creation of our protagonist Fugu, the super-carrot that will spawn every now and then, the score text, and some hidden stuff we’re going to need later.</p><p>Let’s start by adding Fugu, which will be declared in the GameScene’s scope as a Puffer class instance.</p><p>You can check the code in the project if you want more detail, but the Puffer class basically contains the methods that create Fugu’s different animations depending on its state and a boolean property called <em>damageable</em> that we use to understand when Fugu’s vulnerable to enemy attacks.</p><p>Just go under the GameScene and add this:</p><pre>var puffer = Puffer()</pre><p>Now we can go back to the didMove(to) function and create our beautiful pufferfish.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/87b33014951f93eb72fe4cc2cbaa461b/href">https://medium.com/media/87b33014951f93eb72fe4cc2cbaa461b/href</a></iframe><p>As you can see, there are a lot of lines just for a small pufferfish.</p><p>What we just did is set up some of the properties for the puffer instance, such as its position on the screen (in the exact middle), some physics’ properties we’re going to discuss later, its position on the Z-axis so it’s in the front of the screen (because our background is going to be at a lower Z position) and its scale (dimension), since the real asset resolution is higher than the dimension we want on screen so we’re going to set it at 1/4 of its original dimension.</p><p>The most important step in all of this, however, is when we actually add the pufferfish to the GameScene. This is done with the addChild(puffer) command.</p><p>This basically adds a sprite as a child of the GameScene (which is the parent that’s going to contain all our elements), so we’re basically going to use this command every time we want to add something to the screen.</p><p>We can also use this to add the background image and the banner, but we’ll put those later through the editor in order to handle the scene’s size.</p><p>We need <em>one last thing</em> to apply to our pufferfish. Since we’re going to move freely in a huge space we’re going to apply some constraints on Fugu’s range of movement, in order to avoid him going out of the screen.</p><p>Just write this before the previous chunk of code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/0c930bb4a4f1379513cebffaa203af95/href">https://medium.com/media/0c930bb4a4f1379513cebffaa203af95/href</a></iframe><p>What we just did is creating two SKRange values for Fugu’s X and Y positions so that he can’t go out of those bounds. We use the self.frame.width and self.frame.height values to use the frame of the scene (simply the screen’s edges) as a limit.</p><p>We then apply this constraint to the puffer instance with the <em>.constraints</em> modifier.</p><p>Now we need to apply some properties to the scene itself.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ba7a67120100073f07e4b3d0cb66c924/href">https://medium.com/media/ba7a67120100073f07e4b3d0cb66c924/href</a></iframe><p>Aside from all the physics properties that we’re about to discuss later, we can notice some interesting modifiers for the GameScene itself, like .showsFPS<em>, </em>.showsNodeCount<em> and </em>.showsPhysics<em>,</em> which can be respectively used to show the FPS counter, number of rendered nodes on screen, and the nodes’ physics hit-boxes when in runtime.</p><p>As you can see we also added a worldNode child to the GameScene. This is a SKNode value, which acts as a container for other SKSpriteNodes and we’ll use it to pause all the other moving elements on the screen when the game pauses.</p><p>Time for the score label to be added to the scene. This uses a gameScore value that will be used to keep track of the user’s score as time passes.</p><p>Add this under the previously written chunk of code:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/9fc48a86b436cf2a44fd7bbc96fb03d9/href">https://medium.com/media/9fc48a86b436cf2a44fd7bbc96fb03d9/href</a></iframe><p>With this, we added the label in the upper corner of the screen.</p><h3>The update function</h3><p>Let’s now talk about the update function.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2c41611ea8b8d30fe5beaa2314a12c14/href">https://medium.com/media/2c41611ea8b8d30fe5beaa2314a12c14/href</a></iframe><p>This is one of the main functions that you want to know about it works, since it’s a function that your GameScene calls on every frame (when your scene is not paused). That’s a lot of calls, I can assure you!</p><p>If for example, your game is going to run at 60 FPS (frames per second), which usually does, the update function is going to be called 60 times over the span of one second</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zWmckbyqIO8pilzT.png" /><figcaption>Source: <a href="https://developer.apple.com/documentation/spritekit/skscene/responding_to_frame-cycle_events">https://developer.apple.com/documentation/spritekit/skscene/responding_to_frame-cycle_events</a></figcaption></figure><p>This is an image explaining what precisely happens for each frame in a SpriteKit app.</p><p>As you can see, the first thing that happens is running everything that’s inside the update function.</p><p>After the update function, the GameScene (SKScene) evaluates any action (movement of sprites, transitions, etc.) or control statement you might have defined, it then proceeds to simulate its physics (like collisions between sprites), applying constraints (for example you could have a character on a fixed position no matter what force is applied to it) and finally renders every element on the screen.</p><p>Knowing this we can’t imagine using update to make things happen on certain conditions, for example, to play a sound when your character dies, since it would result in playing your sound 60 times per second until your game is paused or until you close the app. <em>We don’t want that.</em></p><p>In our case, however, we can use this function to make our score increase over time.</p><p>Let’s first declare a gameScore variable inside the GameScene’s scope:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bb720fadb56c662dbdf07dede2b3a7cd/href">https://medium.com/media/bb720fadb56c662dbdf07dede2b3a7cd/href</a></iframe><p>Now that we have our score set up to 0 when a game starts, it just needs to be increased.</p><p>Here’s how we did it:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2b080099ba3a92499ae129d90660aa01/href">https://medium.com/media/2b080099ba3a92499ae129d90660aa01/href</a></iframe><p>What it’s going to happen during our gameplay is basically adding 1/3/6 points to our score at the start of every frame as long as the game is not paused. The amount of points given at each frame depends on the pufferState variable, meaning that the more damaged we are, the more points we’ll get since it will be harder for us to avoid the bubbles given the increased size of Fugu.</p><h3>The touchesBegan/touchesMoved/touhesEnded functions</h3><p>These three functions handle what happens in each phase of the user’s interaction with the screen (taps), as you can easily understand from their names. With this part, we’ll handle the movement of Fugu on the screen.</p><h3>touchesBegan():</h3><p>Here we’ll handle the initial part of the interaction, being when we start tapping on the screen.</p><p>This goes in the GameScene’s scope:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/21f585438c6b04f253fa10b309bee935/href">https://medium.com/media/21f585438c6b04f253fa10b309bee935/href</a></iframe><p>What we are doing here is setting a bool value to true when we are controlling Fugu (we’ll use this for the next part) as well as using startTouch, which is a CGPoint value, for pinning the part of the screen we just tapped. We then store in nodePosition the actual position of Fugu, so that we can move him later.</p><h3>touchesMoved():</h3><p>In this function, we’ll now handle what happens when after tapping on the screen we continue moving the finger before releasing it. Write this just after the touchesBegan() function:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/ae56673404fc39a93b7e599496c38ca4/href">https://medium.com/media/ae56673404fc39a93b7e599496c38ca4/href</a></iframe><p>What happens here is pretty simple. It all starts with the premise of us controlling Fugu, meaning that we have started tapping the screen.</p><p>We just simply change Fugu’s position with an SKAction.move to computed values of X and Y that simply take its original position from nodePosition (with its value set in the touchesBegan function) and add to it the X and Y’s of location, a temporary value used in this function to keep track of where the finger’s moving while holding it on the screen. That’s all there is to it!</p><h3>touchesEnded():</h3><p><em>A</em>s we said before, touchesEnded() handles what happens in the moment we lift the finger off the screen.</p><p>We are not using this function for any particular reason other than setting the controlling bool to false so that we know we’re not controlling Fugu anymore.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d8d87f4adba07b1322bd7b25996048d8/href">https://medium.com/media/d8d87f4adba07b1322bd7b25996048d8/href</a></iframe><h3>Let’s Get Physical</h3><p>We’re now going to talk about the part that makes the game alive, being physics.</p><p>We use this to create certain events in a game, like being hit by a projectile, touching an enemy, or getting a powerup. Physics can also simulate collisions, apply forces, and more, but we’re not going to need that for this game.</p><p>The way SpriteKit handles physics is quite simple. We can assign to every entity (in our case, SKSpriteNodes) certain .physicsBody values. Let’s start by analyzing Fugu’s properties.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d695a3194871ffe2750b9280f2dfd9b0/href">https://medium.com/media/d695a3194871ffe2750b9280f2dfd9b0/href</a></iframe><p>You can see that we have a lot of modifiers for .physicsBody, but don’t feel discouraged, understanding how this work is not hard as it looks.</p><p>Before talking about the actual modifiers assigned to it, we must understand which kind of physics body our sprite has. There are 3 possible physics bodies, being square, circle, and alpha mask.</p><p>In our case, it’s a circle body with a radius that’s equal to the original height of puffer’s assigned sprite (so it’s not counting the 0.25 scale we set in the <em>didMoveTo</em> function), meaning that if you set the view.showsPhysics value from the didMove(to) to true, you’ll see something like this around Fugu’s body:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*uuRSqDL0s4lR_veAalUNsw.png" /><figcaption>Fugu’s surrounded by a mysterious circle.</figcaption></figure><p>This is the actual physics’ body we assigned to it, and it has the shape of a circle. Simple enough.</p><p>The other two attributes that are self-explanatory are .affectedByGravity and isDynamic.</p><p>Basically by setting those two to false we’re not applying any force caused by the whole scene’s gravity (which is set to 0 anyway) and we’re also sure that no matter what happens Fugu’s body will not clash when in contact with other bodies.</p><p><em>Now for the fun part.</em></p><p>In SpriteKit’s physics, we use category bitmasks to understand which category of the body comes in contact with another. We wouldn’t be able to understand, for example, when Fugu’s touching an enemy projectile, the enemy itself, or simply the edge of the screen.</p><p>Let’s declare our category bitmasks out of the GameScene’s scope:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2634a51e77ee3c3a81271c54870da0b9/href">https://medium.com/media/2634a51e77ee3c3a81271c54870da0b9/href</a></iframe><p>Category bitmasks are no other than binary integers, as you can see their actual value in the comments.</p><p>Don’t brush your head on making calculations with them, once declared we can just use their names for any operation we need.</p><p>Back to puffer.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc4d4fb9b903889147b6f79cb20426e2/href">https://medium.com/media/bc4d4fb9b903889147b6f79cb20426e2/href</a></iframe><p>You can see that puffer is identified (by his .categoryBitMask) as a PhysicsCategory.Ally, the only category of bodies it will collide with (resulting in stopping itself or moving the other body with enough impulse) are PhysicsCategory.Wall bodies, and the bodies we want to know about when in contact (yep, it’s .contactTestBitMask) are Bullet, Enemy, Carrot, Letter and Wall. What this means is that if we don’t put these categories under the .contactTestBitMask we won’t be able to control when these will be colliding.</p><p>Take a bit of your time to better digest these concepts, since all the logic behind SpriteKit’s physics goes around these three modifiers!</p><p>Now, let’s talk about the last two GameScene’s functions that are specific to SpriteKit’s physics: didBegin() and didEnd(). These are two functions that take part when a collision between two bodies starts and ends (as their name suggests), but in order for these two functions to work, we need to have a SKPhysicsContactDelegate who’s in short a scene that has the right to watch out for physics’ contacts. We already assigned it to our GameScene when declaring it!</p><pre>class GameScene: SKScene, SKPhysicsContactDelegate {</pre><p>We just need to add this line of code to the didMove(to) function:</p><pre>physicsWorld.contactDelegate = self</pre><p>With this, the GameScene’s been officially assigned as a contact delegate!</p><p>Let’s move to its two functions.</p><h3>didBegin():</h3><p>This function is called by our game whenever a contact between two SKPhysics bodies happens.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cf3275c776ed7828d769d11f7e2a9660/href">https://medium.com/media/cf3275c776ed7828d769d11f7e2a9660/href</a></iframe><p>Here we have a collision constant that’s equal to the contact between a bodyA and bodyB.</p><p>Since category bitmasks are binary values SpriteKit reckons a contact between two with a <strong>|</strong> (logical OR) operator.</p><p>With the premise that Fugu can take damage (since there can be phases when he’s invulnerable), we’ll call different functions depending on which bodies clash with each other.</p><p>What’s important to notice is that the order of the bodies counts, that’s why we have two cases that call the enemyHit() function that occurs when Fugu touches or is touched by an enemy.</p><p>Since the bullets will always go at a fixed speed those will always be the first body to have contact with Fugu, so we only need one condition for taking damage from the bullets.</p><p>The same goes for the super-carrot since its position will always be fixed and the first body that collides with it will be Fugu no matter what.</p><h3>didEnd():</h3><p>There’s not much to say about this function, since it occurs when contact between two bodies comes to an end. It can be useful in certain situations (for example when a character steps off from a switch), but we won’t use it at all.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/49e34c63ef510cc9e34fd00a7c077a94/href">https://medium.com/media/49e34c63ef510cc9e34fd00a7c077a94/href</a></iframe><h3>And that’s it for now!</h3><p>If you want to know more about making games for iOS using Apple’s frameworks <a href="https://medium.com/@orleone.dev/make-it-structured-gameplaykit-6d7e79d5a44a">this article</a> written by <a href="https://medium.com/u/fe472f263de1"><em>Oreste Leone</em></a><em> </em>can come in handy. Here Oreste is going to cover how GameplayKit works! I highly suggest you do since GameplayKit is an awesome framework that’s going to help you make your games even more structured.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=547a871b690f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/how-to-make-your-arcade-ios-game-using-spritekit-and-gameplaykit-make-it-spritey-547a871b690f">How to Use SpriteKit in Your iOS Arcade Game</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From first success to Game Of The Year — How Supergiant Games’ Business Model Changed]]></title>
            <link>https://medium.com/@scaps/from-first-success-to-game-of-the-year-how-supergiant-games-business-model-changed-9c6c6f11a5f?source=rss-4263bee5b0e3------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c6c6f11a5f</guid>
            <category><![CDATA[research]]></category>
            <category><![CDATA[business-model-canvas]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[supergiant-games]]></category>
            <dc:creator><![CDATA[Luigi Minniti]]></dc:creator>
            <pubDate>Wed, 06 Apr 2022 11:01:20 GMT</pubDate>
            <atom:updated>2022-04-06T11:01:20.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KMbOl8i2mn5fv9Vyj1jDaQ.png" /></figure><h3>From first success to Game Of The Year — How Supergiant Games’ Business Model Changed</h3><p><em>Co-created with </em><a href="https://medium.com/u/fe472f263de1"><em>Oreste Leone</em></a></p><p><strong>Hello</strong>! It’s <em>Oreste</em> and <em>Luigi</em>, and in this article we’re going to create and analyze two business model canvases based on different games made by the same indie game developer.</p><p>We basically wanted to do this in order to better understand what can push a rookie game developer to the next level, and that’s why for this article we decided to analyze <strong>Supergiant Games</strong>, a software house who recently became well known in the gaming industry thanks to their rogue-like action RPG named <strong>Hades</strong>.</p><p>They have been popular before as well in the indie game scene thanks to their games preceding Hades, which are (in order of release) <strong>Bastion</strong>, <strong>Transistor</strong> and <strong>Pyre</strong>. These titles share a unique hand painted art style that, with their isometric camera angle and well thought gameplay, became an easy recognizable trademark of the studio.</p><h3>About Supergiant Games</h3><p>Supergiant Games is an indie game developer <strong>founded in 2009 by Amir Rao, Gavin Simon and Greg Kasavin.</strong> They have been working at the Los Angeles studio of Electronic Arts, involved with the Command &amp; Conquer Series, until they decided to quit their job to start their indie game development studio, inspired by the work of small teams that created games they were playing in that period.</p><p>During an interview Greg Kasavin said:</p><blockquote>It was really inspiring, these games were made by just a handful of people, but they’re really well-crafted and just more interesting in a lot of ways than what was happening then in the big triple-A space. That’s when we started thinking, ‘What would we do if we could ever do something like this?’</blockquote><p>In their vision, big teams can’t work with an Agile Mindset.</p><blockquote>The other big part of it is speed. Big teams are slow. With a small team, anyone can have an idea and minutes or hours later it’s in the game. When you’re small, you can fail fifty times a week to get to the good stuff instead of finding out at some big milestone that what you have just isn’t as good as it could be.</blockquote><p>And that’s why their team never saw an high increase in numbers, and we could say that their formula worked really well if they reached a <strong>Game of the Year nomination and won two Game Awards (best indie game, best action game) </strong>in 2020 with their last game: Hades.</p><h3>Bastion</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VWlEFRpl8qt59XXW-I960A.jpeg" /></figure><p>Bastion, the first successful hit, is an Isometric Action-packed role-playing games set in apocalyptic wastelands with unique elements, like a narration system that actually reacts to the player’s actions within the game, dreamy hand painted graphics and immersive fantasy world, that draw the player deeper into the experience.</p><blockquote>We just started building the game immediately without any paper designs as soon as we moved in together. That seed was a very small part of what I think ended up making Bastion distinct and interesting: the reactive narration, the hand-painted art style, the finesse of the combat, the way the world comes together as you move through it.</blockquote><p>One of the key point of their success was the partnership with Warner Bros Interactive that allowed them to publish on Xbox Live Arcade and Steam Marketplace</p><blockquote>Basically, to get on Xbox Live Arcade, you need a publisher and that publisher can be Microsoft first-party or it can be a third-party publisher. So after we showed the game at PAX Prime, we had interest from all sorts of people from publishers of all kinds. But Warner Bros were the most excited about the game, and they had a ton of respect for what we had been able to do so far and for our independence. We were looking for a distribution partner, we weren’t looking for someone to fund our game, but we were looking for people who had bought into the vision [of the game]. So yeah, we went with them because they were the most thrilled about it. They have been amazing to work with so far.</blockquote><p>As they were starting, they relied only on their strengths plus some freelancer to speed up the work, reaching the stores in just 17 months of development, working from Rao’s and Korb’s houses and traveling around to convention to show the game itself.</p><blockquote>All of these were a result of exhaustive experimentation and having people join us who could actually make this stuff work while still staying small. We’re about seven people now: Greg, Jen, Andrew, Gavin and I are all crammed into a living room right now trying to make this game come alive, while Darren Korb and Logan Cunningham are recording hundreds of audio lines tucked away in an apartment in New York.</blockquote><p>With their <em>Modus Operandi,</em> they didn’t plan anything in advance for “what’s after” the release. Bastion success was unexpected for them and after 3 years, before Transistor, they sold over 2 million copies across all platforms, validating the team decision to quit their various jobs in AAA Development and lock themselves inside a house to work on something they were passionate about.</p><h3>Hades</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D2FoqzLIw0dKzXa4yGu0iw.jpeg" /></figure><p>While Bastion was a game with a development process where freelancers were a critical resource, Hades resulted in a product entirely made by Supergiant alone. After 13 years the developer team saw a modest increase in numbers, going from measly 10 people to 20! They also moved their workplace from private houses to an headquarter based in San Francisco.</p><p>The way they develop games roughly remained the same, relying on their custom game engine (which was rewritten for this game and resulted in being a <strong>cost structure</strong>).</p><p>What is different here in comparison to Bastion is that the final part of the dev process was heavily defined through <strong>Early Access</strong> (made possible by the partnership with Epic Games)<strong>,</strong> where some players could try a WIP build of the game and give feedback to the dev team in order to make it closer to the customers’ expectations. They could afford to make multiple iterations to the dev process since the team was made by 20 people, so interacting with each other was easier compared to the team of a big company where the numbers are doubled if not more.</p><p>The following words are from an interview with <strong>Greg Kasavin</strong> at the 2019’s Game Awards:</p><blockquote>We’ve been really really happy with how <strong>Early Access</strong> has been going so far. Thankfully, even given the Early Access nature of the game, the initial technical challenges were pretty minimal, so everybody was, for the most part, able to get into the game and start playing. The response we’ve been getting, we’re really really happy with. I will never ever take for granted having a group of our players actually like the stuff that we work on. I will never take that for granted. So every time we launch a game and our players say “hey this is cool, thank you for making this,” I wipe the sweat off my brow and I breathe a sigh of relief. That response has been really encouraging.</blockquote><p>With Bastion being a single player game made with the intention of being enjoyed by a single person, Hades resulted in a single player game like Bastion, but made to be <strong>an experience that’s either fun to watch and play.</strong> We can also see this objective in reflected in the business model canvas, where the <strong>blue elements</strong> representing everything that’s connected to <strong>content creators</strong> (streamers, social media influencers etc.)</p><blockquote>One of the factors with Hades is that we want this game to be <strong>highly enjoyable to watch as well as to play</strong>. It’s a game designed around immediacy and re-playability among other factors, and you get in there and hopefully start having fun with it, have a unique experience each time, and have the action be very readable if a friend is next to you or if you’re streaming it or something like that. Part of Epic’s focus with the store is to help enable streamers and YouTube content creators to essentially get a piece of the action. You’ve seen the <strong>Fortnite</strong> support-a-creator program, where creators basically just get compensated for their work. I think streamers and YouTube content creators have had such a significant and overall beneficial influence on games over the years that it’s really only fair that they should be able to benefit more from the incredibly hard work that they do. So on a personal level, that spoke to me, I think it spoke to other folks I work with, just as part of the priority that Epic was interested in.</blockquote><p>Then comes the element that got every customer crazy about Hades: the greek mythology setting along with its charming characters. This came from a deep research made by the creative direction team, being a key resource in the whole process. It’s easy to say that Hades’ characters and its landscapes resulted in overshadowing its gameplay! (which is the main focus of the game to begin with)</p><blockquote>Given our other priorities, it felt like, once again, let’s make something new, let’s make something that really, really fits this set of design goals. <strong>We looked to Greek mythology in this case as a source.</strong> In one sense, it’s a well-worn theme for video games, but in another sense, something that we felt was both a perfect fit for what we were doing. In some ways it’s really unexplored. As the person doing the writing, I was very drawn to a particular angle on Greek mythology. What I feel is often lost in the shuffle is that the gods are a big dysfunctional family that we can see ourselves in. I think part of the reason these characters have survived for thousands of years is because they relate so strongly to so many people and they relate not because they are gods but because they are human. So we wanted to explore some of that. It felt rich with potential for us, so yeah we started making it.</blockquote><h3>Wrapping it up:</h3><p>In conclusion, from this research we can see that Supergiant Games was able to maintain their <em>modus operandi</em> of a small indie developer while making progress as a company since they could move from working in personal houses to their headquarters AND making a game that won two awards (<strong>best indie game</strong> and <strong>best action game</strong>) and could get a nomination for <strong>Game of the Year!</strong></p><p>For everyone who wants to go this route, we leave you with this quote from Amir Rao about getting into the indie game development from an interview</p><blockquote>There is a lot of worry in being independent. First, you worry if the game is going to be good, then you worry if anyone will like it, then you worry if it will ever come out, then you worry if something bigger will come out right on top of it, then when it’s finally out, you worry if it will sell well enough to let you do a second one. Find the right people and the right platforms and just do it. You don’t have to quit your day jobs immediately. You’ll know when it’s time to switch over to spending all your energies on your own work. We quit before even starting the game, but that’s not always necessary.</blockquote><p><strong>Thanks for the time spent into reading this article.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c6c6f11a5f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>