<?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 @goshki on Medium]]></title>
        <description><![CDATA[Stories by @goshki on Medium]]></description>
        <link>https://medium.com/@goshki?source=rss-15f409600036------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*T6ixbvcD3rSMlVNGRFnNWg.png</url>
            <title>Stories by @goshki on Medium</title>
            <link>https://medium.com/@goshki?source=rss-15f409600036------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 09:34:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@goshki/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[Things about masking I wish I had learned earlier in life]]></title>
            <link>https://medium.com/@goshki/things-about-masking-i-wish-i-had-learned-earlier-in-life-3a7025fa5463?source=rss-15f409600036------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a7025fa5463</guid>
            <category><![CDATA[unsolicited-advice]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[tedtalks]]></category>
            <category><![CDATA[humor]]></category>
            <dc:creator><![CDATA[@goshki]]></dc:creator>
            <pubDate>Sun, 25 Oct 2026 15:31:43 GMT</pubDate>
            <atom:updated>2026-10-25T15:31:43.921Z</atom:updated>
            <content:encoded><![CDATA[<h3>Things about masking I wish I had learned earlier in life (even if my brain wasn’t developed enough to fully grasp them)</h3><p><em>Why the fewer masks you wear, the happier you will be — I wish my teenage brain could have comprehended this earlier!</em></p><p>For this sunny Sunday afternoon session of pseudo-philosophical musings nobody actually asked for, I present to you:</p><p>Things I wish I had learned earlier in life (as a kid or teenager, even if my brain wasn’t developed enough to fully grasp them).</p><p>Here goes:</p><ul><li>many of my own behaviors are actually masks</li><li>everyone else wears masks too (sometimes unconsciously), or even projects entire personas</li><li>a single person can use multiple personas, some of which you will never get to know</li><li>all public figures use personas, even if they claim to be completely authentic</li><li>masks and personas are used either out of fear or for personal benefit</li><li>we tend to project our own fears and motivations onto others, so it is worth giving people the benefit of the doubt</li><li>some people will try to impose their perception of you onto you</li><li>you owe them nothing but rejecting their projection may have consequences</li><li>most people wear masks even around their loved ones</li><li>if you find someone who allows you to feel genuine and drop your masks, cherish that relationship (but make sure doing so doesn’t require you to adopt new masks in exchange)</li><li>the fewer masks you need to wear, the happier you will generally be</li><li>dropping a mask (or persona) is always a choice, but it comes with consequences</li><li>building your view of the world, society, and the people around you only on the masks and personas you get to see is damaging, because you end up basing your understanding of reality on a performance</li><li>failing to learn all this makes life unnecessary harder and the sooner you understand it, the easier your life will generally be (even if certain aspects of it become harder)</li></ul><p>Anyway, thanks for coming to my TED Talk. Have a great evening and stay hydrated.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a7025fa5463" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Game genre expectations (mis)-management]]></title>
            <link>https://medium.com/@goshki/game-genre-expectations-mis-management-4a74fc84590b?source=rss-15f409600036------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a74fc84590b</guid>
            <category><![CDATA[point-and-click-adventure]]></category>
            <category><![CDATA[game-design]]></category>
            <category><![CDATA[game-development]]></category>
            <dc:creator><![CDATA[@goshki]]></dc:creator>
            <pubDate>Thu, 03 Sep 2026 14:38:49 GMT</pubDate>
            <atom:updated>2026-09-03T14:38:49.376Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Musings on why Phonopolis left me tired, frustrated, and disappointed (and what it means for Wright Files: Egerton’s Pickle).</em></p><p>This post has been inspired by <em>Phonopolis</em>. Specifically, by not enjoying playing <em>Phonopolis</em> to the point of abandoning it after this particular puzzle.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s2KtxySr1rBSc_-DMeWITA.png" /><figcaption>After watching a fragment of a L<em>et’s Play</em> with the solution of this puzzle (in which the player needs to obtain an extra bulb for the projector), I’ve just closed the game and watched the rest of the <em>let’s play</em> to find out how the game ends…</figcaption></figure><p>I had reached a point in the game where you need to obtain an extra bulb for a projector. To get it, you need to interact with a kind of a “cooking machine” which is one of those tactile contraptions where you poke around, rotate parts, activate components, and try to figure out the rules purely through trial and error (I call them “tinker-toys” but we’ll get to it).</p><p>I poked at it for a while, but instead of curiosity or satisfaction, I just felt tired and impatient. Eventually, I opened YouTube to watch a fragment of a L<em>et’s Play</em> showing the solution.</p><p>I watched the <em>let’s player</em> solve it, saw all the steps required, and suddenly realized that I had zero desire to switch back to the game window and repeat those steps myself. I didn’t want to poke at this contraption anymore, and I certainly didn’t want to face whatever similar puzzle was waiting for me in the next room especially that it was not the first solution I’ve looked up in <em>Phonopolis</em>.</p><p>My brain was already saturated from the sequence of puzzles leading up to it, and I felt like I was grinding instead of having fun discovering what happens next. So, I’ve just closed the game and watched the rest of the L<em>et’s Play</em> to find out how the story ends and to freely enjoy the audio-visual craft without having to interact with it.</p><p>That moment caught me off guard… what happened here?</p><h3>The unspoken promise of a genre</h3><p>You see, I’m a big fan of Amanita Design’s games (although, now that I think of it, it’s a rather complicated relationship, with each new title deepening a sense of dissonance). And it’s safe to say that <em>Phonopolis</em> is a typical, instantly recognizable Amanita’s game, crafted with immense care and great passion. Yet there I was: tired, frustrated, and disappointed enough to walk away mid-game.</p><p>How does an objectively good game made by a studio you genuinely love end up pushing you to the point of quitting?</p><p>Make no mistake, it <em>is</em> a great game. There is nothing wrong with <em>Phonopolis</em>. It’s just not the experience I was expecting to have when I launched it.</p><p>The issue isn’t the game itself, but the expectation I’ve brought to it. Almost all of Amanita’s titles are categorized under the umbrella term of “point &amp; click adventure games.” But that label can mean very different things to different people.</p><p>When I hear “point &amp; click adventure”, I instinctively expect a story-rich experience bundled with logical deduction and fact association. I expect to engage with the world through a classic toolkit of puzzles — inventory management, environmental interactions, and NPC dialogue — while having a certain degree of freedom in how I experience the world and unravel the story.</p><p>Instead, when I played <em>Phonopolis</em>, I got a very different kind of game.</p><p>To understand why this created such a jarring dissonance — and why it ultimately pushed me to quit — one has to look back at how my relationship with Amanita Design formed in the first place, and how my own mental template of their games was built.</p><h3>Amanita = Machinarium</h3><p>My first proper encounter with Amanita’s games was <em>Machinarium</em>.</p><p>I was aware of <em>Samorost 1</em> and <em>2</em>, but back then they felt more like bite-sized “tinker-toy” mini-games originating from the world of 10-minute Flash games.</p><p><em>Machinarium</em>, on the other hand, was a full-blown PC adventure game. It offered several hours of an experience that felt like both a revival and a breath of fresh air in the point &amp; click adventure genre. It had the classic structure, with a rich variety of puzzles: logic-based, environment-based, equipment/inventory-based, and NPC-based. But it also introduced tactile interactions where you manually operated levers, knobs, sliders, and latches. For me, that game set the benchmark for what an Amanita adventure looked and felt like.</p><p>Then came the gradual evolution:</p><ul><li><strong>After <em>Machinarium</em>, there was <em>Botanicula</em>:</strong> It was much simpler mechanically, but it retained a wonderful feeling of exploration and discovery.</li><li><strong>Then came <em>Samorost 3</em>:</strong> This felt like Amanita cranking up to 11 everything <em>Machinarium</em> had achieved. At the same time, it began introducing more “tinker-toy” scenes — puzzles that relied almost solely on the player’s curiosity and the willingness to reason about a mechanism simply by poking around with it.</li><li><strong>After <em>Samorost 3</em>, the shift deepened:</strong> Amanita started to gradually opt out of classic adventure game elements (inventories, item combinations, broader environmental backtracking) in favor of standalone, self-contained interactive vignettes. <em>Creaks</em> was a noticeable exception here — a puzzle-platformer that relied on careful observation, but operated on strict logic and mechanical rules where knowledge accumulated from room to room (it’s worth noting though that I didn’t finish <em>Creaks</em> due to mechanical difficulty level).</li></ul><p>And then came the announcement and release of <em>Phonopolis</em>.</p><p>Looking at the hand-crafted aesthetic, the perspective, and the setting, it looked very much like a return to the classic adventure game genre. But as I would find out, Amanita hadn’t actually returned to <em>Machinarium</em> which I considered as their roots — they had continued following the path they had been on all along.</p><h3>Two very different ways to think</h3><p>I’ve used the term “tinker-toy” a couple of times now, so it’s worth taking a moment to clearly define what I mean by it — and how it differs from a classic deductive puzzle.</p><p>In a traditional <strong><em>deductive adventure puzzle</em></strong>, problem-solving starts with a mental model:</p><ul><li><strong>Observation and hypothesis:</strong> You look at the environment, notice an obstacle, and observe the established rules of the world.</li><li><strong>Reasoning before action:</strong> You check your inventory, connect clues, and formulate a hypothesis <em>before</em> you act (e.g., “<em>The boiler needs pressure, the pipe is cracked, and I have a wrench and tape in my inventory — if I patch the pipe and turn the valve, the steam will power the lift.</em>”).</li><li><strong>Execution:</strong> You apply the solution. If it fails, it’s usually because your logical chain has a missing link.</li></ul><p>A <strong><em>tinker-toy</em></strong>, on the other hand, operates on a completely different cognitive loop:</p><ul><li><strong>No upfront rules:</strong> You are presented with an isolated, self-contained mechanism — a box with gears, a strange panel of buttons, or an abstract contraption. The world gives you little to no prior context on how it functions.</li><li><strong>Curious poking:</strong> You cannot reason about the solution beforehand because the rules haven’t been established yet. Instead, you’re expected to just interact with: pull levers, turn dials, and click parts just to see what changes and how.</li><li><strong>Feedback-driven experimentation:</strong> The rules are discovered purely through immediate audiovisual feedback and trial-and-error. You poke at it until the internal logic of the toy reveals itself, and then you align the pieces to finish the sequence.</li></ul><p>There is nothing inherently wrong with tinker-toys. When used sparingly, they can be very charming, tactile, and playful — which is why <em>Machinarium</em> and <em>Samorost 3</em> felt so fresh for me.</p><p>The problem arises when a game shifts almost entirely from deductive problem-solving to continuous tinker-toy manipulation, especially when those toys are chained together back-to-back.</p><h3>Death by a thousand minigames</h3><p>This brings me to the real issue I’ve had with <em>Phonopolis</em>: the pacing of the type of puzzles.</p><p>In a traditional adventure game, you have natural cognitive breathers. Between challenging puzzles, you walk across screens, explore the environment, talk to characters, listen to dialogue, inspect non-essential background details or just enjoy the view. These moments give your brain time to reset and digest what just happened before you tackle the next obstacle.</p><p>In <em>Phonopolis</em>, there is very little room to breathe. On multiple occasions, the game leads you directly from one complex tinker-toy scene into another.</p><p>To give you a better idea, here’s the sequence of puzzles leading to the lightbulb scene that made me quit:</p><ol><li><strong>A crane picking up and combining train wagons:</strong> a multi-layered tinker-toy puzzle</li><li><strong>Avant-Garde Artists in a bathhouse:</strong> a multi-layered tinker-toy puzzle</li><li><strong>Entering Byro in the Bureaucratic Quarter:</strong> a short observation puzzle</li><li><strong>Rotating clerks preparing your pass to Avant-Garde Quarter:</strong> a multi-layered tinker-toy puzzle</li><li><strong>Moving the lady with the dirty dishes cart in a mess-hall:</strong> a short logic puzzle</li><li><strong>Obtaining the extra bulb for the projector:</strong> a multi-layered tinker-toy puzzle</li></ol><p>The entire sequence described above takes roughly 30–45 minutes to complete (maybe longer if you’re tired or maybe 15–20 minutes if you’re a speed runner and you already know the rules of each of those puzzles). In that short window, you are asked to solve six distinct, standalone minigames in a row with almost zero downtime in between.</p><p>Now, someone might argue that all these puzzles are quite logical and once you understand the rules they’re quite obvious to solve. But that’s the point! To understand them, you need to poke around and use trial and error. You cannot reason based on your knowledge of previous puzzles or in-game rules of the world. And once you do understand them, they become a chore.</p><p>And that’s why by the time I’ve reached that projector bulb contraption my patience was completely worn down. Any single one of those puzzles in isolation might have been totally fine, even enjoyable. But stacked one after another was just too much for me. The game kept asking me to perform the exact same type of trial-and-error poking without ever giving my brain a moment to rest.</p><h3>The Egerton’s Pickle pickle</h3><p>As I sat there analyzing why I had abandoned the game, a rather unsettling thought hit me:</p><p><strong><em>Wright Files: Egerton’s Pickle</em> — my very own game that I’ve started building 5 years ago — is at risk of falling into the exact same trap.</strong></p><p>If you look at the game’s aesthetic, setting, and premise, your brain makes immediate assumptions. You see an aristocratic English manor where each room is a separate scene, each full of furniture and other objects to inspect, you see a cast of characters to interrogate. Visually and thematically, it instantly brings to mind traditional 90s adventure games. A player glancing at a few screenshots will easily fill in the blanks:</p><ul><li><em>“Ah, an adventure game with enclosed-rooms where each location is a separate scene… looks like a classic point &amp; click detective adventure.”</em></li><li><em>“This implies that I’ll be able to experience the world at my own pace and the story will wait for my actions before unfolding.”</em></li><li><em>“And it’s a detective mystery game… I bet I’ll be interrogating suspects to find discrepancies in their testimonies by asking questions and pushing them in branching dialogues.”</em></li></ul><p>If a player enters <em>Egerton’s Pickle</em> with those assumptions, they will experience the same cognitive dissonance I had with <em>Phonopolis</em>. They will arrive prepared for one type of gameplay loop, only to find the underlying mechanics work completely differently. When a player expects one thing and gets another, they don’t judge the game on its own merits; they judge it on its failure to be something it maybe never intended to be.</p><p>As I’ve already mentioned several times before, it’s a love letter to Sam Manthorpe’s 1986 Commodore 64 classic <em>The Detective</em>, combined with the time-pressure mechanics of Roberta Williams’ <em>The Colonel’s Bequest</em> (1989).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i2_2X_kA3DyFbFip_bTvwA.gif" /><figcaption>A typical experience when playing <em>Wright Files: Egerton’s Pickle</em> — search an object to find an item, inspect the item to reveal a finding. This finding will count to your final investigation score.</figcaption></figure><p>That design choice creates four distinct gameplay differences:</p><p><strong>Direct movement and contextual menus.</strong></p><p>You control Eugene Wright directly using arrow keys or a gamepad. Standing near a character or an object you can bring up a contextual action menu: <em>Inspect</em>, <em>Analyze</em>, <em>Use</em>, <em>Ask About [Topic]</em>, etc. This keeps the interaction clean and immediate, drawing from pre-mouse arcade design rather than pixel hunting. Oh, did I mention, there’s no pointing &amp; clicking at all?</p><p><strong>A living, real-time schedule.</strong></p><p>Standard adventure games freeze the world until the player’s action initiates change, but <em>Egerton’s Pickle</em> runs on an active clock. Characters follow their own daily routines, hold private conversations behind closed doors, and move between rooms whether you are there to witness them or not. Spending twenty minutes analyzing paintings in the study means missing whatever argument just happened in the parlour.</p><p><strong>Embracing freedom and incomplete information.</strong></p><p>Players accustomed to linear adventures often try to comb every room and exhaust every dialogue option in a single sweep. <em>Egerton’s Pickle</em> expects the opposite: you have to prioritize your limited time, decide who to tail, and accept that you cannot be everywhere at once. What’s more, after the initial introductory cutscene, you’re left to your own devices. You’re completely free to do anything (or nothing at all) and you can reach the credits with only a partial picture of the crime, or piece together the full timeline to earn a high-scoring case solution.</p><p><strong>Your final score depends on how much you’ve witnessed and found out.</strong></p><p>The Colonel’s Bequest introduced something called “Sleuth-O-Meter” that ranks your detective skills. At the end of the game, it graded you on how many hidden details, items, and subplots you actually managed to uncover. <em>Egerton’s Pickle</em> relies on a similar system. Your objective is to gather all evidence and reveal all possible findings to achieve the highest possible evaluation at the end of the investigation: a perfect case solution as it was described in the titular <em>Wright Files</em>.</p><p>Now, my job as the developer is to make sure that players are aware of those design choices so they can create their own mental contract of what to expect.</p><h3>Honesty over inflated wishlists</h3><p>I cannot control the memories, nostalgic biases, or personal templates a player brings to my game. I can control the signals I send them.</p><p>That’s why I’m deliberately trying to make <em>Wright Files: Egerton’s Pickle</em> clear about what it is and what it isn’t. It draws from <em>The Detective</em> and <em>The Colonel’s Bequest</em>, and because of that it’s not a classic point &amp; click adventure. There’s no pointing and clicking! The world keeps moving while you investigate, and the game expects you to work with incomplete information rather than exhaust every room and every conversation.</p><p>Many players will reject the game because of that. I’m fine with it.</p><p>I’d rather have a smaller audience that starts the game with the right expectations than a larger audience that feels misled when they discover how it actually plays. I don’t want to spend years building the game only to have players bounce off it because they were expecting something I never intended to make.</p><p>Expectation management is part of the game’s final polish. The store page, screenshots, trailer, demo, and genre labels are all part of the experience because they help establish the mental model the player brings with them.</p><p>Whether that model is actually going to make <em>Egerton’s Pickle</em> a good and interesting game is something I’m still going to have to find out.</p><p>But if you know what <em>The Detective</em> was about, and you like Roberta Williams’ idea of a mystery where the world doesn’t wait for you, <em>Wright Files: Egerton’s Pickle</em> might be right up your alley. :-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a74fc84590b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fifth year of “Wright Files: Egertonʼs Pickle” development]]></title>
            <link>https://medium.com/@goshki/fifth-year-of-wright-files-egerton%CA%BCs-pickle-development-14a9681c4fe4?source=rss-15f409600036------2</link>
            <guid isPermaLink="false">https://medium.com/p/14a9681c4fe4</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[adventure]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[indie-game]]></category>
            <category><![CDATA[mystery]]></category>
            <dc:creator><![CDATA[@goshki]]></dc:creator>
            <pubDate>Wed, 15 Jul 2026 10:35:31 GMT</pubDate>
            <atom:updated>2026-07-15T10:35:31.863Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pp-xpBbop4_BszHYwUabIw.png" /></figure><p>Today marks exactly the fifth anniversary of starting the “Wright Files: Egerton’s Pickle” project. What started as a tiny love letter to Sam Manthorpe’s “The Detective” on the Commodore 64 has gradually evolved into something much bigger and more ambitious.</p><p>If you compare the game with its initial inspiration (i.e., “The Detective”) or even with how it looked a year ago… it’s a different kind of beast. Story, mechanics, graphics, tech — all of these have come a long way to where they are now.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fpv-osTBcuTY%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dpv-osTBcuTY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fpv-osTBcuTY%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/bab24516a50fd5bc29054872e1be97f6/href">https://medium.com/media/bab24516a50fd5bc29054872e1be97f6/href</a></iframe><p>But the core idea remains the same. It’s still a tiny detective mystery game where the world around you lives its own life. Itʼs a game where you can miss most of the story and still get to the end (unless you do something obviously stupid and end up dead), and where you are actually encouraged to replay the game, using previously gathered knowledge to affect the ending you experience.</p><p>Now that I think of it, it’s a daunting task to create such a “sandbox” adventure, and it makes me giggle (somewhat hysterically) that my initial estimate for finishing the game was a mere 3 months (or 6 in a pessimistic scenario). I have nothing but sheer appreciation for Sam Manthorpe (and Roberta Williams for “The Colonel’s Bequest”) for pulling this off in the ’80s. As for me, I’m still not there yet.</p><p>That being said, I still stand by my declaration that the demo (not the full game!) will be completed before 2026 ends. There are still some loose ends and issues I need to tackle, but I can see the finish line. It’s closer than it’s ever been!</p><p>So, stay tuned and if youʼd like to be the first to know when the gameʼs demo is available, follow <a href="https://goshki.itch.io/wright-files-egertons-pickle">“Wright Files: Egertonʼs Pickle” on Itch.io</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14a9681c4fe4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating games you never knew you wanted to play in your childhood]]></title>
            <link>https://medium.com/@goshki/creating-games-you-never-knew-you-wanted-to-play-in-your-childhood-b0a97b900409?source=rss-15f409600036------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0a97b900409</guid>
            <category><![CDATA[nostalgia]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[creativity]]></category>
            <category><![CDATA[manifesto]]></category>
            <category><![CDATA[personal-essay]]></category>
            <dc:creator><![CDATA[@goshki]]></dc:creator>
            <pubDate>Tue, 16 Jun 2026 13:08:10 GMT</pubDate>
            <atom:updated>2026-06-16T13:09:24.252Z</atom:updated>
            <content:encoded><![CDATA[<h4>A hopelessly nostalgic, but ultimately pragmatic, playful maker’s manifesto</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*G-B_QOQHq4U4ElygaHDJSw.png" /><figcaption>[<em>Best read in the voice of Alan Watts while listening to looped “Pictionary” by Eyeliner</em>]</figcaption></figure><h3>The Spark</h3><p>Perhaps you grew up standing on your tiptoes in a smoky arcade, too young for pocket money, watching older kids pump coins into cabinets and battle through <em>Rastan Saga</em>, <em>Gun.Smoke</em> or <em>Gauntlet</em>. Colorful pixels and the sharp, metallic clatter of the sound effects imprinted in your brain forever. A pure, untouchable fascination.</p><p>Perhaps your first encounter happened in your nephew’s living room, where you clutched a joystick and booted up <em>H.E.R.O.</em>, sending a tiny protagonist with a helicopter backpack into the caves, dying over and over but remaining completely captivated. That same afternoon you witnessed a legendary family anecdote: the nephew’s father getting so frustrated with the punishing difficulty of <em>Montezuma’s Revenge</em> that he literally ripped the joystick apart with his bare hands.</p><p>Maybe you remember a local community center’s room packed with children pairing up in front of ZX Spectrums with their weird, mushy rubber keys, an instructor expecting a five- or six-year-old you to write programs. You sat there staring blankly at the blinking cursor, uncaring of syntax, simply wanting them to load <em>Dizzy</em>.</p><p>Or maybe none of that sounds familiar at all. Maybe your timeline is completely different.</p><p>Maybe your first formative experience came from hacking weird and quirky Flash games in a school computer lab, building custom maps for <em>Quake III Arena</em>, <em>Unreal Tournament</em> or <em>Counter Strike</em> to be played at local LAN tournaments at your favorite Internet café, running a modded <em>Minecraft</em> server with friends, or cloning <em>Flappy Bird</em> for your iPhone.</p><p>It doesn’t really matter how you got here.</p><p>What matters is that you’ve tried, or are trying, to make something. And it has probably been harder than you expected.</p><p>You experienced a game and it planted a creative seed <em>inside</em> you. To build something similar all by yourself — adjusted to your needs, aligned with your way of seeing, and expanded by your imagination.</p><p><em>Yours.</em></p><p><em>Better.</em></p><p>Whatever that meant for you in that particular moment. And it’s worth understanding what that actually was. Because until you do, you’ll keep looking for it in the wrong places.</p><h3>The Consciousness of Childhood</h3><p>When you were young, you had not yet fully learned to watch yourself. You were free to simply be inside things.</p><p>A game gave that kind of consciousness a particularly rich surface to inhabit. It had just enough structure to hold your gaze and just enough mystery to demand imagination. The abstract shapes — whether low-resolution sprites, flat polygons, or simple blocks — did not fully depict a world. They <em>suggested</em> one. And your mind, eager and undefended, rushed in to complete the picture. The game and the player were not separate. The experience was seamless.</p><p>What the games of your childhood gave you was not just enchantment. They were the frame through which your imagination moved. And when a frame opens onto something extraordinary, it is very natural, and very human, to become attached to it ever afterward — mistaking it for the view, chasing the vessel in hopes of capturing the spirit.</p><h3>The Illusion of the Catch</h3><p>When you grow up longing for those early experiences, a strange sort of amnesia takes over. You remember that feeling of absolute absorption, and because it was triggered by specific games, you make the logical, yet flawed, assumption that the magic was contained within those games.</p><p>It wasn’t. The software was only half the equation. The other half was <em>you</em> — your age, the fact that the world was still unmapped, and a mind untethered by adult responsibilities. Nostalgia is rarely about the past. It is about a quality of unhurried presence that existed then and seems, now, difficult to reach. The magic was not in the game. It was in the meeting between a particular piece of work and your undivided attention.</p><p>The oversimplifying mind reaches backward. It identifies the last moment you felt that focus and thinks: <em>if I can rebuild the frame, perhaps the feeling will return.</em></p><h3>What You Are Actually Seeking</h3><p>When the attempt doesn’t feel the way you remember, what do you do?</p><p>It’s tempting to add more.</p><p>More detail. More complexity. More ambition. The simple project becomes a remaster, the remaster becomes a reimagining, and the reimagining becomes an endless, over-scoped project with crafting, procedural generation, and a feature list that would humble a professional studio. You are trying to reconstruct the original feeling by increasing the scale of the container — as though the magic were hiding somewhere in the detail, waiting for you to render it at a high enough resolution.</p><p>But a child’s mind, encountering a game with limited detail, did not experience poverty. It experienced an open landscape. When everything is fully rendered, the mind is deprived of the very emotion it yearns for.</p><p>The real question was never “<em>how do I recreate this game?”</em> It was always “<em>how do I find that level of engagement again?”</em></p><p>And here is where the shift occurs. That total immersion is already available to you, in the very act of <em>making</em>.</p><p>When you are deep in a design problem, the self-critical observer in your mind quiets. The gap between you and the work closes. You are no longer watching yourself build.</p><p>You are entirely inside the craft.</p><p>The finished game is not a predetermined destination. It is the artifact left behind by the process of discovery. You do not write its blueprint in advance, from a safe distance. You find the game, bit by bit, through the very act of making it. The play begins long before the game even exists.</p><h3>The Way of the Playful Maker</h3><p>To fully savor the highs and survive the lows of game creation without burning out, you must adopt the way of the playful maker.</p><p>The playful maker’s mantra is simple: be where the work is. Not hovering above it, managing it, or worrying whether it’s good enough. Be inside it.</p><p>When you are genuinely engaged with a coding problem, painstakingly shaping a sprite, carving out a corridor in a level editor, or searching through sound samples for the precise creak of a closing door in an empty hallway, you are no longer performing the act of making. You are simply making.</p><p>When creating the experience, experience the creation.</p><p>This is not always easy or effortless and it does not always feel transcendent. Often it is simply tedious. It is frustrating. It is three evenings on an esoteric edge-case with nothing to show but a working fix and a cold cup of tea. But the playful maker learns to recognize that this kind of resistance, stayed with rather than fled from, is where the concentration eventually becomes absolute.</p><p><em>The tinkering, with all its splinters, is the reward.</em></p><h3>The Gift of Limits</h3><p>Here is where the philosophy meets the practical.</p><p>The limits that shaped the games you loved were aesthetic: low resolution invited your imagination to complete what the hardware could not render. Your limits are different in kind but identical in function.</p><p>You are one person.</p><p>Perhaps you have only a handful of unoccupied hours after the household goes to sleep, a finite battery of mental energy after a day job, and a highly specific, uneven set of skills.</p><p>Or maybe you’re bound by something different. The principle holds regardless: whatever your limits are, they are the design parameters of your game.</p><p>Your limitations define the edges of your particular canvas. But only if you work with them deliberately, rather than against them or despite them. A constraint accepted and shaped becomes a style; a constraint merely suffered stays a deficiency.</p><p>If you cannot draw fine details, silhouettes let players complete the visual world. If you cannot compose orchestral scores, simple tones and silence become your evocative tools. If your strength is in coding, the artistry of your work lives in the tactile precision, responsiveness and emergence awakened by the game’s systems.</p><p>Classic games thrived within severe technical limits of memory and processing power. Your modern constraints — such as a lack of budget, time, or specialized skills — serve the same purpose: keeping your scope manageable and vision sharp.</p><p>The goal is to know your limits so intimately that they cease to feel like restrictions. This keeps the creative process an internal dialogue between you and the work, rather than a chase after industry standards.</p><h3>The Playful Maker at Work, The Mind at Peace</h3><p>You will not become again the child who played those games. That is true, and it is not a tragedy.</p><p>The capacity for that quality of focus has never gone anywhere. It surfaces when your code finally does what you wanted it to do, in the patient work of building your world into existence — piece by piece, one evoked emotion at a time. Your task is not to copy an old blueprint, but to hone the sensibilities you’ve carried all this time.</p><p>Sit down at the blinking cursor. Let the expectations fade.</p><p>Because when you build from a place of intent, unbothered play, you realize the ultimate victory was never about recreating past experiences. It was about allowing the work to surprise you — and, in doing so, uncovering the games you never knew you wanted to play in your childhood.</p><p>Created for <a href="https://itch.io/jam/manifesto-jam-2026"><strong><em>Manifesto Jam 2026</em></strong></a>, originally published on <a href="https://blog.vigeo.dev/post/819146708209582080/creating-games-you-never-knew-you-wanted-to-play"><em>Vigeo Games blog</em></a>.</p><p><a href="https://www.streamlinehq.com/icons/download/gamepad-minimalistic--29193">Gamepad icon</a> by <em>480 Design</em> licensed under a <a href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a></p><p><em>P.S.: If you’d like to have it in a PDF format, it’s available </em><a href="https://goshki.itch.io/creating-games-you-never-knew-you-wanted-to-play-in-your-childhood"><em>here</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0a97b900409" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Project Zeewolf-like — one year later]]></title>
            <link>https://medium.com/@goshki/project-zeewolf-like-one-year-later-3af6b416eb1a?source=rss-15f409600036------2</link>
            <guid isPermaLink="false">https://medium.com/p/3af6b416eb1a</guid>
            <category><![CDATA[time-management]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[unity]]></category>
            <dc:creator><![CDATA[@goshki]]></dc:creator>
            <pubDate>Fri, 02 Feb 2018 12:02:36 GMT</pubDate>
            <atom:updated>2018-02-02T12:02:36.668Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve recently checked my devlog and — surprise, surprise — a full year has passed since I’ve started working on Project Zeewolf-like. Oh boy, the time really does fly. I must say I’m really glad I’ve decided to start a devlog this time because now I’ve got a chance to look back on a full year of my hobby game-development work and share some insights.</p><p>Let’s start with the amount of days I was able to put into my after-hours gamedev work. December 5th, 2016 is the day of the first entry in my devlog and since then I’ve put <em>119</em> work-days in total. This translates to one work-day for every three days (and it translates well to my self-imposed rule of having at least two work-days each week). Important thing to note is that when I say “day” it rather means a couple of hours in a given day. I guess it wouldn’t be far from truth to say that on average I was able to put around three hours of work on a given work-day. This gives us around <em>380</em> hours of work for a whole year. Not that much… quite little, actually. Let’s see how it looks laid out on a whole year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xkvx05yprox-nqLobjG_tA.png" /><figcaption>Project Zeewolf-like game-development work chart for 2017.</figcaption></figure><p>Oh my, what happened here… Turns out I wasn’t working only on Project Zeewolf-like this year. There have been quite a few distractions an they have taken quite some time. Only <em>61</em> days was actual work on Project Zeewolf-like. But the truth is, some of those distractions were closely related to my main goal. I’ve just decided it would be easier to work on a specific feature in a clean environment. I adnotated those pseudo-distractions with the feature they were related to (touch-screen controls, game architecture, meta-game, etc.). After adding time of those pseudo-distractions the overall work time on Project Zeewolf-like is <em>106</em> days out of <em>119</em>. Not bad! I’ve actually managed to stay focused for most of the year. I can pat myself on the back, right? Well, yes and no.</p><p>Out of those <em>119</em> work days, there have been <em>13</em> days of pure distraction. That’s about a month of work considering my average monthly workload. Another thing to note is that moving a feature out to a clean project was usually preceeded by several days of highly inefficient work where I was mainly wondering how to actually implement a given feature. This was due to my lack of experience or knowledge and resulted in a lot of procrastination. I stayed focused on the project but delved into various details, insignificant at that point (like aesthetics, controls feel or movement feel). Perhaps the most beneficial distraction of all was the last one. It focused mostly on the most mundane tasks like game architecture, level configuration, persistence, player progress and a lot of tiny (and large) things that are invisible to the player but thechnically constitute a proper game. It was the longest running pseudo-distraction and ironically I’ve reached a moment where I felt an urge to make a distraction within that distraction. How meta is that?</p><p>Overall, it was my most efficient game-development years ever. And even though it might seems there was not much visual progress, I feel like I’ve achieved much more than in all previous years combined. I know much more about Unity, I have a much better understanding of various components that make a game and a more mature approach to game development. There’s still much more I need to learn but now I at least know how much work awaits me (a lot!). I’ve also gained valuable insight into my strongest and weakest work characteristics and how they affected my previous (mostly failed) projects. Most importantly, I’ve learned how to beat my procrastination habits (at least a bit) and how to make some actual progress instead of marking time.</p><p>Thanks for your time and stay tuned for more progress reports! They’ll come, sooner or later. No doubt about it. ;-)</p><p>The post originally appeared on <a href="http://blog.vigeogam.es/post/168180198984/project-zeewolf-like-one-year-later">Vigeo Games blog</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3af6b416eb1a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing out Unity with a little Zeewolf-like thing]]></title>
            <link>https://medium.com/@goshki/testing-out-unity-with-a-little-zeewolf-like-thing-e0bb9dd1587?source=rss-15f409600036------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0bb9dd1587</guid>
            <category><![CDATA[game-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[unity]]></category>
            <dc:creator><![CDATA[@goshki]]></dc:creator>
            <pubDate>Wed, 10 Feb 2016 08:36:56 GMT</pubDate>
            <atom:updated>2018-02-02T12:05:04.013Z</atom:updated>
            <content:encoded><![CDATA[<p>Things have been really slow on the <a href="http://gamejolt.com/games/through-gbjam-4-version/85283">Through</a> front lately but the project gradually transforms into a proper game. I’m currently in the process of expanding and refactoring the level editor. In the meantime I’ve had the oportunity to get acquainted with Unity and decided to take a shot at a little idea I’ve had for quite a while, an arcade 3D shooter.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*beZC0K_J4ixth2RwTtLpbA.png" /></figure><p>Growing up in the era of 16-bit computers gave me the chance to play a lot of excellent Amiga games. One of them was <a href="https://en.wikipedia.org/wiki/Zeewolf">Zeewolf</a>, an arcade 3D shooter game where the player pilots an attack helicopter, performing various objectives like retrieving captured vehicles, rescuing POWs, and bringing mayhem and destruction to enemy units.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FToz9ngqrhW8%3Ffeature%3Doembed&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DToz9ngqrhW8%26feature%3Dyoutu.be&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FToz9ngqrhW8%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="640" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e3c19d52c10c4aea384a561a433b595c/href">https://medium.com/media/e3c19d52c10c4aea384a561a433b595c/href</a></iframe><p>While Zeewolf definitely is an arcade game, it’s not as hectic as a typical shoot ’em up. It has a slower pace and requires more tactical thinking, especially considering that ammo and fuel resources constantly deplete and require resupply. This makes gameplay less about pure manual skill in delivering destruction and more about clever planning how to approach given tasks and combat situations.</p><p>The theme and gameplay of Zeewolf resemble an earlier Sega Megadrive hit — <a href="https://en.wikipedia.org/wiki/Desert_Strike">Desert Strike</a> (which turned into a series of “Strike” games) but differs in few key elements, like 3D graphics, semi-automatic aiming, more varied missions and ability to pilot other types of vehicles. The third dimension made it possible to also control the helicopter’s height, particularly when using mouse-based controls (default joystick-based controls were much easier to learn but more limited when it comes to movement freedom).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/545/1*O8rHBXK_qjuo9krnuUavcQ.jpeg" /><figcaption>Zarch box art</figcaption></figure><p>It’s worth mentioning that Zeewolf’s 3D rendering engine bears a strong resemblance to the rendering engine of <a href="https://en.wikipedia.org/wiki/Zarch">Zarch/Virus</a>, a game developed by <a href="https://en.wikipedia.org/wiki/David_Braben">David Braben</a> (of Elite fame). In spite of all the similarities, Zeewolf is in no way related to Zarch.</p><p>Zeewolf and its sequel, Zeewolf 2: Wild Justice, were critically acclaimed games even though they were published in the beginning of the end of Amiga’s era (1994 and 1995 respectively). Nonetheless, in my personal opinion, they were one of the most innovative, unique, and fresh games in the Amiga’s shooter genre at their time with virtually no true successors.</p><p>Returning to my prototype and arcade 3D shooter idea, up to this day I have not found any game (be it PC, console or mobile) that would truly capture the spirit of Zeewolf experience. Of course it has many irks, shortcomings and annoyances by today standards but the design has aged suprisingly well and I’d love to revive it in my prototype, to see how it fits into today’s gaming landscape.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*-z7i2dQXQs7dBjhzXAyzgg.gif" /></figure><p>And this is how the prototype looks in motion right now. All the assets used in this scene come from the Unity Asset Store and are just placeholders that will definitely change. The purpose of the prototype is mostly to capture the feel of Zeewolf.</p><p>The post originally appeared on <a href="http://blog.vigeogam.es/post/138753202894/testing-out-unity-with-a-little-zeewolf-like-thing">Vigeo Games blog</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0bb9dd1587" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>