Thanks for coming to check out this feature. Before we start, we must cover the essentials.

Beta notice: please read

As opposed to other betas this one is using our normal servers instead of separate beta servers. This means you can use all your usual boards and play with people not using the Beta as there is no risk of data loss or incompatibilities with this change.
Leaving the beta will clear some cached files and so community content will re-download on next use (either automatically or when prompted based on your settings).

Reporting Bugs

This branch is all about the bugs, so we have set up a temporary bug reporting channel for reporting problems specific to this branch.

You can find it here: https://feedback.talespire.com/b/content-handling-changes-beta
Game Photo

Switching to the Beta branch


To switch to the beta branch, you do the following:

  • Open Steam
  • Right-click on TaleSpire
  • Choose "Properties..."
  • Switch to the "BETAS" tab
  • Enter the password 357n49xc7075v0
  • Click the "Check Code" button
  • Click on the blue "Opt Into" bar that appears

If it doesn't automatically switch the active beta for you, you can pick `beta-content-handling` from the "Select the beta you would like to opt into:" drop-down.

Switching branch should enqueue a download for the Beta build of TaleSpire.

Leaving the Beta branch

To leave the beta branch, you do the following:
  •  Open Steam
  •  Right-click on TaleSpire
  •  Choose "Properties..."
  •  Switch to the "BETAS" tab
  • Choose "None" from the "Select the beta you would like to opt into:" drop-down.

This should enqueue a download for the standard build of TaleSpire.

NOTE
Leaving the Beta will cause community content to have to be downloaded again. It doesn't affect any boards or campaigns, this is just a result of cached files being cleared.

Expected Behavior

The expected behavior is to behave exactly identically to how the game plays currently.

We have tweaked a bunch of code that handles loading community content, and have changed the name and layout of some internal directories where we stored content downloaded via the community-content browser.

We are testing internally, but nothing beats real player testing on a wide range of hardware and software setups.

The test condition is simple; if it worked before, it should work now.
Things that didn't work before will be tackled in the future.

Thank You

Thanks for checking it out. We are very eager to get this to the rest of the community, and your help is much appreciated.

We'll see you in the bug reports :P