Hi,
I am not sure where your issue is, but the following might help:
-- if you have more than one similar component on the same gameObject, Unity will pick the first one, that's not something PlayMaker can have control over. simply do not have twice the same component if you are planning on a framework using templates that access a gameobject to get to a particular component programmatically. That would be one "rule" for your system to work. and that's fine. I hardly ever need two similar component, especially within ngui and other 2d framework.
-- are you properly setting your FsmObject initial type? if you are doing all this within fsm logic, getting a component from a gameobject will only be useful if you make it of the right type in the FsmObject that will receive it.
else, can you elaborate with a concrete example?I'll then come up with something.
bye,
Jean