GTX, nooooo! D:

... Well.... Damn... No transparency, got it...
Well, had to learn it one day or another x3

Oh-... It gets rid of transparency?....
Well... Yeah, no... That's... Kinda bad...
How does embeds work?...
derpibooru.org/images/3695732
.... Not much better from what I can see in post-preview...

If I were to make a dedicated "Dance Avatar" however... /Then/ it might get worth it, but... Until then?... Eh.

And that, is where due to discovering just how much parameter space the /selector/ menu takes and how funky it may be if I can even get the receiver menu to /work/, that I figure; on-the-go customization is not worth it, considering everything else I could fit on an avatar instead of it.

However, this comes with the caveat as you can see on the post at the top, where you can see at the end, switching to another "item", the settings for the previous item remains.
Meaning, suddenly, switching from Item Nr. 3 to Nr.4, Item Nr.4 gets Item Nr.3's configured settings.

This way, I could use the exact same menu, and set the "ID" I use upon entering the menu, to drive whatever animation controller a compatible item may have, that uses the "ID" as a key.
(Yes, you can set Bools, Ints and Floats upon entering a SubMenu, RadialPuppet or any AxisPuppet menu.)

The idea itself was this:
I wanted a template menu, that I could put onto everything that had an emission that I wanted to be able to modify, and to find a way to use the least amount of parameters or "synced bits"

The idea was to use an "ID Selector" and parameter logics to decide what gets edited

.. Huh, you're still here, or scrolling to the end just to see how long this is... alright.

"But, how did you imagine the thing to work?" is coming up next!

So, if you want to show off the configured glow settings or change them on the go, each item you want to configure needs a duplicate of these parameters to keep the information synced, as far as I understand it.

VRCFury has a way to compress parameters, but... By how much exactly?...

For those still interested in "why", I will explain what I /think/ I know.

VRChat has "Expression Parameters".
Syncing these parameters has a memory cost.

Selecting I *may* be able to get away with not syncing, but each AL item would require a synced version, unless you want to disco alone.

I say "at most" because I haven't really looked into what the "receiver" component of this menu would require, really.

So this project is dead as fast as it started, and I now know why avatars with many AudioLink stuff to them either have few AL items or not much of on-the-go customization...