Why is the fortune teller on fire, or already dead, when I reach her?

Steps

1. Check your build before you change anything else. Every fix for this shipped between 17 and 19 August 2026. A copy that has not taken an update since launch day is the single most likely cause.
2. Find her early. The game’s own introduction places her on the hill above Pichess, who stands in the town square — that is the elevated position off the market square, not a building on the outskirts.
3. Talk to her before you go wandering. Her reading is a real dialogue branch with its own page on this site, and a dead NPC does not give it to you.
4. If she is already dead when you arrive, loot her. The one recording of this happening takes her book off the body, and no guard reacts.
5. If she is alive but on fire, nothing in any recording here shows a player successfully putting her out. The one attempt fails.

What NerveLabs patched, and when

Three separate changelog entries in three days touch this. They are the developer’s own words, not a creator’s account, which is why this page exists at all:

Hotfix 1, 17 August 2026 — the launch-day patch — lists, between a bread rebalance and a laptop GPU fix: “Chialani no longer self immolates by accident.” That is a named NPC in a named patch, and it is the strongest single line of evidence on this page.

Hotfix 4, 18 August 2026, widens it from one NPC to all of them: “NPCs should no longer get stuck on their beds after they sleep. Also shouldn’t self immolate.” The same patch also tones down the Brandbearer fire effects. A second fix a day later means the first one did not fully hold.

Hotfix 5, 19 August 2026, attacks the environment instead of the NPC: “Collision on bonfires smaller.” The same list contains “NPC persistence”, “NPC appearances fixed / made consistent”, and — separately — “A certain quest NPC is no longer mercy killed by vicious frogs.” That last line is not this bug and this page does not treat it as one, but it establishes that more than one quest NPC was dying on its own in launch week.

Update 6, 20 August 2026, adds a fourth angle: “NPCs in the wilderness much less likely to get attacked by enemies.” Again a different failure mode, listed here only so you can tell the two apart — one is fire and one is monsters.

The one recording that caught it

Tomato’s session, uploaded 20 August 2026, opens by going straight for her. The player explains why on camera before he moves:

“Where’s that fortune teller? There’s a reason I want to go find them quick. It’s because apparently they are spawned directly next to a fire that kills them. And it’s a hotfix that’s coming out, but I don’t know if it’s out yet. I have to go find them and try to save them because I already know that they’re dead if I don’t find them fast.”

He does not make it. He shouts “are you in here? Fortune teller—”, the audio turns to screaming, and he shouts “YOUR ROBE’S ON FIRE” twice. Then: “I guess I’ll take their book.”

Two things make that clip worth citing rather than filing away. The player independently describes the same mechanism the changelog describes — spawned next to a fire — without having the changelog’s wording in front of him. And he says out loud that he does not know whether the fix is live on his build, which is a more honest statement of his own version than most recordings give you.

Where she is, in the game’s own words

The introduction lists the townspeople worth knowing, and four unrelated channels transcribe that narration in the same words across three days. Two of them are cited here; the seer’s own page on this site lists all four:

“Pichess stands in the town square, selling anything he can get his hands on. On the hill above him lives [the seer], a fortune teller of sorts, but one with true sight and not after your coins.”

Two of those captions carry a name in that slot and two drop it. Because all four render the rest identically, this is scripted narration rather than one creator’s summary, and it is the only source in this repository that says where she lives in the game’s own voice.

This is also the sentence that ties the two words together. Players searching for “fortune teller” and players searching for “the seer” are looking for the same NPC, and the game says so itself.

Her name, and why this page still prints Chi’Alani

There are now three written forms of this name and none of them is on-screen game text.

This site prints Chi’Alani, taken from a creator writing it out in a video description. Two machine captions render it Chilani. NerveLabs, in Hotfix 1, write it Chialani.

The developer’s spelling is the most authoritative source that has appeared so far, and on its own it would settle the question. It does not, quite, because the same changelog drops apostrophes elsewhere — the Update 7 list contains “Rolds claymore” for a weapon the game calls Rold’s, while spelling Magdal’s Rest and Bok’s poker correctly in the same paragraph. A document that is inconsistent about apostrophes cannot rule one out.

So this page reports all three forms and changes nothing. What the changelog does establish, beyond argument, is that the name is roughly this and that the NPC it names is the one that was catching fire.

Requirements / limits

• The recording’s upload date, 20 August 2026, is three days after the first fix. Upload date is not recording date, and the player says on camera that he does not know which build he is on. This page therefore does not claim the bug was still live after Hotfix 1 — only that someone recorded it.
• Nothing here establishes that Tomato’s fortune teller and the Chialani of Hotfix 1 are the same NPC by any direct statement. The chain is: the changelog names one NPC self-immolating; the intro narration calls the seer a fortune teller; the player goes looking for the fortune teller and finds her burning. That is strong and it is still an inference.
• No recording in this repository shows the bug on a build known to be current. If you are on Update 7 and she still burns, that is new information and this site would want to hear about it.
• Nothing establishes what her death blocks. She answers a main dialogue question and she is a step in Moon In The Man; no recording here shows either after she is dead.
• Hotfix 5’s “NPC persistence” line is quoted as written. The changelog does not say what it changed, and this page does not guess whether it makes deaths survive a reload.

Common mistakes

• Reloading an old save to fix it. Every fix here is in the game build, not the save file. Update first.
• Assuming you did it. Nobody attacks her. The developer’s own word for it is “by accident”.
• Confusing this with the NPC killed by frogs. Hotfix 5 lists that separately, and it is a different NPC and a different cause.
• Walking past her because she is uphill. The intro tells you she is there, once, in a list of five names, and most players are still reading the interface at that point.
• Treating her death as cosmetic. She holds one of the answers the main quest is built around.

Still unverified

• Is the bug still reachable on a current build?Not verifiedThree patches address it between 17 and 19 August 2026. No recording here is confirmed to have been made after all three.
• Is her name Chialani, Chi’Alani or Chilani?Single unconfirmed reportThe developer writes Chialani, a creator writes Chi’Alani, two captions render Chilani. No source in this repository shows the name as on-screen game text.
• Does her death block Moon In The Man?Not verifiedShe sends the player on to the hermit Detta in that quest. No recording here attempts the quest after she has died.
• Can you put her out?Not verifiedOne player tries to reach her in time and fails. No recording shows an extinguishing attempt.
• Does she stay dead across a reload?Not verifiedHotfix 5 lists “NPC persistence” without saying what it does.
• Which quest NPC did the vicious frogs kill?Not verifiedHotfix 5 says “a certain quest NPC” and does not name it. No recording here catches it.