ウズスタジオ 公式ガイド
UZU STUDIO
UZU STUDIO
  • Uzu Studio Official Guide
  • Introduction
    • What is Uzu Studio
    • How to log in
    • Process from creation to release
      • Creating a new scenario
      • Test play
      • Submitting your work
        • Detailed review for paid works
        • How to use the test play questionnaire
        • Common feedback on text
    • Murder Mystery completion template that only requires filling in
      • Basic usage
      • Advanced usage
    • Key visual creation regulations
    • List of feature updates
    • Business days and hours
    • What can and cannot be done with Uzu Studio v2
  • Top (Scenario list screen)
    • Changing the author profile
    • Agreeing to various terms
    • Receiving sales revenue
    • Checking evaluations and badges
    • Collection feature
  • Scenario Home
    • About the home screen
    • Work overview
      • Setting sub-images
    • Marketing
    • Release management
    • Reports
    • Members
  • Feature details
    • Characters
      • Basic character items
      • Missions
      • Second playthrough characters
    • Phases
      • Creating and overview of phases
        • Basic phases
        • Script reading phase
        • Voting phase
        • Game flow display phase
      • Phase progression
    • Text
    • Rooms
    • Post-game discussion screen
    • Clues
    • Decks
    • Tokens
    • Actions
    • Effects
      • BGM
      • SE and narration
      • Movies
      • Background images
      • Color themes
    • Common settings: conditions
    • Top right button: Demo
    • Top right button: Create the latest version
  • Advanced
    • Incorporating an investigation phase
    • Distribute all endings
    • Change displayed content based on character
    • Insert images during script reading
    • Create a rescue phase when moving forward before everyone finishes investigating
    • Adjust the volume of audio files
    • Set up expandable blocks
  • Official resources
    • Character icons
  • Others
    • Migrate v1 scenarios to v2
  • Frequently Asked Questions
    • Frequently Asked Questions
    • FAQ: v1 to v2 migration
Powered by GitBook
On this page
  • How to Create the Latest Version
  • Error Check and Correction

Was this helpful?

Edit on GitHub
  1. Feature details

Top right button: Create the latest version

Last updated 8 months ago

Was this helpful?

How to Create the Latest Version

Once you have finished creating your scenario, first reflect the content in the app and conduct a test play. To do this, you need to follow the steps to create a version.

Pressing the top right button will automatically perform an error check to see if a new version can be created.

Error Check and Correction

If there are any settings missing, unconfigured areas will be displayed, so please make the necessary corrections.

Clicking "Go to the corresponding section" will take you directly to the location of the error.

\

If everything is set up correctly, a popup for creating the version will appear.

The input field is a memo field for your own use to make it easier to check what was modified later. It is not visible to anyone other than the author, so feel free to fill it in. It's also okay to leave it blank.

※What is the Latest Version?

The latest version is for test play and can only be created by the author; general users on the app cannot play this version.

In version 2, compared to version 1, there is more freedom, which means more settings and considerations, and it is more prone to implementation errors. To prevent a version with remaining errors from being released, it has become standard to create the latest version once. The latest version is displayed as "Latest Version" on the release management screen.

Pressing "Release Latest Version" on the release management screen releases it on the app as a version that general users can also play. For works transitioning from v1 to v2, you cannot press "Release Latest Version" until the transition application is approved.

For more about the "Release Management" screen where versions are managed, see .

here