<?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: david deng</title>
    <description>The latest articles on DEV Community by david deng (@daviddeng).</description>
    <link>https://dev.to/daviddeng</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%2F4084628%2F47cee371-455d-4c7c-b4cb-3f58518e4ee2.png</url>
      <title>DEV Community: david deng</title>
      <link>https://dev.to/daviddeng</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/daviddeng"/>
    <language>en</language>
    <item>
      <title>The hotfix with no version number: what Mortal Shell 2's November 16 patch actually fixed</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Thu, 19 Nov 2026 02:42:13 +0000</pubDate>
      <link>https://dev.to/daviddeng/the-hotfix-with-no-version-number-what-mortal-shell-2s-november-16-patch-actually-fixed-137g</link>
      <guid>https://dev.to/daviddeng/the-hotfix-with-no-version-number-what-mortal-shell-2s-november-16-patch-actually-fixed-137g</guid>
      <description>&lt;p&gt;On November 16, Mortal Shell 2 got its first patch since the Rotten Autumn hotfix (build 1.000.015, shipped October 23), and the announcement is titled, in full: "Hotfix: Nov 16, 2026". No version number appears anywhere in the body — nothing to type into an update check. SteamDB records build 26640691 for the window — corroboration, not a version. It hit PC, PS5, and Xbox the same day.&lt;/p&gt;

&lt;p&gt;Third report from my crash tracker: 56 issues — 22 fixed by patches, 13 with workarounds only, 11 pending, plus a handful acknowledged, investigating, partial, or unverified — last verified November 18. The first report was a methodology, the second read October's notes; this one reads a hotfix that refuses to identify itself.&lt;/p&gt;

&lt;h2&gt;
  
  
  How do you even confirm you're on it?
&lt;/h2&gt;

&lt;p&gt;Version-less releases break basic patch advice — update and retry — because no menu shows a number to compare. The checks are behavioral: the Mether's Pulse option is now clickable at Beacons (more below); the Rotten Autumn Halloween set dressing is gone.&lt;/p&gt;

&lt;h2&gt;
  
  
  What 37 lines actually contain
&lt;/h2&gt;

&lt;p&gt;Transcribed in full, the notes resolve to 8 sections and 37 lines. Levels &amp;amp; Dungeons dominates with 10: softlocks in Winterglass Lake and the Marty's Blade dungeon, a fall through the Ashen Cathedral floor after the Sariel fight, gates that stayed shut in the Neglected Ward. Shells &amp;amp; Combat adds 7 — Smert's kick failing to connect after transforming back from a sheep, Gragu's punch re-equipping your melee weapon mid-punch. The rest: Tarstones &amp;amp; Items 4, Bosses &amp;amp; NPCs 3, Photo Mode 3, UI &amp;amp; Localization 5, Other 3.&lt;/p&gt;

&lt;p&gt;Stability &amp;amp; Performance is exactly two lines: a performance improvement around coffin enemies and props, and one crash fix — "Fixed a crash that could occur when leaving an area while effects were still active." That sentence is the stability payload of a hotfix three weeks in the making: no error string, no signature, no hardware context. Next to the D3D12 dumps still on the forums, shipped-versus-diagnosable is the whole story.&lt;/p&gt;

&lt;h2&gt;
  
  
  Patch notes close forms, not entries
&lt;/h2&gt;

&lt;p&gt;The discipline when reconciling notes against a tracker: a patch line closes the form it names, nothing more. Entry #56, Mether's Pulse upgrades, had two forms on file. Form (a): pulse efficiency upgrades silently do nothing — one player bought the upgrade five or six times and still could not refill a large health bar with all 7 charges. Form (b): the Beacon's Mether's Pulse option can be hovered but not clicked, blocking any purchase. The November 16 line reads, verbatim: "Mether Pulse can now be selected with the mouse in the beacon menu." Same entity, same menu, same failure mode — form (b) flips to fixed. Form (a) is named nowhere in the 37 lines and stays open. The entry moves to partial, stamped "form b only". Collapse it to "fixed" and every player with dead flask upgrades concludes they are patched. They are not.&lt;/p&gt;

&lt;h2&gt;
  
  
  A hotfix can also un-fix
&lt;/h2&gt;

&lt;p&gt;The inverse belongs on the checklist too. Entry #31 is the Windows 11 launch block — "Failed to start Process… An Application Control policy has blocked this file (0x11C7)" — acknowledged since August, with a developer-recommended Smart App Control workaround. After the November 16 hotfix, one player reported the block re-appearing — a watch item, not a trend: the entry stays acknowledged, report logged, dated. Precedent: the night-mode merchant bug rode in with the October 14 stability hotfix.&lt;/p&gt;

&lt;h2&gt;
  
  
  What survived into November
&lt;/h2&gt;

&lt;p&gt;As of the November 18 verification, the open column was untouched. The full &lt;a href="https://mortalshell2.lol/fixes/crashing/?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=ms2_outreach_w47&amp;amp;utm_content=w47_devto_crash"&gt;mortal shell 2 crashing fixes&lt;/a&gt; tracker carries all 56 entries with status and build stamps. The short version:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Continue-button crash is still the headline.&lt;/strong&gt; Three independent players since late August, different hardware, same form: consistent crash on first load while continuing an existing save. The workaround that holds is a 30 FPS lock set before pressing Continue — reporter-verified, re-applied after every restart. Acknowledged in August; never named in notes since.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The night-mode Collector is still "investigating" on PC.&lt;/strong&gt; Trading during night mode makes the merchant UI vanish and locks input — a regression that arrived with the October 14 stability hotfix. The PS5 build got its fix on October 16; PC and Xbox were promised to follow.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Also open:&lt;/strong&gt; shell-unlock achievements that never pop (#47), trials that spawn no enemies (#48, reload workaround unconfirmed), the Smert invincibility from kick-spamming during Last Vow (#53), and the Ritual Grounds chest that stays locked after you clear the dungeon (#55).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;And the tracker's newest entry is itself a crash.&lt;/strong&gt; #58: after repeated weapon swaps — including applying Arbiter's Prize or swapping Tarstones — equipping a new weapon eventually crashes the game with an Unreal report. Three reporters, one Reddit thread, all on 1.000.015: an RTX 4070 and an RX 7900 XT, Windows 10 and 11. One player watched the odds climb the longer the inventory stayed open; another reproduced it on a second run with a fixed Tarstone sequence ending in the Veteran Axe. The developer collected mods, specs, shells, loadouts and screenshots — and could not reproduce it. The only workaround on file is one reporter's own finding, unverified: close and reopen the inventory before changing weapons. Every report predates November 16, so survival on this build is unconfirmed — hence pending, not a footnote.&lt;/p&gt;

&lt;h2&gt;
  
  
  The triage order stands
&lt;/h2&gt;

&lt;p&gt;The phase order still holds. Thirty-second fixes first: Frame Generation off, Ray Tracing off, NVIDIA shader cache to Unlimited, FSR to TSR, verify files. Two-minute fixes next: a DDU clean driver reinstall, deleting corrupted input saves. Five-minute fixes last: shader cache clears, a static 16/32 GB page file. Stop when the crash stops. If your crash hits when equipping weapons after a long inventory session, try the inventory-reopen workaround — and report your loadout.&lt;/p&gt;

&lt;h2&gt;
  
  
  What an unversioned hotfix teaches
&lt;/h2&gt;

&lt;p&gt;Four things generalize:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Date facts to builds, not announcements.&lt;/strong&gt; With no number to anchor, the tracker's version field stays at 1.000.015 — "update to the latest patch" is advice without a target.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Notes close forms, not entries.&lt;/strong&gt; Mether's Pulse leaving as "form b only" is the cleanest proof in the dataset.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The stability payload can be one unnamed line.&lt;/strong&gt; 37 lines, a single crash fix, no error string. Triage from notes alone and you know less than you think.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-test old workarounds after every patch, in both directions.&lt;/strong&gt; Old crashes can finally die; old fixes can quietly rot — see the Smart App Control watch item.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The next patch will presumably come with a number. The tracker will be watching.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This tracker is a fan-run project and is not affiliated with Cold Symmetry. Every status cites its source tier and build stamp on the tracker page.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>mortalshell2</category>
      <category>crashes</category>
      <category>gamedev</category>
      <category>troubleshooting</category>
    </item>
    <item>
      <title>How Tall Are The Freak Circus Characters? Every Listed Height, Ranked (and Why They're All "Unverified")</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Thu, 19 Nov 2026 00:52:52 +0000</pubDate>
      <link>https://dev.to/daviddeng/how-tall-are-the-freak-circus-characters-every-listed-height-ranked-and-why-theyre-all-5098</link>
      <guid>https://dev.to/daviddeng/how-tall-are-the-freak-circus-characters-every-listed-height-ranked-and-why-theyre-all-5098</guid>
      <description>&lt;p&gt;Search "how tall is Columbina" or any height query about The Freak Circus and you'll hit the same wall every time: a wall of confident numbers with no source anywhere behind them. I fell down this particular rabbit hole last week and came out with the full lineup, the lineage of where these numbers actually come from, and a new appreciation for wikis that label their uncertainty. Here's the complete ranking — with the honesty attached.&lt;/p&gt;

&lt;h2&gt;
  
  
  The full lineup, tallest first
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Character&lt;/th&gt;
&lt;th&gt;Listed height&lt;/th&gt;
&lt;th&gt;Status&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;The Doctor&lt;/td&gt;
&lt;td&gt;207 cm (6'9")&lt;/td&gt;
&lt;td&gt;Unverified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Pierrot&lt;/td&gt;
&lt;td&gt;198 cm (6'5")&lt;/td&gt;
&lt;td&gt;Unverified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jester&lt;/td&gt;
&lt;td&gt;192 cm (6'3")&lt;/td&gt;
&lt;td&gt;Unverified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Harlequin&lt;/td&gt;
&lt;td&gt;187 cm (6'2")&lt;/td&gt;
&lt;td&gt;Unverified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Ticket Taker&lt;/td&gt;
&lt;td&gt;183 cm (6'0")&lt;/td&gt;
&lt;td&gt;Unverified&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Columbina&lt;/td&gt;
&lt;td&gt;180 cm (5'10")&lt;/td&gt;
&lt;td&gt;Unverified&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;That's the entire cast with a listed number. Everyone else — the MC, Carol, the Boss, the Fools — has no figure at all. The MC's height is player-variable by design (customizable protagonist), and the minor cast simply has never had numbers attached.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where the numbers actually come from
&lt;/h2&gt;

&lt;p&gt;Here's the part most copy-paste listicles skip: the developer, Neko Bueno, has &lt;strong&gt;never published a developer-confirmed height for any character.&lt;/strong&gt; Not in devlogs, not in developer posts, not on the itch.io page. Every cm figure in circulation traces back to a single source — a fandom wiki snapshot — and all six numbers above come from that same snapshot. Rank them however you like, but the ranking is only as reliable as that one source. If the snapshot updates, the heights everyone quotes as gospel quietly change underneath them.&lt;/p&gt;

&lt;p&gt;That's why searches like "columbina height tfc" and "tfc characters heights" produce such a consistent wall of identical numbers with zero provenance: everyone is quoting the same snapshot, several generations downstream.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I like that the wiki says "unverified" out loud
&lt;/h2&gt;

&lt;p&gt;The community wiki that maintains the deepest character documentation does something unusual: it keeps the numbers — because they're what players search for — but stamps every single one &lt;strong&gt;Unverified&lt;/strong&gt;, right in the table, and separates them explicitly from developer-made fact. The Columbina page goes further and notes that the 180cm figure "circulates via fandom wiki" and doesn't appear in any developer post.&lt;/p&gt;

&lt;p&gt;This matters more than it sounds. Horror VN fandoms run on trivia, and trivia hardens into pseudo-canon the moment someone strips the caveat. Six months from now, "the Doctor is 207cm" will be stated as fact somewhere with the sourcing sanded off. The discipline of labeling is what keeps the community's own documentation honest — and it's the difference between a wiki you can trust for lore and one that's laundering headcanon into fact.&lt;/p&gt;

&lt;h2&gt;
  
  
  Reading the lineup as character design
&lt;/h2&gt;

&lt;p&gt;Even as unverified fandom consensus, the ladder tells you something about how the cast reads:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The &lt;strong&gt;Doctor&lt;/strong&gt; looming over everyone at a hypothetical 207cm tracks with his role — the one who tends to you after your first disorienting encounter, courtesy with something unsettling underneath.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pierrot at 198cm&lt;/strong&gt; fits the silent-observer design: he watches from shadows and doorways, and the frame makes him loom even when he's still.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Harlequin a head shorter than the Doctor&lt;/strong&gt; but still imposing at a hypothetical 187cm suits the rivalry reading — loud where Pierrot is quiet, performing where Pierrot watches.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Columbina at 180cm&lt;/strong&gt;, the deceased former partner whose memory shadows Pierrot's entire route, lands almost exactly at Harlequin's shoulder — the geometry of a love triangle, if the numbers were canon. Which, again: they are not.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  If you want the full dossiers
&lt;/h2&gt;

&lt;p&gt;The complete breakdown, with each character's profile, role, and the verified/unverified status kept honest on every number, lives in &lt;a href="https://thefreakcircus.wiki/blog/the-freak-circus-characters-heights-guide?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=tfc_outreach_w46&amp;amp;utm_content=heights" rel="noopener noreferrer"&gt;The Freak Circus characters heights guide&lt;/a&gt; — and the &lt;a href="https://thefreakcircus.wiki/characters?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=tfc_outreach_w46&amp;amp;utm_content=roster" rel="noopener noreferrer"&gt;full character roster&lt;/a&gt; covers all ten named characters with profiles that separate what's confirmed from what the fandom circulates.&lt;/p&gt;

&lt;p&gt;The game itself is free in your browser. The ticket is ornate, old-fashioned, and clearly not from any modern coffee shop. You'll go anyway. They all do.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: this piece comes from the team behind a fan-made The Freak Circus companion wiki. We're not affiliated with Neko Bueno, Garula, or itch.io. Heights are fandom-snapshot numbers labeled unverified at the source; no developer-confirmed height data exists at time of writing.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>guides</category>
      <category>discuss</category>
    </item>
    <item>
      <title>The Freak Circus, Day by Day: A Spoiler-Light Walkthrough of the Free Horror Visual Novel</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Thu, 19 Nov 2026 00:52:42 +0000</pubDate>
      <link>https://dev.to/daviddeng/the-freak-circus-day-by-day-a-spoiler-light-walkthrough-of-the-free-horror-visual-novel-4n6b</link>
      <guid>https://dev.to/daviddeng/the-freak-circus-day-by-day-a-spoiler-light-walkthrough-of-the-free-horror-visual-novel-4n6b</guid>
      <description>&lt;p&gt;The Freak Circus has been quietly climbing every horror-visual-novel search bar for weeks now, and the interesting thing is how few walkthroughs treat it the way it deserves: as a game that is &lt;em&gt;tracking you&lt;/em&gt; while you click through it. I spent time going through it day by day — what triggers what, which choices the game actually branches on, and where people lose the good ending — without dumping the endgame in your lap. This is the map I wish I'd had before my first run.&lt;/p&gt;

&lt;h2&gt;
  
  
  What The Freak Circus actually is
&lt;/h2&gt;

&lt;p&gt;It's a free gothic horror otome visual novel from solo developer Neko Bueno, playable in your browser. You play a coffee shop worker whose shift takes a turn when you find a strange ticket — ornate, old-fashioned, completely out of place next to the espresso machine. The game's pull is immediate: you feel compelled to go, and the moment you hand that ticket to the Ticket Taker at the circus gate, you get a cryptic warning about the nature of the circus.&lt;/p&gt;

&lt;p&gt;Then the introductions start, and each one is a thesis statement for the character delivering it:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Pierrot&lt;/strong&gt; watches you silently from the shadows. He was outside your workplace on Day 1 doing exactly that. No dialogue, no explanation.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Harlequin&lt;/strong&gt; performs — loud, theatrical, openly cruel, and entertaining enough that you understand why people watch his act.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Jester&lt;/strong&gt; runs the show as master of ceremonies and your guide through the circus.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The Doctor&lt;/strong&gt; tends to you after your first disorienting encounter inside.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;By the time Day 1 closes, you're not leaving. You spend the night trapped in the circus — and on Day 2 you wake up chained to a bed with your silent clown hovering apologetically nearby. That's the moment you realize the alley stranger never let you go.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 1 — the ticket, the gate, the trap
&lt;/h2&gt;

&lt;p&gt;Day 1 is deceptively linear: coffee shop, ticket discovery, arrival, cast introductions, lights out. But the branching starts immediately. Whether you investigate the mysterious ticket is a tracked decision, and the community walkthrough marks it as a verified key choice — one of the points where the game is quietly logging how curious (or cautious) you are.&lt;/p&gt;

&lt;p&gt;My advice for a first run: say yes to curiosity, but pace yourself. Day 1 plants everything — Pierrot's stillness, Harlequin's cruelty as performance, the Ticket Taker's warning — and none of it pays off until later. If you rush the introductions you'll miss the seeds.&lt;/p&gt;

&lt;h2&gt;
  
  
  Day 2 — trust becomes a mechanic
&lt;/h2&gt;

&lt;p&gt;Day 2 is where The Freak Circus stops being a tour and starts being a relationship audit. The characters you met now react to how you've treated them, and the game's community wiki has verified the pattern that matters most: &lt;strong&gt;trust thresholds, evaluated by the end of Day 2, decide whether you can reach a good ending at all.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;There is currently one fully confirmed ending in the game — the "Missing" bad ending, where your character is never found — and it triggers exactly when those trust thresholds are not met by the end of Day 2. Every other ending is still being mapped by the community, choice by choice, which is honestly part of the fun: the game is new enough that guides are being written &lt;em&gt;by&lt;/em&gt; the players &lt;em&gt;while&lt;/em&gt; they play.&lt;/p&gt;

&lt;p&gt;Two practical notes for Day 2:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Don't skip character scenes to "get to the point." The point &lt;em&gt;is&lt;/em&gt; the character scenes — that's where trust accrues.&lt;/li&gt;
&lt;li&gt;Pierrot's route hinges on something the developer has been unusually direct about: asked point-blank whether Pierrot would ever abandon the player character, the answer was "NO. There is nothing that would make Pierrot abandon MC. Never." He's not the one who walks away in any route. If your run is failing, look elsewhere.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  Day 3 — where the map goes incomplete
&lt;/h2&gt;

&lt;p&gt;Day 3 is real, it's in the walkthrough hub, and it's the least documented stretch of the game — which tells you something about how far most first runs get before they start over. I won't spoil what little is confirmed. What I'll say: the character dynamics you fed on Day 2 are the currency Day 3 spends, and the Doctor's early-introduction courtesy starts looking very different in hindsight.&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on the wiki's honesty — use it
&lt;/h2&gt;

&lt;p&gt;One thing I appreciate about the community documentation: every choice and every claim is tagged Verified or Unverified right in the guide. Even the famous character heights (the Doctor 207cm, Pierrot 198cm, and down the lineup) are labeled unverified fandom numbers — nobody has published developer-confirmed data, and the guides say so instead of laundering trivia into canon. That discipline makes the walkthroughs unusually trustworthy for a horror VN this new.&lt;/p&gt;

&lt;p&gt;If you want the complete day-by-day route — every choice, every ending, every verified branch point — the full &lt;a href="https://thefreakcircus.wiki/walkthrough?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=tfc_outreach_w46&amp;amp;utm_content=guide-hub" rel="noopener noreferrer"&gt;The Freak Circus walkthrough&lt;/a&gt; is the fastest way in, and the &lt;a href="https://thefreakcircus.wiki/walkthrough/day-1?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=tfc_outreach_w46&amp;amp;utm_content=guide-day-1" rel="noopener noreferrer"&gt;The Freak Circus Day 1 walkthrough&lt;/a&gt; covers the opening in spoiler-free and full-spoiler versions so you can control exactly how much you learn before playing.&lt;/p&gt;

&lt;p&gt;The ticket is free. The circus, as the Ticket Taker would tell you, is forever.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: this piece comes from the team behind a fan-made The Freak Circus companion wiki. We're not affiliated with Neko Bueno, Garula, or itch.io. All lore and choice details above come from the game and the wiki's own research pages, with verified/unverified status preserved as tagged.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>guides</category>
      <category>discuss</category>
    </item>
    <item>
      <title>REA on a Clean Linux Box: A 15-Minute Lab-Tested Setup Walkthrough</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Fri, 13 Nov 2026 05:57:07 +0000</pubDate>
      <link>https://dev.to/daviddeng/rea-on-a-clean-linux-box-a-15-minute-lab-tested-setup-walkthrough-19n2</link>
      <guid>https://dev.to/daviddeng/rea-on-a-clean-linux-box-a-15-minute-lab-tested-setup-walkthrough-19n2</guid>
      <description>&lt;p&gt;If an AI agent offered to dissect a binary for you, but every answer it gave came out of a black box, how much would you trust it? That discomfort is exactly the problem REA is built around. REA — the &lt;code&gt;rea-agents&lt;/code&gt; npm package — is an orchestration layer for reverse engineering: you describe a goal in your AI coding agent, REA plans the tool calls, drives the analysis engines, and returns structured results with receipts attached. Every run mints a verifiable record — a content-addressed evidence ID, the analyzed input's sha256, the exact library versions that produced the result. You're not just told the answer; you're handed the paperwork to check it.&lt;/p&gt;

&lt;p&gt;The good news is that the setup that gets you to your first receipt is genuinely short. This walkthrough is the same 15-minute run I execute in my lab before every REA release, and I re-ran it this week — 2026-11-13 — on REA 6.8.0 (shipped 2026-10-25), the current release as I write this. Every output below is quoted from that run or from my dated baseline records from October. One disclosure up front: I run an independent, lab-verified tutorial site for REA and I'm not affiliated with the REA project — that site is the one link at the very end of this article.&lt;/p&gt;

&lt;p&gt;One ground rule before touching the terminal: only analyze software you own or are licensed to inspect. In my lab that means the toolchain itself and binaries I compiled from my own source code. Nothing in this walkthrough needs a target shadier than hello world.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 1: install the agent
&lt;/h2&gt;

&lt;p&gt;REA ships as a single npm package, &lt;code&gt;rea-agents&lt;/code&gt;. You'll want Node 20 or newer, and I recommend a scratch directory so nothing pollutes your real projects:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;$ npm install rea-agents@latest
$ npx rea --version
rea@6.4.0 — Reverse engineer anything from your terminal or agent.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That's my October baseline: 6.4.0, 35 dependencies, zero vulnerabilities. This week's re-run on the same machine reports 6.8.0. One caution from my upgrade testing: 6.8.0 tightened the Node requirement to &lt;code&gt;^22.23.4 || ^24.22.1 || &amp;gt;=26.12.1&lt;/code&gt;, and my lab box runs Node 22.22.0 — so &lt;code&gt;rea doctor&lt;/code&gt; flags a &lt;code&gt;missing_dependency&lt;/code&gt; on it. The analyses themselves still run, but if your pipeline gates on doctor's health verdict, upgrade Node before you upgrade REA.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 2: run &lt;code&gt;rea doctor&lt;/code&gt; first
&lt;/h2&gt;

&lt;p&gt;Before anything else, run the built-in environment diagnosis:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ npx rea doctor
healthy: false
- node: ok (22.22.0)
- host: UNSUPPORTED — opencloudos 9.4
  remediation: "REA supports macOS 12+, Ubuntu 24.04+, Fedora 41+, Nobara 44+,
  64-bit Arch Linux, CachyOS, Omarchy, and the experimental Windows x64 Ghidra
  P0 boundary."
- hopper: missing_analysis_engine (/opt/hopper/bin/Hopper not found)
- ghidra: missing_analysis_engine (GHIDRA_INSTALL_DIR not set)
- ida-registration: not_configured
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;My lab distro isn't on the supported-host list, and doctor says exactly that — with a remediation string, not a shrug. Here's the honest part: REA still ran everything I needed it to on this unsupported host. Doctor's job isn't to stop you; it's to make sure you can never say "nobody told me." Every failing check names its cause and what would fix it. That fail-loudly-instead-of-fail-silently philosophy is the through-line of the whole tool, and it starts here.&lt;/p&gt;

&lt;p&gt;While you're in diagnostic mode, run &lt;code&gt;npx rea capabilities&lt;/code&gt; once. It lists 18 operations with declared side effects and limitations — effectively the spec of REA's evidence contract. Reading it takes five minutes and explains most of the behavior you'll hit later.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 3: wire REA into your AI agent (MCP)
&lt;/h2&gt;

&lt;p&gt;REA speaks the Model Context Protocol, and one command registers it with your agent client — with an automatic config backup and a companion skill install:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ npx rea setup -y --client hermes
appliedActions[2]: configured_hermes, installed_skill
- configure_client:hermes → config.yaml (automatic .rea.backup)
- install_skill:hermes → skills/reverse-engineer-anything
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The config it wrote, verified on disk:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight yaml"&gt;&lt;code&gt;&lt;span class="na"&gt;mcp_servers&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
  &lt;span class="na"&gt;rea&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;
    &lt;span class="na"&gt;command&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s"&gt;npx&lt;/span&gt;
    &lt;span class="na"&gt;args&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;&lt;span class="s"&gt;-y&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;rea-agents@6.4.0&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="s"&gt;mcp&lt;/span&gt;&lt;span class="p"&gt;]&lt;/span&gt;
    &lt;span class="na"&gt;enabled&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="kc"&gt;true&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;I then probed the MCP server directly with a small stdio JSON-RPC script rather than trusting the config on faith. &lt;code&gt;initialize&lt;/code&gt; returned &lt;code&gt;serverInfo: rea, version 6.4.0&lt;/code&gt;, and &lt;code&gt;tools/list&lt;/code&gt; enumerated 170 tools. On 6.8.0 this week, the same surface check reports 229 tools, 6 prompts, and a catalog digest where expected equals observed — &lt;code&gt;rea mcp doctor&lt;/code&gt; comes back &lt;code&gt;healthy: true&lt;/code&gt;, protocol level &lt;code&gt;2025-11-25&lt;/code&gt;. That last detail is worth pausing on: the tool's own surface is part of the audited evidence, so you can verify the toolbox itself, not just the analyses it performs.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 4: light up the zero-cost engine
&lt;/h2&gt;

&lt;p&gt;Full honesty about tiers here. REA's deep analysis commands — &lt;code&gt;analyze&lt;/code&gt;, &lt;code&gt;decompile&lt;/code&gt; — need a heavyweight engine underneath: Ghidra, Hopper, or IDA. Without one, they refuse to run, by design. But there's a free path that covers ELF layout work, and it's enough for your first case: the built-in &lt;code&gt;pwntools-elf&lt;/code&gt; provider.&lt;/p&gt;

&lt;p&gt;REA never installs Python or packages on its own — you point it at an interpreter that already has what the provider needs:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;$ python3 -m venv .rea-python
$ .rea-python/bin/pip install &lt;span class="nv"&gt;pwntools&lt;/span&gt;&lt;span class="o"&gt;==&lt;/span&gt;4.15.0 &lt;span class="nv"&gt;pyelftools&lt;/span&gt;&lt;span class="o"&gt;==&lt;/span&gt;0.33 &lt;span class="nv"&gt;unicorn&lt;/span&gt;&lt;span class="o"&gt;==&lt;/span&gt;2.1.2
$ &lt;span class="kd"&gt;export&lt;/span&gt; &lt;span class="nv"&gt;REA_PWNTOOLS_PYTHON&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$PWD&lt;/span&gt;/.rea-python/bin/python
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Those three version numbers aren't decorative — pin them exactly, because the evidence records will cite them to the patch digit, and a mismatch is the kind of thing you want to catch at install time, not in a report review.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 5: your first evidence-backed case
&lt;/h2&gt;

&lt;p&gt;The lawful first target is one you compile yourself. One file, one known constant:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight c"&gt;&lt;code&gt;&lt;span class="cp"&gt;#include &amp;lt;stdio.h&amp;gt;&lt;/span&gt;
&lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="nf"&gt;secret&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="n"&gt;x&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;x&lt;/span&gt;&lt;span class="o"&gt;*&lt;/span&gt;&lt;span class="mi"&gt;1337&lt;/span&gt;&lt;span class="o"&gt;+&lt;/span&gt;&lt;span class="mi"&gt;7&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;&lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="kt"&gt;int&lt;/span&gt; &lt;span class="nf"&gt;main&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="nb"&gt;printf&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="s2"&gt;"hello realearn %d\n"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="nf"&gt;secret&lt;/span&gt;&lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="mi"&gt;42&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;return&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;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Compiled with &lt;code&gt;gcc -O0 -o hello hello.c&lt;/code&gt;, it prints &lt;code&gt;hello realearn 56161&lt;/code&gt; — and 42 × 1337 + 7 = 56161 checks out, giving you a runtime ground truth before any tool touches the binary. Now ask REA for the layout:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ rea inspect-binary-layout hello
evidence_id: ev_6e479c83fba06374c38ab8f9fa3876e561d28d3515aa68473598e9f94dcb556c
  subject: hello / sha256 36cdabb6…4207352 / elf / x86_64
  provider: pwntools-elf @ pwntools 4.15.0;pyelftools 0.33;unicorn 2.1.2
  normalized_result: 31 sections, entry_point 0x400320
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Read that record as four proofs, because that's what it is:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The evidence ID is content-addressed&lt;/strong&gt; — derived from the record itself, so the ID &lt;em&gt;is&lt;/em&gt; the integrity check. Change one input byte and a different ID proves it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The subject sha256&lt;/strong&gt; pins exactly which bytes were analyzed. "I analyzed this file" becomes "I analyzed the file with this hash" — a claim anyone with the file can verify.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The provider block cites exact library versions&lt;/strong&gt; — pwntools 4.15.0, pyelftools 0.33, Unicorn 2.1.2 — so anyone reproducing your run knows precisely what to install.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The normalized result is independently checkable.&lt;/strong&gt; I cross-checked the 31-section count against manual &lt;code&gt;readelf -h&lt;/code&gt; / &lt;code&gt;readelf -s&lt;/code&gt; output on the same binary, and they agreed line by line — entry point &lt;code&gt;0x400320&lt;/code&gt;, symbols intact (my &lt;code&gt;-O0&lt;/code&gt; build isn't stripped, so &lt;code&gt;secret&lt;/code&gt; sits right there at &lt;code&gt;0x400406&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last bullet is the habit that makes agent-driven analysis trustworthy: before trusting the tool's receipts, hold your own ground truth for the same bytes.&lt;/p&gt;

&lt;p&gt;Now the part I consider the real news of this re-run. The &lt;code&gt;hello&lt;/code&gt; binary in my lab has not changed since October — same bytes, same sha256 — and this week's 6.8.0 re-run minted an evidence ID &lt;strong&gt;byte-for-byte identical&lt;/strong&gt; to the one in my October 6.8.0 baseline records: &lt;code&gt;ev_5cad21e9933f…c0cec&lt;/code&gt;, quoted in full in my dated lab records. Not "close enough." Identical. A deterministic contract you can build on.&lt;/p&gt;

&lt;p&gt;Two honest footnotes to that. First, IDs are version-scoped: in my two-version comparison runs between 6.7.0 and 6.8.0, some outputs re-minted their IDs across the upgrade even for identical inputs. The rule I've adopted: pin the tool version in every report header and compare evidence IDs only within one version. Second, don't take my word for the determinism — that's the point of the receipts. Rerun the command on your own box and diff the records.&lt;/p&gt;

&lt;p&gt;When you want a stretch goal, try two. One: run the same command on a stripped build (&lt;code&gt;gcc&lt;/code&gt; with &lt;code&gt;-s&lt;/code&gt;, or &lt;code&gt;strip hello&lt;/code&gt;) — the ELF in my lab named &lt;code&gt;hello-stripped&lt;/code&gt; still yields a clean evidence record with zero symbol names, and seeing what survives stripping is a lesson in itself. Two: scale up. I ran the CLI against my system's 4.5 MB &lt;code&gt;libcrypto.so.3&lt;/code&gt; — OpenSSL 3.0.12, Apache-2.0 licensed, which explicitly permits this kind of inspection — and got the full result: 30 sections, 11 segments, every record carrying its evidence ID. When a result is too large to return over MCP, REA refuses with &lt;code&gt;resource_constraint&lt;/code&gt; and points you at the exportable evidence bundle instead of silently truncating. A tool that refuses to lie to you by omission — that's the design working as intended.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step 6: know the two tiers
&lt;/h2&gt;

&lt;p&gt;After the win in step 5, it's important to be equally clear about the boundary. Ask REA for deep analysis with no engine installed and it fails closed:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ rea analyze ./hello
error: Analysis failed
code: provider_unavailable
candidate_ids[3]: ghidra,hopper,ida
rejections[3]: ghidra(not_configured) / hopper(executable_missing) / ida(not_configured)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;No plausible-looking guess, no silent degradation — a named refusal with per-engine diagnosis. And if you explicitly request the free provider for a deep operation, it refuses just as precisely: &lt;code&gt;capability_unavailable&lt;/code&gt;, "The requested analysis provider is unknown. Choose one of: ghidra, hopper, ida."&lt;/p&gt;

&lt;p&gt;So the honest mental model: REA is an orchestration layer, not a decompiler. The free tier covers ELF layout analysis plus the full evidence lifecycle — records, bundles, exports. When you eventually install Ghidra and set &lt;code&gt;GHIDRA_INSTALL_DIR&lt;/code&gt;, the decompiler slots in underneath REA and the evidence contract stays intact. That pairing — Ghidra as the engine, REA as the auditable agent driving it — is the configuration I'd recommend to anyone serious about agent-driven analysis.&lt;/p&gt;

&lt;h2&gt;
  
  
  Can you reproduce this?
&lt;/h2&gt;

&lt;p&gt;My box: OpenCloudOS 9.4 x86_64 (not on REA's supported-host list — see step 2), Node 22.22.0, gcc with binutils, isolated venv for the Python trio, &lt;code&gt;rea-agents&lt;/code&gt; 6.8.0 for this week's re-run and 6.4.0/6.7.0 for the baseline records. Everything quoted here came from those runs; versions and numbers will age, which is exactly why every claim in my records carries a date and a tool version. Your outputs should match structurally — same fields, same self-checkable shapes — but your evidence IDs will be your own, minted from your own records. If REA ever hands you a result you can't verify, treat that as a bug to investigate, not a workflow to accept.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where this goes next
&lt;/h2&gt;

&lt;p&gt;Once your first receipt is in hand, the natural next steps are the evidence lifecycle: export a session bundle with the MCP &lt;code&gt;export_evidence_bundle&lt;/code&gt; tool, verify it standalone with &lt;code&gt;rea evidence-export&lt;/code&gt;, and start attaching evidence IDs to your own reports the way the tool attaches them to its own outputs.&lt;/p&gt;

&lt;p&gt;The setup itself teaches the philosophy: run the doctor, read the refusal, hold your own ground truth, and never accept an answer without its paperwork. The full maintained version of this walkthrough — every step with its terminal sessions, kept current release by release — lives on the &lt;a href="https://reaguide.online/rea-setup-guide?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=reaguide_devto_202611"&gt;REA setup guide&lt;/a&gt;, the independent, non-affiliated REA tutorial site I run.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Facts, versions and numbers above come from my lab runs dated 2026-10-12 (baseline) and 2026-11-13 (6.8.0 re-run) and will age. Use every tool discussed only on software you own or are licensed to analyze.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>reverseengineering</category>
      <category>aiagents</category>
      <category>security</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>Mortal Shell 2 crash triage: what the October patch notes actually fixed</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Thu, 12 Nov 2026 05:54:38 +0000</pubDate>
      <link>https://dev.to/daviddeng/mortal-shell-2-crash-triage-what-the-october-patch-notes-actually-fixed-4fdl</link>
      <guid>https://dev.to/daviddeng/mortal-shell-2-crash-triage-what-the-october-patch-notes-actually-fixed-4fdl</guid>
      <description>&lt;p&gt;Mortal Shell 2 launched into the familiar Unreal Engine 5 launch-window chaos: shader compilation freezes, D3D12 GPU faults, a crash on the Continue button. I've kept a crash tracker since those first weeks: every entry is a verified symptom, the real error string where present, a fix, and a status tag tied to a build. As of build 1.000.015 (last verified November 6), it holds 54 issues: 22 fixed by patches, 13 with workarounds only, 10 pending, plus a few acknowledged, investigating, partial, or unverified.&lt;/p&gt;

&lt;p&gt;This is the October report: which crashes died, which survived, and what the notes teach about debugging a live game.&lt;/p&gt;

&lt;h2&gt;
  
  
  The tracker behind this post
&lt;/h2&gt;

&lt;p&gt;A word on method, because it separates this from fix-guide sprawl. Each entry carries one of six statuses — fixed, workaround, pending, acknowledged, investigating, partial — and a version stamp for where that status was last verified. Sources are tiered: developer-published patch notes first, developer Steam replies next, then community reports cross-checked across independent threads. Nothing gets marked fixed on a single forum post; workarounds are labeled reporter-verified or unconfirmed. The full &lt;a href="https://mortalshell2.lol/fixes/crashing/?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=ms2_outreach_w46&amp;amp;utm_content=w46_devto_crash"&gt;Mortal Shell 2 crashing fixes tracker&lt;/a&gt; covers all 54 entries under that same discipline.&lt;/p&gt;

&lt;h2&gt;
  
  
  What October actually fixed
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;September 24 — Hotfix 1.000.011.&lt;/strong&gt; The densest stability release of the fall: dungeons refusing to load when using Egon's Stone, players falling through elevator lifts, and trophy fixes for "Seeking the Past" and "Bring My Ova Back to Me". Ten tracker entries flipped to fixed in a single release — the biggest movement in the game's dozen tracked updates.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;October 14 — Hotfix 1.000.012.&lt;/strong&gt; Four more entries closed: Slayer Seal and Punch issues, a soft lock backing out of Mether's Breath's second warning, Genessa Clones stuck with the Obsidian Hammer, and blocked Gragu possession.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;October 16 — PS5 Hotfix 1.000.013.&lt;/strong&gt; Two named console fixes: stuttering (around death and pick-ups) and a soft lock when interacting with the collector. Announced by the developer on Reddit rather than a Steam news post — monitor Steam only and you'd have missed it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;October 23 — Rotten Autumn Hotfix 1 (build 1.000.015), notes published October 30.&lt;/strong&gt; The Rotten Autumn content update (1.000.014) landed October 20 — Photo Mode, and a dungeon pool that jumped from 36 to 51 — with the hotfix following three days later at roughly 800MB on PC. The notes arrived a week after the build. For crash triage, the money line sits in Stability &amp;amp; Performance: "Several crash fixes and stability improvements (including Zmey and dungeon crashes)" — the first patch-note line to name Zmey crashes directly — plus smoother dungeon transitions: "background checkpoint saves, less hitching and better memory handling". The same notes also fixed the Orrem elevator-floor form, the Proxima invincibility exploit (tracker entry #46 flipped to fixed), and night mode triggering inside the hub.&lt;/p&gt;

&lt;h2&gt;
  
  
  The crashes that survived October
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;The Continue-button crash is still open.&lt;/strong&gt; Three independent players have reported it since late August on different hardware: the game consistently crashes on first load while continuing an existing save. The developer acknowledged the crash cluster on August 26 — "We are aware of these crashing issues and are looking into a solution" — but this specific form hasn't been named in any notes since. Two reporter-verified workarounds: set a 30 FPS lock in settings before pressing Continue, or load a fresh save slot first, then your real one — both re-applied after every restart.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The night-mode merchant bug is the newest open wound.&lt;/strong&gt; After the October 14 hotfix, talking to The Collector during night mode can make the merchant UI vanish and lock input. The developer confirmed on October 15 the team is investigating — a regression from a stability hotfix, unresolved as of 1.000.015.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Also pending:&lt;/strong&gt; achievements that never pop (shell-unlock ones, while the unlock-all-shells achievement does trigger), trials spawning no enemies (reloading is player-reported, unconfirmed), the Smert invincibility from kick-spamming during Last Vow, the Ritual Grounds chest stuck locked, and Mether's Pulse upgrades doing nothing to flask healing.&lt;/p&gt;

&lt;h2&gt;
  
  
  The triage order that still works
&lt;/h2&gt;

&lt;p&gt;Phase 1, thirty seconds each: confirm you're on the Week 1 Update (1.000.008) or newer, verify file integrity in Steam, disable Frame Generation and Ray Tracing, set NVIDIA Shader Cache Size to Unlimited, and switch FSR to TSR. Phase 2, two minutes each: a clean GPU driver reinstall with DDU from Safe Mode, deleting corrupted input save files (the keybind-menu crash), Borderless to Fullscreen, and the preset dropped to High with a 60 FPS cap. Phase 3, five minutes each: clear shader caches, set a static page file at 16/32 GB, try the community Ultimate Engine Tweaks mod, and push textures to High for the out-of-video-memory form. Stop when the crash stops — stacking Phase 3 fixes on a Phase 1 success only pollutes your next debugging session.&lt;/p&gt;

&lt;p&gt;The do-not-do list: &lt;code&gt;-UseFixedTimeStep&lt;/code&gt; (a Unity-era flag that migrated into UE5 guides through copy-paste drift), globally disabling Control Flow Guard (a security feature, with documented stability trade-offs), and trusting any "confirmed memory leak" claim that names neither build nor error signature.&lt;/p&gt;

&lt;h2&gt;
  
  
  A quick word on Steam Deck
&lt;/h2&gt;

&lt;p&gt;Deck players get a split answer: Playable on Valve's compatibility scale, running under proton-11.0-2RC with no forced compatibility tool, at a combat-locked ~30 FPS playable without changes. The annoyance: the graphics menu is locked on Deck by default, with global illumination stuck on Low. The closest thing to a documented &lt;a href="https://mortalshell2.lol/fixes/steam-deck/?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=ms2_outreach_w46&amp;amp;utm_content=w46_devto_deck"&gt;Mortal Shell 2 Steam Deck fix&lt;/a&gt; for that lock is a launch-option bypass — add &lt;code&gt;SteamDeck=0 %command%&lt;/code&gt; to unlock the full menu, where TSR beats the default upscaler on the Deck's panel. The crash side is Proton-specific: users report D3D12 GPU crashes under Proton, plus a separate Valve-tracked AMD graphics-queue timeout whose suggested first step is a single-queue launch option. Don't reach for &lt;code&gt;-dx11&lt;/code&gt; on Linux — it trades crashes for visible rendering glitches.&lt;/p&gt;

&lt;h2&gt;
  
  
  What reading patch notes like a debugger teaches
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Notes lag builds.&lt;/strong&gt; Build 1.000.015 shipped October 23; its notes arrived October 30. Date every fact to the build, not the announcement.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Named fixes don't name forms.&lt;/strong&gt; "Including Zmey and dungeon crashes" names the target, not the symptom — keep workarounds up until a form is confirmed dead in the wild; note lines are covering claims, not confirmations.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Patches breed regressions.&lt;/strong&gt; The merchant UI bug arrived with a stability hotfix. Re-test save/load, fast travel and merchants after every patch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;High-end hardware isn't safe.&lt;/strong&gt; The tracker's most persistent crash forms draw reports from top-spec machines as often as budget ones. Minimum specs predict whether a game runs, not whether it's stable.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;This tracker is a fan-run project and is not affiliated with Cold Symmetry. Every status cites its source tier, with the build and date verified on the tracker page.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>mortalshell2</category>
      <category>crashes</category>
      <category>gamedev</category>
      <category>troubleshooting</category>
    </item>
    <item>
      <title>Should You Buy The Blood of Dawnwalker This Black Friday? A Framework From a Month of Price History</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Thu, 12 Nov 2026 03:06:27 +0000</pubDate>
      <link>https://dev.to/daviddeng/should-you-buy-the-blood-of-dawnwalker-this-black-friday-a-framework-from-a-month-of-price-history-16b7</link>
      <guid>https://dev.to/daviddeng/should-you-buy-the-blood-of-dawnwalker-this-black-friday-a-framework-from-a-month-of-price-history-16b7</guid>
      <description>&lt;p&gt;Black Friday week is here, and The Blood of Dawnwalker — Rebel Wolves' vampire RPG that sold a million copies in its first month — is in its first real sale season. Should you buy it now, wait for a deeper cut, or skip it entirely? A month of tracked price history, plus one awards night, gives us enough to build an honest framework: dated numbers, a few structural facts about how this game is sold, and no crystal ball.&lt;/p&gt;

&lt;p&gt;Context, reported November 11 at the Golden Joystick Awards 2026: the game finished 5th for Ultimate Game of the Year (Resident Evil Requiem won with 17%) and 2nd in Best Storytelling at 21%, behind Dispatch's 41% — its lead-actor nomination didn't convert either. A strong first-year showing, zero trophies. None of it changes the purchase math below; if anything, the Storytelling result confirms what reviews said all along (Metacritic ~83, OpenCritic ~84 at launch): the narrative is the hook.&lt;/p&gt;

&lt;h2&gt;
  
  
  Step one: which edition — and why the answer is awkward right now
&lt;/h2&gt;

&lt;p&gt;The game sells in two editions: Standard at $69.99 and Eclipse at $79.99. The ten-dollar gap buys digital extras only — a world artbook, the soundtrack, a comic — with zero gameplay content. For most buyers, that decision collapses to Standard.&lt;/p&gt;

&lt;p&gt;Here's the awkward part: Black Friday's first PSN wave discounted only Eclipse (20% off), while Standard sat at full price on Steam, GOG and the PlayStation Store alike. The edition most people should buy is currently the one &lt;em&gt;not&lt;/em&gt; on sale — which makes "wait for Standard to enter a wave" a better strategy right now than paying the Eclipse premium. Whether that happens is exactly what the refresh window below is for. I'm not going to predict it; nobody honestly can.&lt;/p&gt;

&lt;h2&gt;
  
  
  Three routes, and what each one is good for
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Route 1 — PSN digital.&lt;/strong&gt; Eclipse is 20% off at $63.99 / €63.99, with the first wave ending November 20 (07:59 UTC on the US listing; UK and Germany listings show 23:59 UTC the same day). Sony's broader sale runs through November 30 and refreshes once around November 16, per the sale announcement coverage. The refresh date is a published fact; whether Standard re-enters at a different cut is not something anyone can promise.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Route 2 — Physical.&lt;/strong&gt; Amazon listed the PS5 physical edition at €52.90, down 24% from €69.99, reported November 4 (per Gamekult's coverage). A disc has one structural advantage no digital deal can offer: it can be resold later. That's not a nudge to flip games — just an option key shops and PSN can't give you.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Route 3 — Key stores.&lt;/strong&gt; The tracked picture as of November 9 (per GoCDKeys, all excluding payment fees): PC keys hit €36.90 at Driffle including a coupon, against a ~€38.32 all-time low from September; on console, the PlayStation Store's own September sale (€48.99) still beats every third-party PS5 price to date, and Xbox Series X|S sits at €50.99 via Instant Gaming against a €48.45 low from K4G back in September. Two classic pitfalls before checkout: confirm whether you're buying a key or an account-format purchase (accounts are usually cheaper but are not a key), and check region restrictions — the cheap listings are rarely region-free.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Route 4, sort of — the $1 mystery crate.&lt;/strong&gt; Fanatical's mystery crate has a chance to contain a The Blood of Dawnwalker Steam key for one dollar. The odds are not published, so the honest framing is exactly that: a chance, at a one-dollar trial cost. If it lands, it's the lowest legitimate route that exists. No guarantees are printed on the box.&lt;/p&gt;

&lt;h2&gt;
  
  
  What counts as a good price (history, not prophecy)
&lt;/h2&gt;

&lt;p&gt;The tracked record says PC keys have lived in a €38–39 band since August, with the €36.90 coupon price as the new low; console deals have swung in a €48–52 band, and September's console low was set by the PlayStation Store itself, not by key shops. If you want thresholds instead of predictions: PC below ~€38 and console below ~€48 are, historically, good prices. Above them, patience has been rewarded before. That's a record of what happened — not a forecast that it will repeat on schedule.&lt;/p&gt;

&lt;p&gt;Three dated nodes frame the rest of the month, all published facts: the ~November 16 PSN refresh, November 20 (first Eclipse wave ends), and November 30 (the sale event closes). Everything between those dates is speculation, and social media already has plenty of that.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who should just buy it, and who should wait
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;If you bounced off in the first two weeks:&lt;/strong&gt; Update 1.1 (October 22) is your re-entry. The new respec item refunds the in-game days you spent on a wrong build, and the additional Story mode turns the 30-day timer down from stress generator to backdrop. Polygon called 1.1 a "game-changer"; the timer design itself found a defender in Larian's publishing director, who argued the pressure is the point. My own take on that debate lives &lt;a href="https://dev.to/daviddeng/the-blood-of-dawnwalkers-30-day-timer-design-mistake-or-the-whole-point-m24"&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you're waiting for New Game Plus:&lt;/strong&gt; there is no timetable. The studio has confirmed it's looking into it, and that's the whole answer so far — "wait for NG+" is not currently a dated strategy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If awards move you:&lt;/strong&gt; last night's results — 5th, 2nd, no trophy — tell you the narrative is the hook. The narrative is exactly what a $63.99 Eclipse download or a €36.90 PC key buys you into.&lt;/p&gt;

&lt;h2&gt;
  
  
  Over to you
&lt;/h2&gt;

&lt;p&gt;Are you buying during Black Friday, holding out for a Standard discount, or sitting this one out? And if you've already grabbed a key: key-format or account-format, and did the payment fees at checkout surprise you? Comments are open — I'm curious how the tracked lows are holding up in practice.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Further reading&lt;/strong&gt; (from our fan-made companion site):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://thebloodofdawnwalker.lol/guides/news/black-friday-savings-guide?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=tbodw_outreach_w47&amp;amp;utm_content=bf-savings"&gt;Black Friday savings guide — editions, routes, and good-price thresholds, all dated and sourced&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thebloodofdawnwalker.lol/guides/news/black-friday-price-guide?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=tbodw_outreach_w47&amp;amp;utm_content=bf-price"&gt;The price guide — every figure in this piece, with dates and sources&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thebloodofdawnwalker.lol/guides/endgame/new-game-plus?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=tbodw_outreach_w47&amp;amp;utm_content=ngplus"&gt;New Game Plus — what's confirmed, what isn't, and why "waiting" has no calendar&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Disclosure: this piece comes from the team behind a fan-made The Blood of Dawnwalker companion site. We're not affiliated with Rebel Wolves or Bandai Namco Entertainment. Prices are quoted from the tracked sources named in the text with their dates; secondary coverage is cited in text.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>rpg</category>
      <category>guides</category>
      <category>discuss</category>
    </item>
    <item>
      <title>Lethal Crescendo and the 35-Point Question: When Is a Vampirism Ultimate Actually Worth It in The Blood of Dawnwalker?</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Fri, 06 Nov 2026 13:03:03 +0000</pubDate>
      <link>https://dev.to/daviddeng/lethal-crescendo-and-the-35-point-question-when-is-a-vampirism-ultimate-actually-worth-it-in-the-27am</link>
      <guid>https://dev.to/daviddeng/lethal-crescendo-and-the-35-point-question-when-is-a-vampirism-ultimate-actually-worth-it-in-the-27am</guid>
      <description>&lt;p&gt;Every RPG has one build decision that splits the community, and in The Blood of Dawnwalker it might be the ultimates at the bottom of the Vampirism tree. Take Lethal Crescendo: the documented effect is a single line — kills raise the damage of your claw attacks. Simple, legible, very vampire. The interesting part is everything around that line.&lt;/p&gt;

&lt;h2&gt;
  
  
  What's actually documented
&lt;/h2&gt;

&lt;p&gt;Lethal Crescendo is recorded as a rank-1 ultimate in the Vampirism tree, night-locked, with community sources citing a 35-point cost for the pick — unconfirmed, and worth treating that way. The unlock note matters: ultimates sit at the bottom of the tree, so this is not an early pickup by design. You buy it after the tree has already eaten a serious chunk of your points, on a 30-day calendar where those points cost in-game days to earn.&lt;/p&gt;

&lt;p&gt;The effect itself is a snowball: kills buff subsequent claw damage. No documented duration, no documented stacking limit, no documented decay — the record is one line long, and everything beyond it is anecdote. As with the rest of this game's skill entries, the honest position is: one line is documented, the rest is community-reported.&lt;/p&gt;

&lt;h2&gt;
  
  
  The 35-point question
&lt;/h2&gt;

&lt;p&gt;If the 35-point figure is right, the real cost isn't 35 points — it's 35 points plus every day you spent earning them, late in a run where days are the scarcest resource. That's the same sunk-cost logic that made Update 1.1's respec item (the Draught of Mind Rebirth) the most welcome change in the patch: this is a game where a wrong investment isn't just suboptimal, it's calendar time you don't get back.&lt;/p&gt;

&lt;p&gt;So the decision shape is: a bottom-of-tree snowball whose payoff scales with how much clawing you do, priced at the point where a build is mostly committed. Against grouped night content where kills come fast, the snowball reads strong. Against sparse elites or boss-focused nights — remember the tree's other picks and what they're documented to do — the ramp may never get going before the fight is over.&lt;/p&gt;

&lt;h2&gt;
  
  
  The honest comparison problem
&lt;/h2&gt;

&lt;p&gt;Here's the snag nobody can currently resolve from documentation: the per-rank numbers across the Vampirism tree aren't reliably public. Without them, "is Lethal Crescendo worth it over more rank picks" can't be answered with math — only with vibes and anecdote. Which is exactly why the pages I trust print the one documented line, cite the 35 points as unconfirmed, and leave the rest blank instead of filling blanks with folklore.&lt;/p&gt;

&lt;p&gt;Update 1.1 didn't touch this — the patch's respec item lets you undo a pick, but the numbers behind the pick are still not documented anywhere developer-published. Our sourced database entry (linked below) keeps that line honest: one documented effect, one unconfirmed cost, everything else marked as it is.&lt;/p&gt;

&lt;h2&gt;
  
  
  Over to you
&lt;/h2&gt;

&lt;p&gt;Have you actually run Lethal Crescendo? Curious about the real-world version of the 35-point question: which night content made the claw snowball pop off — and where did it feel like 35 points of nothing? And if the respec potion changed your answer, that's worth hearing too.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Further reading&lt;/strong&gt; (from our fan-made companion site):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://thebloodofdawnwalker.lol/database/skills/lethal-crescendo?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=tbodw_outreach_w46&amp;amp;utm_content=lethal-crescendo-article"&gt;Lethal Crescendo — the sourced database entry, unconfirmed numbers left null&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thebloodofdawnwalker.lol/guides/builds/best-skills-meta?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=tbodw_outreach_w46&amp;amp;utm_content=best-skills-meta"&gt;Best skills &amp;amp; meta build — where the community consensus lands on the Vampirism tree&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Disclosure: this piece comes from the team behind a fan-made The Blood of Dawnwalker companion site. We're not affiliated with Rebel Wolves or Bandai Namco Entertainment. Skill details are stated as documented, with unconfirmed figures labeled as such.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>gamedesign</category>
      <category>rpg</category>
      <category>guides</category>
    </item>
    <item>
      <title>REA Evidence IDs Changed Between 6.7 and 6.8 — I Measured Exactly What Survives</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Fri, 06 Nov 2026 02:01:03 +0000</pubDate>
      <link>https://dev.to/daviddeng/rea-evidence-ids-changed-between-67-and-68-i-measured-exactly-what-survives-fcf</link>
      <guid>https://dev.to/daviddeng/rea-evidence-ids-changed-between-67-and-68-i-measured-exactly-what-survives-fcf</guid>
      <description>&lt;p&gt;If your analysis tool hands you receipts — input hashes, pinned library versions, content-addressed IDs — then a version upgrade is not just a changelog event. Every proof you attached to a report last month was minted by a specific version of the tool, and the quiet question nobody answers in release notes is: what happens to those proofs when the tool moves?&lt;/p&gt;

&lt;p&gt;So before I let REA 6.8.0 anywhere near my working notes, I re-ran the same artifacts through 6.7.0 and 6.8.0 on the same machine, same day, and compared the receipts line by line.&lt;/p&gt;

&lt;p&gt;Short version: the evidence IDs are version-scoped — same input bytes, different tool version, different ID. The read side of the contract held: a bundle exported under 6.7.0 re-exported cleanly under 6.8.0. And the fail-closed refusals — errors that name their cause instead of guessing — carried over as the best part of the design.&lt;/p&gt;

&lt;p&gt;Disclosure up front: I run an independent, non-affiliated tutorial site for REA (Reverse Engineer Anything); everything below comes from runs I executed myself on 2026-10-26, with baseline records from 2026-10-12. The single link to my site is at the end of this article. No affiliation with the REA developers, no affiliate links anywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  The contract in one command
&lt;/h2&gt;

&lt;p&gt;For context: REA is an agent-first reverse-engineering toolkit. Every analysis it runs emits an evidence record, and the record reads like a contract — every field is a promise. Here's one from my 2026-10-12 baseline (6.7-era tooling), inspecting a self-compiled &lt;code&gt;hello&lt;/code&gt; ELF:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;$ rea inspect-binary-layout hello
ok evidence_id: ev_6e479c83fba06374c38ab8f9fa3876e561d28d3515aa68473598e9f94dcb556c
  subject: hello / sha256 36cdabb6…4207352 / elf / x86_64
  provider: pwntools-elf @ pwntools 4.15.0;pyelftools 0.33;unicorn 2.1.2
  normalized_result: 31 sections, entry_point 0x400320
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Four claims, four proofs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;evidence_id&lt;/strong&gt; — content-addressed: derived from the record itself, so the ID &lt;em&gt;is&lt;/em&gt; the integrity check. Change one input byte and a different ID proves it.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;subject sha256&lt;/strong&gt; — exactly which bytes were analyzed. "I analyzed this file" becomes "I analyzed the file with this hash."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;provider + pinned versions&lt;/strong&gt; — pwntools 4.15.0, pyelftools 0.33, Unicorn 2.1.2, to the patch number. Anyone reproducing your run knows precisely what to install.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;normalized_result&lt;/strong&gt; — the finding, in a form your own binutils can check. I cross-checked that 31-section count against manual &lt;code&gt;readelf&lt;/code&gt; output on the same binary, and they agreed.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;That last point is the discipline that makes the rest of this post measurable: before trusting the tool's IDs, I had my own ground truth for the same bytes.&lt;/p&gt;

&lt;h2&gt;
  
  
  The experiment: same bytes, two versions
&lt;/h2&gt;

&lt;p&gt;The setup was deliberately boring. One Linux box (OpenCloudOS 9.4, x86_64, Node 22.22.0), two isolated installs — one pinned to 6.7.0, one to 6.8.0, separate &lt;code&gt;node_modules&lt;/code&gt; trees so nothing could leak between them — and two analysis subjects whose bytes I fixed before starting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;code&gt;hello&lt;/code&gt; — the self-compiled ELF above, sha256 &lt;code&gt;36cdabb6…4207352&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;lab08-session.har&lt;/code&gt; — a recorded web-session capture, sha256 &lt;code&gt;d2e45b8d…c88b76e&lt;/code&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Same commands into both versions. The IDs that came out:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;subject&lt;/th&gt;
&lt;th&gt;6.7.0 evidence_id&lt;/th&gt;
&lt;th&gt;6.8.0 evidence_id&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;inspect-binary-layout hello&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ev_79a48ab6902dcd75…9670b&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ev_5cad21e9933f327f…c0cec&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;code&gt;inspect-web-network-capture lab08.har&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ev_a94aa7273d27a8af…cdb9e&lt;/code&gt;&lt;/td&gt;
&lt;td&gt;&lt;code&gt;ev_d864f4a7df7c4946…ef14e&lt;/code&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Same bytes in, different IDs out, on both subjects. That is a contract change between versions — the derivation itself was touched, not just the tool surface. (I'm showing truncated IDs here; the full strings sit in my dated lab records.)&lt;/p&gt;

&lt;p&gt;Fresh artifacts minted under 6.8.0 behaved the same way. The capture inspection above returned &lt;code&gt;ev_d864f4a7df7c4946…ef14e&lt;/code&gt;, and two brand-new analysis views — &lt;code&gt;environment-manifest&lt;/code&gt; and &lt;code&gt;environment-state&lt;/code&gt;, neither of which exists in the 6.7.0 view enumeration — each minted their own IDs (&lt;code&gt;ev_a70dc817…18d396&lt;/code&gt; and &lt;code&gt;ev_37de4d01…c651ddf&lt;/code&gt;). New surface, same rule: the ID is bound to the record and the version that produced it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What survived: the read side
&lt;/h2&gt;

&lt;p&gt;Here's the part that matters more than the ID churn: backward compatibility on the verification path.&lt;/p&gt;

&lt;p&gt;A bundle my lab had exported under 6.7.0 — &lt;code&gt;hello-bundle-670.json&lt;/code&gt; — went through 6.8.0's &lt;code&gt;rea evidence-export&lt;/code&gt; without complaint: validation passed, records: 1, 39,142 bytes. Contrast that with the 6.4→6.7 transition in my records, where the exporter refused older material with &lt;code&gt;evidence_integrity_mismatch&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;So the current behavior splits cleanly into two rules:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Mint is version-scoped.&lt;/strong&gt; New evidence IDs differ per version, even for identical input bytes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Read is compatible.&lt;/strong&gt; Existing bundles stay verifiable across this particular upgrade.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The practical meaning: your old archives remain checkable, but your new claims are only comparable within one version. If a colleague's evidence_id doesn't match yours for the same artifact, check tool versions before you suspect corruption — that mismatch is exactly what my two-version table looks like.&lt;/p&gt;

&lt;h2&gt;
  
  
  Fail-closed carried over — and that's the feature
&lt;/h2&gt;

&lt;p&gt;A contract is only worth something if it refuses to sign bad paper. The refusals I hit on 6.8.0, all by running the tool, all with named causes:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Summary delivery requires evidence.&lt;/strong&gt; &lt;code&gt;rea function hello main --detail summary&lt;/code&gt; is rejected at the schema level unless you also pass &lt;code&gt;--evidence_output&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;invalid_request / issues[0]: path evidence_output, invalid_value
"Summary delivery requires --evidence_output so complete source
 Evidence remains available."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Spelling trap worth flagging: the hyphenated &lt;code&gt;--evidence-output&lt;/code&gt; is an &lt;em&gt;Unknown flag&lt;/em&gt;; the underscore form is the real one. With the flag correctly supplied and no deep-analysis engine installed, the call then fails with &lt;code&gt;provider_unavailable&lt;/code&gt; — a plain refusal, no silent degradation to a weaker answer.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. JSONL wants collections.&lt;/strong&gt; Asking &lt;code&gt;inspect-binary-layout&lt;/code&gt; for &lt;code&gt;--format jsonl&lt;/code&gt; doesn't emit a mangled partial record; it emits one structured error envelope:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;{"$rea":"jsonl/v1","type":"error","ok":false,
 "result":{"code":"unreadable_output",
 "reason":"JSON Lines requires an array or one explicit rows, items,
 records, or occurrences collection."}}
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;…plus a remediation line: use &lt;code&gt;--format json&lt;/code&gt; for the complete document, or select one record collection with &lt;code&gt;--filter-output&lt;/code&gt;. Even the error path wears the same envelope as success paths — machine-parseable all the way down.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Raw records are not bundles.&lt;/strong&gt; Feeding a single evidence record straight into &lt;code&gt;evidence-export&lt;/code&gt; gets rejected with &lt;code&gt;wrong-kind&lt;/code&gt; and a pointer to the right path: export a session bundle with the MCP &lt;code&gt;export_evidence_bundle&lt;/code&gt; tool first. The CLI and MCP channels have different jobs, and the tool refuses to let you blur them.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Ceiling configs fail loudly.&lt;/strong&gt; Setting &lt;code&gt;REA_MCP_MAX_RESPONSE_BYTES=1&lt;/code&gt; refuses at startup: "REA configuration is invalid: REA_MCP_MAX_RESPONSE_BYTES: Too small: expected number to be &amp;gt;=10485760." The default is 10 MiB and it's a &lt;em&gt;floor&lt;/em&gt;, not a target — 20 MiB validates fine. Its sibling &lt;code&gt;REA_BRIDGE_MAX_REQUEST_BYTES&lt;/code&gt; defaults to 16 MiB with a valid range of 7,464 to 536,870,887 bytes, and an invalid value surfaces as a named runtime-configuration check in &lt;code&gt;rea mcp doctor&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;That last command deserves its own spotlight: on 6.8.0, &lt;code&gt;rea mcp doctor&lt;/code&gt; reported healthy with tools 229/229 expected-and-observed, prompts 6/6, and a catalog digest where expected equals observed (&lt;code&gt;fe938a7c…&lt;/code&gt;). You can verify the tool surface itself, not just the analyses — the protocol level (2025-11-25) is part of the audited surface too.&lt;/p&gt;

&lt;h2&gt;
  
  
  Context: what 6.8.0 actually added
&lt;/h2&gt;

&lt;p&gt;Quick orientation, because the contract narrative shouldn't hide the release. rea-agents 6.8.0 shipped on 2026-10-25 (GitHub tag 08:36 UTC, npm 09:07 UTC). Tool count went 207 → 229 (+22), and the CLI command catalog moved 170 → 175 across the same span in my doctor diffs.&lt;/p&gt;

&lt;p&gt;The big one for agent builders: the environment toolchain — &lt;code&gt;environment-serve&lt;/code&gt;, &lt;code&gt;environment-export&lt;/code&gt;, &lt;code&gt;environment-build&lt;/code&gt;, &lt;code&gt;environment-compare&lt;/code&gt; — now ships in the npm package. I served a recorded web session as a local MCP endpoint over streamable HTTP and the replay was exact: calling &lt;code&gt;get_users&lt;/code&gt; returned the recorded 200 response body with &lt;code&gt;replay.exact_match: true&lt;/code&gt;; calling &lt;code&gt;get_users_by_id&lt;/code&gt; with id 99 faithfully replayed the &lt;em&gt;recorded 404&lt;/em&gt;. When I poked the endpoint with a malformed agentenv call, it answered &lt;code&gt;-32600 invalid request&lt;/code&gt; — fail-closed even at the transport layer. &lt;code&gt;environment-export&lt;/code&gt; produced a runnable directory (README, env.toml, Dockerfile, manifest, evidence bundle, verification scripts, smoke task), and &lt;code&gt;environment-build&lt;/code&gt; did the same job in one step from the capture file.&lt;/p&gt;

&lt;p&gt;One upgrade blocker to know first: the Node engines requirement moved to &lt;code&gt;^22.23.4 || ^24.22.1 || &amp;gt;=26.12.1&lt;/code&gt;. My box runs Node 22.22, so &lt;code&gt;rea doctor&lt;/code&gt; flags &lt;code&gt;missing_dependency&lt;/code&gt; — the analyses themselves ran fine, but if your pipeline gates on doctor health, upgrade Node before you upgrade REA.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means for your evidence hygiene
&lt;/h2&gt;

&lt;p&gt;Three rules I'm adopting in my own lab after this run:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Treat evidence_id as version-scoped.&lt;/strong&gt; Never compare IDs across REA versions and call the mismatch corruption. Compare subject sha256 and normalized_result instead — those stayed stable across my two-version run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Pin the tool version in every bundle you hand off.&lt;/strong&gt; The provider block already records exact library versions; the REA version itself belongs in your report header, next to the date.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Re-baseline after upgrades.&lt;/strong&gt; An upgrade is a contract event. One re-run of your standing artifacts, diff the old IDs against the new, note the replacements — twenty minutes of work that keeps every future claim comparable.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you build checker scripts on top of evidence bundles: verify the envelope framing constants first, compare normalized results against your own tools (&lt;code&gt;readelf&lt;/code&gt; agreed with every section count in my runs), and only then look at IDs — within a single version.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verdict
&lt;/h2&gt;

&lt;p&gt;The evidence contract is the reason I put up with re-baselining. A tool that mints proof per version and still verifies yesterday's bundles is behaving exactly like a versioned artifact store should: mint scoped, read compatible, refuse loudly. Most analysis tools show you an answer. This one shows you an answer plus receipts — and after watching receipts survive an upgrade with their verification path intact, I trust them more, not less.&lt;/p&gt;

&lt;p&gt;The full walkthrough — every refusal quoted verbatim, the two-version ID table, and the bundle re-export log — lives on the &lt;a href="https://reaguide.online/rea-evidence-contract?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=reaguide_outreach_w45"&gt;evidence contract&lt;/a&gt; page of reaguide.online, the independent, non-affiliated REA tutorial site I run.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Facts, versions and numbers above come from lab runs dated 2026-10-26 (REA 6.8.0 baseline) and 2026-10-12 (6.7-era records). They will age.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>reverseengineering</category>
      <category>aiagents</category>
      <category>security</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>I Made an AI Birthday Song for My Dad's 70th — Here's What Happened</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Fri, 06 Nov 2026 00:52:40 +0000</pubDate>
      <link>https://dev.to/daviddeng/i-made-an-ai-birthday-song-for-my-dads-70th-heres-what-happened-4lm</link>
      <guid>https://dev.to/daviddeng/i-made-an-ai-birthday-song-for-my-dads-70th-heres-what-happened-4lm</guid>
      <description>&lt;p&gt;Last month my dad turned 70. In our family that's not just a birthday, it's an event — and I'm the one who usually handles the "something special" part. The obvious move was a slideshow. I couldn't do another slideshow.&lt;/p&gt;

&lt;p&gt;Then my daughter asked me to "make grandpa a song with his name in it" — kids sing the name in Happy Birthday anyway, that's the whole fun of it. I had been building a small side project exactly for this: a tool that turns a name into a birthday song. So I typed in his name, picked a style, and let it run.&lt;/p&gt;

&lt;p&gt;What came back was about a minute long: an original composition, built around the lyrics "Happy birthday dear grandpa..." with his name sung right in the chorus. Was it a professional recording? No. Was it his kind of song? Honestly, yes.&lt;/p&gt;

&lt;p&gt;At the party I played it off my phone. Three things happened:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;The moment of recognition.&lt;/strong&gt; He caught his name in the chorus, turned to me, and asked "how did you do that?" Being asked "how did you do that?" by a 70-year-old is worth more than any gift receipt.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The kids replayed it.&lt;/strong&gt; They had it on repeat like it was a single he released. I have never seen them replay a gift before.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;He shared the link himself.&lt;/strong&gt; He sent it to my uncle with his own hands — that's the real success metric for a birthday gift: the recipient forwards it.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two small things I'd do differently: I'd bring a small speaker instead of relying on phone volume at a restaurant (about one minute long — long enough to feel real, short enough to play twice — but phones are quiet). And I'd preview the lyrics first and hand-write them into the card, because the kids treated the lyrics as the second gift.&lt;/p&gt;

&lt;p&gt;About the tool: it's called &lt;a href="https://happybirthdaysongwith.name/name/abigail?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=hbswn_outreach_w45" rel="noopener noreferrer"&gt;Happy Birthday Song With Name&lt;/a&gt; — every name gets its own page with a sample and a lyrics preview (that link shows Abigail's). I typed my dad's name into the same generator, picked a style, and got the song. Hear a 40-second preview free (sharing the link is free too; the full MP3 is a $4.99 one-time or with Pro). Every song is an original AI-composed composition, created fresh from a name and a style. No account needed just to listen.&lt;/p&gt;

&lt;p&gt;Curious how it treats a different name? The &lt;a href="https://happybirthdaysongwith.name/name/ella?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=hbswn_outreach_w45" rel="noopener noreferrer"&gt;ella birthday song&lt;/a&gt; page shows the same setup on another name — sample audio and lyrics preview included.&lt;/p&gt;

&lt;p&gt;He turns 71 next year. I already know what I'm making — and honestly, he's already asking what style he gets to pick.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: this is my own side project — I built it.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>ai</category>
      <category>music</category>
      <category>webdev</category>
      <category>discuss</category>
    </item>
    <item>
      <title>I Built a Little Tool That Turns Any Name Into a Birthday Song</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Fri, 30 Oct 2026 05:54:19 +0000</pubDate>
      <link>https://dev.to/daviddeng/i-built-a-little-tool-that-turns-any-name-into-a-birthday-song-3mg1</link>
      <guid>https://dev.to/daviddeng/i-built-a-little-tool-that-turns-any-name-into-a-birthday-song-3mg1</guid>
      <description>&lt;p&gt;My friend's birthday was coming up, and I kept running into the same problem: every "personalized birthday song" option out there was either a card with a stock melody, or a service where you fill out a form, wait three days, and pay before you even hear anything.&lt;/p&gt;

&lt;p&gt;So I built the thing I actually wanted: &lt;a href="https://happybirthdaysongwith.name/?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=hbswn_outreach_w44" rel="noopener noreferrer"&gt;Happy Birthday Song With Name&lt;/a&gt; — type in a name, pick a music style, and get a birthday song that sings that name in the lyrics, in a few seconds.&lt;/p&gt;

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

&lt;ul&gt;
&lt;li&gt;You enter the birthday person's name (any name — the more unusual, the more fun)&lt;/li&gt;
&lt;li&gt;Pick a style: pop, acoustic, and a few others&lt;/li&gt;
&lt;li&gt;The song gets generated from scratch — melody, vocals, and lyrics are all synthesized, nothing sampled from existing recordings&lt;/li&gt;
&lt;li&gt;Listen to the full result free, share it as a link&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For example, &lt;a href="https://happybirthdaysongwith.name/name/henry?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=hbswn_outreach_w44" rel="noopener noreferrer"&gt;here's what it generates for "Henry"&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  How it works, briefly
&lt;/h2&gt;

&lt;p&gt;The pipeline has three parts: a lyrics generator that fits the name naturally into the verses, a text-to-singing model for the vocals, and an instrumental generator matched to the chosen style. The tricky part is prosody — making a 4-syllable name land on the melody without sounding like a robot reading a phone book. Short names sing naturally; long ones forced some creative syllable splitting.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;The whole flow works without an account: type a name, listen, share. Downloads are optional and paid, mostly because bandwidth and generation credits are not free on my side.&lt;/p&gt;

&lt;p&gt;If you test it with a weird name, I'd genuinely like to hear how it handled the pronunciation — that's the next thing I'm trying to improve.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>javascript</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>The Blood of Dawnwalker Update 1.1, Explained: Respec, the New Difficulty Lineup, and What 1,100+ Fixes Actually Changed</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Wed, 28 Oct 2026 13:39:06 +0000</pubDate>
      <link>https://dev.to/daviddeng/the-blood-of-dawnwalker-update-11-explained-respec-the-new-difficulty-lineup-and-what-1100-3d6f</link>
      <guid>https://dev.to/daviddeng/the-blood-of-dawnwalker-update-11-explained-respec-the-new-difficulty-lineup-and-what-1100-3d6f</guid>
      <description>&lt;p&gt;Six weeks after launch, The Blood of Dawnwalker just got its first big post-release patch, and it goes directly at the two most common complaints since launch: "I built my character wrong and can't undo it" and "the difficulty curve turns the timer into pure stress." Update 1.1 went live on October 22, 2026 on PC, PS5 and Xbox Series X|S — SteamDB logs it as a major update on build 25915545 — and the developer's changelog closes with a striking line: over 1,100 other improvements and fixes, alongside the headliners.&lt;/p&gt;

&lt;p&gt;Here's what actually changed, who it's for, and one thing it deliberately doesn't do.&lt;/p&gt;

&lt;h2&gt;
  
  
  The headliner: you can finally rebuild your character
&lt;/h2&gt;

&lt;p&gt;The Draught of Mind Rebirth is the respec item this RPG has needed since day one. In the changelog's own wording, it makes you "forget all your Swordmastery, Witchcraft, and Vampirism abilities, and use the time you spent learning them to master a different set of abilities."&lt;/p&gt;

&lt;p&gt;That time-refund clause matters more here than in most RPGs, because The Blood of Dawnwalker charges in-game days for learning abilities. On a 30-day calendar, a bad build wasn't just annoying — every point you'd sunk into the wrong tree was days of your life you could never get back. The respec doesn't just rearrange points; it hands back the clock. That's an unusually elegant piece of systems design: the fix respects the very resource the whole game is built on.&lt;/p&gt;

&lt;p&gt;What the changelog still doesn't say: what the Draught costs, where you get it, whether it's single-use or repeatable, or whether Ultimate Perk lockouts reset with it. None of that is public yet, so I'm not going to guess — and honestly, the fact that a fan wiki's 1.1 coverage leaves those fields blank instead of filling them with folklore is a good way to tell which guides to trust this week.&lt;/p&gt;

&lt;h2&gt;
  
  
  Difficulty: five tiers, and a real easy mode
&lt;/h2&gt;

&lt;p&gt;The other big swing is the difficulty rework. Story — the previous easiest tier — is renamed Forgiving, and a brand-new Story mode with additional combat assist takes its place at the bottom. The post-patch lineup reads: Story / Forgiving / Fair / Challenging / Duelist.&lt;/p&gt;

&lt;p&gt;Context: back on September 21, the game director told Eurogamer a first big patch was planned for early October, describing exactly this kind of five-tier rework plus combat changes. Early October came and went. On October 16, Update 1.1 was announced for "next week" with a difficulty rework, targeting and disengagement improvements — items that line up with the September plan nearly point for point — and it shipped on the 22nd. So 1.1 isn't a surprise content drop; it's the patch the studio had been telegraphing for a month, finally dated.&lt;/p&gt;

&lt;p&gt;The combat side is quieter but real: improved targeting, locking on, and disengaging from enemies, plus camera animation adjustments and traversal improvements — per the notes, Shadowstep and Planeshift targeting and surface-attaching respond better. Smaller quality-of-life items rode along: a merchant buyback tab, rebalanced late-game item upgrade costs, controller deadzone settings, and gear that can now sit in both your day and night presets at once.&lt;/p&gt;

&lt;h2&gt;
  
  
  About that "1,100+" number
&lt;/h2&gt;

&lt;p&gt;It's real, but read it correctly. "Over 1,100 other improvements and fixes" is the changelog's own closing line — quoted verbatim by Push Square, Eurogamer and GameRant — and no per-category breakdown has been published. So the honest framing is: the patch is enormous, the marquee items are the ones above, and the long tail is undocumented publicly beyond the notes themselves.&lt;/p&gt;

&lt;p&gt;The notes do flag at least one known open issue: on AMD's RX 9070 XT, switching FrameGen off and back on mid-session can crash the game. Until that's patched, the safe move is to leave FrameGen where you set it. And if you're waiting for New Game Plus: 1.1 doesn't include it. The studio has said publicly it's looking into it, with no timetable — the same answer as at launch.&lt;/p&gt;

&lt;h2&gt;
  
  
  If you bounced off in the first two weeks, this patch is your re-entry
&lt;/h2&gt;

&lt;p&gt;A lot of players who dropped the game early did so for one of two reasons: a build that felt wrong with no way back, or a difficulty curve that turned the 30-day timer into a stress generator. Update 1.1 addresses both levers — you can now rebuild toward the community meta (Swordmastery passives as the backbone, Witchcraft hexes for the day phase, Vampirism sustain and control for the night) without the sunk-cost penalty, and the new Story mode gives stressed players a pressure valve that didn't exist before.&lt;/p&gt;

&lt;p&gt;What the patch doesn't change is the calendar itself. Quests still age out, the world still moves on, and day 30 still lands whether you're ready or not. That design debate — mistake or the whole point — is exactly what &lt;a href="https://dev.to/daviddeng/the-blood-of-dawnwalkers-30-day-timer-design-mistake-or-the-whole-point-m24"&gt;my previous piece&lt;/a&gt; dug into, and 1.1 reads like the studio's answer: we're keeping the clock, but we'll make it easier to live with.&lt;/p&gt;

&lt;h2&gt;
  
  
  Over to you
&lt;/h2&gt;

&lt;p&gt;Did Update 1.1 pull you back in — or are you still holding out for New Game Plus? And if you've used the Draught of Mind Rebirth: what did you rebuild into, and did the time refund work the way the changelog describes? Comments are open — I'm curious whether the respec economy holds up in practice, since nobody outside the studio knows the item's cost yet.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Further reading&lt;/strong&gt; (from our fan-made companion site):&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://thebloodofdawnwalker.lol/guides/news/update-1-1-announcement?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=tbodw_outreach_w45&amp;amp;utm_content=update-11-patchnotes"&gt;The Blood of Dawnwalker Update 1.1 — the full shipped changelog, dated and sourced&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://thebloodofdawnwalker.lol/guides/builds/best-skills-meta?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=tbodw_outreach_w45&amp;amp;utm_content=update-11-patchnotes"&gt;Best skills &amp;amp; meta build — the community consensus to respec toward, with unsourced numbers left null&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;em&gt;Disclosure: this piece comes from the team behind a fan-made The Blood of Dawnwalker companion site. We're not affiliated with Rebel Wolves or Bandai Namco Entertainment. Patch details are quoted as published in the developer's changelog; secondary coverage is cited in text.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>gamedev</category>
      <category>gamedesign</category>
      <category>rpg</category>
      <category>guides</category>
    </item>
    <item>
      <title>REA vs Ghidra: I Ran Both in a Lab for a Week - Here's the Honest Comparison</title>
      <dc:creator>david deng</dc:creator>
      <pubDate>Fri, 23 Oct 2026 04:31:26 +0000</pubDate>
      <link>https://dev.to/daviddeng/rea-vs-ghidra-i-ran-both-in-a-lab-for-a-week-heres-the-honest-comparison-1jf5</link>
      <guid>https://dev.to/daviddeng/rea-vs-ghidra-i-ran-both-in-a-lab-for-a-week-heres-the-honest-comparison-1jf5</guid>
      <description>&lt;p&gt;&lt;em&gt;Disclosure: I run &lt;a href="https://reaguide.online/?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=reaguide_outreach_w43"&gt;reaguide.online&lt;/a&gt;, an independent, lab-verified tutorial site for REA. It is not affiliated with the REA project (morluto) or the Ghidra project. Every REA-side claim below comes from runs I executed myself on 2026-10-12 in my own lab; Ghidra-side facts come from its developer-published documentation, cited inline.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Every "REA vs Ghidra" take I've seen so far is written by people who already live in disassembly view. I'm not here to relitigate that. Two weeks ago I knew neither tool, so I ran both from zero on a clean Linux box — same machine, same day, one week of actual use. This is the comparison I wish I'd found: &lt;strong&gt;two dimensions that matter — the evidence each tool gives you, and what its analysis output can actually resolve&lt;/strong&gt; — plus the honest install experience.&lt;/p&gt;

&lt;p&gt;If you want the full beginner-oriented version with checklists, the companion page is &lt;a href="https://reaguide.online/ghidra-vs-rea-for-beginners?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=reaguide_outreach_w43"&gt;Ghidra vs REA for beginners&lt;/a&gt;. What follows is the condensed, evidence-first version.&lt;/p&gt;

&lt;h2&gt;
  
  
  The one-paragraph setup
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Ghidra&lt;/strong&gt; is a free, open-source reverse-engineering suite: disassembler, decompiler, interactive GUI, scripting, headless analyzer. Originally developed by the NSA, released as open source in 2019. &lt;em&gt;[Source: Ghidra project documentation]&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;REA&lt;/strong&gt; (the &lt;code&gt;rea-agents&lt;/code&gt; npm package, MIT) is &lt;em&gt;not&lt;/em&gt; a rival on the same layer. It's an agent orchestration layer: you describe a goal in your AI coding agent, REA plans the tool calls, runs analysis engines — including Ghidra itself — and returns structured, citable results over MCP. Installed in one &lt;code&gt;npm install rea-agents&lt;/code&gt;, no engine required for first use.&lt;/p&gt;

&lt;p&gt;That layer difference resolves half the "vs" before it starts. The interesting question is what each one hands you when you ask it a question.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dimension 1: the evidence trail (the sharpest difference)
&lt;/h2&gt;

&lt;p&gt;This is about trust, not power.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;REA stamps every result.&lt;/strong&gt; In my lab runs, each output carried a content-addressed &lt;code&gt;evidence_id&lt;/code&gt;, the analyzed input's sha256, and the exact provider + library versions. On a 4.5 MB system library (&lt;code&gt;libcrypto.so.3&lt;/code&gt;, OpenSSL 3.0.12 — Apache-2.0 explicitly permits decompilation for research), the CLI returned the full result: 30 sections, 11 segments, each record verifiable. When a result is too large to return over MCP, REA &lt;strong&gt;refuses&lt;/strong&gt; with &lt;code&gt;resource_constraint&lt;/code&gt; and points you at an exportable evidence bundle — it never silently truncates.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ghidra reports what its analyzers find&lt;/strong&gt; in its own UI and exports. There is no built-in, cross-run, content-addressed audit artifact of the kind REA emits — and that's not a defect. Ghidra was built as an analyst's workbench, where the analyst &lt;em&gt;is&lt;/em&gt; the chain of custody. But if your output has to convince someone else — a report, a ticket, a reproducible claim — REA's trail does that out of the box.&lt;/p&gt;

&lt;p&gt;One concrete moment sold me on the design: with &lt;strong&gt;no engine installed&lt;/strong&gt;, REA's &lt;code&gt;analyze&lt;/code&gt; command fails closed — &lt;code&gt;provider_unavailable&lt;/code&gt;, plus a per-engine diagnosis (&lt;code&gt;ghidra: not_configured / hopper: executable_missing / ida: not_configured&lt;/code&gt;). It refuses to guess rather than fabricating a plausible-looking answer. Anyone who has watched an LLM hallucinate a function name from a mangled decompilation knows why that matters.&lt;/p&gt;

&lt;h2&gt;
  
  
  Dimension 2: what the analysis output actually resolves
&lt;/h2&gt;

&lt;p&gt;I ran the same minimal target through both: a tiny &lt;code&gt;hello.c&lt;/code&gt; I compiled myself (the lawful first target — you own it, you can analyze it).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Reading the binary by hand (Ghidra's home turf):&lt;/strong&gt; the classic loop is &lt;code&gt;file&lt;/code&gt; → &lt;code&gt;readelf -h&lt;/code&gt; → &lt;code&gt;readelf -s&lt;/code&gt; → &lt;code&gt;objdump -d&lt;/code&gt;, and the payoff is real. The symbol table shows a function named &lt;code&gt;secret&lt;/code&gt;; the disassembly shows &lt;code&gt;imul eax, eax, 0x539&lt;/code&gt; then &lt;code&gt;add eax, 0x7&lt;/code&gt;. You infer &lt;code&gt;secret(x) = x·1337 + 7&lt;/code&gt;, run the binary to confirm (42 → 56161), and you've closed the loop: hypothesis, evidence, verification. Ghidra's decompiler window industrializes exactly this reading skill — that's its superpower, and it's the vocabulary every RE course assumes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Asking an agent (REA's home turf):&lt;/strong&gt; same binary, one natural-language request — "inspect this ELF's layout" — and REA returns the section table, entry point &lt;code&gt;0x400320&lt;/code&gt;, and an evidence ID whose sha256 I recomputed afterward to confirm it matched the input. The result agreed with the manual &lt;code&gt;readelf&lt;/code&gt; numbers line by line. The workflow you learn is different: phrasing goals, reading evidence records, auditing what the agent claims.&lt;/p&gt;

&lt;p&gt;Honest limits, from the same runs: REA's free built-in engine (&lt;code&gt;pwntools-elf&lt;/code&gt;) covers ELF &lt;em&gt;layout&lt;/em&gt; only. Ask it to decompile with no engine installed and it refuses — by design. Point it at a Ghidra install (&lt;code&gt;GHIDRA_INSTALL_DIR&lt;/code&gt;) and the decompiler comes along with the evidence contract intact. &lt;strong&gt;The strongest configuration is both&lt;/strong&gt;: Ghidra as the engine, REA as the auditable agent driving it.&lt;/p&gt;

&lt;h2&gt;
  
  
  The install experience, day one
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;REA&lt;/strong&gt;: &lt;code&gt;npm install rea-agents&lt;/code&gt;, then &lt;code&gt;rea doctor&lt;/code&gt;. Install finished clean, zero vulnerabilities; &lt;code&gt;doctor&lt;/code&gt; printed a plain-language checklist — including flagging that my distro wasn't on the supported-host list, before I wasted an hour. Working CLI in minutes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Ghidra&lt;/strong&gt;: download the release archive, install a supported JDK, extract, launch the GUI. &lt;em&gt;[Source: Ghidra installation guide]&lt;/em&gt; None of it is hard, but there are more steps, and the first GUI session assumes you already know what you're looking at.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For a complete beginner the sequencing that worked for me: &lt;strong&gt;REA first&lt;/strong&gt; for momentum and the evidence-first habit, &lt;strong&gt;Ghidra second&lt;/strong&gt; when you want to read disassembly yourself.&lt;/p&gt;

&lt;h2&gt;
  
  
  Verdict
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Need your conclusions to be &lt;strong&gt;auditable by someone else&lt;/strong&gt; → REA's evidence trail is the differentiator.&lt;/li&gt;
&lt;li&gt;Want to &lt;strong&gt;learn classic RE&lt;/strong&gt; and read decompiled code by hand → Ghidra, full stop.&lt;/li&gt;
&lt;li&gt;Doing serious agent-driven analysis → both, wired together.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Neither is "better." They're on different layers — and the search results that told me otherwise cost me a weekend.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Facts, versions and numbers above reflect lab runs on 2026-10-12 and will age. Full setup walkthrough with terminal sessions: &lt;a href="https://reaguide.online/rea-setup-guide?utm_source=dev.to&amp;amp;utm_medium=article&amp;amp;utm_campaign=reaguide_outreach_w43"&gt;realearn setup guide&lt;/a&gt;. Use every tool discussed only on software you have the right to analyze.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>reverseengineering</category>
      <category>aiagents</category>
      <category>security</category>
      <category>tutorial</category>
    </item>
  </channel>
</rss>
