almost like you’re writing up the documentation for an API

Never wrote one, don’t know how even writing one looks like. Thus, reason why we’re failing to communicate properly lmfao.

as you said, static nodes only

u mean non-static lol.

I had similar idea for the window for it lmao, just didn’t want to have clutter of 300 different segments being put into one window.


Also very rough draft for the rigging mode.

Emphasis on having multiple figures in the same Rigging mode, not just one stick. I basically was designing this for stuff like “if variable X is equal Y, then Stick1 switches to Stick2 at Z angle” when the target is the main node. And variables would also provide data between segments, it would get confusing if we get 2 of #69 segments.

I had a bunch of stuff in mind when it comes to rigging, on top of what we discussed, but that’s like more or less later-development shit. I know how it could be handled, just wanted to set a place for it.

okay if that’s what you mean by rigging

I don’t know what to call it atm, so I just go with whatever name as for now because I suck at naming and never got any suggestions. Lmao.

similarly, with max-inverse, what you mean is “pingpong”

This one is kinda funny, let’s say we have 1:1 mirror of length. Segment A is the controller, segment B is controlled by A, segment B has max of 200. Both segments start with length of 100.

Now if we stretch A, after passing 200 length, segment B would start going backwards. For example reasons the numbers are (A, B):
(150, 150), (200, 200), (250,150), (300,100), (400,0), (500,100)
With the last number, this is what I meant by “ping-pong”, as B would end up oscillating between 0 and 200. Would be neat if it could be somehow transformed into a sin/cos motion, but I’m keeping this example simple for now.

what this implies is you NEED 4 things for a “nodegramming statement”

Nerd, I already went through this.

We get a controller segment, then create a variable that is one of the controller’s properties (length, angle, scale etc.), then we get a target segment, set it so one of it’s will match the variables number at 2.00 (user customised) scale.

So if we stick with variable and target both reading and applying the numbers to angle, and their controller-target starting angles would be (0,90) then:
(45,90+90), (90,90+180), (180,90+360).

last part question

This is why I said the rigging thing should only work with non-static segments to avoid headaches. Especially since they break smart-stretch continuity, but can start one themselves.

If a segment is being “target”, it can’t be interacted with in animation mode. Simple as that.

Where you should be worried about is what if controller is attached to target. Mathematically would be “simple”, but will be totally broken ui wise lmao. (spoiler alert, the app would just give nah son).

Anyway, the reason why variables would exist is to allow for better way to handle it UI wise, as well as give option for user to switch between variables and properties without breaking fuck all.

Will give mockups on how everything will look, don’t worry about that lmao.

@ralph as a transparent png export connoisseur, I am absolutely disgusted by your incompetence.

What stuff would you guys make if you had either of these

Yeah I actually saw that myself when reviewing the stick myself. I lol’d.

Like having some more or less automated/customised movement for your segments.

Stuff like you stretching segment A and as a result segment B does the same.

Around 70% of submissions get rejected. With ~150 submissions coming in daily.

However, these numbers are greatly boosted due to people submitting either the default sticks that come with the app, most notably _Background (City), as well as countless recolors of already published sticks, mainly dbz, Godzilla, and anything that’s trendy among the Roblox community (doors, rainbow friends, stuff like that…)

I’ve went as far as playing this and actually understanding this shits. Though you’d probably guess that’s just me being insane as usual.
https://store.steampowered.com/app/1349230/5D_Chess_With_Multiverse_Time_Travel/

Ora’os