Understanding path drawing between Research Tree's nodes with an example
This is a simple guide to help you understand how Research Trees draw lines between nodes.
9 Replies
Each node (mNodeDataStruct) has a ChildrenAndRoads property you can edit to make a fancier looking paths - Research Tree editor widget can't draw them properly if they deviate from a certain pattern.
Each node's child has a list of checkpoints which serve as a guideline towards drawing a path. For better understanding of how many points you need for path refer to the image below
Notes:
- If rules are broken, the entire path gets converted into a straight line, not its part.
- Can't exactly say if pattern breaks when paths go upwards. What is certain is that there won't be any game crashes caused by your creativity.
- When straight lines get drawn due to broken rules, the (0;0.5) offset isn't applied
can you explain more about why 4;3 and 5;4 bypasses the coordinate system and draws a line instead?
it seems like it would become 4;3.5 and 5;4.5 following what you wrote
Lacks verticality
Oh, i forgot, right
I will add to the notes that if there are no vertical lines, the pattern also breaks. Or something similar
what is the road data array representation of the path you drew out with arrows here? if you have it in the editor, I think you can copy the field and paste it here
And I meant those as in path between Nodes (4;3) and (5;4)
