Demo
Guildrun Steam Beta Branch Guide
Leyline told Steam FAQ readers that a beta branch on the demo Steam page will incorporate community feedback alongside weekly patches running since January 2026 alpha. This guide explains how Steam beta branches work for Guildrun, when to opt in, and how to report issues without corrupting your main demo save.
Last updated: August 2026
What the Steam Beta Branch Is
Steam lets developers ship alternate builds under the same demo listing through a beta branch (sometimes labeled beta, experimental, or preview in the Betas tab). Leyline uses this channel to test balance changes, UI tweaks, and co-op groundwork before promoting patches to the default demo branch.
Opting in means your Steam client downloads beta build files instead of the stable default. Opting out returns you to the standard demo branch. Both remain free — no codes required.
How to Opt In on Steam
Open your Steam library and select Guildrun Demo. Right-click or use the gear icon → Properties → Betas. Choose the beta branch Leyline lists — name may vary by patch (read the dropdown description). Steam will download the beta build; first launch may take longer while files sync.
If no beta appears, Leyline may have closed the branch between experiments. Check Steam news, Discord at discord.gg/guildrun (also reachable via discord.gg/ezKdXVS8C9), and our weekly updates page for announcements when a new beta opens.
- Step 1: Library → Guildrun Demo → Properties
- Step 2: Betas tab → select Leyline branch
- Step 3: Wait for Steam download to finish
- Step 4: Launch and verify build version in menus or news post
- Step 5: Opt out to "None" to return to stable demo
Beta vs Default Demo
Beta branches may include unreleased relic tuning, work-in-progress co-op menus, or UI experiments not documented on this wiki yet. Expect bugs — that is the point. Stable default demo is better for leaderboard attempts and tutorial learning via the beginner guide.
Profile progression and planned progress carryover may still apply on the same Steam account, but mid-run saves from beta might not load on stable or vice versa if build versions diverge sharply. Finish runs or avoid cross-branch save reliance during experiments.
Giving Feedback That Helps Leyline
Structured feedback beats vague praise or rage. Note difficulty tier, relic names, hero archetypes, encounter type, and steps to reproduce bugs. Post to Discord #bug-report or equivalent channels after reading rules, and mirror critical issues on Steam discussions so other players can confirm.
Balance opinions should explain why a relic or modifier feels overtuned in PvE context — not just "nerf pls." Leyline's designers include Hearthstone and The Bazaar veterans who respond to trigger-frequency arguments similar to our build guide framework.
Wiki Policy on Beta Content
We document verified stable demo mechanics first. Beta-only heroes, relics, or co-op prototypes appear here only after Leyline confirms them in Steam news or promotes them to default branch. Follow Steam FAQ for official answers that supersede beta leaks.
When beta changes promote to default, we update English guides first then localized pages in the same revision cycle — matching policy on the weekly updates page.
Frequently Asked Questions
Is the beta branch mandatory?
No. Default demo branch is fine for most players. Beta is optional for early testers comfortable with bugs.
Can I lose progress in beta?
Mid-run saves may break across branch switches. Profile unlocks on your Steam account generally persist, but verify after major beta experiments.
Does beta include co-op?
Only if Leyline enables it in that branch. Co-op is in development — watch patch notes rather than assuming every beta ships it.
How do I leave beta?
Properties → Betas → select "None" or default branch. Steam redeploys the stable demo build.
Where does Leyline announce beta openings?
Steam news, Discord, and sometimes the playguildrun.com site linked from press materials.