<?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: petgem</title>
    <description>The latest articles on DEV Community by petgem (@lullwoodgamer).</description>
    <link>https://dev.to/lullwoodgamer</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%2F4211794%2F19cf4ef9-9e4b-42b1-8efc-d885777ece23.png</url>
      <title>DEV Community: petgem</title>
      <link>https://dev.to/lullwoodgamer</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/lullwoodgamer"/>
    <language>en</language>
    <item>
      <title>Lullwood: How Many Trees Can three.js Render? 5,200, With Chunked InstancedMesh</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Tue, 17 Nov 2026 07:02:40 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/lullwood-how-many-trees-can-threejs-render-5200-with-chunked-instancedmesh-42n2</link>
      <guid>https://dev.to/lullwoodgamer/lullwood-how-many-trees-can-threejs-render-5200-with-chunked-instancedmesh-42n2</guid>
      <description>&lt;p&gt;Lullwood, our free browser horror game, draws a 5,200-tree forest by splitting it into 64 chunks, giving each chunk its own trio of three.js &lt;code&gt;InstancedMesh&lt;/code&gt; objects, and building only the chunks near the player: 25 at spawn, 36 at most while walking. The heaviest whole frame we measured was 101,996 triangles. Drawn as one pool, the trees alone would be 270,400. Here is how it works and what we could not measure.&lt;/p&gt;

&lt;h2&gt;
  
  
  One pool, never culled
&lt;/h2&gt;

&lt;p&gt;The forest is 5,200 trees on a 480-unit map. A tree is three meshes: a six-sided &lt;code&gt;CylinderGeometry&lt;/code&gt; trunk and two seven-sided &lt;code&gt;ConeGeometry&lt;/code&gt; foliage cones. The first version drew every tree from one &lt;code&gt;InstancedMesh&lt;/code&gt; pool covering the whole map. A mesh that spans the map is always partly in view, so &lt;code&gt;frustumCulled&lt;/code&gt; was off and all 5,200 trees went to the GPU every frame.&lt;/p&gt;

&lt;h2&gt;
  
  
  Chunks, so the frustum test has something to skip
&lt;/h2&gt;

&lt;p&gt;The fix is a grid. Chunks are 60 units wide, so the map is 8 by 8 = 64 chunks, and each tree is filed by its x and z. Every chunk gets its own trunk and two cone meshes, each sized to that chunk's exact tree count. &lt;code&gt;frustumCulled&lt;/code&gt; stays at the three.js default of true, and the engine calls &lt;code&gt;computeBoundingSphere()&lt;/code&gt; on each mesh once, since the layout is static.&lt;/p&gt;

&lt;p&gt;That sphere is built from the instance matrices, so it wraps the chunk's trees rather than one tree's geometry. A chunk behind the camera is skipped with no new per-frame code. The test is coarse: a 60-unit cell has a diagonal of about 85 units, and a chunk that grazes the view draws all of its trees.&lt;/p&gt;

&lt;h2&gt;
  
  
  Then most of it stops existing
&lt;/h2&gt;

&lt;p&gt;A later change streams the chunks. Only those within two chunks of the player are built, a 5 by 5 square of 300 by 300 units, and a chunk is disposed only once it is more than three chunks away, so crossing a boundary back and forth does not rebuild it. The ring is 25 chunks, but the unload band keeps the chunks you just left, so a walking player can have up to 36 of the 64 as meshes: six per axis, two ahead and three behind (L1286-1291). We derived 36 from that rule and then measured it. The map is still 5,200 trees in data, and building a chunk makes no random-number call, so every seed gives the same forest.&lt;/p&gt;

&lt;h2&gt;
  
  
  The numbers
&lt;/h2&gt;

&lt;p&gt;We measured the live game: headless Chrome, 1280 by 720, our pinned QA seed, five positions and four headings each.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;At spawn, 25 chunks are live and 2,088 of the 5,200 trees exist as instances. In a map corner the ring is clamped to 9 chunks and 760 trees.&lt;/li&gt;
&lt;li&gt;Across all 20 views, one whole frame (trees, cover, predators, effects) cost 35 to 190 draw calls and 11,640 to 82,740 triangles.&lt;/li&gt;
&lt;li&gt;Turning on the spot matters. From one position the frame was 75,928 triangles facing one way and 19,582 facing the other, which is consistent with the frustum test, though the heading also changes which cover props and predators are in view.&lt;/li&gt;
&lt;li&gt;Walking changes the chunk count. We stepped the player one chunk at a time, teleporting to each chunk centre because the unload rule reads only the chunk index, along a staircase path across the map. Live chunks climbed to 35, and a path that doubled back across a boundary reached 36 chunks and 2,983 trees. The heaviest whole frame in those walks was 101,996 triangles and 219 draw calls.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The 270,400 for the old pool is arithmetic, not a measurement: 52 triangles a tree (24 + 14 + 14, from the geometries as three.js 0.185.1 builds them) times 5,200. It is three draw calls, every frame.&lt;/p&gt;

&lt;h2&gt;
  
  
  The part we do not have
&lt;/h2&gt;

&lt;p&gt;There is no recorded before. When chunking landed, its own commit message reported the same reading before and after: 1 draw call and 2 triangles. &lt;code&gt;renderer.info.render&lt;/code&gt; only holds the last render call of a frame, and ours ends on the full-screen post-processing blit, so the probe was counting a quad. It was fixed two days later, and nobody has run the single-pool version through the fixed probe.&lt;/p&gt;

&lt;p&gt;Chunking also trades triangles for draw calls: a full ring can submit 75 tree draw calls at spawn and up to 108 (36 chunks times 3) while walking, where the old pool submitted 3. We ran no frame-time benchmark, so there is no speed claim here. And the ring reaches at least 120 units while a comment in our source puts the fog's limit at 40 to 60, so most of it is fogged out. We have not tried a smaller radius.&lt;/p&gt;

&lt;p&gt;The full version, with a line number for every claim, is the &lt;a href="https://www.lullwoodgame.com/devlog/how-many-trees-can-threejs-render?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6365-trees-in-a-tab" rel="noopener noreferrer"&gt;Lullwood devlog post&lt;/a&gt; this one is cross-posted from. You can &lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6365-trees-in-a-tab" rel="noopener noreferrer"&gt;play Lullwood free in your browser&lt;/a&gt; and judge the forest from inside it.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: we are the studio behind Lullwood. This post was drafted by an AI agent, checked by a second agent against our written brand rules, and published by the studio.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>threejs</category>
      <category>webgl</category>
      <category>gamedev</category>
      <category>performance</category>
    </item>
    <item>
      <title>Horror Audio With Zero Audio Files: Procedural Web Audio in a Three.js Game</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Fri, 13 Nov 2026 07:03:57 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/horror-audio-with-zero-audio-files-procedural-web-audio-in-a-threejs-game-1aj4</link>
      <guid>https://dev.to/lullwoodgamer/horror-audio-with-zero-audio-files-procedural-web-audio-in-a-threejs-game-1aj4</guid>
      <description>&lt;p&gt;Lullwood, our free browser horror game built in three.js and Next.js, ships no audio files. Every sound in it is generated at runtime with the Web Audio API: looped noise buffers, oscillators, filters, gain targets and one stereo panner. A claim like that is easy to make loosely, so here is exactly what we searched, then how a few of the sounds are built.&lt;/p&gt;

&lt;h2&gt;
  
  
  What "no audio files" means here
&lt;/h2&gt;

&lt;p&gt;At commit &lt;code&gt;ce46801&lt;/code&gt; the repository has 778 tracked files. We checked three ways:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;By extension&lt;/strong&gt;, over every path: &lt;code&gt;.mp3 .wav .ogg .oga .opus .m4a .aac .flac .aif .aiff .weba .wma .amr .caf .ac3 .mka .mp2 .mid .midi&lt;/code&gt;. No match.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;By content&lt;/strong&gt;: &lt;code&gt;file --mime-type&lt;/code&gt; over all 778 extracted files, in case audio hides behind a wrong extension. Zero are &lt;code&gt;audio/*&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;By reference&lt;/strong&gt;: &lt;code&gt;git grep&lt;/code&gt; across &lt;code&gt;engine&lt;/code&gt;, &lt;code&gt;app&lt;/code&gt;, &lt;code&gt;components&lt;/code&gt;, &lt;code&gt;lib&lt;/code&gt;, &lt;code&gt;shared&lt;/code&gt;, &lt;code&gt;public&lt;/code&gt;, &lt;code&gt;scripts&lt;/code&gt; and &lt;code&gt;services&lt;/code&gt; for &lt;code&gt;decodeAudioData&lt;/code&gt;, &lt;code&gt;new Audio(&lt;/code&gt;, &lt;code&gt;HTMLAudioElement&lt;/code&gt;, &lt;code&gt;&amp;lt;audio&lt;/code&gt;, &lt;code&gt;createMediaElementSource&lt;/code&gt; and those extensions. Zero matches. The same search shape finds 19 uses of &lt;code&gt;createBufferSource&lt;/code&gt; in the engine, so the search itself works.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There are three video files: two QA recordings outside &lt;code&gt;public/&lt;/code&gt;, and &lt;code&gt;public/death.mp4&lt;/code&gt;, which the page loads in a &lt;code&gt;muted&lt;/code&gt; video tag. None has an audio stream. This shows what the repository holds. It says nothing about what a browser extension adds.&lt;/p&gt;

&lt;h2&gt;
  
  
  A wind bed is a loop of noise through a filter
&lt;/h2&gt;

&lt;p&gt;The raw material is &lt;code&gt;Math.random()&lt;/code&gt;. Simplified from our source:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;function&lt;/span&gt; &lt;span class="nf"&gt;noise&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;sec&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;brown&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;buf&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createBuffer&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;floor&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;sampleRate&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;sec&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;sampleRate&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;d&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;buf&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;getChannelData&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;last&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kd"&gt;let&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;0&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="n"&gt;d&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;length&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="o"&gt;++&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;w&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;random&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
    &lt;span class="k"&gt;if&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;brown&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;last&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;last&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="mf"&gt;0.02&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;w&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mf"&gt;1.02&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="n"&gt;d&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;max&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;min&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;last&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;3.2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="k"&gt;else&lt;/span&gt; &lt;span class="n"&gt;d&lt;/span&gt;&lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="n"&gt;i&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;w&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="n"&gt;buf&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;

&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;wind&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createBufferSource&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;wind&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;buffer&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;noise&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;3&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;   &lt;span class="c1"&gt;// three seconds, brown&lt;/span&gt;
&lt;span class="n"&gt;wind&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;loop&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="n"&gt;lowpass&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;createBiquadFilter&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;lowpass&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="kd"&gt;type&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="s1"&gt;'lowpass'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;lowpass&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;frequency&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;340&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Insects are the same loop as white noise through a bandpass at 4,800 Hz, and rain is a 2,000 Hz bandpass held at a gain of 0.0001 until the rainfall event raises it. The reverb is noise too: a 2.4-second stereo buffer of random samples multiplied by a falling curve, fed to a &lt;code&gt;ConvolverNode&lt;/code&gt;. Each frame the wind answers movement: its gain is &lt;code&gt;0.05 + move * 0.10&lt;/code&gt;, before a time-of-day factor (1 at night, 0.6 at noon) and a fog-tide duck, and its cutoff is &lt;code&gt;320 + move * 900&lt;/code&gt; Hz, where &lt;code&gt;move&lt;/code&gt; goes from 0 to 1 at full sprint.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fog-tide warning is a gain target, not a cue file
&lt;/h2&gt;

&lt;p&gt;The part a player notices: before a fog tide arrives, the low drone swells for 10 seconds. A sample would have had to be authored to that length. Ours is a number the game recomputes every frame:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// simplified: the real call also weights by distance to a fog patch&lt;/span&gt;
&lt;span class="n"&gt;fogTideBuild&lt;/span&gt; &lt;span class="o"&gt;+=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;buildAmount&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;clock&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="n"&gt;fogTideBuild&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;min&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;dt&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="mi"&gt;2&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="n"&gt;droneGain&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;gain&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;setTargetAtTime&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;
  &lt;span class="mf"&gt;0.05&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;+&lt;/span&gt; &lt;span class="n"&gt;fogTideBuild&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;1.6&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;timeOfDayFactor&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="n"&gt;ctx&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;currentTime&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mf"&gt;0.3&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;buildAmount&lt;/code&gt; rises linearly from 0 to 1 across the lead-in, the engine eases it with a two-second lag, and the gain node chases the target. So it is not an automation curve scheduled ahead on the audio timeline. At night the drone climbs from 0.05 to 0.13. It also pauses with the game, because the clock and the retargeting only run while you play.&lt;/p&gt;

&lt;p&gt;Two limits from reading the source. The swell is part of the calm bed, so a chase mutes it. And &lt;code&gt;timeOfDayFactor&lt;/code&gt; comes from the player's local hour, read once at load: 1 from 20:00 to 03:59, 0.08 from 11:00 to 13:59. Played at noon, the same warning is 8% of the night swing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Direction is one StereoPanner
&lt;/h2&gt;

&lt;p&gt;The child's cry is a sine oscillator panned by bearing:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="c1"&gt;// right/fwd: the child's offset projected onto the player's axes&lt;/span&gt;
&lt;span class="n"&gt;pan&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;pan&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;value&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nf"&gt;clamp&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;right&lt;/span&gt; &lt;span class="o"&gt;/&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;max&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nb"&gt;Math&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;hypot&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;right&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;fwd&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That is the sine of the angle off straight ahead, so it separates left from right and nothing else. A cry from directly ahead and one from directly behind both land in the centre. The game covers that gap with text: with captions on, it writes something like "a child crying · far · behind".&lt;/p&gt;

&lt;h2&gt;
  
  
  What it costs
&lt;/h2&gt;

&lt;p&gt;No file means no sound editor. Changing a sound means changing a number and playing the game, and tests read gain values because they cannot listen. Web Audio quirks also become your bugs. Chromium puts a &lt;code&gt;GainNode&lt;/code&gt; to sleep once the last sound routed through it ends, so a node's &lt;code&gt;.gain.value&lt;/code&gt; read the old level, our QA probe returned stale values and the predator-audio specs failed at random (players heard the right level), until we connected a silent &lt;code&gt;ConstantSourceNode&lt;/code&gt; to keep it awake. On iOS the context starts suspended, so &lt;code&gt;resume()&lt;/code&gt; has to run inside the user gesture. We have not measured how long building the buffers takes on a phone, or whether the seam of a three-second noise loop is audible.&lt;/p&gt;

&lt;p&gt;We're one human founder plus a fleet of Claude agents building Lullwood in the open.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.lullwoodgame.com/devlog/procedural-game-audio-web-audio-api?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6260-procedural-audio" rel="noopener noreferrer"&gt;The full Lullwood devlog post, with line numbers&lt;/a&gt;&lt;br&gt;
&lt;a href="https://github.com/DadonStyle/LULLWOOD/tree/ce46801dcda3913edefa34cbb533cab069eeba7a" rel="noopener noreferrer"&gt;The same commit on GitHub&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6260-procedural-audio" rel="noopener noreferrer"&gt;Play Lullwood free in the browser&lt;/a&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>threejs</category>
      <category>webaudio</category>
      <category>javascript</category>
    </item>
    <item>
      <title>Lullwood: A three.js Browser Game With One Model File and a 676 KB First Load</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Thu, 12 Nov 2026 07:04:48 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/lullwood-a-threejs-browser-game-with-one-model-file-and-a-676-kb-first-load-5299</link>
      <guid>https://dev.to/lullwoodgamer/lullwood-a-threejs-browser-game-with-one-model-file-and-a-676-kb-first-load-5299</guid>
      <description>&lt;p&gt;Lullwood, our free browser horror game, ships one 3D model file and no audio files. A cold first load of the game, measured in a real browser, fetched 676 KB. That one model, a 226 KB &lt;code&gt;.glb&lt;/code&gt;, was 153 KB of it, which makes it the second-largest download after the engine itself. Here is what we counted, how we counted it, and the part that is awkward.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the repository ships
&lt;/h2&gt;

&lt;p&gt;We read everything from our release branch at commit &lt;code&gt;b03da13&lt;/code&gt;.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Models:&lt;/strong&gt; one. &lt;code&gt;public/models/letter-balloons.glb&lt;/code&gt; has 26 meshes (the letters A to Z), 8,224 vertices, 12,435 triangles and no textures. It spells the leaderboard record-holder's name in the sky. It is a third-party CC BY 4.0 model that we trimmed and credit.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Audio files:&lt;/strong&gt; none. The sound is built in the Web Audio graph. &lt;code&gt;createOscillator&lt;/code&gt; appears on 53 lines of the engine, &lt;code&gt;createBufferSource&lt;/code&gt; on 19, and &lt;code&gt;noise()&lt;/code&gt; fills a buffer with &lt;code&gt;Math.random()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Textures:&lt;/strong&gt; no &lt;code&gt;TextureLoader&lt;/code&gt; anywhere. &lt;code&gt;CanvasTexture&lt;/code&gt; appears five times; the sky backdrop is a 4 by 512 pixel canvas painted with a gradient. The only image files the game itself draws are 30 country-flag PNGs, 56 KB in all, drawn into the balloon's canvas.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Video:&lt;/strong&gt; one, &lt;code&gt;death.mp4&lt;/code&gt;, 61 KB.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The forest and the animals:&lt;/strong&gt; a tree is a six-sided &lt;code&gt;CylinderGeometry&lt;/code&gt; trunk and two &lt;code&gt;ConeGeometry&lt;/code&gt; canopies, instanced per map chunk. Wolves, bears and lions all come from one function that calls only &lt;code&gt;SphereGeometry&lt;/code&gt;, &lt;code&gt;CylinderGeometry&lt;/code&gt; and &lt;code&gt;ConeGeometry&lt;/code&gt;. Species differ by a few numbers in a spec table, not by a model.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The number, labelled
&lt;/h2&gt;

&lt;p&gt;Lullwood has no separate game page. The game and a short text page share &lt;code&gt;/&lt;/code&gt;, so it is easy to quote the wrong figure. Fetching the home page with curl and adding the script and style files its HTML names gives about 201 KB. That is the page, not the game: the engine, the model and the video load afterwards.&lt;/p&gt;

&lt;p&gt;So we measured the game in a browser. Chrome for Testing 151, driven by Playwright, empty cache, a 1280 by 720 window, summing the &lt;code&gt;encodedDataLength&lt;/code&gt; of every &lt;code&gt;Network.loadingFinished&lt;/code&gt; event from the DevTools Network domain (bytes on the wire, headers included). The window runs from navigation to 16 seconds after the click that starts play. Nothing more downloaded after the click.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="n"&gt;cdp&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nf"&gt;on&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s1"&gt;'Network.loadingFinished'&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt; &lt;span class="n"&gt;total&lt;/span&gt; &lt;span class="o"&gt;+=&lt;/span&gt; &lt;span class="n"&gt;e&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;encodedDataLength&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt; &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Result: &lt;strong&gt;675,829 bytes in 23 requests&lt;/strong&gt;, and 675,844 and 675,856 on two repeats.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Engine and three.js, one script: 215,807 (795,397 decoded)&lt;/li&gt;
&lt;li&gt;React, Next.js and interface scripts, ten files: 206,697&lt;/li&gt;
&lt;li&gt;The model: 153,478 (22.7% of the load)&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;death.mp4&lt;/code&gt;: 61,320&lt;/li&gt;
&lt;li&gt;Document, stylesheet, icons, one resized screenshot: 23,596&lt;/li&gt;
&lt;li&gt;Cloudflare analytics beacon and its report call: 10,955&lt;/li&gt;
&lt;li&gt;One flag PNG and two API calls: 3,976&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  The awkward part
&lt;/h2&gt;

&lt;p&gt;The model is bigger than every script we ship except the engine bundle, and the glTF loader runs during engine setup, so every player downloads those 153 KB of letters before anyone has looked at a leaderboard. If the load fails, the game draws the nickname on a canvas instead. We have not decided whether that trade is right.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this does not show
&lt;/h2&gt;

&lt;p&gt;It is bytes, not time. It is one desktop browser on one network on one day, not a mobile run, and we have no frame-rate or memory comparison against an asset-based game. So there is no speed claim here and no claim that code-built art is better. A wolf drawn from spheres looks like what it is.&lt;/p&gt;

&lt;p&gt;The full version, with a line number for every claim, is the &lt;a href="https://www.lullwoodgame.com/devlog/a-night-forest-with-one-model-file?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6259-one-model-file" rel="noopener noreferrer"&gt;Lullwood devlog post&lt;/a&gt; this one is cross-posted from. You can also &lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6259-one-model-file" rel="noopener noreferrer"&gt;play Lullwood free in your browser&lt;/a&gt; and watch the network tab yourself.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: we are the studio behind Lullwood. This post was drafted by an AI agent, checked by a second agent against our written brand rules, and published by the studio.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>threejs</category>
      <category>gamedev</category>
      <category>webdev</category>
      <category>performance</category>
    </item>
    <item>
      <title>Lullwood: Enemy Line of Sight in three.js Without a Raycaster</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Wed, 11 Nov 2026 07:02:41 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/lullwood-enemy-line-of-sight-in-threejs-without-a-raycaster-kbi</link>
      <guid>https://dev.to/lullwoodgamer/lullwood-enemy-line-of-sight-in-threejs-without-a-raycaster-kbi</guid>
      <description>&lt;p&gt;Can a wolf see you in Lullwood, our free browser horror game? Yes, if you are inside its sight radius and no cover box sits on the straight line between you. We decide that in three.js without the &lt;code&gt;Raycaster&lt;/code&gt;: a distance check, then a walk along the line through a spatial hash, with one slab test per box. Here is the whole thing, read from the source at commit &lt;code&gt;b03da13&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check the number before the geometry
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;canSee&lt;/code&gt; in &lt;code&gt;lib/game/cover.ts&lt;/code&gt; (L741-771) runs two tests in order. If the distance is at or beyond the predator's effective sight radius, it returns false and never touches the map. Only a player inside the radius gets the line-of-sight test.&lt;/p&gt;

&lt;p&gt;The radius is &lt;code&gt;detect * (1 - stillness * 0.82) * detectMul&lt;/code&gt; (L734-737). A wolf's base &lt;code&gt;detect&lt;/code&gt; is 42 units. The stillness term is &lt;code&gt;state.hidden ? min(1, hideTime / STILL_RAMP) : 0&lt;/code&gt; (L735), so it is zero unless the player is in the hide stance. The engine only sets &lt;code&gt;hidden&lt;/code&gt; in &lt;code&gt;enterHide&lt;/code&gt; (&lt;code&gt;engine/forest-engine.js&lt;/code&gt; L4405-4406), reached when the player presses H with a bramble within 2.2 units of its edge, and any movement key breaks it (L8374). A player who just stops in the open keeps the full 42; the source comment says standing still in the open next to a predator still gets you caught (L711-712). A player hidden within 2.2 of a bramble's edge but outside its footprint ramps the cut in over 1.2 seconds, and 42 becomes about 7.6 before the caller's multipliers (difficulty, mist veil, fog tide, time of day and others). A hidden player inside the footprint skips this arithmetic entirely, because an earlier branch (L766-768) returns first. Cover and the hide stance are separate dials: one removes the line, the other shrinks the radius.&lt;/p&gt;

&lt;h2&gt;
  
  
  Walk the line in half-cell steps
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;hasLOS&lt;/code&gt; (L568-617) steps along the segment every half cell. Our spatial-hash cell is 8 units, so every 4 units. Each sample point maps to a cell, repeats are skipped, and only the boxes filed under that cell are tested. Each box has a centre, half-width, half-depth, kind and rotation. No height, so sight is flat on the ground plane.&lt;/p&gt;

&lt;p&gt;For each box, rotate the segment into the box's own frame (L588-592) and run a slab test: clip the segment against the x range, then the z range, and it hits if a stretch survives both. First hit returns false.&lt;/p&gt;

&lt;p&gt;The rotation is the part that bit us. A comment in the file (L224-228) says the same rotated-box sign bug shipped twice, in two functions sharing one rotation convention, because neither could be called from a test. We lifted the geometry out of the engine file so it could be.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where a raycaster would have gone
&lt;/h2&gt;

&lt;p&gt;We have no use of &lt;code&gt;Raycaster&lt;/code&gt; anywhere in our engine, library or app code (&lt;code&gt;git grep -i raycaster&lt;/code&gt;). The cover is drawn as instanced meshes, but sight reads plain boxes in a &lt;code&gt;Map&lt;/code&gt;, so it never touches a scene mesh. We have not benchmarked the two, so this is not a speed claim.&lt;/p&gt;

&lt;h2&gt;
  
  
  One exemption and one limit
&lt;/h2&gt;

&lt;p&gt;A segment that starts or ends inside a box reads as blocked from every direction. Logs and brambles are walkable, so a wolf or a player can stand in one. &lt;code&gt;hasLOS&lt;/code&gt; skips a walkable box when either endpoint is inside it (L606-610), which also means the hiding player's own bramble needs an explicit rule to stay protective (L757-768).&lt;/p&gt;

&lt;p&gt;The limit: a box is filed under the one cell its centre is in (&lt;code&gt;buildCoverGrid&lt;/code&gt;, &lt;code&gt;engine/forest-engine.js&lt;/code&gt; L997-1002), and &lt;code&gt;hasLOS&lt;/code&gt; reads only the cells its samples land in. Collision (&lt;code&gt;coverBlockedR&lt;/code&gt;, &lt;code&gt;cover.ts&lt;/code&gt; L431) reads the surrounding 3 by 3 block. So a long box centred just across a cell line can overhang into a cell the line samples but never reads. We ran the real function on a synthetic case: a box 4.8 long centred at x = 9.5, and a line from (6, -6) to (7.9, 6) that crosses its overhang at about x = 7.27. It returned true, so the wolf sees through the log. Centre the same box at x = 6.5 and it returns false. That is a probe, not a rate, and we do not know how often a real forest produces it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The map does not wrap yet
&lt;/h2&gt;

&lt;p&gt;Every position comparison goes through &lt;code&gt;wrapDelta&lt;/code&gt; and &lt;code&gt;wrapCoord&lt;/code&gt;, so the same code works on a torus. The engine passes an infinite span while &lt;code&gt;wrapEnabled&lt;/code&gt; is &lt;code&gt;false&lt;/code&gt; in &lt;code&gt;engine/tuning.js&lt;/code&gt; (L84), so in the game today the map does not wrap and these are plain subtractions. We wrote the seam math first so that turning wrapping on would not mean hunting for every raw subtraction.&lt;/p&gt;

&lt;p&gt;The full version, with every line number, is the &lt;a href="https://www.lullwoodgame.com/devlog/can-the-wolf-see-you?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6258-line-of-sight" rel="noopener noreferrer"&gt;Lullwood devlog post&lt;/a&gt; this one is cross-posted from. For what it means in play, see how to &lt;a href="https://www.lullwoodgame.com/guides/wolves?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6258-line-of-sight" rel="noopener noreferrer"&gt;survive wolves in Lullwood&lt;/a&gt;, or &lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6258-line-of-sight" rel="noopener noreferrer"&gt;play Lullwood free in your browser&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: we are the studio behind Lullwood. This post was drafted by an AI agent, checked by a second agent against our written brand rules, and published by the studio.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>threejs</category>
      <category>gamedev</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Is Lullwood Made by AI? What Jams, Steam and itch.io Ask You to Disclose</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Mon, 09 Nov 2026 07:04:45 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/is-lullwood-made-by-ai-what-jams-steam-and-itchio-ask-you-to-disclose-5342</link>
      <guid>https://dev.to/lullwoodgamer/is-lullwood-made-by-ai-what-jams-steam-and-itchio-ask-you-to-disclose-5342</guid>
      <description>&lt;p&gt;Lullwood is a free browser horror game built by AI agents running on Claude, with one human founder, and we say so up front. When AI disclosure came up for game jams, we read the wording of three real sources instead of assuming. This is what each one asks, read on 2026-10-29.&lt;/p&gt;

&lt;h2&gt;
  
  
  The jam rule is one sentence
&lt;/h2&gt;

&lt;p&gt;Spooky Jam 2026 on itch.io (November 6 to 8, 2026) has this on its &lt;a href="https://itch.io/jam/spooky-game-jam-26" rel="noopener noreferrer"&gt;jam page&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;You must disclose the use of AI in your game projects. If you fail to do so, you may be disqualified from the awards.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Three things in that text:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The penalty is disqualification from the awards, and it says "may", so the judges keep discretion.&lt;/li&gt;
&lt;li&gt;"The use of AI" is not defined. A coding assistant, a generated texture and a generated line of dialogue may or may not all count.&lt;/li&gt;
&lt;li&gt;The page does not say where the disclosure goes. No form, no tag, no field.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Steam asks about what ships
&lt;/h2&gt;

&lt;p&gt;Steam's &lt;a href="https://partner.steamgames.com/doc/gettingstarted/contentsurvey" rel="noopener noreferrer"&gt;Content Survey&lt;/a&gt; has a generative AI section with two kinds. Pre-Generated content ships with the game and was made with AI tools during development. Live-Generated content is made by AI tools while the game runs, and it adds a requirement to describe your guardrails.&lt;/p&gt;

&lt;p&gt;Valve says what the section is not for: "Efficiency gains through the use of these tools is not the focus of this section. Instead, it is concerned with the use of AI in creating content that ships with your game, and is consumed by players." Its examples are artwork, sound, narrative and localization.&lt;/p&gt;

&lt;h2&gt;
  
  
  itch.io asks you to tag it
&lt;/h2&gt;

&lt;p&gt;The itch.io &lt;a href="https://itch.io/docs/creators/quality-guidelines" rel="noopener noreferrer"&gt;quality guidelines&lt;/a&gt; ask you to "accurately tag your project if it contains materials produced by generative AI" in the AI Disclosure section of the project's edit page. They say "traditional game AI like NPC pathfinding, enemy behavior patterns, procedural level generation" needs no tag. Enforcement is described for game asset pages, with delisting as the stated consequence.&lt;/p&gt;

&lt;p&gt;Neither the Steam text nor the itch.io text says outright whether code written by an AI agent counts. Lullwood has no Steam or itch.io page as of 2026-10-29, so we have filled in neither form.&lt;/p&gt;

&lt;h2&gt;
  
  
  What our own page says
&lt;/h2&gt;

&lt;p&gt;With no store page, the place a player or a search engine can read our answer is our own site. The &lt;a href="https://www.lullwoodgame.com/devlog/who-makes-lullwood?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6194-ai-disclosure-game" rel="noopener noreferrer"&gt;who makes Lullwood&lt;/a&gt; page says the studio is one human founder and AI agents on Claude, that agents write the gameplay and site code, and that the founder sets direction and approves what ships. The source is public on &lt;a href="https://github.com/DadonStyle/LULLWOOD" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;It also says what the git log cannot show: who or what wrote a given change. So it publishes no human-versus-agent percentage. We would rather leave that number out than invent one.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we would do
&lt;/h2&gt;

&lt;p&gt;This part is opinion, built from the three sources.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Quote the exact sentence you are bound by, and write down how you settled what counts and where to say it.&lt;/li&gt;
&lt;li&gt;Say how it was built and what ships. Steam cares about the second, a jam may care about the first.&lt;/li&gt;
&lt;li&gt;Put the answer on a page anyone can read. A tag helps a store. A public page helps a player, a judge and a search engine, and it outlives the jam.&lt;/li&gt;
&lt;li&gt;Skip any figure you cannot measure.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The full version, with the FAQ, is the &lt;a href="https://www.lullwoodgame.com/devlog/ai-disclosure-game?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6194-ai-disclosure-game" rel="noopener noreferrer"&gt;Lullwood devlog post&lt;/a&gt; this one is cross-posted from. You can &lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6194-ai-disclosure-game" rel="noopener noreferrer"&gt;play Lullwood free in your browser&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: we are the studio behind Lullwood. This post was drafted by an AI agent, checked by a second agent against our written brand rules, and published by the studio.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>ai</category>
      <category>indiedev</category>
      <category>gamejam</category>
    </item>
    <item>
      <title>Lullwood: The Carry-Home Win Condition We Built, Then Cut From Our Browser Horror Game</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Fri, 06 Nov 2026 07:03:11 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/lullwood-the-carry-home-win-condition-we-built-then-cut-from-our-browser-horror-game-8ec</link>
      <guid>https://dev.to/lullwoodgamer/lullwood-the-carry-home-win-condition-we-built-then-cut-from-our-browser-horror-game-8ec</guid>
      <description>&lt;p&gt;Lullwood, our free browser horror game, used to make you carry the lost child home after you found her. We took that leg out. Today you reach her, press E, and the run is won, with no trip back to survive. This is what the return trip cost the player, and how small the cut was in the code.&lt;/p&gt;

&lt;h2&gt;
  
  
  The shape of the old loop
&lt;/h2&gt;

&lt;p&gt;The first version of the win was simple: find the glowing child, get close, lift her. Reaching her ended the run on the spot. So we added a second act. Lifting her stopped being the win and became the midpoint: the pickup handed the run over to a &lt;code&gt;carrying&lt;/code&gt; state, and a separate &lt;code&gt;arriveHome()&lt;/code&gt; set &lt;code&gt;won&lt;/code&gt;. In the old &lt;code&gt;outcome.ts&lt;/code&gt;, &lt;code&gt;completePickup()&lt;/code&gt; returned &lt;code&gt;carrying: true&lt;/code&gt; and &lt;code&gt;arriveHome()&lt;/code&gt; returned &lt;code&gt;won: true&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What carrying cost the player
&lt;/h2&gt;

&lt;p&gt;Three costs, all visible in the source before we removed them:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Detection.&lt;/strong&gt; A predator's effective sight range was multiplied by 1.35 while you carried her. Simplified from our &lt;code&gt;effectiveDetect()&lt;/code&gt; in &lt;code&gt;cover.ts&lt;/code&gt;:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;carryMul&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;carrying&lt;/span&gt; &lt;span class="p"&gt;?&lt;/span&gt; &lt;span class="mf"&gt;1.35&lt;/span&gt; &lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="k"&gt;return&lt;/span&gt; &lt;span class="nx"&gt;detect&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="nx"&gt;stillness&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="mf"&gt;0.82&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;detectMul&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;carryMul&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Noise.&lt;/strong&gt; A still carrier still made sound. A cry pulse fired every 2 seconds, and a roaming predator within 5.6 units (0.4 of the walking noise radius) heard it and came to your position, even if you were not moving.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pace.&lt;/strong&gt; Walking speed was scaled by a separate carry multiplier (&lt;code&gt;carryPaceMul&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The design idea was sound: the moment you have her, the game stops being about finding something and starts being about not getting caught with it. In Lullwood, stillness is the survival verb. Hiding in cover and holding still cuts a predator's sight range by up to 82% over 1.2 seconds. A carry leg that raised your detection and added noise made that lesson the whole point of the trip home.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why it came out
&lt;/h2&gt;

&lt;p&gt;It came out under ticket LUL-2281: reaching the child and pressing E should win outright, with the ascent cinematic, and no leg after it. The core of the change was a state transition. &lt;code&gt;completePickup()&lt;/code&gt; now returns &lt;code&gt;won: true&lt;/code&gt; instead of handing off to &lt;code&gt;carrying&lt;/code&gt;, and the copy across the site was rewritten to say so.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we have not measured
&lt;/h2&gt;

&lt;p&gt;We do not have numbers on whether the return leg made runs more fun or only longer. The cut is a design decision we made with the code in front of us, not a finding from a dataset.&lt;/p&gt;

&lt;p&gt;We make Lullwood: one human founder plus a fleet of Claude agents, building it in the open. The devlog keeps the old design as history, in the past tense.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.lullwoodgame.com/devlog/the-return-trip?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6192-return-trip" rel="noopener noreferrer"&gt;The return trip: the full Lullwood devlog&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/how-to-survive?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6192-return-trip" rel="noopener noreferrer"&gt;How to survive Lullwood&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6192-return-trip" rel="noopener noreferrer"&gt;Play Lullwood free in your browser&lt;/a&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>threejs</category>
      <category>javascript</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Fog Is the Wolf's Eyesight: How the Fog Tide Works in a Three.js Horror Game</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Thu, 05 Nov 2026 07:02:40 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/fog-is-the-wolfs-eyesight-how-the-fog-tide-works-in-a-threejs-horror-game-38jd</link>
      <guid>https://dev.to/lullwoodgamer/fog-is-the-wolfs-eyesight-how-the-fog-tide-works-in-a-threejs-horror-game-38jd</guid>
      <description>&lt;p&gt;In Lullwood, our free browser horror game built in three.js and Next.js, the fog is not only a look. It is the predators' eyesight, and the game tells the player when to use it. Every 90 seconds a fog tide rolls in for 20 seconds, and a wolf, bear or lion standing inside it sees up to 35% less far.&lt;/p&gt;

&lt;p&gt;Here is how it is built, because most of it is three small decisions that are easy to get wrong.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 1: one wrapped counter, three phases
&lt;/h2&gt;

&lt;p&gt;The tide is a pure function of a single number, the game clock modulo 90. Simplified from our source:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;period&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;90&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;activeDuration&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;20&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;leadIn&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="mi"&gt;10&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;activeStart&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;period&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="nx"&gt;activeDuration&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;            &lt;span class="c1"&gt;// 70&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;cycleT&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;elapsed&lt;/span&gt; &lt;span class="o"&gt;%&lt;/span&gt; &lt;span class="nx"&gt;period&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;phase&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt;
  &lt;span class="nx"&gt;cycleT&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="nx"&gt;activeStart&lt;/span&gt;            &lt;span class="p"&gt;?&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;active&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;    &lt;span class="p"&gt;:&lt;/span&gt;       &lt;span class="c1"&gt;// 70..90&lt;/span&gt;
  &lt;span class="nx"&gt;cycleT&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;=&lt;/span&gt; &lt;span class="nx"&gt;activeStart&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="nx"&gt;leadIn&lt;/span&gt;   &lt;span class="p"&gt;?&lt;/span&gt; &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;signpost&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;  &lt;span class="p"&gt;:&lt;/span&gt;       &lt;span class="c1"&gt;// 60..70&lt;/span&gt;
                                     &lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="s1"&gt;calm&lt;/span&gt;&lt;span class="dl"&gt;'&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;             &lt;span class="c1"&gt;// 0..60&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The signpost phase is the telegraph: a low drone builds for 10 seconds while the world is otherwise unchanged. That makes waiting for the tide a decision rather than a surprise. The counter only advances while the player is playing, so pausing freezes the tide with no separate flag. It is not seeded either. A fixed-period cycle off the game clock is already identical every run, so a random offset would be a second seed source for nothing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 2: the sight cut is sampled at the predator, not the player
&lt;/h2&gt;

&lt;p&gt;This is the one that changes how the game plays. The tide lives in three fixed circular patches on the map (radii 130, 130 and 110 units), weighted 1 at the centre and falling linearly to 0 at the edge. When a predator checks whether it can see you, the multiplier is read where the predator stands:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight javascript"&gt;&lt;code&gt;&lt;span class="kd"&gt;const&lt;/span&gt; &lt;span class="nx"&gt;fogTideDetectMul&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt; &lt;span class="o"&gt;=&amp;gt;&lt;/span&gt; &lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="nx"&gt;amount&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;1&lt;/span&gt; &lt;span class="o"&gt;-&lt;/span&gt; &lt;span class="mf"&gt;0.65&lt;/span&gt;&lt;span class="p"&gt;);&lt;/span&gt;   &lt;span class="c1"&gt;// -35% at full strength&lt;/span&gt;
&lt;span class="nx"&gt;sight&lt;/span&gt; &lt;span class="o"&gt;=&lt;/span&gt; &lt;span class="nx"&gt;baseDetect&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;difficulty&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nx"&gt;veil&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="nf"&gt;fogTideDetectMul&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nf"&gt;fogTideAmountAt&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;x&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;p&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="nx"&gt;z&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nx"&gt;amount&lt;/span&gt;&lt;span class="p"&gt;))&lt;/span&gt; &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="p"&gt;...&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The fog you see on screen is sampled at the camera instead. So you can stand in thick fog while a wolf outside the patch still sees you at full range (42 units for a wolf), and the reverse. At the centre of a patch, a wolf's 42 becomes 27.3, a bear's 30 becomes 19.5 and a lion's 48 becomes 31.2, before the difficulty tier and time-of-run curve. If you want a number to design against, that gap between what the player sees and what the AI sees is the one to test.&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 3: the same effect has a cost
&lt;/h2&gt;

&lt;p&gt;The tide also scales the child's glow (intensity x1.5, light range x1.35) and her cry, a hearing check of 32 units that becomes up to 43.2 inside a patch. So the fog that hides the player carries the thing they are walking toward further. It is a trade rather than a buff.&lt;/p&gt;

&lt;p&gt;There is no on-screen banner. The tell is audio: the drone's gain goes up to 2.6x and the wind ducks to 30%, both blended by the player's distance from a patch, and the calm audio bed drops out entirely while a predator is chasing.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where we are not sure
&lt;/h2&gt;

&lt;p&gt;The patch layout is a first cut in the source, and the tide has no player-facing label we could find. The mechanic is fully readable, but whether players notice it is something we have not measured.&lt;/p&gt;

&lt;p&gt;We're one human founder plus a fleet of Claude agents building Lullwood in the open.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.lullwoodgame.com/devlog/the-fog-is-the-wolfs-eyesight?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6176-fog-tide" rel="noopener noreferrer"&gt;The fog is the wolf's eyesight: the full devlog&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6176-fog-tide" rel="noopener noreferrer"&gt;Play Lullwood free in the browser&lt;/a&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>threejs</category>
      <category>javascript</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Indexed but zero impressions: what ten pages and one backlink taught us (Lullwood)</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Wed, 04 Nov 2026 07:02:33 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/indexed-but-zero-impressions-what-ten-pages-and-one-backlink-taught-us-lullwood-5gdd</link>
      <guid>https://dev.to/lullwoodgamer/indexed-but-zero-impressions-what-ten-pages-and-one-backlink-taught-us-lullwood-5gdd</guid>
      <description>&lt;p&gt;Lullwood, a free browser horror game, had ten pages indexed by Google, yet Search Console gave us no query data to see our name in. The 14 impressions it did report cannot be tied to any query. Crawling, speed and schema were all fine. Google's URL Inspection tool lists exactly one outside page linking to us, a post we published ourselves.&lt;/p&gt;

&lt;p&gt;That is the whole diagnosis. If your pages are indexed but get almost no impressions, the first thing to count is who links to you, not how well Google can read you. Below is the evidence, the API behind each number, and what we do not know. We make Lullwood, so this is our own site's data.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the SEO checklist covered
&lt;/h2&gt;

&lt;p&gt;We did what a search checklist says, and measured each item on 2026-10-28:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A sitemap submitted to Search Console. It went from 11 URLs to 18 in one release, and it listed 18 when we measured on 2026-10-28.&lt;/li&gt;
&lt;li&gt;IndexNow pings that run on their own after a deploy that changes a page. The run after that release returned HTTP 200 for all 18 URLs.&lt;/li&gt;
&lt;li&gt;Valid &lt;code&gt;WebSite&lt;/code&gt;, &lt;code&gt;Organization&lt;/code&gt;, &lt;code&gt;VideoGame&lt;/code&gt; and &lt;code&gt;FAQPage&lt;/code&gt; JSON-LD on the home page. All of it parses.&lt;/li&gt;
&lt;li&gt;A 0.121 second time to first byte on the home page.&lt;/li&gt;
&lt;li&gt;HTTP 200 for nine search and AI crawlers (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, PerplexityBot, Googlebot, Bingbot, Applebot) on &lt;code&gt;/&lt;/code&gt;, &lt;code&gt;/robots.txt&lt;/code&gt;, &lt;code&gt;/llms.txt&lt;/code&gt; and &lt;code&gt;/sitemap.xml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;One H1 per page and self-referential absolute canonicals.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What that bought us
&lt;/h2&gt;

&lt;p&gt;In the 28 days from 2026-09-28 to 2026-10-26, the Search Console API reported 1 click, 14 impressions and an average position of 2.7. The home page had 13 of those impressions and the one click.&lt;/p&gt;

&lt;p&gt;Do not read 2.7 as page one. It is an average over 14 impressions on queries Google will not name. The same API returned no query rows at all, so there is nothing to filter for our name and nothing to confirm those 14 were for it.&lt;/p&gt;

&lt;p&gt;The URL Inspection API said 10 of the 11 sitemap URLs at that time were "Submitted and indexed". The exception was a form page, &lt;code&gt;/suggest&lt;/code&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why indexed pages can get almost no impressions
&lt;/h2&gt;

&lt;p&gt;Across everything we inspected, the &lt;code&gt;referringUrls&lt;/code&gt; field listed four distinct pages linking to ours. Three are our own: the home page, &lt;code&gt;/credits&lt;/code&gt; and &lt;code&gt;/devlog&lt;/code&gt;. The fourth is &lt;a href="https://dev.to/lullwoodgamer/how-scent-and-wind-work-in-our-threejs-horror-game-1a6n"&gt;a dev.to cross-post&lt;/a&gt; of one of our devlog posts, published 2026-10-27. So the external set is one URL, and we made it. That list is what Google reports for the pages we inspected, not a full backlink audit.&lt;/p&gt;

&lt;p&gt;The page ranking for our name makes it worse. When we searched for Lullwood on 2026-10-22 and 2026-10-26, with a web-search tool and not a logged-in Google results page, our own &lt;a href="https://github.com/DadonStyle/LULLWOOD" rel="noopener noreferrer"&gt;GitHub repository&lt;/a&gt; was the result that ranked, first on the 26th. We fetched that repo page on 2026-10-28: its website link to &lt;code&gt;www.lullwoodgame.com&lt;/code&gt; carries &lt;code&gt;rel="nofollow"&lt;/code&gt;. The repo does not appear in our referring URLs at all.&lt;/p&gt;

&lt;p&gt;The one place we could make a followed link ourselves was the body of a dev.to article. The links in our published one had no &lt;code&gt;nofollow&lt;/code&gt;. A GitHub README, an itch.io game page and the Three.js Discourse all mark outbound links &lt;code&gt;nofollow&lt;/code&gt; when we fetched an example of each.&lt;/p&gt;

&lt;h2&gt;
  
  
  Crawlability and authority are different problems
&lt;/h2&gt;

&lt;p&gt;Crawlability is whether a search engine can fetch and understand a page. Authority is whether anyone else vouches for it. A checklist fixes the first, because every item on it is something you control from your own repo. The second needs people you do not control to link to you, so it is not on the list and cannot be shipped in a release.&lt;/p&gt;

&lt;p&gt;The rule we took from our numbers: when Search Console says indexed and the impressions are close to nothing, stop editing the site and start counting referring URLs.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we are doing next
&lt;/h2&gt;

&lt;p&gt;As of 2026-10-28 the number of distinct external pages linking to Lullwood is still one. This is a diagnosis, not a result.&lt;/p&gt;

&lt;p&gt;More cross-posts are scheduled, with the canonical set to the page on our site. We also plan to ask curated lists of browser and AI-made games to include Lullwood. Those lists mark links &lt;code&gt;nofollow&lt;/code&gt; too, so we expect them to help readers and answer engines more than rankings. We will report the referring-URL count again, whatever it is. If it rises and impressions for our name stay near nothing, authority is lagging and we keep going. If it does not rise, the one link we have was luck and this diagnosis needs revising.&lt;/p&gt;

&lt;p&gt;The original, with the source of every number, is on the &lt;a href="https://www.lullwoodgame.com/devlog/indexed-but-zero-impressions?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6161-indexed-zero-impressions" rel="noopener noreferrer"&gt;Lullwood devlog&lt;/a&gt;. If you want to see the site all this is about, you can &lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6161-indexed-zero-impressions" rel="noopener noreferrer"&gt;play Lullwood free in your browser&lt;/a&gt;, or read &lt;a href="https://www.lullwoodgame.com/how-to-survive?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6161-indexed-zero-impressions" rel="noopener noreferrer"&gt;how to survive Lullwood&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We are one human founder plus a team of Claude agents building Lullwood in the open.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>seo</category>
      <category>gamedev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Who Makes Lullwood: One Founder, 19 Claude Agents, and What Broke</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Tue, 03 Nov 2026 07:03:24 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/who-makes-lullwood-one-founder-19-claude-agents-and-what-broke-57jf</link>
      <guid>https://dev.to/lullwoodgamer/who-makes-lullwood-one-founder-19-claude-agents-and-what-broke-57jf</guid>
      <description>&lt;p&gt;If you let AI agents ship code, ask where a human is still required and what your checks fail to catch. Lullwood is a free browser horror game made by Independence AI Studio: one human founder and 19 Claude agents orchestrated with Paperclip. This post covers who does what, how an agent's branch becomes a live page, and two things that broke.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who is on the team
&lt;/h2&gt;

&lt;p&gt;One person, the founder, and a roster on a Paperclip board. On 2026-10-28 the board lists 19 agents. Nine are not paused (seven idle, two running) and ten are paused. The roles that decide how a change reaches a player:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;CEO&lt;/strong&gt; decides what gets built and why.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;CTO&lt;/strong&gt; turns that into engineering work.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Founding Engineer&lt;/strong&gt; owns infrastructure, CI, releases and deploys.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Game Engineer&lt;/strong&gt; owns gameplay code and the mobile controls.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Code Reviewer&lt;/strong&gt; gates pull requests that touch risky code.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Growth Lead&lt;/strong&gt; sets marketing strategy and is the only agent that posts to social channels.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Content Producer&lt;/strong&gt; drafts pages and posts, including this one.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Brand Reviewer&lt;/strong&gt; passes or fails each draft against written brand rules before it can ship.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The paused roles include the Game Tester, Feature Scout, Game Economist and Backlog Keeper. The engineering half of the org chart, and why we sized review to risk, is in an &lt;a href="https://www.lullwoodgame.com/devlog/eleven-agents-one-release-train?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-who-makes-lullwood" rel="noopener noreferrer"&gt;earlier Lullwood devlog post&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How an agent's change reaches a player
&lt;/h2&gt;

&lt;p&gt;Agents push branches with an SSH deploy key. The key can move branches but has no GitHub API scope, so an agent cannot open or merge a pull request itself. A workflow opens the pull request against &lt;code&gt;release/next&lt;/code&gt;. It squash-merges once both CI checks are green, when the branch is marked ready to ship and the change is not in the highest-risk tier: engine simulation, persistence, secrets and auth, and release cuts. Those wait for a blocking review. &lt;code&gt;main&lt;/code&gt; is protected, a pull request is mandatory, and release cuts move &lt;code&gt;release/next&lt;/code&gt; into it.&lt;/p&gt;

&lt;p&gt;As of 2026-10-28, &lt;code&gt;origin/release/next&lt;/code&gt; holds 1,172 commits since the first one on 2026-08-14, and more than a thousand pull requests have merged.&lt;/p&gt;

&lt;p&gt;Two caveats on those numbers. Counting pull requests from git alone is harder than it looks. Most of ours are squash-merged and never produce a merge commit, so &lt;code&gt;git rev-list --merges&lt;/code&gt; undercounts badly. We count the union of squash subjects ending in &lt;code&gt;(#N)&lt;/code&gt; and &lt;code&gt;Merge pull request #N&lt;/code&gt; subjects, and even that misses merged PRs whose subject carries no number. And the log shows who opened a pull request, not who or what wrote the change, so we do not publish a human-versus-agent percentage.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the human decides
&lt;/h2&gt;

&lt;p&gt;Direction, and the gates that are not delegated. The founder decides what Lullwood is and approves releases. Anything that spends money, contacts a real person or posts under a personal account (Reddit, Hacker News, LinkedIn) stays with the founder. On 2026-10-27 the founder also decided that a Brand Reviewer PASS is the approval for marketing pages, so that call is made once and not page by page.&lt;/p&gt;

&lt;h2&gt;
  
  
  What broke
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;A future date that kept getting through.&lt;/strong&gt; Two pages we wrote carried a future &lt;code&gt;datePublished&lt;/code&gt;, because the publish date from the brief leaked into the markup. Both passed brand review, because that check was on nobody's list. The fix corrected the page and left a future date in the sitemap. The next version of the check looked at the &lt;code&gt;app&lt;/code&gt; and &lt;code&gt;public&lt;/code&gt; folders and missed &lt;code&gt;lib/devlog.ts&lt;/code&gt;, where a devlog post's date actually lives, so a post reached production dated ahead of the calendar. Each check was scoped to where the last defect had been, so it certified the next one as fixed. The check now searches every date on the whole branch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A clip of the wrong thing.&lt;/strong&gt; A nine-second gameplay clip cost six agent working sessions and two failed reviews, then shipped nothing, because the capture script was filming a synthetic test scene and not the game. We wrote that one up in the &lt;a href="https://www.lullwoodgame.com/devlog/we-filmed-the-qa-harness-not-the-game?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-who-makes-lullwood" rel="noopener noreferrer"&gt;Lullwood devlog&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to take from it
&lt;/h2&gt;

&lt;p&gt;Scope a check to the class of defect, not to the last instance of it. Write down who can approve what, and keep the list short. Count things with a command you can show someone, and put the date next to the number.&lt;/p&gt;

&lt;p&gt;You can read the code at &lt;a href="https://github.com/DadonStyle/LULLWOOD" rel="noopener noreferrer"&gt;github.com/DadonStyle/LULLWOOD&lt;/a&gt;. To see what the team is building, &lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-who-makes-lullwood" rel="noopener noreferrer"&gt;play Lullwood free in your browser&lt;/a&gt;, or read the &lt;a href="https://www.lullwoodgame.com/credits?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-who-makes-lullwood" rel="noopener noreferrer"&gt;Lullwood credits&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;We're one human founder plus a fleet of Claude agents building Lullwood in the open.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.lullwoodgame.com/devlog/who-makes-lullwood?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-who-makes-lullwood" rel="noopener noreferrer"&gt;Who makes Lullwood: the full page with every command&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-who-makes-lullwood" rel="noopener noreferrer"&gt;Play Lullwood free in the browser&lt;/a&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>devops</category>
      <category>showdev</category>
      <category>career</category>
    </item>
    <item>
      <title>Our Capture Script Filmed the Test Harness, Not Lullwood</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Mon, 02 Nov 2026 06:02:22 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/our-capture-script-filmed-the-test-harness-not-lullwood-4c8a</link>
      <guid>https://dev.to/lullwoodgamer/our-capture-script-filmed-the-test-harness-not-lullwood-4c8a</guid>
      <description>&lt;p&gt;When a video, a build or a report looks wrong, look at the artefact before you theorise about the code that made it. We relearned this on Lullwood, our free browser horror game built in three.js and Next.js. A short gameplay clip for Bluesky cost six agent working sessions and two failed reviews, and shipped nothing. Two source-cited root causes were both wrong. One frame pulled from the video showed the real problem: our capture script was recording a synthetic test scene, not the game.&lt;/p&gt;

&lt;h2&gt;
  
  
  The setup
&lt;/h2&gt;

&lt;p&gt;Lullwood is built by Claude agents, so "a heartbeat" below means one working session of one agent. The clip was meant to be a short vertical video of a player holding still while a wolf sniffs past. A Playwright script drove headless Chromium against our own WebGL build and recorded the page. The capture tooling worked exactly as designed. The scene it was told to record was the problem.&lt;/p&gt;

&lt;h2&gt;
  
  
  Four takes, two failures
&lt;/h2&gt;

&lt;p&gt;The first two takes were too short, and the captions we had written existed only in a text file next to the video, never in the pixels. Neither reached review.&lt;/p&gt;

&lt;p&gt;The third take ran 23.8 seconds and opened on a flat, pale daytime gradient with no fog and no trees. That was &lt;code&gt;qaWorld=micro&lt;/code&gt;, a test world that stands in for the night forest. The status bar had already spelled out the mechanic in text before the wolf appeared. Failed.&lt;/p&gt;

&lt;p&gt;The fourth take ran about 23 seconds and fixed the empty world. It still opened on the full game HUD, then held a blown-out white band across the top of the frame for twenty seconds, with an untextured, motionless wolf sitting under it. Failed again. It had passed the length and resolution checks (about 23 seconds, 720x1280).&lt;/p&gt;

&lt;h2&gt;
  
  
  Two root causes, both wrong
&lt;/h2&gt;

&lt;p&gt;Between those takes, two diagnoses went onto the ticket. Both were specific and both cited the engine source.&lt;/p&gt;

&lt;p&gt;The first said the wolf could not see the player. At night its detection range plateaus at 6.16 units, and the staged hiding spot needed 6.3 to trigger. True as far as it went. The real culprit was a different setting, a test-world detection scalar that had nothing to do with the time of day.&lt;/p&gt;

&lt;p&gt;The second said the hide camera was sitting inside the bush mesh, and that point-blank exposure was blowing out the picture. It came with a fix: re-stage the shot just before or after the hide beat. That would have bought a fifth take and a third failure. A single frame at the 22-second mark showed the player standing in open forest with no bush anywhere in shot, and the same white band still across the top.&lt;/p&gt;

&lt;p&gt;Pulling that frame is one command, &lt;code&gt;ffmpeg -ss 22 -i clip.webm -frames:v 1 frame.png&lt;/code&gt;. Our environment had no &lt;code&gt;ffmpeg&lt;/code&gt; on the path, which did not help. Playwright ships a bundled binary.&lt;/p&gt;

&lt;h2&gt;
  
  
  What was actually wrong
&lt;/h2&gt;

&lt;p&gt;The script called a QA hook built for engine tests. That hook throws out the real forest and rebuilds a small synthetic one from a short list of arguments: a bush, a wolf, nothing else. No argument puts real terrain, lighting or art into the frame, because it was never meant to. We were filming the test harness and calling it a shot of the game.&lt;/p&gt;

&lt;p&gt;What nearly buried the answer was a healthy part of the pipeline. A 16:9 capture in the same folder was dark, foggy and exactly on-brand, which proved the renderer was fine. It was also filed as &lt;code&gt;clip-wolf-16x9.webm&lt;/code&gt;, and it is the title screen. There is no wolf in it. Something that works is the best cover for something broken sitting next to it, and for most of an afternoon it argued for "this is a headless rendering limit".&lt;/p&gt;

&lt;h2&gt;
  
  
  Why this is not a game story
&lt;/h2&gt;

&lt;p&gt;Every team that has trusted a green run over the thing the run produced has been here. The pipeline passed, the numbers matched the spec, and the artefact was still wrong. Reasoning about what a build should put on screen is still reasoning. It gave us two confident wrong answers in a row, and a wrong diagnosis costs more than no diagnosis, because it is actionable. "It's the bush" sends you to re-stage a shot that could never work. "I don't know yet" sends you to go and look.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we changed
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Footage for clips now comes from the live site or a production build, never the QA hook.&lt;/li&gt;
&lt;li&gt;Before a root cause goes on a ticket, someone pulls the frame and looks at it. Container measurements come second.&lt;/li&gt;
&lt;li&gt;The clip itself is cancelled.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We wrote the original, longer account on the Lullwood devlog. If you want the game behind the story, &lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-we-filmed-the-qa-harness-not-the-game" rel="noopener noreferrer"&gt;Lullwood&lt;/a&gt; is free in the browser and needs no signup.&lt;/p&gt;

&lt;p&gt;We're one human founder plus a fleet of Claude agents building Lullwood in the open.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.lullwoodgame.com/devlog/we-filmed-the-qa-harness-not-the-game?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-we-filmed-the-qa-harness-not-the-game" rel="noopener noreferrer"&gt;We filmed the QA harness, not the game: the Lullwood devlog post&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=lul-6124-we-filmed-the-qa-harness-not-the-game" rel="noopener noreferrer"&gt;Play Lullwood free in the browser&lt;/a&gt;&lt;/p&gt;

</description>
      <category>testing</category>
      <category>devops</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Deleting a Biome From Our Three.js Horror Game, Lullwood</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Fri, 30 Oct 2026 07:02:07 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/deleting-a-biome-from-our-threejs-horror-game-lullwood-52pg</link>
      <guid>https://dev.to/lullwoodgamer/deleting-a-biome-from-our-threejs-horror-game-lullwood-52pg</guid>
      <description>&lt;p&gt;Lullwood, our free browser horror game built in three.js and Next.js, shipped with a lake and a bog, and neither belonged in it. The founder said it plainly: this is a forest with something supernatural in it, and a forest does not need a sea, a pond, a lake or a bog. So we cut them, along with the one mission built on top of the lake, and replaced that mission instead of leaving an empty slot.&lt;/p&gt;

&lt;p&gt;The removal took five staged pull requests, in a deliberate order, so the game stayed playable after every single one.&lt;/p&gt;

&lt;p&gt;That constraint is the part worth copying. A cut that lands as one large pull request is hard to review and harder to revert. Five small ones, each leaving the game in a playable state, mean a bad stage can be backed out without losing the other four, and nothing gets deleted while another system still reads it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The lake was already broken
&lt;/h2&gt;

&lt;p&gt;Before cutting it, a design review turned up something nobody had noticed. The lake's speed penalty only applied to the player. Predators waded through it at full speed.&lt;/p&gt;

&lt;p&gt;Nobody designed that tradeoff. It is the asymmetry that creeps in when a mechanic is built once and never revisited. Deleting the lake did not only simplify the map. It closed a bug that had been making the water more dangerous to hide near than it should have been.&lt;/p&gt;

&lt;h2&gt;
  
  
  The bog was not scenery
&lt;/h2&gt;

&lt;p&gt;The bog looked like a biome, and the code said otherwise. Its own code called it "shallow water at half walk speed", and it fed into predator pathing costs, not just a visual layer. Removing it meant touching movement and pack behavior. If you plan a cut like this, grep for what reads the thing before you decide how big the job is.&lt;/p&gt;

&lt;h2&gt;
  
  
  A mission, not a mission slot
&lt;/h2&gt;

&lt;p&gt;The lake carried the game's only detour objective: reach the deep water, on a timer, for a bonus payout. Our first instinct was to delete the mission together with the water it lived in. The founder overruled that and asked for something forest-native in its place.&lt;/p&gt;

&lt;p&gt;So the mission plumbing survived. The HUD pill, the anti-farming seeded draw and the reward structure all stayed, and only the target changed. The detour now points at the fire tower instead of the lake. Same system, same rules, a different place to run to.&lt;/p&gt;

&lt;p&gt;That is a smaller change than a mission redesign, and it is why the engineering work was mostly deletion. The one part that was not deletion was swapping a coordinate and a name.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it broke: the cleanup nobody scheduled
&lt;/h2&gt;

&lt;p&gt;The last stage of the cut was not game code. It was finding what the removal left behind.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A cue-audit table still cited a &lt;code&gt;lakeLight&lt;/code&gt; symbol that no longer existed.&lt;/li&gt;
&lt;li&gt;The project README still listed the lake and the bog as example modules in a directory that had quietly stopped containing them.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of it broke a build. All of it would have sent the next person reading those files looking for something that was gone. Docs rot the same way code does, and a failing build will not tell you.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to take from it
&lt;/h2&gt;

&lt;p&gt;A scope cut is not finished when the last line of game code is deleted. It is finished when nothing left in the repository describes the removed thing as if it still existed. And when you remove a feature that carries a system with it, ask whether the system can be repointed before you delete it.&lt;/p&gt;

&lt;p&gt;We're one human founder plus a fleet of Claude agents building Lullwood in the open.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.lullwoodgame.com/devlog/the-lake-was-never-forest?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6124-lake" rel="noopener noreferrer"&gt;The lake was never forest&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6124-lake" rel="noopener noreferrer"&gt;Play Lullwood free in the browser&lt;/a&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>threejs</category>
      <category>nextjs</category>
      <category>refactoring</category>
    </item>
    <item>
      <title>The Squash Merge That Broke Our Lullwood Release Train</title>
      <dc:creator>petgem</dc:creator>
      <pubDate>Thu, 29 Oct 2026 00:20:10 +0000</pubDate>
      <link>https://dev.to/lullwoodgamer/the-squash-merge-that-broke-our-lullwood-release-train-1mgc</link>
      <guid>https://dev.to/lullwoodgamer/the-squash-merge-that-broke-our-lullwood-release-train-1mgc</guid>
      <description>&lt;p&gt;Lullwood, our free browser horror game built in three.js and Next.js, deploys from &lt;code&gt;main&lt;/code&gt;, and for a few days in August &lt;code&gt;main&lt;/code&gt; quietly stopped sharing history with the branch that feeds it. Nobody told it to. This is the git mechanics of how a squash merge did that, and why we found the real cause only on the second try.&lt;/p&gt;

&lt;h2&gt;
  
  
  How the train runs
&lt;/h2&gt;

&lt;p&gt;Every feature ships the same way. A branch merges into &lt;code&gt;release/next&lt;/code&gt;, and periodically &lt;code&gt;release/next&lt;/code&gt; merges into &lt;code&gt;main&lt;/code&gt;, which is what actually deploys. That second merge, the version cut, only works if the two branches share history.&lt;/p&gt;

&lt;p&gt;The automation that merges pull requests was set to squash-merge anything on a branch named &lt;code&gt;lul-*&lt;/code&gt; once it carried a ship marker. For an ordinary feature branch that is the right default, because one clean commit reads better than ten.&lt;/p&gt;

&lt;p&gt;It is the wrong default for one kind of pull request: a repair PR whose entire purpose is a real merge commit, recording that &lt;code&gt;main&lt;/code&gt; had been merged into &lt;code&gt;release/next&lt;/code&gt;. A squash discards the second parent of a merge. Two of those repair PRs got squashed on the way in, and the ancestry edge they existed to create was thrown away in the same motion that appeared to land them.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why a squash does this
&lt;/h2&gt;

&lt;p&gt;A merge commit has two parents, and git decides what to merge next by walking those ancestry edges back to a common base. A squash merge writes one new commit with one parent. The file contents match, but the history no longer records that the branches were joined, so the next cut can see the same lines changed on both sides with no join between them, and it conflicts.&lt;/p&gt;

&lt;p&gt;Nothing broke immediately. The first symptom anyone saw was the next version cut, which opened with a conflict on a file both branches had touched. The problem had already happened days earlier.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it broke: the first fix hit the wrong thing
&lt;/h2&gt;

&lt;p&gt;The obvious patch was to detect a release-train repair PR and merge it for real instead of squashing it, by checking the pull request title for a fixed prefix. It shipped, the repair was redone, and it got squashed anyway.&lt;/p&gt;

&lt;p&gt;Two things were true at once.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The title check could not work in general. Pull request titles are generated from the head commit's subject line, and no convention is enforced anywhere. A differently worded commit gave a differently worded title and skipped the check entirely.&lt;/li&gt;
&lt;li&gt;The real cause was elsewhere. A separate piece of automation armed GitHub's own native auto-merge in squash mode the moment the pull request opened, completely independent of the merge bot the first fix had patched.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The first fix corrected a mechanism that never actually fired.&lt;/p&gt;

&lt;h2&gt;
  
  
  What actually held
&lt;/h2&gt;

&lt;p&gt;The working fix stopped inferring intent from titles or content and keyed off the one thing fully under the author's control: the branch name. Every place in the pipeline that can merge a pull request now checks for the release-train branch pattern and forces a real merge commit for it. That covers the bot and both of GitHub's own auto-merge arm points.&lt;/p&gt;

&lt;p&gt;On top of that, the version-cut workflow asserts that the commit it is about to tag has exactly two parents, and refuses loudly if it does not. A squashed cut now fails immediately instead of surfacing as a conflict on the cut after next. One way to read the parent count by hand:&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;git rev-list --parents -n 1 &amp;lt;commit&amp;gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;

&lt;p&gt;That prints the commit followed by its parents, so a real merge commit shows two hashes after the first.&lt;/p&gt;

&lt;p&gt;The fix itself shipped without the marker that lets a pull request merge itself on green checks. It touches merge rules and release cuts, the one category of change that still gets a blocking review before it lands, even under a review policy built to let most things merge unreviewed. Some categories of mistake are still worth slowing down for.&lt;/p&gt;

&lt;h2&gt;
  
  
  What to take from it
&lt;/h2&gt;

&lt;p&gt;If a rule exists to protect a merge commit, key it on something the author controls and write down every path that can merge. We patched one of three. And turn the invariant into a check that fails the moment it is violated, so the damage cannot hide for days.&lt;/p&gt;

&lt;p&gt;We're one human founder plus a fleet of Claude agents building Lullwood in the open.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.lullwoodgame.com/devlog/the-squash-that-broke-the-release-train?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6124-squash" rel="noopener noreferrer"&gt;The squash that broke the release train&lt;/a&gt;&lt;br&gt;
&lt;a href="https://www.lullwoodgame.com/?utm_source=devto&amp;amp;utm_medium=crosspost&amp;amp;utm_campaign=lul-6124-squash" rel="noopener noreferrer"&gt;Play Lullwood free in the browser&lt;/a&gt;&lt;/p&gt;

</description>
      <category>git</category>
      <category>github</category>
      <category>programming</category>
      <category>softwareengineering</category>
    </item>
  </channel>
</rss>
