Miscellaneous setup

In addition, the following fields serve for further customizability:

Hide spline for a scan:

If you want to hide spline for a scan, like, a "CLASS I S ALARM", which has only 1 bioscan, simply set HideSpline to true:

"HideSpline": true,

However, if you want to hide spline of an entire cluster scan, you'll have to:

1. hide spline for the cluster parent
2. hide spline for all its children.

Override previous puzzle position:

This part serves to customize starting position of spline. Here's a reference usage video:

https://github.com/Inas-07/ExtraChainedPuzzleCustomization/pull/1

To achieve the effect in the video, there're 2 means:

1. Specify PrevPosOverride to the desired starting position, for example:

"PrevPosOverride": {
  "x": 2,
  "y": 9,
  "z": 45
},

By this means, the spline will always start from the given position.

Note: the position should be close enough to a point on the nav-mesh (i.e. ground)

2. Specify PrevPosOverrideIndex to puzzleOverrideIndex of another scan.

Like:

"PrevPosOverrideIndex": 26

By this means, the spline will always start from the position of the given scan.

NOTE: due to an implementation design issue, PrevPosOverrideIndex must be less than puzzleOverrideIndex of current scan.

For example, the following setup won't work:

{
   "Index": 10, // puzzleOverrideIndex of current scan
   "PrevPosOverrideIndex": 11 // WON'T work! `PrevPosOverrideIndex` must be a value less than `Index`!
}