It works as intended, but I have yet to do something with the C variable so I don’t know why it gives birth to many children. And I plan to have more than 20 C, so does this mean that i’ll end up with 340+ null variables that are not needed? Or is this simply a visual glitch of the debugger? I just don’t want it to affect my game.
this is indeed just a display bug in the debugger, and the game works well. No extra variables are created, and your structure is exactly what you defined.
To avoid freezing the game, the debugger does not read variables past a certain nesting depth, and the editor was wrongly showing that cut-off point as a list of NULL children.
We’ll implement a clearer message for deeply nested variables in the next version. In the meantime, if you need to check those values, display them in a Text object or use the “Save a scene variable into a JSON file” action, which both show the real content.
Alternatively, you can split the deepest children into separate, less nested
variables so the debugger can show them.
