SPIRITVALE

News / 5 min read

SpiritVale PTR Server Guide: How to Join and What to Test

Checked September 22, 2026: the official September 21 announcement publishes Update 0.32.0, Advanced Artifacts and Advanced Grimoires. The earlier maintenance notice is now historical; use the 0.32.0 announcement for released changes rather than the earlier PTR preview. This does not confirm real-time server availability. The September 10 PTR announcement invited players to test these features and described test items near the center of Nevaris. The instructions below describe the testing branch, not a requirement for accessing the released update: test progression remains separate from live progression. Report PTR issues in the official Discord channel specified by the developer.

SpiritVale news gameplay screenshot

How to join the PTR

In Steam Library, right-click SpiritVale, choose Properties, open Game Versions & Betas, select publictest, then launch the game and join the test server. This is the developer's published path from the July 31 announcement; if the Steam labels change, check a newer official post before relying on an old route.

What the PTR has been used to test

Official posts identify item-related changes, Auction House (AH), Trading, Guild Storage, and other fixes as PTR targets. The August 2 update said the next update was being tested for 1-on-1 trade, vending/AH, guild storage, party/chat fixes, item loss, and exploits. The later 0.30.10 notes confirm several of those systems were re-enabled or fixed, but PTR plans are never proof that every planned feature is live.

Protect your expectations

Do not use PTR results as proof of live drop tables, prices, character progression, or a best build. The developer says PTR progression may be reset or changed and that live release depends on stability and testing. Record the server type, date, client version, and observed behavior before sharing a report.

Where to report a problem

The official PTR post asks testers to report issues in the SpiritVale Discord. Include the exact feature, steps to reproduce, whether it happened on PTR or live, and the expected versus actual result. Keep live-server and PTR observations separate.