<?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 Pat Scott on Medium]]></title>
        <description><![CDATA[Stories by Pat Scott on Medium]]></description>
        <link>https://medium.com/@Stralor?source=rss-481baa1906a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*LQsRnheh7ZDYPpXI.jpg</url>
            <title>Stories by Pat Scott on Medium</title>
            <link>https://medium.com/@Stralor?source=rss-481baa1906a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:00:03 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Stralor/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: Share Ship Designs from Destination Ares]]></title>
            <link>https://medium.com/@Stralor/how-to-share-ship-designs-from-destination-ares-d9b12b6f4b6e?source=rss-481baa1906a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9b12b6f4b6e</guid>
            <category><![CDATA[filesystem]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[games]]></category>
            <dc:creator><![CDATA[Pat Scott]]></dc:creator>
            <pubDate>Fri, 13 Jul 2018 00:39:44 GMT</pubDate>
            <atom:updated>2018-07-13T00:46:27.488Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bbTvBqcJYT0kcKXXztYpeg.gif" /></figure><p>You’ve (finally) built a cool ship, and you want your friend to play it. Now what?</p><p><strong>Without painstakingly recreating it, is there a way to share it?</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/636/1*c15_D5fwYytNyDWvfPchgA.gif" /><figcaption>Good news, everyone!</figcaption></figure><p>Yep! There’s a (fairly) easy solution. Get ready: we’re about to dig deep into some folders on your computer.</p><h4>Step one: Access the AppData folder</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/389/1*prdby5L0JgNCjWxUdWwHIA.png" /></figure><p><em>Easy solution:</em> search “%appdata%” in Windows Search (or Cortana).</p><p><em>Harder solution (if you’re more technically inclined):</em> turn on the setting to show hidden files and folders, then go to C:\Users\[YOUR USERNAME]\AppData\</p><h4><strong>Step two: Navigate to …\AppData\LocalLow\PS Studios\Destination Ares\</strong></h4><p>If you took the easy solution above, it’ll have put you into \AppData\Roaming. That’s fine. Just hit the up arrow to go back into AppData.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*ac3cqleXjkARqtfk7NxssQ.png" /></figure><p>Within AppData, there’s a folder called LocalLow. That’s the one we need! Double-click it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*oVBqfSscw5tYhY--E_baJQ.png" /><figcaption><em>(psst: sort by name to make this easier, if you aren’t already)</em></figcaption></figure><p>Then, scroll down until you see the folder “PS Studios”. If you’re anything like me and play lots of indie games, you’ll have to scroll for a little while. No problem, I can wait.</p><p>…</p><p>…</p><p>Got it? OK, good, double-click it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*o89W6I6yrXORiCaybLXpzQ.png" /><figcaption>If you see more than just a Destination Ares folder, I’m impressed and …confused.</figcaption></figure><p>Finally, double-click on “Destination Ares”.</p><h4>Step three: Grab your ship!</h4><p>We’ve made it!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/604/1*PfSvzAUY4IW-z0qzJhJ4zw.png" /><figcaption>Eh, dev computers are weird.</figcaption></figure><p>You see all those files of type .ship (or labelled “SHIP File”)? Those are <strong><em>your</em></strong><em> </em>designs!</p><p>Copy the ship you wanted to share, and send it to a friend!</p><p><em>For your own safety, please ignore the .ares files; here be dragons.</em></p><p><strong>Aaand that’s it. </strong>Happy human-herding, A.I.!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9b12b6f4b6e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Destination Ares Sales Pricing Structure]]></title>
            <link>https://medium.com/@Stralor/destination-ares-sales-pricing-structure-bd10cacf6ec9?source=rss-481baa1906a------2</link>
            <guid isPermaLink="false">https://medium.com/p/bd10cacf6ec9</guid>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[pricing-strategy]]></category>
            <dc:creator><![CDATA[Pat Scott]]></dc:creator>
            <pubDate>Wed, 14 Mar 2018 00:21:36 GMT</pubDate>
            <atom:updated>2018-03-14T00:34:10.014Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This is a cross-post of my announcement on Steam, which can be found </em><a href="https://steamcommunity.com/games/553470/announcements/detail/1646502308038773758"><em>here</em></a><em>.</em></p><p>You may have noticed that <em>Destination Ares</em> has had suppressed sales prices on Steam.</p><p>This was an intentional experiment.</p><p>From launch onwards, every sale was 10% off, plus 1% per sale before it. So, the second sale was 11% and the sixth was 15%. My goal was to build a sense of consistency and transparency with my sales pricing structure.</p><h4>Of course, there were two issues with this method.</h4><p><strong>First,</strong> I didn’t tell anyone that I was doing this.</p><p>Whoops, there goes the transparency part.</p><p><strong>Second,</strong> 1% per sale is too slow for a game of this scale, if we consider how many Steam sales can be squeezed in a year. My rough estimate based on previous data is 12 sales per year (5 or 6 weeklongs + 4 seasonals + 2 or 3 randoms [like the Lunar New Year event that happened recently]). If Valve ever reaches out to do a special promotion, this could go up slightly.</p><p>Still, that’s only 22% off, max, by the game’s launch anniversary, *if* I participated in every sale opportunity (which, for various reasons, doesn’t always happen). 22% is a respectable discount, but doesn’t light a candle against other pricing schedules.</p><p>I could see some games making that ‘1% per sale’ work. It hasn’t worked for this title, however.</p><h4>So, I’ve decided to amend my strategy.</h4><p><em>Step one:</em></p><p>Let you all in on the secret.</p><p>Done.</p><p><em>Step two:</em></p><p>Make up a bit for lost time.</p><p>This week and this week only, <em>Destination Ares</em> is 20% off on Steam.</p><p><em>Step three:</em></p><p>Decide and announce the new pricing structure.</p><h4>From now on, <em>Destination Ares’</em> sales price will add 3% each time.</h4><p>Today it’s 20%, next time it’ll be 23%, then 26%, and so on.</p><p>It’s not a dramatic increase from sale to sale, and it’s not supposed to be!</p><p><strong>I want you to be confident that you’re getting a good deal</strong> when you buy this game that I put so much literal blood, sweat, and tears into making. Whether you buy it on sale or not, you should know what you’re getting into, and part of that is knowing how much you could be paying.</p><p>However, if you’re going to wait anyway, I don’t want you to have to wait until the heat death of the universe.</p><h4>Hopefully, this will be the sweet spot.</h4><p>Thanks for taking this ride with me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JK6WkXSgjrC3f2dgR1XO9Q.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bd10cacf6ec9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Crew A.I. in Destination Ares]]></title>
            <link>https://medium.com/@Stralor/crew-a-i-in-destination-ares-a90a44141433?source=rss-481baa1906a------2</link>
            <guid isPermaLink="false">https://medium.com/p/a90a44141433</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Pat Scott]]></dc:creator>
            <pubDate>Thu, 08 Mar 2018 01:54:27 GMT</pubDate>
            <atom:updated>2018-03-08T02:01:07.606Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Deep Dive</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*wBhsqPeEBehmXNqG51IcNA.gif" /></figure><p>Not long ago, I was asked to do a post about how the A.I. works in <a href="http://store.steampowered.com/app/553470/Destination_Ares/"><em>Destination Ares</em></a>. I haven’t blogged since before the game launched, so why not tackle the topic?</p><p>Today I’ll go over crew A.I., <em>specifically</em>. Other A.I. topics, like the adaptive difficulty director and the behavior of ship systems, will have to wait on my whim (probably ~indefinitely~).</p><p><strong>Disclaimer:</strong> reader beware — this isn’t a how-to or a guide on best practices. It’s just how it went down. And though I did accidentally do *some* things well, it’s almost certainly the ‘wrong’ way to go about it.</p><p><em>Then again, the ‘wrong’ way still worked enough to ship a game. YMMV</em></p><p>OK. Get ready for information overload. Let’s begin.</p><p>Over the course of development, crew A.I. in <em>Destination Ares</em> changed direction quite a bit. I was inspired by GOAP, but I set out making a state machine. As you can guess, it was all pretty deterministic initially.</p><p>Sleepy? Sleep.</p><p>Hungry? Eat instead of Sleeping.</p><p>Alarm? Go there.</p><p>It was all handled by a pathfinder, and the character themselves. The idea was to foster crew behavior that was consistent.</p><p>Which was the wrong idea (for this game).</p><p>It didn’t meet the needs of future mechanics of the game, like different alarms, personalities, and work preferences. It didn’t create any room for emergent behaviors. And it also caused huge line bloat in the ‘Character’ class, where two divergent purposes were fighting for space: data storage and behavior management. (Which might have made sense if it was just a state machine)</p><p>That all changed… But slowly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Tb2VWStofkS2YhFt8gaSA.png" /><figcaption>Blah Blah Blah</figcaption></figure><p><em>So,</em> let’s skip ahead to the end, to the accidental result of all my iteration:</p><h4>A utility-based A.I.</h4><p>(Which, I might add, makes a TON of sense for a sim game.)</p><p>Here are the components of crew A.I. in the shipped game (code line counts include empty spaces and copious comments):</p><ul><li>‘<strong>SimplePath</strong>’ (~400 lines)<br> • A pathfinding and movement management script built on Aron Granberg’s A* library<br> • Placed on each character<br> • Probably ironically named</li><li>‘<strong>BehaviorHandler</strong>’ (~900 lines)<br> • Controls game logic and actual character action (after movement)<br> • Placed on each character</li><li>‘<strong>Character</strong>’ (~1300 lines)<br> • The walking (*ahem* floating) state machine that is each character<br> • Basically a bundle of data and ways to interact with that data<br> • DEFINITELY placed on each character</li><li>‘<strong>Alert</strong>’ (~300 lines)<br> • State machine for player-initiated alarms<br> • Placed on each object that can have an alarm</li><li>‘<strong>Job</strong>’ (~800 lines)<br> • Data container for a given behavior goal, linking character to task and target <br> • Also decides idle behavior goal, if idling<br> • Created and destroyed as needed; stored in a mysterious and nameless void</li><li>‘<strong>JobAssignment</strong>’ (~600 lines)<br> • Manager class that decides who should be doing what, when<br> • i.e. creates and manages <strong>Jobs </strong>(I’ll deep dive into how these two classes work in a bit)<br> • Placed as a separate, standalone manager object (but still in scene so I can tinker from inspector)</li><li>‘<strong>DegradationChecker</strong>’ (~200 lines)<br> • Acts as the tick system for the game (10 seconds per tick, at normal speed)<br> • In a new random order every tick, rolls damage against both crew and systems, based on each object’s current state and values<br> • Also slowly drains extra energy from the ship, and causes damaging power surges when you’re out of energy, because I’m an asshole<br> • Basically the threat in this game</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*BHkSwKK6Jnxucld515NI8w.gif" /><figcaption>A game where the human crew are controlled by an A.I. and the A.I. character is controlled by a human player.</figcaption></figure><h3>How it all works together</h3><p>Every tick, the <strong>DegradationChecker </strong>does its damage. Part of that is hurting systems that have been in use. The other is increasing both stress and stressors (e.g. needs) in the crew. In this way, <strong>hunger </strong>and <strong>sleep </strong>(and, after eating, <strong>feces</strong>) build up in the crew. These needs combine with <strong>loneliness </strong>(affected by the number of living crewmates and the number of dead crewmates) to form the core stressors.</p><p>Then, if the combined and weighted stressors are large enough, the crew member’s stress increases [1]. Whenever a crew member’s stress increases, they have a chance to take damage (injury, pass out, go crazy, die, etc.). [2] Finally, the crew member breathes some oxygen. If they can. Heh.</p><p>If the player can see the signs of system or crew damage, and is paying attention, they may at this point set an <strong>Alert</strong>. <strong>Alerts </strong>come in a few flavors: <strong>Ignore</strong>, <strong>Emergency</strong>, <strong>Warning</strong>, and <strong>Use</strong>.</p><p><strong>Ignore </strong>tells crew to not interact with something, including fixing it. Essentially, this pulls the object out of consideration by Jobs and JobAssignment.<em> Critical for high-level play; criminally underused.</em></p><p><strong>Emergency </strong>and <strong>Warning </strong>are two flavors of the same idea: “fix this.” If the target is a system, that means repairing it. If the target is a crew member, that means healing it. The difference between the two is that <strong>Emergency </strong>has a (much) higher priority. <em>Newbies often kill their crew by overusing Emergency when Warning would suffice.</em></p><p><strong>Use </strong>tells the crew to make a system do work. [Manual] systems require crew interaction to function, and this makes the crew prioritize them.</p><p>While all this is going down, <strong>JobAssignment </strong>is flipping through all of its tracked objects every frame, looking to make shit happen. When it sees an active <strong>Alert</strong> (other than <strong>Ignore</strong>), it begins the process of finding an appropriate crew member to assign that task to.</p><p>First, it figures out what the task is. As of writing, a task can be <strong>Heal</strong>, <strong>Repair</strong>, <strong>Using </strong>[ew, I guess I broke my own naming convention], <strong>Idle</strong>, <strong>Maintenance</strong>, or <strong>Socializing</strong> <em>(not used)</em>. If it’s an <strong>Alert</strong>, it’s one of the first three.</p><p>Then it starts its search for an appropriate crew member. The initial pool of characters it looks through is limited to the task-specific job team. E.g.: the [Engineer] team is preferred for <strong>Repair </strong>tasks, [Medical] is preferred for <strong>Heal </strong>tasks, and [Science] is preferred for <strong>Using </strong>tasks.</p><p>It finds all crew members that match within the following queries, jumping to #4 if there’s at least one crew found after any given section:</p><ol><li><strong>Are you in “Good” condition?</strong><br> <strong>• Are you idling?<br> • Is your idle task less important than this one? </strong>[3]<strong><br> • Is this target valid for you? </strong>[4]</li><li><strong>Are you controllable (aka conscious and sane)?</strong><br> • Are you idling?<br> • Is your idle task less important than this one? <br> • Is this target valid for you?</li><li>Are you controllable?<br> • <strong>Is your current task less important than this one? </strong>— <em>Note: if we’ve gotten to this point, we’re considering kicking a crew member off another Alert</em><br> • Is this target valid for you?</li><li><strong>Of those we’ve found for this Alert, who’s closest?</strong></li></ol><p>If it finds no one within the job team that matches any of its queries (which often happens when no one is assigned to that team, everyone is knocked out from oxygen deprivation on the floor, or everyone is too busy with other work), it does the whole search again. This time it searches EVERY crew member on the ship, including crew without teams and those from other teams.</p><p>At this point, when (if) it’s found someone to do the task, it boots them off their old task and creates a <strong>Job </strong>object. In the <strong>Job</strong>, it throws the chosen crew member, the task, the target, and the task’s priority (which it mathed out earlier using a bunch of factors). Their old <strong>Job</strong>, associated with their last task, is destroyed.</p><p>It does this until it’s gone through all of the unassigned <strong>Alerts</strong>. After it’s taken care of all the <strong>Alerts </strong>it can, it looks through any remaining crew who aren’t doing anything. Being dead counts as doing something, I guess.</p><p>For each inactive crew member, it creates a new <strong>Job </strong>with the <strong>Idle </strong>task and hands it to them.</p><p>Now, the individual <strong>Jobs </strong>take over.</p><p>When a <strong>Job </strong>is created, it flips a bunch of switches in <strong>Character</strong>, <strong>BehaviorHandler</strong>, and <strong>SimplePath</strong>, letting them know what they need to about what’s going down. If the task is <strong>Idle</strong>, it also figures out what that means.</p><p><strong>Idle </strong>sorting works like this:</p><ol><li>Do you (the character) need to eat/ sleep/ shit/ destress (work out)?<br> • Throw all of the ones you said ‘yes’ to into a randomly ordered list<br> • Find the first one on the list that you can do *at this moment*, based on ship state<br> • Target the nearest spot to do so</li><li>No-can-do? Look for work around the ship (<strong>Maintenance</strong>, non-Alerted <strong>Repairs </strong>and <strong>Healing</strong>, or <strong>Using </strong>systems/ resource production [5])<br> • If it’s your job team’s work type, put it on the list<br> • Also roll a die as a chance to consider other tasks (‘want’ to work, I guess)<br> • If you can find work with those constraints, pick one at random<br> • Target the nearest spot to do the chosen work</li><li>Didn’t find work (that you wanted to do)? Well, <em>could </em>you eat/ sleep/ shit/ work out if you had to?<br> • Put any that are possible on a randomly ordered list<br> • Throw “wandering around aimlessly like an idiot” on the list, because that’s always an option<br> • Pick one</li></ol><p>From here, the <strong>Job </strong>finishes flipping all the switches and tells <strong>SimplePath </strong>to start moving to the target’s location.</p><p><strong>SimplePath </strong>does its thing. [6] When it arrives, it tells <strong>BehaviorHandler</strong>.</p><p><strong>BehaviorHandler </strong>goes, “What am I doing? Oh, yeah.” If that task is “wander around aimlessly”, it decides it’s done and wraps up the job. If not, then it figures out what it needs to actually do. If it’s a ‘real’ task, it rolls lots of dice. Lots of dice.</p><p>Once it’s done that, it asks itself: did I fuck this up? (Probably) If yes, make a mess of everything, abandon all hope, and run away (get a new <strong>Job</strong>).</p><p>If no, it logs how much progress it made. Then it asks: is the task complete? If it is, it starts the <strong>Job </strong>wrap up process. If it isn’t, it waits a bit [7] then asks, “What am I doing?” again and does it all over. Repeat until it bails, finishes, or gets interrupted.</p><p>In addition to feeding into the game, all of this information created along the way also loops back into character classes such as:</p><ul><li>‘<strong>CharacterAnim</strong>’ — which controls, you guessed it, character animation</li><li>‘<strong>CharacterColors</strong>’ — which determines appearance (all character sprites start white and then have a subtractive color applied, per piece)</li><li>‘<strong>CharacterSpeech</strong>’ — which manages all that babbling they do, delimited by the character’s personality and current thoughts</li></ul><p>And that’s the gist of it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9JDiM4lD8RSUe_DLOZKj1Q.jpeg" /><figcaption>Game Over</figcaption></figure><p><em>Some more notes:</em></p><ol><li>Crew stress comes from all kinds of sources, not just the core stressors. Stuff like messing up a job, being hurt by a medic, and in-game events are all sources of extra stress.</li><li>Damage is dealt by last task type. Physical work results in more physical injuries, etc.</li><li>Those “bunch of factors” in priority evaluations? They’re the following: job team, task type, alert type, needs, stress, injuries, and character roles (e.g. ‘Military’ causes increased task stickiness and lowered consideration of needs).</li><li>In the “Is this target valid for you” question, it kicks off anyone else who is currently interacting with that target. Of course, it considers relative priorities before deciding to do that. For example: if there’s a <strong>Warning </strong>on a Bed with someone sleeping in it, and <strong>JobAssignment </strong>decides there’s an [Engineer] perfect for the job, it’ll check HOW IMPORTANT sleep is to that other crew member. If it’s not more important than the <strong>Warning</strong>, it’ll give them the boot and wake them up before declaring the target as valid.</li><li>Yes, Job.Idle() is thorough enough to check if a resource can be made before trying to assign that task. Yes, this means I used<strong>~x-<em>reflection</em>-x~</strong>.</li><li>Pathfinding in <em>Destination Ares</em> isn’t done on a traditional navmesh or graph. It’s based on individual nodes, spaced somewhat irregularly. Nodes are placed on each square of a ship room (manually linked to each other on the prefab), and they automatically link to any other nodes within a very short distance, no matter the angle. In this case, that only means doors. The result is a very discrete movement space, walls that don’t need colliders, and player-designed ships that don’t accidentally allow spacewalking.</li><li>If I could do it differently, a lot of this wouldn’t be built on per-frame checks or timers. I’d use more callbacks. That’s a personal preference. Mostly it’s inexpensive the way it is, at the scale I need.</li><li>Apparently, I can keep talking forever, so I’ll cut it off here. Reach out directly if you have more questions.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a90a44141433" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Release Unto the Dark]]></title>
            <link>https://medium.com/indie-game-devlogs/release-unto-the-dark-d76f939c16cc?source=rss-481baa1906a------2</link>
            <guid isPermaLink="false">https://medium.com/p/d76f939c16cc</guid>
            <category><![CDATA[space]]></category>
            <category><![CDATA[simulation]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[indiedev]]></category>
            <dc:creator><![CDATA[Pat Scott]]></dc:creator>
            <pubDate>Thu, 07 Sep 2017 20:04:07 GMT</pubDate>
            <atom:updated>2017-09-07T20:04:07.883Z</atom:updated>
            <content:encoded><![CDATA[<p><em>&gt;&gt; Destination Ares</em> has a release date (and it’s soon)!!</p><p>Let’s talk about this game I’ve dedicated over three years and roughly 8000 hours of my life to make.</p><p><em>(skip to the bottom of the post if you want to get straight to the date)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JiNk4SSTcu9vaRZ7aLd7Dw.png" /></figure><p><em>Destination Ares</em> is a game about humanity. It’s a lens into the cruelty, fallibility, idiocy, isolation, kindness (and potential redemption) inherent in all of us. It’s about the struggles we face and that we cause each other to face. It’s about groping in the dark for a better way.</p><p>Of course, it’s also a game where you’re not human: you’re just a witness to all of this.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Tb2VWStofkS2YhFt8gaSA.png" /></figure><p>In <em>Destination Ares</em>, you play as an artificial intelligence. Specifically, you’re the sentient computer system of a colony ship on a one-way trip to the red planet. The cameras and sensors give you sight and sound, the electrical grid gives you life. You were birthed into this piecemeal hunk of scrap (that was somehow deemed space-worthy), and your existence is bound to its metal flesh. For all intents and purposes, this ship is your body.</p><p>The entire experience is limited to the short months it takes to burn hard across the “Ink” between planets, alone in the void with your crew. <br>… You’ll never see life on either planet, hypermalthusian nor frontier.</p><p>Any interactions with people outside the ship (whether organic or digital) will be few and fleeting.</p><p>Your crew will test you. They will succumb to the stresses of abandoning the only life and people they’ve ever known. They will cry, laugh, and curse at you. They will wreck shit, then flounder when the need for repairs is dire.</p><p>The ship will break down. Systems required for life-support, flight, communication, and even feces-storage will degrade and eventually wear out. Resources you need to keep going will be in short supply from the get go. And they’ll only run out from there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lThG84Z7Kp3o-FSNEu17hA.png" /></figure><p>It’s a game about isolation, about the internal struggle rather than the external. Most of your challenges come from within the ship, not without.</p><p>It’s a non-violent game backgrounded by a world of brutal, systemic violence.</p><p>It’s a game based on hard science, then skewed wildly for a stylized representation.</p><p>It’s a game where the humans are computer-controlled and the computer is human-controlled.</p><p>It’s a space game without aliens.</p><p>It’s a weird game.</p><p>It’s a hard game.</p><p>Most players will never see any ending other than tragic defeat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LKsJ-Blhx5gtFhFx53hqcw.png" /></figure><p>Those who do see an end will be able to do so in play sessions lasting <strong>under thirty minutes,</strong> though they can spend hours idly building their own ships from scratch and optimizing every system to make the trip.</p><p>The game falls into an odd space between genres: barely narrative adventure, somewhat deep strategy, not fully colony sim, and lightly touched with puzzles. It’s pseudo-procedural, yet actively balances RNG with responsiveness to both player skill and bad luck. There’s nothing else <em>quite </em>like it.</p><p>To make<em> Destination Ares</em>, I studied mythology, linguistics, depictions of AIs in art and literature, historical and cultural representations of Mars, life aboard the International Space Station, submarine blueprints, orbital physics, and countless other topics.</p><p>… then I threw it all together into some unholy abstraction.</p><p>It’s been a long journey. It’s not what I expected (the journey or the game).</p><p><em>Hey, it never is, right?</em></p><p><em>Destination Ares</em> is *almost* ready to be proferred to the <strong>terrifying </strong>judgment of the public.</p><p>I can’t wait for you to play it.</p><p><strong>If you’re a member of the press</strong> and would like to review this odd little gem, you can request a temporary Steam key at: <a href="https://dodistribute.com/access/w1rQuwbf1d/">https://dodistribute.com/access/w1rQuwbf1d/</a></p><p>(Press keys will be going out starting on September 19th.)</p><p><strong>If you’re a player </strong>anxious to see it come together in this homestretch, the Early Access version is currently available on itch.io and Steam:<br><a href="https://stralor.itch.io/destination-ares">https://stralor.itch.io/destination-ares</a><br><a href="https://store.steampowered.com/app/553470">https://store.steampowered.com/app/553470</a></p><p><strong>If you’re a fellow dev </strong>looking for commiseration or inspiration, you can catch me at various conventions (and parties) in San Diego / Cali / the US / Earth — AFTER MY GAME IS DONE!</p><p><strong>In any case,</strong> you can find me on Twitter <a href="http://twitter.com/_stralor">@_stralor</a>. Follow the development, remind me about bugs, or babble incoherently with me about late nights and the glory of Redvines.</p><h3>&gt;&gt; Destination Ares launches on September 22nd &lt;&lt;</h3><p>See you there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/202/1*LS7mcCAkDSBEdjPN6Bl4qQ.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d76f939c16cc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/indie-game-devlogs/release-unto-the-dark-d76f939c16cc">Release Unto the Dark</a> was originally published in <a href="https://medium.com/indie-game-devlogs">Indie Game Devlogs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fast Travel Sucks]]></title>
            <link>https://medium.com/@Stralor/fast-travel-sucks-5966cf7f7284?source=rss-481baa1906a------2</link>
            <guid isPermaLink="false">https://medium.com/p/5966cf7f7284</guid>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[exploration]]></category>
            <category><![CDATA[gaming]]></category>
            <dc:creator><![CDATA[Pat Scott]]></dc:creator>
            <pubDate>Wed, 12 Jul 2017 08:46:01 GMT</pubDate>
            <atom:updated>2017-07-12T16:58:14.555Z</atom:updated>
            <content:encoded><![CDATA[<h4>Fast travel is a crutch. It’s lazy design.</h4><blockquote>Written By: <a href="https://medium.com/@Stralor"><strong>Pat Scott</strong></a></blockquote><p>Instead of allowing for downtime:<strong> it breaks pacing.</strong><br>Instead of reinforcing the setting: <strong>it degrades the experience.</strong><br>Instead of creating conflict:<strong> it makes movement boring.</strong><br>And instead of encouraging excellent level design: <strong>it encourages sprawling expanses of blandness and bugginess.</strong></p><p>Why make an open world game with exploration if the OPEN WORLD and EXPLORATION aren’t inherently interesting?</p><p>A platformer should be engaging to hop across, whether that’s because of threats &amp; obstacles, mutating environs, or tight design that doesn’t force you to retrace your steps.</p><p>And, I mean, what’s a <em>racing</em> game if you aren’t racing?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*Nbdx6ukEaD_-4LYE.jpg" /></figure><h3>When Games Work</h3><p>The best parts of <em>GTA </em>games? Dicking the fuck around in the world, not teleporting from landmark to landmark.</p><p>Done right, you see games like <em>Dark Souls</em>, with spaces that wrap into each other and keep distances palatable and movement engrossing. <em>I talked a bit about this in my </em><a href="http://blog.patrick-scott.com/post/160752615950/design-spotlight-the-witness"><em>Design Spotlight for </em>The Witness</a><em>.</em></p><p>You also see this ethos coming back in games like <em>Rust </em>(and probably <em>DayZ, H1Z1, Unturned</em>, etc.): are you ever alone? are you ever safe?</p><p>You can risk that shortcut through a populated area, or you can skirt the long way, hoping to stay under cover and maybe find worse loot.</p><h3>Train to Zone</h3><p>I think I first realized how much fast travel takes away from games when I was a kid playing <em>Everquest</em>. When I started playing early in its lifecycle, teleportation was pricey (esp. for a lowbie like me), and therefore fairly rare. A lot of travel was done on foot or seafaring boat <em>(BOOAAAAT IS HERE!)</em>.</p><p>This forced me to actually venture into places I probably shouldn’t so I could get to the places I wanted to be. <strong>And I discovered wonders.</strong> Fascinating changes in biomes, fauna, and moods. Areas devoid of players, abandoned for more optimal grinding grounds, yet full of designer love and care.</p><p>I had to constantly assess my surroundings; threats could be anywhere.</p><p>I stopped playing around when teleporting became commonplace.</p><p>In my brief stint with <em>WoW</em>, my favorite adventure was taking a puny lvl 12 mage overland from Stormwind to Ironforge. I died, a lot. But it was a ton more interesting and adventurous than some underground tunnel my friends were babbling about.</p><p>Just today, I was talking about how fascinating movement across the map of <em>Sunless Sea</em> is. It’s slow and the controls aren’t terribly engaging (if wonderfully simple). Yet, movement is the primary stressor of the game. And it works incredibly well. When you travel, time is passing: fuel is burning, food is eaten, and terror rises.</p><p>This constant balancing act of resources, hugging coasts then beelining across open waters while timing the running lights, builds the atmosphere. Without it, even <strong><em>I</em></strong> would bore of endless beautiful prose.</p><p>It should come as no surprise I’m making a game that takes place entirely mid-travel. In <em>Destination Ares</em>, you’re always in space. Even pre-game building and designing of ships isn’t technically planet-side. It’s a game about the internal conflict of a rust bucket stuck in the void nothingness between the only two places humankind has ever managed to make barely livable. <em>What’s that like? What’s it take to survive?</em> As the computer keeping things running, you’re not responsible for launch and landing, just <strong>existing.</strong></p><p>Of course, that’s an extreme. Other games have done the travel experience with an eye looking outward: <em>Oregon Trail, FTL, </em>and <em>One Way Heroics</em> (to name a few personal inspirations and favorites).</p><p>There are spaces here many of games fail to explore. The grueling nature of monotony. Isolation. Being stuck alone when trouble comes. The raw intensity of putting one foot in front of the other, especially as it gets harder and harder.</p><h3>A Confession</h3><p>I’ll admit it, I like travel. <em>And I don’t mean I like lounging under a palm tree shade with a mai tai somewhere (though no complaints).</em> I mean I like the experience of <strong>going </strong>from place to place.</p><p>I like scrambling up talus and trudging down mountains. I like drinking beers and babbling on a train with a bunch of other travelers. I like napping between legs of a flight. I like blasting the music and the A/C on a long car ride. I like watching people shuffle about their day on a bus or subway, being present in this sublime ubiquitousness.</p><p>Mostly importantly, I like getting lost.</p><p>I like the stress of it, and I like the moments of <br>contemplation and<br>reflection and <br>meditation.</p><p>It’s beautiful and engaging unlike anything else.</p><h3>A Challenge</h3><p>So, here’s a challenge to my fellow game designers: <strong>cut out the fast travel; refuse lazy design.</strong> Create tighter, more interesting spaces that wrap on themselves. Craft movement systems that are challenging and threats that won’t let you forget. Build a world worth exploring, re-exploring, and wandering through again and again and again.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*v_laAOxcgEIbaZ2OWXBs-Q.jpeg" /><figcaption>author’s father, Steve Scott (c. 1970s)</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5966cf7f7284" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The End is in Sight: A Destination Ares Update]]></title>
            <link>https://medium.com/@Stralor/the-end-is-in-sight-a-destination-ares-update-f222b7a6163c?source=rss-481baa1906a------2</link>
            <guid isPermaLink="false">https://medium.com/p/f222b7a6163c</guid>
            <category><![CDATA[games]]></category>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[indie]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[Pat Scott]]></dc:creator>
            <pubDate>Wed, 28 Jun 2017 00:01:11 GMT</pubDate>
            <atom:updated>2017-06-28T00:01:11.813Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y9gpR4Z6Eilb1aJnUOnwfw.png" /></figure><p><em>Destination Ares</em> has been in Early Access for 7 months, after an initial closed development period of 27 months. Today, I’m announcing that there’s a light at the end of that (long, arduous) tunnel.</p><p>Since we (yes, you and I, unknown reader) started this journey through Early Access, <em>Destination Ares</em> has changed dramatically. Let’s highlight some additions I couldn’t imagine living without:</p><ul><li>The full soundtrack from R Kim Shultz (17 tracks!)</li><li>A revamped minigame</li><li>5 new ship systems</li><li>Steam Achievements</li><li>The <em>Folivora</em> alternate default ship</li><li>Half a dozen new events</li><li>And countless quality of life improvements, effects, sounds, particles, and upgrades</li></ul><p><strong>The game has come pretty far.</strong> And yet there is so much left to do! I believe the most important items will be coming together in the next couple of months.</p><p>I’ll be real with you, reader. Early Access hasn’t been everything I hoped. There are so many things it could have provided: community, <strong>feedback</strong>, a little extra cash flow, and visibility. It has been a great opportunity to bring players into the development process, and it has almost entirely missed the mark on all of this.</p><p>It’s probably my fault for working <em>only </em>full-time on it. I need another few hands, I think. At least somewhere to put all these <em>hats</em>.</p><p>Now, look here. I’m a stubborn bastard who puts too much emphasis on his word. This means I’m all the more determined to deliver this game, nearly three years after the project began, and despite the missteps in publicity and development.</p><p>So, I’ll put it out in the world: my goal is to reach full release in early Fall.</p><p>It’s ambitious, but, hey, I wouldn’t be doing a solo dev project if I weren’t an <em>ambitious </em>kind of guy. If I miss the Fall window, we’ll be stuck waiting until Spring! (that’d be awful)</p><p>To that end, I implore players of <em>Destination Ares</em> to help me sort what needs the most attention and what would be really awesome to have as we make our way to a version 1.0</p><p>A few specific items already on my priority hit list (and not yet in the next release):</p><ul><li>Revamped tutorial</li><li>Improved controls</li><li>Metagame progression</li><li>Steam Cards</li><li>Ditching the useless “Interpersonal” skill for: “Command”</li></ul><p>Of course more content is <em>always </em>on my list. More events, more chatter, <strong>more everything</strong>.</p><p>I’ve also got a HUGE wishlist from which I’ll be throwing as many things on as I can.</p><p><em>A few questions to help me sort my thoughts before release:</em></p><ol><li>What stats and info do you want in the side bar when building ships? There’s a lot of simulation under the hood; what’s worth knowing about?</li><li>How can I better teach the minigame? Some players understand that the pips are how many mines are nearby, some never figure it out (yes, despite the explanation scrolling underneath)</li><li>What events are awesome and what events are awful? Before release, I’m sure to do a bunch of writing and that’s a great chance to do some tweaks</li><li>What still confuses you about the game? Is there anything so obscure as to be unreasonably difficult?</li><li>What bugs are still aggravating you to this day?</li><li>How’s the performance on your computer?</li><li>Am I the only person who thinks the difficulty is too easy and I should add a hard mode? (the answer to this one is yes; I’ve only seen one other person beat it legitimately, ever)</li><li>Any cool ideas for more achievements and/or in-game unlocks?</li></ol><p>Thanks for everything; see you around, folks.</p><p>-Pat</p><p>P.S. I apologize for missing a blog post two weeks ago. I thought I prepped one for while I was at E3. I simply never did. Thanks for hanging around all the same :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f222b7a6163c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design Spotlight: Geneshift Demo]]></title>
            <link>https://medium.com/indie-game-devlogs/design-spotlight-geneshift-demo-c663b1dcb064?source=rss-481baa1906a------2</link>
            <guid isPermaLink="false">https://medium.com/p/c663b1dcb064</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[geneshift]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[design-spotlight]]></category>
            <category><![CDATA[indie]]></category>
            <dc:creator><![CDATA[Pat Scott]]></dc:creator>
            <pubDate>Wed, 31 May 2017 02:22:24 GMT</pubDate>
            <atom:updated>2017-05-31T02:22:24.529Z</atom:updated>
            <content:encoded><![CDATA[<p>A week ago, a game appeared on <a href="http://store.steampowered.com/app/308600/Geneshift/">Steam</a> and the front page of <a href="https://www.reddit.com/r/gaming/comments/6cvfli/in_one_hour_im_clicking_the_big_green_button/">reddit</a>: <em>Geneshift</em>, by one Ben “bencelot” Johnson.</p><p>It’s a “GTA2 inspired shooter” with zombies, or so goes the pitch. It’s chock full of decisions I disagree with as a designer. And it happens to be <strong>good fun</strong>.</p><p>Keeping in form with my Design Spotlight series, let’s talk about one design choice that I found to be excellent.</p><h4>The Demo is Multiplayer</h4><p>Yep, ^there it is. Here’s the why and how I think this is a “<em>good move, bro”</em>: <em>Geneshift </em>is a tiny indie game. It’s going to be crippled, as all multiplayer-focused games these days seem to be, by the fickle, fleeting populations so critical to success. AAAs can’t avoid this flash-in-the-pan world, but indies get the short stick: they often start out the gate as wastelands.</p><p><em>Anybody here ever play </em>The Showdown Effect<em> back in the day? That’s a great example of what to expect in this environment, even with a stellar product.</em></p><p><em>Geneshift </em>is further hurt by a lack of matchmaking. It uses the classic server browser interface, which is a great way of showing people, “Look at all of these empty servers and how many people don’t play!” rather than hiding it away in a (rage-inducingly long) queue. The queue might be a bitch, but at least players will put a little faith in it every now and then.</p><p><em>For example, </em>Duelyst <em>(which I’ve </em><a href="http://blog.patrick-scott.com/post/128670845678/design-spotlight-duelyst"><em>talked about before</em></a><em>) uses a matchmaking system. Back in beta, I could sit upwards of 40 minutes waiting for a match. Yet, by all appearances, it’s doing fine these days.</em></p><p>But <em>Geneshift </em>somehow just might stand a chance. And I don’t mean because Ben Johnson here has the obstinance and determination of a mule, though he does (<em>Geneshift </em>has been in development for 8 years — <em>makes me feel a bit better about how long my own recent project is taking</em>).</p><p><em>Geneshift </em>stands a chance because it’s accessible. He’s not afraid to have a demo that gives away what seems to be the core of the game FOR FREE. He’s confident that:<br>• players will find and engage with the demo<br>• players who love the demo will convert to paid for more SP and MP game modes<br>• and, players who don’t convert will stick around and keep the servers active</p><p>It still has tons of empty servers a week on, sure, but all accounts seem to show the community is growing. Who knows, maybe it’ll survive.</p><p><em>The model reminds me quite a bit of CCP’s recent move to open Eve Online to free players. </em><strong><em>I wonder if it’ll pay off.</em></strong></p><p>Best of luck to this odd little gem and its creator, from a fellow indie.</p><p><em>Normally, as I’ve done for the past few years, I write my posts over on my </em><a href="http://blog.patrick-scott.com/"><em>Tumblr-powered blog</em></a><em>. This week, I thought I’d stray from the norm and give Medium a try; it seems more suited to this long(ish) form.</em></p><p><em>Please send all fan- and hate-mail inspired by this decision to my twitter: </em><a href="https://medium.com/u/481baa1906a"><em>Pat Scott</em></a><em> (I’m looking for feedback)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c663b1dcb064" width="1" height="1" alt=""><hr><p><a href="https://medium.com/indie-game-devlogs/design-spotlight-geneshift-demo-c663b1dcb064">Design Spotlight: Geneshift Demo</a> was originally published in <a href="https://medium.com/indie-game-devlogs">Indie Game Devlogs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>