Well, i'll let you know as i keep using it.
My current use-case is for a card-like game.
One thing i am noticing is that i need to loop over data all the time, and i'm not sure if using a FSM to create my looping constructs is really the right way to do it . I'm worried that i'm creating states which are really more akin to functions, rather then a "state" of the application.
I think that i need to move some of the logic out of the state itself and into a script, and then use "Invoke Method" to actually do a bunch of the work.
Perhaps i should ask for a Loop Action
 - I have a State which does some work. It then increments and checks a "counter" variable. If the value is less then X, it fires a "continue" event, which is routed back to itself. If the value is equal or greater then, fire the "FINSHED" event and continue on. Love to hear of other ways of doing this kind of thing.