About Pyrehead

What this site is

Pyrehead is a fan-run site about Pyrestorm, an MMORPG still in development. The two names are different things and worth keeping apart: Pyrestorm is the game, Pyrehead is this site about it.

It is unofficial. We are not affiliated with the people making Pyrestorm, we do not speak for them, and nothing here should be read as an announcement. What we have is what they have shown in public, turned into something you can read, search and link to.

Watch the developer's Twitch channel →

How we work

Developer streams are where Pyrestorm actually gets explained, and a stream is close to the worst possible place to keep information: hours long, unsearchable, and gone the day the recording expires. Everything below exists to move what was said out of the video and into something that survives it.

• One stream, one write-up

  An article starts from a single developer stream and names it: which broadcast, which date, who was streaming. It is not assembled from other people's summaries.

• Every claim to a timestamp

  The recording is transcribed in full and the claims in it are checked against what has already been said elsewhere. Key moments are listed with the timestamp they happened at, so you can go and hear it yourself instead of taking our word for it.

• Findings outlive the video

  What a stream adds to the sum of what is known is filed as its own sourced entry in the knowledge base. Those entries still resolve after Twitch has deleted the recording behind them — which, eventually, it always does.

How sure we are

Not everything said on a stream is a promise, and pretending otherwise is how fan sites end up quoted as sources for features that never existed. Findings carry one of three labels:

Confirmed

Said outright by the developers, on stream, on the record.

Rumored

Heard second-hand, inferred from what was shown, or said as a maybe. Treat it as a maybe.

Outdated

True when it was said and superseded since. Kept visible rather than deleted, so the change itself stays on the record.

When sources disagree

Where something said on stream is contradicted by another source, the article says so on the spot: a “suspected inaccuracy” note sits inline with the claim and opens to show both sides. We would rather show you the disagreement than quietly pick a winner and present it as settled.

What is automated, and what is not

Transcription, the first pass over the claims and the first draft of the text are machine work — nobody is going to hand-transcribe hours of stream a week for a fan site, and pretending we do would be its own small lie. What is not automated is publication: nothing appears here until it is published by hand, and the sourcing rules above apply to the result either way. Where something could not be verified, it gets labelled rather than smoothed over.

Corrections

If something here is wrong, we want to know — a site whose whole argument is “check the timestamp” has no business being precious about being corrected.

Bring the article and, if you have it, the moment on stream that contradicts us; that is usually enough to settle it in one message.

Ask in the community Discord →

Corrections are made in the article rather than in a footnote nobody reads, and an edited article carries a visible updated date. Claims that turn out to have been superseded are marked outdated rather than deleted.

Follow new write-ups by RSS →

Who writes here

Articles here are written and published by LongBeam — whose name is on the byline of every one of them. There is no anonymous editorial “we” behind that: it is one person, and the mistakes are theirs.

• steamcommunity.com

Privacy

Short version: the site asks you for nothing.

• No accounts. There is nothing to sign up for and no login for readers — reader registration is switched off, not merely unbuilt.
• No forms, no email. We collect no addresses and send no mail; the site has no mail sending configured at all. Everything that would be a contact form happens on Discord instead.
• Traffic measurement via Cloudflare Zaraz. Aggregate analytics are handled by our host, configured in the Cloudflare dashboard rather than by a tracking tag written into these pages.
• Third parties are their own thing. Links out to Discord, Twitch and Reddit hand you over to services with their own policies, which are worth reading and are not ours to summarise.