This is very unintuitive IMO. If I create a behaviour tree and I work on that and name it “DeerBT” it’s because I want to be able to quickly select it from the hierarchy. If, at some point, I decide to use this tree also as a nested BT in a FSM, NC should never change its name (especially without asking) because a) “it ruins my plan” and b) I could have referenced that tree by name in some of my scripts and it wouldn’t work anymore.
With no offence 🙂
I also noticed that on the other hand, a nested FSM node in a BT doesn’t work that way. It works as I would expect.
So I changed the code in FSMNestedBT.cs at line 131 to this:
nestedBT.graphName = EditorGUILayout.TextField(“Name”, nestedBT.graphName);//nodeName;
etabubu
