I asked him, he doesn't have integration for Behavior DesignerThat is likely the cause. I would ask the obfuscator developer as they have an integration with Behavior Designer and are familiar with the process.
Thanks,Interesting, I know that he used to but I don't see it listed anymore.
I haven't used the obfuscator before so I'm not sure of the workflow, but any object within the BehaviorDesigner.Runtime namespace is a potential class that you need to include.
Hey sorry to ping you again any idea why when I do build the tree will stop working? is it because unity code strip or something?Interesting, I know that he used to but I don't see it listed anymore.
I haven't used the obfuscator before so I'm not sure of the workflow, but any object within the BehaviorDesigner.Runtime namespace is a potential class that you need to include.
Hey thank you, I checked that and its seems that after I removed the obfuscator Its still doing it any change its unity code striping ?It sounds like the obfuscator is stripping out some of the classes. I would confirm that it works without the obfuscator, and if it does you can add all of the Behavior Designer classes to the ignored list.
Oh, i see thank you, is there link.xml ready for the behavior tree that I can use?Yes, then that's related to code stripping. You can use a link.xml file to prevent Unity from stripping the classes.