Hi.
I made a prefab that uses some inspector variables used to assign GameObjects from the scene. I later modified my prefab adding a new GO variable and it messed up the variables assignment of my scene.
I noticed this happens if my new variable goes previously to the other one in the automatic alphabetical order. It looks like playmaker identifies the variables through their number in the list.
For example: my first variable is "Target" (currently n1). It's public and Used in scenes to assign gameobjects in the inspector. Then I add a new one named "missile" and, because M goes before T in alphabetical order, "missile" will be n1 and Target will become n2. In the inspector, I will end up with "Target" losing it's target and "missile" having them if public.
Note this as no influence in the playmaker editor but messes things up in the inspector.
So far I mananged to avoid the issue by adding up variables with a name that goes after like "zMissile" but it's easy to forget and screw up a game badly while working.
To avoid that I think an easy fix would be to deactivate the alphabetical order and leave the variables in the order they were created. This way, whatever is n1 will keep that ID and so on.
I hope that will be as easy as I describe. ^^'
Thanks.