Ideally the only extra code should be to improve the UX, not because of misalignment between the value and the schema. For example, "Node" could use a custom widget like this for the Flex values:

So… I'll need to add custom code to map the data for some components. For example, "Transform" values arrive as an array "translation: [x, y, z]", but BRP expects struct notation when modifying the values: ".translation.x".

This kind of special cases are brittle and will certainly break.

Oh, I didn't think about headless scenarios, makes sense. Anyway, there is also a VS Code BRP extension which also allows to edit the components.

This is read-only for now. Although I'll give the editing part a try later on. I'll push the code to a repo, soon™.

Not yet, I need to do the hardest task: decide a name for the repo/project. I'll upload the code during the next week, probably without builds.

It's a directional light pointing slightly upwards, that way it's (almost) not noticeable on the ground. Also is set as the child of the camera so it moves with it.

Next week I'll try to move the rim light to the shader as I want a different hue for each character... 🤞

Perfect material for a demoscene demo or a VJ set 😂

The next step is to break cycles and then assign a rank (vertical ""position"") to each node.

There is an easy algorithm which gives poor results. I'll start with that so I can move to the next stages of the algorithm: nodes positioning, edges routing…

This is the visualization of my test data (I've done the layout manually). In the previous image the dashed lines represent the "hierarchy", and the solid lines represent the "connections".