<aside> 💡 If you are not in a position to integrate the SDK, you can upload a DRM FREE build directly through the Manage Build Upload menu in STOVE Studio, which will automatically activate the DRM MAKER and integrate the essential SDK.

Find more about DRM Maker here.

</aside>

<aside>

What Is STOVE PC SDK?

</aside>

<aside>

Supported Game Engines

</aside>

<aside>

Main Features

</aside>

<aside> 📢 Before starting, please follow the steps below

A. Pre-Preparation

It would help if you prepared in advance before conducting a build test.

1. Join STOVE Studio and register for a project

• Log into the studio with an account registered with STOVE and register as a store developer.
• Register a new project through the "Launch in Studio" menu on the studio screen.
• When you register a new project, you can check the "Game ID" and "Application Key" values ​​on the project screen and obtain the project information required for PC SDK linkage.

2. Complete PC SDK linkage to game build

• PC SDK must be linked to the game build, and the studio's project information (Game ID, Application Key) must be included accurately when linking the SDK.

If the project information is not entered accurately, the build test will not proceed.

3. Download New Client

• Download New Client through the top menu (GNB) of the STOVE store and install it on the PC to be tested.

B. Activating Developer Mode

Activating developer mode is the task of allowing the New client to recognize the game build (linked with the PC SDK) running on the local PC.

1. Creating a developer mode configuration file

• To activate the developer mode of the New client, the configuration file must be created with the name policyconfig.json. If the file name is incorrect, the New client will not recognize the configuration file.
• Go to C:\\Users\\%username%\\AppData\\Local\\STOVE\\Config and create a policyconfig.json file.

Path: ...\\\\AppData\\\\Local\\\\STOVE\\\\Config\\\\PolicyConfig.json

2. Enter the configuration contents

The final step to activate the developer mode of the New client is to write the configuration contents as shown in the box below.

<aside> 💡

If the Stove Launcher is on, you must restart the Stove Launcher after writing. When testing via editor or exe, you must run it in administrator mode.

</aside>

You can enter multiple game IDs registered in the studio in dev_game_list, and the game build that matches the entered game ID will communicate with the New client in developer mode, and build testing is possible on the local PC.

{
"stove_launcher_policy_config":
{
"dev_game_list": [ "Game ID", "Game ID"]
}
}

If the developer mode of the New client is not activated, check if the location of the policyconfig.json file is correct, and check if the game ID entered in policyconfig.json exactly matches the game ID registered in the studio. >

C. Proceed with the build test

Since the developer mode of the New client has been activated through the process described above, all the problematic steps have been completed, and the build test is possible by simply running the game build linked to the PC SDK while the New client is running.

The build test can be conveniently performed by running the exe file directly or in the debug mode of the development tool (Visual Studio, Unity, Unreal, etc.), so you can perform the debugging process by conveniently performing the build test.

The above method is not supported if a test payment is required in a game build linked to the IAP SDK. To perform a test payment, you must upload the build to the studio, enter the Studio Test menu of the New client, and then attempt the test payment.

</aside>

<aside> 💡 **After the above steps are done, run the STOVE PC Client and log in with the STOVE ID you applied for in STOVE Studio.

Now, we are ready to go!**

</aside>

<aside>

Follow Through (Sample)

</aside>

<aside>

SDK Integration Documentation

</aside>

<aside>

Authentication Integration (+OpenID)

</aside>

<aside>

Error Codes

</aside>

<aside>

Glossary

</aside>