Hi,
you'll need to remove all the use of "Get property" custom actions to remove the need for reflections.
I am afraid this is the only way.
What's your use of Get Property, I may be able to write a custom action for you to solve that issue.
bye,
Jean
Heads up: I solved this for nowThank you!
I didn't use set property, but hundreds of get property in my game scene. Luckily in general, they do a same thing-- get a component from its own GameObject.
I put a script named Expose on each AI character to expose property such as ID, HP and some calculate result(like predict fighting advantage ) to PlayMaker. Those property can be set by both my script and FSM.SendMessage(). I find it in this way, Script and FSM can co-op with each other easily.
What I did is pretty simple, I drag Expose component from the editor inspector to PlayMaker Editor and there will be a GetProperty, then I store this component as object variable in PlayMaker. So I can use GetProperty to get whatever property I need in Expose and store it as variable.
All types I used in Expose: int, string, bool, float, vector3.
If you can help me, I will really appreciate this!
BTW, after review PlayMaker files, I find that compile problem may relate to FsmProperty class' refs. But I don't exactly know what is missing in .NET subset compare with full .NET.
Is it possible to fix the compile problem in short time?