What is the Guildrun release date?
Full release is planned for 2027. The free Steam demo launched July 16, 2026. No frozen day-month full-release stamp is reprinted here as fact.
Guildrun Updates
Guildrun update hub: July 16 2026 demo launch, weekly patch rhythm, planned 2027 release with progress carry-over — follow Steam news and Discord.
Guildrun updates — demo timeline, weekly patches, and release-date framing.
Guildrun update and release date hub
This Guildrun update hub tracks demo freshness for Guildrun by Leyline (Steam AppID 3669200): launch milestones, weekly patch rhythm, how to read changelogs, and the planned Guildrun release date for full launch.
Draft heroes on a hex grid, auto-battle through PvE runs, and craft relic-driven builds in a ~20-minute roguelike.
If you searched Guildrun update, Guildrun release date, or Guildrun patch, start here — then open the live sources. This page does not invent patch version numbers, balance coefficients, or fake “hotfixed today” claims.
Short answer: free demo live since July 16, 2026; full release planned 2027 with demo progress intended to carry over. Exact week-to-week balance lives in Steam news and Discord — not in a frozen wiki changelog dump. Last wiki framing pass: July 20, 2026. Always prefer Steam news and Discord over any static summary.
Guildrun release timeline
Anchor dates below are the public demo / release plan players ask about when searching Guildrun release date. Soft dates stay labeled as planned.
| Milestone | Date | What it means | Certainty |
|---|---|---|---|
| Demo launch | July 16, 2026 | Free Steam demo live (AppID 3669200) | Confirmed |
| Weekly patches | Ongoing (demo period) | Balance, fixes, and content drops | Confirmed cadence |
| Full release | Planned 2027 | Paid / full product after demo | Planned — Soft/TBA on store |
| Progress carry-over | Toward full release | Demo progress planned to transfer | Planned — confirm per patch FAQ |
Demo is the live product today
Until full launch, the free demo is the complete public playable build. Guides on this wiki — beginner, builds, endless, Red Rift — describe demo systems verified around July 20, 2026. Do not wait for 2027 to learn the loop.
Why “2027” not a calendar day
Official communications frame full release as 2027 without a frozen day-month stamp we can reprint as fact. Treat any third-party “ships in Month X” claim as rumor until Steam or Leyline posts it.
Store page still wins
Release date widgets, demo badges, and FAQ text on the Steam store page override older blog mirrors. Bookmark that page and the official Discord announce channel.
Weekly patch rhythm during the demo
During the demo period, Leyline communicates a weekly patch cadence. That rhythm is the heartbeat of every Guildrun update search — and it can slip around holidays or major content drops.
| Cadence signal | Player habit | Wiki habit |
|---|---|---|
| Weekly demo patches | Expect balance + bugfix churn | Re-check builds / tier notes after big swings |
| Steam news posts | Primary written changelog | Link out — do not mirror full notes |
| Discord announce | Fast alerts + clarifications | Cross-check before rewriting guides |
| In-client tooltips | Final truth for numbers | Refuse invented tables |
What “weekly” does and does not promise
Weekly cadence means players should expect frequent iteration — not that every calendar week ships the same size of content. Some weeks are tiny fixes; some rewrite relic math. Size is not something this hub invents.
Where to watch first
Order of truth: (1) Steam news for AppID 3669200, (2) official Discord announcements, (3) in-game patch popup / tooltips, (4) community summary threads. Skip random social reposts that invent version numbers.
Systems most likely to move
Hero ranks, specialization nodes, relic tags, item buy timing, difficulty modifiers, Endless scoring UI, and Red Rift mission text all sit in the weekly blast radius. After a big patch, re-open tier list and builds with fresh eyes.
What this hub will never list
Exact patch IDs, invented “hotfix hour” clocks, or unofficial DPS sheets copied from undated screenshots. Those rot within a week and poison search results. If a number is not in Steam news, Discord announce, or the live client, it does not belong here.
How to read a Guildrun changelog
Changelogs are denser than they look. Use a fixed reading order so a Guildrun update does not bury the change that breaks your board.
| Read order | Look for | Then do |
|---|---|---|
| 1. Headline / intent | “Balance”, “fix”, “content”, “economy” | Decide if your main guide pages need a pass |
| 2. Relics / items | Tag changes, cost, triggers | Re-test your two primary relic axes |
| 3. Heroes / specs | Rank passives, node swaps | Check whether your carry still executes intent |
| 4. Modes | Difficulty, Endless, Red Rift text | Re-verify unlock / scoring / mission notes |
| 5. Known issues | Temporary bugs / Mandates | Avoid building around a buggy exploit |
Do not screenshot one patch forever
A day-one Endless score board can die after two weekly patches. Archive your own notes with the patch date you played — not an undated “meta forever” image.
Translate notes into one sentence
After reading, write: “This patch wants X to be weaker / Y to be stronger / Z to be clearer.” If you cannot write that sentence, you skimmed too fast. Then decide whether difficulty or endless advice still holds.
Community summaries are secondary
Discord players help, but they paraphrase. When a summary conflicts with Steam news, the Steam post wins. Use community chat to learn practical feel, not to invent missing numbers.
Demo progress carry-over plan
Leyline communications state that demo progress is planned to carry over into the full 2027 release. That promise is directional, not a line-item inventory.
| Progress type | Player expectation | Wiki stance |
|---|---|---|
| Difficulty clears | Usually persist on profile | Planned carry-over — confirm FAQ |
| Unlock discoveries | Heroes / systems found in demo | Likely profile-side — verify later |
| Endless best depth | May reset if scoring seasons change | Confirm after scoring patches |
| Red Rift marks | Challenge flags / cosmetics | TBD per reward type |
| Local save quirks | Mid-run saves are run tools | Not the same as profile carry-over |
Play the demo without fear of waste
Learning hex placement, shop freeze, and relic literacy transfers as skill even if a cosmetic flag changes later. Time in the demo is not wasted practice.
What to track yourself
Highest difficulty cleared · Endless personal best · favorite hero/spec pairs · Red Rift missions completed. Keep notes until official trackers exist — then reconcile against the Steam FAQ nearer to launch.
Watch the FAQ near full launch
As 2027 approaches, expect a clearer Steam FAQ entry on what migrates. This hub stays a pointer — the live Steam FAQ remains authoritative.
After each Guildrun update — player checklist
Use this short loop whenever a weekly Guildrun update lands.
- Do01Open Steam news for AppID 3669200 and skim the full post
- Do02Check Discord announce for clarifications or hot follow-ups
- Do03Note whether relics, heroes/specs, or modes moved
- Do04Re-test one standard clear before trusting old Endless / Red Rift muscle memory
- Do05Update personal build notes with the patch date
- Do06Ignore third-party posts that invent version numbers or fake reward tables
FAQ
How often are Guildrun updates?
During the demo period, Leyline communicates a weekly patch cadence. Individual weeks vary in size — read Steam news for each drop.
Where do I find Guildrun patch notes?
Primary: Steam news on the Guildrun store page (AppID 3669200). Secondary: official Discord announcements. In-client tooltips remain the final number source.
Will demo progress carry over to the full game?
Yes — progress is planned to carry over into the full release. Exact transfer details can still be clarified nearer to launch; confirm the Steam FAQ when posted.
Who develops Guildrun?
Leyline — the team behind the Steam PvE hex auto-battler (AppID 3669200).
Why does this page avoid listing patch version numbers?
To prevent stale or invented IDs. This hub explains cadence and reading habits; live Steam / Discord posts own the exact changelog text.
Related pages
Matched by build plan, shared topics, and guide progression — not random related links.