Download via Releases page

You can find more detailed instructions and the demo project Here

1. Introduction

This tool simplifies database design and management for game developers and designers, allowing for easy modification of configurations and statistics.

As projects grow, the need for efficient management of data tables, constants, and IDs increases. This tool centralizes the process, enabling easy searching, modification, and updates.

It supports various data types and utilizes popular spreadsheet tools for data management.

2. Main functions

• Excel and Google Sheets Integration: Manage your entire database using Excel or Google Spreadsheets.
• ID and Constant Management: Make batch adjustments to IDs and constants without impacting the database.
• Localization System: Effortlessly handle multiple languages, with seamless Unity integration.
• JSON Export: Convert data tables to JSON files for easy Unity integration.
• Flexible Data Formats: Support a variety of data formats, adaptable to your design needs.

3. Introduce features and installation instructions

3.1. Export single excel

This is a basic but very important function, helping you get acquainted with the tools. If your Static Database is not too large or complex, and only needs an excel file to contain all data, then this function is enough for your needs. However, if your Static Database is complex and needs to be stored in multiple Excel files, you will need to use the Export Multi Excels function. This function will be introduced in the next section.

The important functions are in the buttons on the right:

• Export IDs: Converts ID sheets to C# files.
• Export Constants: Converts Constants sheets to C# files.
• Export Localization: Exports Localization Data, Localization Components, and Localization API.
• Export Json: Transforms Data Table sheets into JSON data.

3.2. Export multiple Excel Spreadsheets

This is a comprehensive function, everything will be processed with just one button press:

1. Add all the Excel files you want to process.
2. Choose whether to export IDs and Constants by checking the appropriate boxes for each file.
3. Press the Export All button to complete the process.

3.3. Export multiple Google Spreadsheets

Prefer using Google Spreadsheets? No problem.

1. Enter the IDs for the Google Spreadsheet files you want to process.
2. Press the Export All button to begin the export.

3.4. Settings

• Json Data Output: Converts the data table to JSON format and saves it at the specified address.
• Constants Output: Saves IDs, Constants, Localization Components, and Localization API at the given address.
• Localization Output: Stores Localization Data at the provided address, which should be within the Resources folder or in the Localizations folder if you want to load Localizations by Addressable Asset System.
• Namespace: Defines the namespace for the exported C# files.
• Separate IDs:
  • TRUE: Exports [%IDs] sheets to individual C# files named [SheetName] + IDs.cs.
  • FALSE: Merges all [%IDs] sheets from all Excel files into a single C# file named IDs.cs.
• Separate Constants:
  • TRUE: Exports [%Constants] sheets to individual C# files named [SheetName] + %Constants.cs.
  • FALSE: Merges all [%Constants] sheets from all Excel files into a single C# file named Constants.cs.
• Separate Localization:
  • TRUE: Exports [Localization%] sheets to separate groups, each containing Localization Data, Component, and API, with the following file name structure:
    • Localization Data: [SheetName]_[language].txt
    • Component: [SheetName] + Text.cs
    • API: [SheetName].cs
  • FALSE: Merges all [Localization%] sheets from all Excel files into a single group, with the following file name structure:
    • Localization Data: Localization_ + [language].txt
    • Component: LocalizationText.cs
    • API: Localization.cs
• Encrypt Json: Encrypts JSON Data before exporting to a text file.
• Only enum as IDs: For [%IDs] sheets, columns with the extension [enum] will be exported as enums and will not include the Integer Constant form.
• One Json - One Excel: Merges the Data Table from one Excel file into a single JSON file, named [ExcelName].txt.
• Language maps: Used in Localization with TextMeshPro to compile the character table of a language, mainly applied for Korean, Japanese, and Chinese due to their extensive character systems.
• Persistent columns: Specifies the names of columns to retain during processing even if they are empty.
• Excluded Sheets: Specifies the names of sheets to exclude when processing the Data Table.
• GG Client ID: Enter your Google Client ID (retrieved from Credentials in Google Console).
• GG Client Secret: Enter your Google Secret (retrieved from Credentials in Google Console).
• Encryption Key: The key used to encrypt JSON Data.

3.5. Encrypt & Decrypt Text

This function allows you to encrypt or decrypt a string of characters based on the Key provided in the Settings Tab. You can use this function to secure the content of a text, or to open and read the encrypted JSON Data files after they have been exported.

4. Data Design Rules in Excel

4.1. IDs

Download detail example from GitHub

Hero			Building			Pet			Gender[enum]
HERO_1	1	comment	BUILDING_NULL	0	comment	PET_NULL	0	comment	GENDER_NONE	0
HERO_2	2	comment	BUILDING_1	1		PET_1	1		GENDER_MALE	1
HERO_3	3	comment	BUILDING_2	2		PET_2	2		GENDER_FEMALE	2
			BUILDING_3	3		PET_3	3		GENDER_HELICOPTER	3
			BUILDING_4	4		PET_4	4
			BUILDING_5	5		PET_5	5
			BUILDING_6	6		PET_6	6
			BUILDING_7	7		PET_7	7
			BUILDING_8	8

ID Sheets, named with the suffix IDs are used to compile all IDs into Integer Constants. The design rules are:

• The sheet name must end with IDs.
• Only the Integer data type is allowed.
• Each group is organized in 3 consecutive columns.
• The first row contains the group name for easy reference.
• The first column holds the Key Name, and the next column holds the Key Value.
• Key Value must be an integer.
• By default, all IDs in a column will be exported as Integer Constants. Add the suffix [enum] to the group name to export them as an enum.
• To only export enums and skip Integer Constants, select Only enum as IDs in the Settings.

| Group | Key | Comment |
| ----- | --- | ------- |

4.2. Constants

Name	Type	Value	Comment
EXAMPLE_INT	int	83	Integer Example
EXAMPLE_FLOAT	float	1.021	Float example
EXAMPLE_STRING	string	321fda	String example
EXAMPLE_INTARRAY_1	int-array	4	Integer array example
EXAMPLE_INT_ARRAY_2	int-array	0:3:4:5	Integer array example
EXAMPLE_FLOAT_ARRAY_1	float-array	5	FLoat array example
EXAMPLE_FLOAT_ARRAY_2	float-array	5:1:1:3	FLoat array example
EXAMPLE_VECTOR2_1	vector2	1:2	Vector2 example
EXAMPLE_VECTOR2_2	vector2	1:2:3	Vector2 example
EXAMPLE_VECTOR3	vector3	3:3:4	Vector3 example
EXAMPLE_REFERENCE_1	int	HERO_1	Integer example
EXAMPLE_REFERENCE_2	int-array	HERO_1 : HERO_2	Integer array example
EXAMPLE_REFERENCE_3	int-array	HERO_1 | HERO_3	Integer array example
EXAMPLE_REFERENCE_4	int-array	HERO_1 HERO_4	Integer array example
EXAMPLE_FORMULA_1	int	=1*10*36	Excel formula example
EXAMPLE_FORMULA_2	float	=1+2+3+4+5+6+7+8+9	Excel formula example

Constants Sheets, named with the suffix Constants compile project constants. The design rules are:

• The sheet name must end with Constants.
• There are four columns: Name, Type, Value, and Comment.
  • Name: The name of the constant; must be continuous, without special characters.
  • Type: The data type of the constant. Possible data types include: int, float, bool, string, int-array, float-array, vector2, and vector3.
  • Value: The value matching the data type. For array types, separate elements with : or | or newline.

| Name | Type | Value | Comment |
| ---- | ---- | ----- | ------- |

4.3. Localization

idstring	relativeId	english	spanish
message_1		this is english message 1	este es el mensaje en ingles 1
message_2		this is english message 2	este es el mensaje en ingles 2
message_3		this is english message 3	este es el mensaje en ingles 3
content	1	this is english message 1	este es el mensaje en ingles 1
content	2	this is english message 2	este es el mensaje en ingles 2
content	3	this is english message 3	este es el mensaje en ingles 3
title_1		this is english title 1	este es el titulo 1 en ingles
title_2		this is english title 2	este es el titulo 2 en ingles
title_3		this is english title 3	este es el titulo 3 en ingles
whatever_msg		this is a sample message	este es un mensaje de muestra
hero_name	HERO_1	hero name 1	nombre del héroe 1
hero_name	HERO_2	hero name 2	nombre del héroe 2
hero_name	HERO_3	hero name 3	nombre del héroe 3

Localization Sheets are named with the prefix Localization and follow these rules:

• TThe sheet name must start with Localization.
• Each sheet has two key columns: the main key idString and an additional key relativeId.
• The following columns contain localized content.
• The key for each row is a combination of idString and relativeId.
• relativeId can reference an ID from the IDs sheets.

| idString | relativeId | english | spanish | japan | .... |
| -------- | ---------- | ------- | ------- | ----- | ---- |

4.4 Data table - JSON Data

Basic data type: Boolean, Number, String

numberExample1	numberExample2	numberExample3	boolExample	stringExample
1	10	1.2	TRUE	text
2	20	3.1	TRUE	text
3	BUILDING_8	5	FALSE	text
6	HERO_3	10.7	FALSE	text
9	PET_2	16.4	FALSE	text

Extended data type: Array, JSON object

array1[]	array2[]	array3[]	array4[]	array5[]	array6[]	JSON{}
text1	1	1	TRUE	123 66	aaa ccc	{}
text2	2 | 2 | 3	1 | 2 | 3	TRUE | FALSE | TRUE	123 71	aaa ccc	{"id":1, "name":"John Doe 1"}
text1 | text2	1 | 2	1 | BUILDING_2	TRUE | FALSE	123 67	aaa ccc	{"id":2, "name":"John Doe 2"}
text1 | text2 | text3	1 | 2 | 3	BUILDING_1 | HERO_2	TRUE | FALSE | TRUE	123 68	aaa ccc	{"id":HERO_2, "name":"JohnDoe 2"}
text3	4 | 2	BUILDING_3 | HERO_1 | HERO_2	TRUE | FALSE	123 76	aaa ccc	[{"id":HERO_1, "name":"John Doe 1"},{"id":HERO_2, "name":"Mary Sue 2"}]
text1 | text2 | text7	5	1 | 2 | 4 | PET_5	TRUE	123 78	aaa ccc	[{"id":HERO_1, "name":"John Doe 1"},{"id":HERO_2, "name":"Mary Sue 2"}]

• For array type, the column name must have a suffix [].
• For JSON object type, the column name must have a suffix {}.

Special data type: Attributes list

attribute0	value0	unlock0	increase0	max0	attribute1	value1[]	unlock1[]	increase1[]	max1[]	...	attributeN
ATT_HP	30	2	1.2	8						...
ATT_AGI	25	3	1.5	8						...
ATT_INT	30	2	1	5	ATT_CRIT	3 | 2	0 | 11	0.5 | 1	10 | 20	...
ATT_ATK	30	2	1	8	ATT_CRIT	10 | 1	1 | 12	1.5 | 1	10 | 20	...
					ATT_CRIT	10 | 1	1 | 12	1.5 | 1	10 | 20	...

Attribute is a specific data type, specially created for RPG genre games - where characters and equipment can possess various different and non-fixed attributes and stats. This data type makes character and equipment customization more flexible, without restrictions.

To define an attribute object type, the following rules should be followed:

• The attribute column should be placed at the end of the data table.

• Attribute id is a constant integer, so it should be defined in the IDs sheet.

• An attribute has the following structure:

  1. attribute: The column name follows the pattern attribute + (index), where index can be any number, but should start from 0 and increase. The value of this column is the id of the attribute, which is an Integer type, this value should be set in the IDs sheet.
  2. value: The column name follows the pattern value + (index) or value + (index) + [], the value of the column can be a number or a number array.
  3. increase: The column name follows the pattern increase + (index) or increase + (index) + []. This is an additional value, which can be present or not, usually used for level-up situations, specifying the additional increase when a character or item levels up.
  4. unlock: The column name follows the pattern unlock + (index) or unlock + (index) + []. This is an additional value, which can be present or not, usually used for situations where the attribute needs conditions to be unlocked, such as minimum level or minimum rank.
  5. max: The column name follows the pattern max + (index) or max + (index) + []. This is an additional value, which can be present or not, usually used for situations where the attribute has a maximum value.

  Example 1: attribute0, value0, increase0, value0, max0.
  Example 2: attribute1, value1[], increase1[], value1[], max1[].
  

5. Setup for a Unity Project

You can view the demo project Here