Hi
Yeah… this is a slightly buggy behavior. I actually discovered that enabledTags on the path was not being set to seeker.traversableTags when a multi target path was started last week when I was cleaning up the Seeker code a bit. I added this comment and a note in my todo list.
// TODO: This method does not set the enabledTags or tagPenalties
// as the StartPath method does... should this be changed?
// Hard to do since the API has existed for a long time...
I think that in the next update I will change this, potentially adding an optional flag to the start path methods which specifies if those fields should be set to allow users to turn it off. It would be a breaking change, which I do not like, but I guess it is better than this inconsistency.