<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Networking on Reviving Fury</title>
    <link>https://jamerlybob.github.io/fury-devlog/tags/networking/</link>
    <description>Recent content in Networking on Reviving Fury</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Sep 2026 10:00:00 +1200</lastBuildDate>
    <atom:link href="https://jamerlybob.github.io/fury-devlog/tags/networking/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>21. The Client Won&#39;t Talk, So I Opened It Up</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-client-wont-talk-so-i-opened-it-up/</link>
      <pubDate>Wed, 09 Sep 2026 10:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-client-wont-talk-so-i-opened-it-up/</guid>
      <description>The client stopped narrating what it was doing, so the trick that got me through the last four posts was dead. I had to stop watching the game and start reading the machine code underneath it. First disassembler of the project.</description>
    </item>
    <item>
      <title>20. The Client Believes Me</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-clients-first-step-onto-the-map/</link>
      <pubDate>Tue, 08 Sep 2026 23:15:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-clients-first-step-onto-the-map/</guid>
      <description>The server says WELCOME. The client, which has spent this whole project stuck on a transition screen, reads it, packs up, and tries to load the actual arena map. Then it asks to join the match.</description>
    </item>
    <item>
      <title>19. The Handshake Answers Back</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-handshake-answers-back/</link>
      <pubDate>Tue, 08 Sep 2026 21:30:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-handshake-answers-back/</guid>
      <description>Last post my server could hear the client say HELLO. This post it says something back, and the client, which has been shouting into a dead socket for eighteen years, answers with three messages I didn&amp;rsquo;t have to ask for.</description>
    </item>
    <item>
      <title>18. The First Word Heard</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-first-word-heard/</link>
      <pubDate>Tue, 08 Sep 2026 20:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-first-word-heard/</guid>
      <description>I started actually writing the server. It&amp;rsquo;s about a hundred lines so far and it does exactly one thing: it hears the client say HELLO and understands it. But that&amp;rsquo;s the first time anything I&amp;rsquo;ve written has been on the other end of that conversation.</description>
    </item>
    <item>
      <title>17. The Pawn Before the Player</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-pawn-before-the-player/</link>
      <pubDate>Tue, 08 Sep 2026 18:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-pawn-before-the-player/</guid>
      <description>I traced the shortest path through Fury&amp;rsquo;s own code from &amp;lsquo;a player connected&amp;rsquo; to &amp;lsquo;a character exists and can move&amp;rsquo;. The character turns out to exist first.</description>
    </item>
    <item>
      <title>16. The Client&#39;s First Word</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-clients-first-word/</link>
      <pubDate>Tue, 08 Sep 2026 17:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-clients-first-word/</guid>
      <description>I pointed a 16-year-old game client at a server that doesn&amp;rsquo;t exist and listened. It said hello in plain English.</description>
    </item>
    <item>
      <title>15. The Server Nobody Kept</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-server-nobody-kept/</link>
      <pubDate>Tue, 08 Sep 2026 16:30:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-server-nobody-kept/</guid>
      <description>I went looking for an existing Unreal Engine 3 server I could build on top of. Every one I found cheats in a way I can&amp;rsquo;t.</description>
    </item>
    <item>
      <title>14. Time to Build the Server</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/opening-phase-3/</link>
      <pubDate>Tue, 08 Sep 2026 14:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/opening-phase-3/</guid>
      <description>Phase 2 is done. I&amp;rsquo;ve read the whole game. Now comes the part where I have to build the thing that&amp;rsquo;s actually missing.</description>
    </item>
    <item>
      <title>6. Can the Client Host Its Own Game?</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/can-the-client-host-a-game/</link>
      <pubDate>Tue, 08 Sep 2026 06:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/can-the-client-host-a-game/</guid>
      <description>The shortcut was: get the game to quietly host a match for itself, no server needed. I tried it. The door is welded shut, same as the last three.</description>
    </item>
    <item>
      <title>5. What Does the Game Say First?</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/what-the-client-says-first/</link>
      <pubDate>Mon, 07 Sep 2026 15:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/what-the-client-says-first/</guid>
      <description>I point the dead game&amp;rsquo;s login at a tiny program I wrote, just to eavesdrop on the very first thing it tries to say to a server that isn&amp;rsquo;t there anymore.</description>
    </item>
  </channel>
</rss>
