본문으로 건너뛰기
ZokoGames

로그인

이 페이지는 아직 번역되지 않아 영어로 표시됩니다.

Updating a live game

이 페이지의 내용

Updating a live game

Games are never frozen. You can upload a new build, change the listing text or swap artwork at any time. What happens next depends on the stage your game is in.

Stage New build Artwork and listing
Draft Replaces the active build at once. Edit freely.
In review Locked. Withdraw the submission to edit, then submit again. Locked.
Basic launch Goes live right after it passes the validator. Artwork is staged and reviewed; see below.
Full launch Waits for a reviewer, then replaces the live version. Artwork is staged and reviewed.

Shipping a new build#

  1. Make the change locally and test it in local mode and the Preview tool.
  2. In the developer console open the game, go to the Build step and upload the new zip. The validator runs exactly as for the first upload and shows every problem with the offending path.
  3. Run Preview on the new build (ads are on there) and tick through the checklist.
  4. In full launch, submit the update and add a note for the reviewer that says what changed and where to see it. Short, specific notes get faster decisions.
Tip

Keep the index.html path stable and every asset path relative. A build that only changes a few files still needs to be a complete zip.

What a reviewer looks at in an update#

Updates are re-validated automatically and, for live games, re-reviewed when they change gameplay, ads or monetisation. A review of an update focuses on what changed, but a rule break anywhere in the build can still lead to a request for changes or, in serious cases, removal. Re-read the requirements checklist when you add ads, accounts, multiplayer or external links.

Saved data across versions#

Players keep their cloud save when you update. Plan for old saves meeting new code:

  • Store a version number in your save and migrate on load.
  • Ignore keys you no longer use instead of deleting them.
  • Never rename a key without reading the old one first.

See cloud saves in practice.

Changing artwork#

Covers and preview videos are part of the listing and go through their own review. Stage the new files, submit them as one artwork change, or compare versions first with an artwork experiment. Specs are on covers and videos.

Rolling back#

If an update breaks something, upload the previous build again from your own source control and submit it. In basic launch it is live as soon as it validates. In full launch, say in the reviewer note that it is a rollback. Test updates in the Preview tool before you submit so you rarely need this.

Telling players#

Put a short "what is new" line in the game or on your community page. The portal does not send patch notes to players on your behalf.

이 페이지에 불분명하거나, 틀리거나, 빠진 내용이 있나요? 지원팀에 알려 주세요 · 미리보기 도구에서 게임 테스트하기

쿠키 설정

ZokoGames가 사용할 수 있는 쿠키를 선택하세요. 필수 쿠키는 사이트가 작동하는 데 꼭 필요해서 항상 켜져 있어요.

  • 로그인, 언어, 그리고 이 선택 사항에 사용돼요. 항상 켜져 있어요.

  • 최근 플레이한 게임 같은 정보를 이 기기에 기억해요.

  • 무작위 방문자 ID로 플레이 횟수와 페이지 방문을 집계해 서비스 개선에 활용해요.

  • 맞춤 광고를 허용해요. 광고는 무료 게임 운영에 쓰여요.