Steam 설치
로그인
|
언어
简体中文(중국어 간체)
繁體中文(중국어 번체)
日本語(일본어)
ไทย(태국어)
Български(불가리아어)
Čeština(체코어)
Dansk(덴마크어)
Deutsch(독일어)
English(영어)
Español - España(스페인어 - 스페인)
Español - Latinoamérica(스페인어 - 중남미)
Ελληνικά(그리스어)
Français(프랑스어)
Italiano(이탈리아어)
Bahasa Indonesia(인도네시아어)
Magyar(헝가리어)
Nederlands(네덜란드어)
Norsk(노르웨이어)
Polski(폴란드어)
Português(포르투갈어 - 포르투갈)
Português - Brasil(포르투갈어 - 브라질)
Română(루마니아어)
Русский(러시아어)
Suomi(핀란드어)
Svenska(스웨덴어)
Türkçe(튀르키예어)
Tiếng Việt(베트남어)
Українська(우크라이나어)
번역 관련 문제 보고
So i can see the potential, but doubt we would actually use this.
Inside the game it's useful for checking the current branch (without having to do a really awkward web API request), but of course you have to restart the game if you want to change the game files.
It feels this feature have arrived late — usually nowadays i’d prefer to use a Playtest app than some public/user-accessible branch.
You mean checking that the game has a pending update while it’s running? And if there is — ask the player to restart the game.
That certainly sounds like a pretty useful scenario for most global multiplayer games.
Those are not programmer-style branches, Steam branches are simply name revisions, so it’s not possible to use them as VSC-branches, they’re not intended for that.
So gotta use Playtest and Demo apps when you need it to be public — and internal dev-only AppIDs — otherwise.
I agree this is the main Issue with Beta branches in Steam. Having the possibility to install multiple versions at once would be a real life saver.