| Publisher | Mad Cat VR |
|---|---|
| File size | 854.38kB |
| Number of files | 20 |
| Latest version | 1 |
| Latest release date | 2019-01-14 04:16:10 |
| First release date | 2018-03-12 11:03:21 |
| Supported Unity versions | 2018.4.2 or higher |
With this plugin you can store your game or app configuration in a Google spreadsheet. This way you can share it with people who are not very comfortable with Unity and can use the power of spreadsheets for all kinds of calculations and data manipulation. Even for just editing it is way more convenient than Unity inspector or XML/JSON configuration files for example.
By default data from the spreadsheet is parsed to scriptable objects' fields in the editing mode, so you can see it in inspector and access from code without any parsing in run-time.
It is possible to sync with the spreadsheet in run-time too.
Interpretation of the spreadsheet is up to you, no limits for the structure, except for one - first row is for column names, and they have to be unique. That's it. Otherwise you can use multiple sheets, have hierarchies of objects in one spreadsheet (not necessarily it has to be one object per one row), you can use it for:
- settings (by just having name and value columns)
- game design (for example list of units in game, with their stats and abilities)
- localization (by having text key column and translation columns)
- and much more.
Included demo features:
- multiple sheets
- sheet with hierarchy of objects
- example of spreadsheet parsing
- example of data usage in game
Plan for next version:
- add automatic reflection-based parser for trivial cases.
- add localization helpers out-of-box
- add extensions for parsing more types of data
By default data from the spreadsheet is parsed to scriptable objects' fields in the editing mode, so you can see it in inspector and access from code without any parsing in run-time.
It is possible to sync with the spreadsheet in run-time too.
Interpretation of the spreadsheet is up to you, no limits for the structure, except for one - first row is for column names, and they have to be unique. That's it. Otherwise you can use multiple sheets, have hierarchies of objects in one spreadsheet (not necessarily it has to be one object per one row), you can use it for:
- settings (by just having name and value columns)
- game design (for example list of units in game, with their stats and abilities)
- localization (by having text key column and translation columns)
- and much more.
Included demo features:
- multiple sheets
- sheet with hierarchy of objects
- example of spreadsheet parsing
- example of data usage in game
Plan for next version:
- add automatic reflection-based parser for trivial cases.
- add localization helpers out-of-box
- add extensions for parsing more types of data
