cathei
Add support for nested vertical list in other vertical list or dictionary
It is common in game developement to have nested vertical list to ease the workflow of game designers.
For example, an seasonal event CSV can have multiple packages, each package contains multiple rewards, and each reward can be a single item or multiple items. Splitting this kind of data into multiple CSV sheets would make it hard for the designer to track and compare their balancing between those data packages.
I wonder if it requires too much work to support nested vertical lists?
It's hard to promote the use of BakingSheet in my company. Currently I'm the only one use BakingSheet. But atm the game is in alpha stage and doesn't have complex data types. But every single product of my company will eventually need this kind of data at some point in the game's lifetime.
Nested vertical list is not supported due to ambiguity of the structure. If the header looks like
| Id | Values |
|---|---|
| Row1 | 1 |
| 2 | |
| 3 |
If the Values is VerticalList<VerticalList<int>> Values, it's not possible to determine how the list is structured. (This is simplest example but applies to any complex row.)
So that's the limitation of vertical list, this can be usually solved by separating the sheet and using references.
