<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Wang Anthony</title>
    <description>The latest articles on DEV Community by Wang Anthony (@threshingdaygame).</description>
    <link>https://dev.to/threshingdaygame</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4204626%2Fb5378df5-b4e3-4ffd-919a-8402e8594052.jpg</url>
      <title>DEV Community: Wang Anthony</title>
      <link>https://dev.to/threshingdaygame</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/threshingdaygame"/>
    <language>en</language>
    <item>
      <title>A browser story game needs visible consequences, not just more choices</title>
      <dc:creator>Wang Anthony</dc:creator>
      <pubDate>Sat, 24 Oct 2026 12:14:46 +0000</pubDate>
      <link>https://dev.to/threshingdaygame/a-browser-story-game-needs-visible-consequences-not-just-more-choices-1m0b</link>
      <guid>https://dev.to/threshingdaygame/a-browser-story-game-needs-visible-consequences-not-just-more-choices-1m0b</guid>
      <description>&lt;p&gt;I am building &lt;a href="https://threshingdaygame.net/" rel="noopener noreferrer"&gt;Threshing Day Game&lt;/a&gt;, an illustrated fantasy choice adventure. One design problem kept coming up: a reader can enjoy the prose and still have no idea what their last choice actually changed.&lt;/p&gt;

&lt;p&gt;The current interface pairs the scene and choices with six live conditions: health, stamina, focus, composure, dragon attention and danger. These are resources and pressures inside the fiction, rather than a personality assessment of the player.&lt;/p&gt;

&lt;h2&gt;
  
  
  Show both the value and the change
&lt;/h2&gt;

&lt;p&gt;A bar alone gives a rough impression. A number gives precision. A signed delta answers the immediate question: what did that choice just do? The readout combines all three, and exposes the bar as a meter with its current value and limits. This also makes the information available without depending on its gold fill color.&lt;/p&gt;

&lt;h2&gt;
  
  
  Let story and interface explain each other
&lt;/h2&gt;

&lt;p&gt;A choice should be understandable in its scene before the player presses it. Afterwards, the numerical change should support the consequence described by the story. If danger rises after a reckless approach, the scene needs to make that pressure legible. Otherwise the readout becomes arbitrary bookkeeping.&lt;/p&gt;

&lt;h2&gt;
  
  
  Keep returning inexpensive
&lt;/h2&gt;

&lt;p&gt;This project saves runs locally in the browser. It does not require an account, but that means a save belongs to that browser rather than following a player across devices. Music starts off, so opening the page does not unexpectedly play sound. A downloadable ending card gives a finished run something tangible to leave with.&lt;/p&gt;

&lt;h2&gt;
  
  
  Scope and disclosure
&lt;/h2&gt;

&lt;p&gt;This is an independent fan project with original gameplay, developed with Codex and AI-assisted illustrations. It is separate from the official Dragonkind game, and there is no runtime AI generating responses to players. English, Czech and European Portuguese are available.&lt;/p&gt;

&lt;p&gt;You can &lt;a href="https://threshingdaygame.net/" rel="noopener noreferrer"&gt;try the current adventure&lt;/a&gt; and see how the scene, readout and choice panel work together. The question I am still using to judge the UI is simple: can a player explain why their last choice changed the situation?&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: this development note was drafted with AI assistance from the actual project implementation.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
    </item>
  </channel>
</rss>
