Hi,
I would not try to hard code this much, instead:
-- use dedicated transitions ( "MOVE TO STATE B") for example, and each state is responsible for knowing where to go next, but it has severe shortcomings...
-- use an array to describe the various paths and and have a sequence management that will control states transitions, use a convention that each state when finished has to call the sequence manager, which in turn will call the right state ( put a global transition above each state like "ENTER STATE A" and use "SendEventByString" to compose the event to send when you have to deduce it from your sequence manager.
- you could use templates and have several states/transitions for each different way and inside states you don't copy paste actions you run the right template.
Hope this shades some light on some ways