<?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>Decompiler on Reviving Fury</title>
    <link>https://jamerlybob.github.io/fury-devlog/tags/decompiler/</link>
    <description>Recent content in Decompiler on Reviving Fury</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 08 Sep 2026 07:30:00 +1200</lastBuildDate>
    <atom:link href="https://jamerlybob.github.io/fury-devlog/tags/decompiler/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>9. The Decompiler Reads the Whole Game Now</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/the-decompiler-reads-the-whole-game/</link>
      <pubDate>Tue, 08 Sep 2026 07:30:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/the-decompiler-reads-the-whole-game/</guid>
      <description>Last time eight of ten test functions came back readable. Then I pointed the tool at the one class that actually matters and it fell over on 111 functions out of 150. This is the fix, and the moment the whole codebase finally dumped to disk.</description>
    </item>
    <item>
      <title>8. Teaching a Decompiler to Read Fury</title>
      <link>https://jamerlybob.github.io/fury-devlog/posts/teaching-the-decompiler-fury/</link>
      <pubDate>Tue, 08 Sep 2026 07:00:00 +1200</pubDate>
      <guid>https://jamerlybob.github.io/fury-devlog/posts/teaching-the-decompiler-fury/</guid>
      <description>The tool that turns Fury&amp;rsquo;s compiled code back into something readable crashes on the first file. A day later it is reconstructing real Fury functions, and I know the one specific thing still standing between me and the rest.</description>
    </item>
  </channel>
</rss>
