<?xml version="1.0" encoding="UTF-8" standalone="yes"?><oembed><version><![CDATA[1.0]]></version><provider_name><![CDATA[]]></provider_name><provider_url><![CDATA[https://itsthexstream.wordpress.com]]></provider_url><author_name><![CDATA[It's The X-Stream]]></author_name><author_url><![CDATA[https://itsthexstream.wordpress.com/author/itsthexstream/]]></author_url><title><![CDATA[20XX]]></title><type><![CDATA[link]]></type><html><![CDATA[<h1 class="p1"><span class="s2">Design</span></h1>
<ul class="ul1">
<li class="li3"><span class="s1">Procedurally-generated levels: How do you structure them so that they balance challenge and fairness?Level design&#8217;s definitely been a tricky, iterative process for us &#8211; balancing what the generator spits out has been a challenge.</span>
<ul class="ul1">
<li class="li3"><span class="s1">20XX&#8217;s levels are built out of semi-defined &#8220;chunks.&#8221; </span>
<ul class="ul1">
<li class="li3"><span class="s1">“A chunk contains static info like &#8220;how wide/tall is this room?&#8221;, as well as a skeleton of the intended platforming path through it, and a giant list of possible enemies/hazards that can spawn in that section.”</span></li>
</ul>
</li>
<li class="li3"><span class="s1">“When the level decides to make that chunk into a level segment, it populates the chunk with its skeleton, then, based on where in the game you are (is this a hard part or an easy part?) populates that chunk with more platforms, enemies, and hazards to fill it out. The fairness part, then, is in making sure that the potential range for any given difficulty setting feels fair. The skeleton has to be traversable with no upgrades (so it&#8217;s always doable), and the hazard/enemy placements have to be enough to provide some level of resistance. (This is a super iterative process, and some of our first attempts at this really sucked.)”</span></li>
<li class="li3"><span class="s1">“To make it all flow together, each chunk has a well-defined entry and exit point that&#8217;s build to mesh well with whatever pieces come before/after it.”</span></li>
</ul>
</li>
<li class="li3"><span class="s1">20XX is made in a custom C++ engine, which means porting it kind of sucks. That said, we really, really want to</span></li>
<li class="li3"><span class="s1">Echos to Eredu to 20XX dev cycle</span>
<ul class="ul1">
<li class="li3"><span class="s1">Character identities never changed</span></li>
<li class="li3"><span class="s1">Action platform feel w/roguelike elements never changed</span></li>
<li class="li3"><span class="s1">Implementation of game elements changed (soulnut unlocking)</span></li>
<li class="li3"><span class="s1">All art assets were redone from the early build</span></li>
<li class="li3"><span class="s1">Major milestone hit, lead to meaningful discussions about “upping” the games quality</span></li>
<li class="li3"><span class="s1">Clement Scott polished up the visuals</span></li>
<li class="li3"><span class="s1">Really reviewed the playability rules all the time</span></li>
<li class="li3"><span class="s1">Even had a load out system in the beginning, which got scrapped</span></li>
</ul>
</li>
<li class="li3"><span class="s1">Most significant change?</span>
<ul class="ul1">
<li class="li3"><span class="s1">Revamping all of the visuals from an aesthetic viewpoint</span></li>
<li class="li3"><span class="s1">Introducing the “core-aug” system (similar to the armour upgrades from MMX)</span>
<ul class="ul1">
<li class="li3"><span class="s1">Player experience improved as the avatar changes to reflect this</span></li>
<li class="li3"><span class="s1">Slot item filled but now gets the player thinking about the deeper customization features (CONVEYANCE!)</span></li>
<li class="li4"><span class="s1">Adds layers on top of the exploration elements</span></li>
</ul>
</li>
</ul>
</li>
</ul>
<h1 class="p2"><span class="s2">Dev Cycle</span></h1>
<ul class="ul1">
<li class="li3"><span class="s1">Most memorable &#8220;You might be an Indie Game Dev&#8221; moment</span>
<ul class="ul1">
<li class="li3"><span class="s1">“Our first showing at PAX East in 2014 behind the massive Twitch booth was one &#8212; our location was so, so bad and I was so, so excited to have it. “</span>
<ul class="ul1">
<li class="li3"><span class="s1">“My army of friends helping me set up the booth &#8212; the scrapped-together-ed-ness of the whole thing stands out to me as a &#8220;woo, indie dev!&#8221; moment. (Being across from the legendary Soda Drinker Pro.)”</span></li>
</ul>
</li>
<li class="li3"><span class="s1">“Staying up until 5 AM or whatever ungodly time it was the first time MANvsGAME and Ezekiel_III co-op streamed the game last Spring.”</span></li>
<li class="li3"><span class="s1">“The day we launched 20XX in Early Access, we sold 64 copies of the game. I was thrilled. In hindsight, that&#8217;s obviously terrible.”</span></li>
</ul>
</li>
<li class="li3"><span class="s1">As an indie developer, what is your work/life balance like?</span>
<ul class="ul1">
<li class="li3"><span class="s1">“My work quota isn&#8217;t defined in tasks, it&#8217;s defined in &#8220;how productive to I have to be to not feel like a piece of shit at the end of the day?&#8221; I can take off a day after a patch and play Overwatch all day if I want, but I&#8217;m probably going to feel like poop at the end because I wasted the day. I&#8217;m much more likely to work until I lose focus, play a little Hearthstone, and go back to work. Make some level chunks, play a little Diablo, go back to work.”</span></li>
<li class="li4"><span class="s1">“Some weeks I work all day every day, especially coming up on big shows or submission deadlines &#8212; some weeks it&#8217;s a little more lax than that. Since I&#8217;m also the customer support guy, there are multiple variances that contribute to my workload &#8212; when I break stuff or when we have big sale events, the rush of players with issues swells, and I spend more time setting them straight.”</span></li>
</ul>
</li>
</ul>
<h1 class="p2"><span class="s2">Release/Post-Release</span></h1>
<ul class="ul1">
<li class="li3"><span class="s1">Mighty # 9 release helped improve the games sales</span>
<ul class="ul1">
<li class="li3"><span class="s1">Ppl were thirsty for a good MMX-esque game but MN9 didn’t deliver so they looked elsewhere</span></li>
<li class="li3"><span class="s1">They communicated better to their fans to set expectations of what the game will be</span></li>
<li class="li3"><span class="s1">Weeklong steam deals/summer sales did a good job at advertising the game &amp; increasing sales</span></li>
<li class="li3"><span class="s1">Overlap in the fanbases on Steam where the communities advertise for them</span></li>
</ul>
</li>
<li class="li3"><span class="s1">Clear &amp; consistent update schedule for fans while in early access</span>
<ul class="ul1">
<li class="li3"><span class="s1">New bosses</span></li>
<li class="li3"><span class="s1">Armour sets (mix n match)</span></li>
<li class="li3"><span class="s1">Boss weapons have 2ndary purposes</span></li>
<li class="li3"><span class="s1">Vending machines to buy weapons (can knock over the machines &amp; get whatever)</span></li>
</ul>
</li>
<li class="li3"><span class="s1">Moving to launch/post launch</span>
<ul class="ul1">
<li class="li3"><span class="s1">Promising Lvl 9 with unique encounters as a capstone to a run</span></li>
<li class="li3"><span class="s1">Reworking all of the bosses</span></li>
<li class="li3"><span class="s1">Polish/fixing throughout the game itself</span></li>
<li class="li3"><span class="s1">Post launch</span>
<ul class="ul1">
<li class="li3"><span class="s1">Understanding where to port the games</span></li>
<li class="li3"><span class="s1">Additional musical themes for bosses</span></li>
<li class="li3"><span class="s1">Steam Workshop integration/mod availability (goal is for players to make their own segments —&gt;level editor that validates the chunks)</span>
<ul class="ul1">
<li class="li4"><span class="s1">Could lead to infinite level designs by integrating the validated designs in the community</span></li>
</ul>
</li>
</ul>
</li>
</ul>
</li>
</ul>
<h1 class="p2"><span class="s2">Fundraising</span></h1>
<ul class="ul1">
<li class="li3"><span class="s1">Putting own money into the project</span>
<ul class="ul1">
<li class="li3"><span class="s1">“Yup! Pretty much no game these days runs a Kickstarter intending to provide 100% of the game&#8217;s costs, and we were no exception.”</span></li>
<li class="li3"><span class="s1">“Of course, when we ran our Kickstarter, 20XX was relatively garbage-y compared to its current form. “</span>
<ul class="ul1">
<li class="li3"><span class="s1">“We should have waited, but we didn&#8217;t know we&#8217;d end up pushing it this far. “</span></li>
</ul>
</li>
<li class="li5"><span class="s1">“We really did intend to make this as a much smaller scope project, but every time we hit a milestone and got more and more attention, we realized there was really a market for this sort of thing. “</span></li>
</ul>
</li>
</ul>
]]></html><thumbnail_url><![CDATA[https://itsthexstream.files.wordpress.com/2018/08/20xx-banner.jpg?fit=440%2C330]]></thumbnail_url><thumbnail_width><![CDATA[440]]></thumbnail_width><thumbnail_height><![CDATA[233]]></thumbnail_height></oembed>