What changed
0 fixes1 addition5 changes0 removals
changedI've set up a public beta branch for GuitarSesh where I'll stage builds for testing before they go live for everyone.
addedHow it worksThe beta branch always runs either the same build as the default version or a newer one that's being tested. Opting in is low-commitment — you can switch back to the default version anytime. When beta is ahead, you're previewing the next build before it goes live; when it matches, there's nothing new staged yet. Check the changelog to see whether beta is currently ahead of the default version.
changedSeeing what's in a buildEach build ships with its own version number. Once you're on the main menu, look at the top-right corner and click Changelog — it lists each build's version and what changed, newest at the top.
changedHow I'll post updatesI don't plan to post a Steam announcement for every build. For day-to-day changes on both the beta and default branches, the in-game Changelog is the source of truth — I'll keep it updated there. I'll save Steam announcements for the bigger stuff worth surfacing.
changedA note on save dataRight now the beta branch shares your save data with the normal version — your progress carries over both ways. Backward compatibility is always the goal, so a beta build's data changes are meant to work cleanly with the normal version. Verifying that migrations behave as expected is exactly what the beta stage is for — so if a build touches the database or save format, testing it here is how I confirm it's safe before it reaches everyone.
changedHow to opt inRight-click GuitarSesh in your library → Properties → Betas → select beta from the version list (no password needed). To return to the normal version, select Default Public Version .
GuitarSesh changes
changedI've set up a public beta branch for GuitarSesh where I'll stage builds for testing before they go live for everyone.
addedThe beta branch always runs either the same build as the default version or a newer one that's being tested. Opting in is low-commitment — you can switch back to the default version anytime. When beta is ahead, you're previewing the next build before it goes live; when it matches, there's nothing new staged yet. Check the changelog to see whether beta is currently ahead of the default version.
changedEach build ships with its own version number. Once you're on the main menu, look at the top-right corner and click Changelog — it lists each build's version and what changed, newest at the top.
changedI don't plan to post a Steam announcement for every build. For day-to-day changes on both the beta and default branches, the in-game Changelog is the source of truth — I'll keep it updated there. I'll save Steam announcements for the bigger stuff worth surfacing.
changedRight now the beta branch shares your save data with the normal version — your progress carries over both ways. Backward compatibility is always the goal, so a beta build's data changes are meant to work cleanly with the normal version. Verifying that migrations behave as expected is exactly what the beta stage is for — so if a build touches the database or save format, testing it here is how I confirm it's safe before it reaches everyone.
I've set up a public beta branch for GuitarSesh where I'll stage builds for testing before they go live for everyone.
How it works
The beta branch always runs either the same build as the default version or a newer one that's being tested. Opting in is low-commitment — you can switch back to the default version anytime. When beta is ahead, you're previewing the next build before it goes live; when it matches, there's nothing new staged yet. Check the changelog to see whether beta is currently ahead of the default version.
Seeing what's in a build
Each build ships with its own version number. Once you're on the main menu, look at the top-right corner and click Changelog — it lists each build's version and what changed, newest at the top.
How I'll post updates
I don't plan to post a Steam announcement for every build. For day-to-day changes on both the beta and default branches, the in-game Changelog is the source of truth — I'll keep it updated there. I'll save Steam announcements for the bigger stuff worth surfacing.
A note on save data
Right now the beta branch shares your save data with the normal version — your progress carries over both ways. Backward compatibility is always the goal, so a beta build's data changes are meant to work cleanly with the normal version. Verifying that migrations behave as expected is exactly what the beta stage is for — so if a build touches the database or save format, testing it here is how I confirm it's safe before it reaches everyone.
Heads-up
Builds here are newer and less tested than the default version, so expect the occasional rough edge — that's the point of the branch. If you're up for trying things early and reporting back, it's a great way to help shape where the game goes.
How to opt in
Right-click GuitarSesh in your library → Properties → Betas → select beta from the version list (no password needed). To return to the normal version, select Default Public Version.
— Kyle
