pages/assets/guide-to-incrementals_ludology_content_index.md.DASxETSj.js

import{d as n}from"./chunks/git.data.BNwuPjHI.js";import{M as o,q as i,Q as e,K as s,u as t,ag as r,p as h}from"./chunks/framework.Sr2_9k8k.js";const l=e("h1",{class:"p-name"},"Guide to Incrementals/What is Content?",-1),c=["innerHTML"],u=r('<hr><details><summary>Referenced by:</summary><a href="/garden/incremental-social/index.md">Incremental Social</a><a href="/garden/kronos/index.md">Kronos</a><a href="/garden/social-media/index.md">Social Media</a></details><p>If you&#39;ve been in the incremental games community for any amount of time, you&#39;ll quickly find the number one thing players want is <em>content</em>. They want as much of it as possible! The most popular incremental games have tons of content, so they just keep stretching on and on and on, introducing mechanic after mechanic, and players love it. In fact, players seem to value the <em>amount</em> of content over the quality of any <em>specific</em> content. However, there&#39;s a bit of a lack of understanding concerning <em>what</em> content is, and I&#39;d like to explore what counts as content, and how we measure it. As a baseline definition, I think &quot;content&quot; can just be described as the parts of the game that engage the player, but to truly understand it we need to contextualize what that means and how it affects the gameplay experience.</p><p>To clarify the purpose of this page, my goal is not to get (too) nitpicky or to attack games with &quot;low content&quot;. There&#39;s nothing wrong with short / low-content games - I&#39;m quite a big fan of those games myself! This is mostly targeted toward those who <em>ask</em> for content and settle for &quot;long&quot; games, and those who <em>want</em> to provide content but want to make sure they&#39;re not just artificially inflating the game. Ultimately, I suppose the goal is to just reduce the amount of artificially inflated content for the sake of having a &quot;longer&quot; game.</p><h2 id="interaction" tabindex="-1">Interaction <a class="header-anchor" href="#interaction" aria-label="Permalink to &quot;Interaction&quot;">​</a></h2><p>I think it should be a fairly non-controversial opinion that time spent <em>solely</em> waiting should not count towards content. That is not including the time reading various effects or making decisions in your head, but rather time spent waiting for a condition to be met so you can re-engage with the game.</p><p>That is not to say games should necessarily try to minimize this time. Plenty of games lead towards more infrequent interaction and still get popular. In fact, these games appeal to many gamers who want to have something to check up on in between bursts of working on some other activity. These games seem to have fallen slightly out of fashion amongst modern incremental games, but they&#39;re still fully valid. The point I&#39;m trying to make here is just that this time is not content. As an extreme example, a game with no interactions and just a counter that goes up every second could safely be said to have 0 content beyond the time it takes to understand what&#39;s going on. If it has a list of &quot;goals&quot; to hit, then the time understanding those goals and a short time after achieving each one could be considered content, but not the idle times in between.</p><p>Let&#39;s take a look at the opposite end of the spectrum - interaction that is so frequent as to become mindless. This is any mechanic where you need to spam-click something to progress. This may be a more controversial take, but I do not believe this constitutes content either. It does not engage the player, because each consecutive click blends together and they do not individually change the gameplay experience. That is to say, a single click and 100 clicks are not meaningfully different in terms of engaging the player. I&#39;d go as far as to say clicking 100 times would be actively <em>worse</em>, as it&#39;s artificially delaying the next piece of actual content, alongside the issues of accessibility and potentially causing RSI.</p><h3 id="repeatable-purchases" tabindex