AZSlow

.

I think that's a very good approach "general rule wise"!!! Thanks Alexey!!!

My general rule - what works is "right" (even when something looks a bit ugly...) 

This worked...should it have?

1=.500
2=1.00
3=1.00
4=.800
5=0.00

Make "_3states" with 5 states. That will be sufficient to distinguish between 0.5, 0.8 and 1. In conditions use 3,4,5  (currently 1,2,3). And set 0.8 instead or 0.0 in corresponding Value action. The order you regulate by changing which value you send in which state.

Slowly getting there. 1= .500, 2= 1.000, 3=0.800. (According to the Overview tab).

If I set the switch on the GUI to state 1 and flip the button it now cycles from 1 to 3...but does not flip back to one (or reverse cycle if it can't flip back to 1). Once the sequence of moving it through 1,2,3 is done...hitting the button does nothing. There's three of these within this one plug-in. If we get this working I'll copy those additional Action List steps to the other parameter.

Now weirdly, if I'm reading this right...in the Overview tab open and with the Current Value line inserted in the actions list...it "looks" like flipping through the states that 1=0.00, 2=0.50 and 3=1.00, which makes sense in my head but the only way I could get the switch to move in the GUI via the controller was 0.500, 1.000 and 0.800 respectively.

After "Track Volume" (in example, so after you have selected parameter in question) insert Action "Value Current".
Now set the switch (in GUI) to the state you can't change to. Press your button. Open "Overview" Tab.
You should see "Current, timeout touch -> X.XX". The value is from 0. to 1.. That way you know which value you need.
Then calculate the number of states you need, with 3 it covers "0 - 0.33, 0.33 - 0.66, 0.66 - 1", with 4: "0. - 0.25, 0.25-0.5, 0.5 - 0.75, 0.75 - 1.".
I hope you have got the idea

These things are tricky, I know. But you want "trick" the DAW and plug-in, they have not foreseen such behavior and so there is no simple way.
BTW there is right way for plug-in and DAW to implement 3state switch parameters, describing what they are in VST API. But almost no-one is
doing that. BTW if you have 3 states and values are from 0.0 to 0.1, is that not "logical" to use 0, 0.5 and 1 for them? For some reason plug-in developers not always think logical...

Yes...so I created the 3States in Options-Software States tab then added the Logic Action List items you had in your example to the button I'd like to use. So now...it cycles between 1 and 2 but does not go to 3. I'm going to assume that's might be what you were referencing above? I'm not sure I understand how I would determine what value either the plugin or Cakewalk assigns to the 3 states? Is it playing around till you find the right one? Does it move numerically from L-R and low to high?

Maybe interesting questions considering where I was with AZController 2 weeks ago lol.

Possible. Example attached. But it may be dependent from numerical value each attack speed has, f.e. in Cakewalk such "switches" are not always homogeneous in value (so the third state may be not 0.5, and so map to unexpected state, more states in the map are needed then).

But you are moving toward "advanced" use of AZ Controller, not sure "a couple of minutes" is sufficient to do that 

Had a couple of minutes to mess around tonight.

If I have within a plug-in a 3 way toggle switch (lets say for a compressor attack speed of: F/M/S). I'm using one of the rotary encoders push functions. Right now, pushing that encoder with toggle applied...it cycles from F then S, but can't get to M. Is there a way to have that encoder button push cycle through the 3 options. Press after S and it cycles back to F, then M, then S, then F and so on?

Thanks!
-c