@ralph Alright so. Woke up so now I technically have time to write about that suggestion lmfao.

It’s a very advanced feature and you need big brain to understand it. But as a result it would allow us to create massive rigs.

Just like modify branch, it has its own designed button and menu in Stick editor.

Unlike the rest, the window covers entire screen.

On the edge of top right corner we have the X button. On top left we have preview of which Nodes are being input, more on that later. You can change zoom by tapping on the preview and it goes between 3-5 zoom distances.

On the right side of the preview we have the entire coding thing.

It uses a lot of empty windows to input segment IDs, which are the draw order of the segment (the numbers which show which segment are on front). Next to each ID, there’s button to switch between A and L. (More on all coding aspects later, rn just telling the layout). There are two areas to input IDs, then one last window where you type in how big the change is.

Below the code stuff there’s + and – buttons, which are used to add a rule or delete a rule from rule list that exists below, similar to import stickfigure.

The only difference between the rule list and import stick is that its on multiple columns, without the sliders. I’m thinking of 3 columns for it.

So, the update and feature that would be named I’m suggesting as “nodegramming”, basically programming Nodes lol.

The example formula in the coding would look like
|21||L|=>|5||L|=>|120|%

Alright so, the L stands for Length. It works on percents. Where 100 length is 100%.

The segment at the 21 spot affects segment at spot 5, where for every 100 length longer the segment 5 gets longer by 120. The amplitude number (current 120) can also exist in negative numbers.

Simple.

When tapping L to change to A, it works on angles. When swapping it on the 2nd ID, the last symbol changes between % and °.

While for L, 100 units is 100%. 360 degrees is 100% for the angles.

Angles have bit different conversion system. For each 1°, it makes the change by X amount instead. Been thinking for every 360° but that can make things a bit too hard to math later on. Anyway.

|3||A|=>|4|A|=>|0.5|°

I think it’s pretty self explanatory. Each one angle on 3 makes 4 move by half that amount.

Now, there’s the big meat. A to L and L to A.

L to A is basically for each 100 length, it does this many degrees of movement.

While A to L makes this many units of length for each degree.

No example since I think I explained it well, unless asked for.

When you type in your rule, you press the +, which adds to the code list. Example code preview would be 34A=>21L. When tapping on it, it fills in the numbers in the code inputs to see the ampitute etc. You press + to overwrite/confirm, if the id, and A and L match.

The only time when you won’t be able to save the code is if A/L of the 2nd ID is already being affected.

The code list is divided to 3-4.
1st is A to A, 2nd is L to L, last one(s) are A to L and L to A.

Uh- that’s all I guess?

There’s also been thonk moment on some extras to it, like 2nd id also affects children like smart stretch. Or if 1st window id is empty, the angle of the 2nd id stays constant if it’s – to A.

Okay that’s all I have I think. I’ll yeet in images after school if I find time.

@ralph ik sorry for being an ass with complex-ass suggestions.

I mean… I have another one but it ain’t so code crazy. I think.

Let me just ask. Would it be hassle if people could basically “code” a bit how their node functions? Like all segments have their own ID that’s what I know. Would be really troublesome for the coding standpoint if when segment A gets stretched, segment B gets shorter/longer by % set by an user. Same with ids user choose which id affects which.

I actually have a really good UI design that wouldn’t add any new sprites and would utilise everything that is already added.

Just wanted to know if should I hassle with the concept drawing tmrw or if it’s gonna be like “too hard to code lol no”

Okay so that happened for some reason and wouldn’t change when refreshing-