GSDK-Hub V2.5 User Guide
Function Description
Login
GSDK-Hub login and GDev Platform share the same account system, and both use Feishu/Lark login. If there is no corresponding account, please contact GDev Platform.
Link CPID
There are two kinds of CPIDs, one is Nuverse's studio, and the other is the application ID for accessing Nuverse services. Each user of the Hub must be bound to one, so that Nuverse data members can accurately obtain the users of the Hub, so as to achieve accurate push and upgrade communication.
Currently supported studio IDs include: Oasis, Youai, Mutong, 101, Jiangnan, Game Tech Center (for internal members of Game Tech Center). If your studio is not listed, please contact Nuverse members.
Function List
Introduction
After GSDK has been transformed into components, it has become a collection of functions. The information displayed in the function list is the list of core functions supported by GSDK. This information is the basic function of later version management and build management. In the list of functions, each function contains the following information.
| Name | Description | Additional Info |
|---|---|---|
| Component Name | Component Name | |
| Component ID | Component Key, globally unique | |
| Platform | Dual-ended / Android / iOS | Some components exist, only single-ended. Such as Thanos |
| Region | General / Mainland China / Global | |
| Starting version | Which GSDK version does the component start with | |
| Deprecated version | From which GSDK version the component was deprecated | |
| Description | A brief description of the component |
Version List
Example
SDK Build
Select the required version from the version list to enter the SDK configuration generation page.
Example
You can select the required components/modules by yourself, or click "Import Historical Configuration" to select the required component/module combination from the historical configuration.
There may be differences in the composition between the historical version and the target version of the SDK. You can compare the differences between the versions and make changes to the selected components/modules.
After the component/module is selected, click "Generate build configuration", and the selected structure will be saved to the user record, which can be used to obtain the content of the SDK in the subsequent process.
Configuration
Introduction
The configuration list records all configuration build records of the consumer. Each build record includes: GSDK version of the package body, region information, platform information, component collection, build time, and build-related operations.
For each configuration record, GSDK-Hub provides some management operations. as follows
- Delete: delete personal build records
- Notes: Add Notes information to the build record, which is convenient for recording memories
- build: For iOS/Unity, the required dynamic library needs to be obtained according to the information in real time.
- Download: For iOS/Unity, the package is on CDN and can be downloaded locally
- Export: For iOS/Unity, export the download package to the specified location
- Detailed: View the standard DSL display of this record
- View Gradle configuration: For Android, depending on the selected configuration, you will actually get a Gradle configuration suggestion file
Example
Additional Notes
Android build is to produce a configuration of the corresponding component, so the build delay is 0.
iOS build is to generate a dynamic library of corresponding components in real time, generally need to wait 2-10 minutes
Unitybuild generates a UnityPackage of the corresponding components in real time, generally it takes 5-20 minutes to wait
If the same build configuration has been recorded before, the cache will be reused and the build delay will be 0
**Why a dynamic library? **
- The dynamic library is loaded on demand in the true sense, so that the package body is minimized.
- Completely solve the problem of symbol conflict.
- Technology: Does not affect the text segment of the game app.
- GSDK's symbol table manage in GGame Tech Center
Download after build is complete
View Android gradle
You can copy gradle to the game project
Project Record
Introduction
This function is mainly to record local projects for automatic integration of SDK. Each record includes: basic information of the project (project name, path), type (Xcode Project/Unity project), target (SDK needs to be integrated into the target of Xcode Project), etc.
For project records, GSDK-Hub provides some management operations. as follows
- Delete: delete the project record (only delete the record, it will not affect the local project)
- Modification: Modify the basic information of the project, Notes, etc.
- Integration: For iOS/Unity projects, select the self-build SDK for automated integration
Example
Project list:
Select SDK:
Start integration:
Settings
Account Settings
Display account information, you can log out
Cache management
SDK download/integration will be cached locally. In order to save space, you can clear the cache here without affecting the already integrated project.
Update management
You can check the latest GSDK-Hub version
Feedback
If you encounter problems or have any suggestions for GSDK-Hub, please feedback
Command Line Mode
GSDK-Hub supports command line mode, which can be used for automated integration.
After the windows version is installed, it can be run directly on the command line; the mac version needs to be installed before use:
At the same time, you need to make sure that GSDK-Hub has been successfully logged in, and then you can execute the gsdkhub command in the terminal:
The current version supports two subcommands:
- pack: build according to the DSL file and save it to the specified directory
- gradle: Generate gradle code snippets based on DSL files and save them to the specified file
The DSL file in it can be exported from GSDK-Hub GUI mode:
The exported DSL file can be distributed to others in the project team and used in CLI mode. like:
build:
gsdkhub pack --dsl ~/Desktop/dsl.json --output .
Generate gradle configuration:
gsdkhub gradle --dsl ~/Desktop/dsl.json --output ./gradle.snippet