Hi All,
Let me clarify here to remove the confusion. Proton got it right! I'm referring to categorizing actions applied to each state. And it is not always practical to split everything up into multiple states. For example, lets say that you want to click a button that triggers an animation, plays a video with sound, activates 3 game objects and deactivates 3 game objects. Currently, just to play a video with sound you have to assign three different actions (play movie texture, set movie audio, play audio). Triggering the animation is another action and finally each game object that requires activation or deactivation requires it's own action. Now, since I cannot create and name a folder on my state I'm stuck with 10 actions on my state... all of which cannot currently have custom names. And this is only one button! I have like 20 buttons to code in a similar fashion. I'm in the process now of building a complex animated 3D video player with a multi-level table of contents. All the buttons are 3D buttons (Maya files with animations for button press and release). The TV screen animates in and out of view. As I have progressed through this project it has become harder to deal with in terms of trying to remember what all the various actions are for on each button state.... some buttons pause a movie, some play a movie, some play a different movie, some stop all movies from playing or pause all movies from playing and animate a new set of buttons onto the screen, etc. Also, even though for example the action is titled "Play Movie texture" that still doesn't tell me which movie texture is going to be played. I have to expand the little triangle and then click on the texture button to find out what video is going to play. Now imagine that you are going to be have a series of buttons all of which will be playing different videos when pressed and pausing different videos when pressed. PlayMaker starts to get really difficult to manage when you have move then one or two actions assigned to a state.
Specifically, what would be useful to me is to be able to create a folder on a "STATE" and give that folder a custom name such as "Play Intro Video" and then drag and drop all the actions associated with playing that particular video into that folder (play movie texture, set movie audio, play audio). Then I could create another folder on that same "STATE" that says something like "Pause all other movie textures" and I could then drag and drop all the different Pause Movie actions I have into that folder. The list could go on an on but I think you get the idea now how these folders on states could be really useful and require the use of less states.