The plan is supposed to be a standardized way of describing the progress of a Reactive Fastmap service. Therefore the naming is important so that the first and the last state is recognizable as well as having a "self" component that shows the overall...
Sorry to say that this is an known issue that needs to be resolved in a future release.
There is an undocumented feature in the behavior-tree to use a plan-location i.e another path for the plan, which then will need to be created and maintained. Thi...
