Ah I misunderstood; I thought you meant right click the layer in the layer properties, not the actual layer itself. I got it to work for a new sprite I tested, but I can't seem to find the one I'm having an issue with, and it seems I'm not creating it anywhere in the event system. I'll just resort to deleting the object and recreating it for now.

Thanks for both your help!

— - the way the pathfinding behavior works is that it has to search the entire map when created or enabled. Because the layout is over 16k by 16k, it takes about 4 seconds on creation. So if we had 50 enemies each with their own individual pathfinding sprite, it would take a few minutes to load the game. (and before you ask, the game is a very small pixel scale, so that amount of memory shouldn't be a problem).

Things will be dynamically created and destroyed in the end, so the best way I figured to have pathfinding in the game was to only have 1 object generate the map and just link each pathfinding sprite to any sprite that utilizes it (enemies, your dog, etc.) Hopefully that makes more sense?

Also, side question; what looks dangerous every tick?

UPDATE: Also, confirmed - it is not selecting the appropriate sprite on the UID check. Not sure why, though, the numbers match. I've been having a lot of issues with integers and strings ever since I switched to the new runtime.

NoSoul8 - nah that didn't work. Disabling that wouldn't; it would also break more things below that line (that have nothing to do with pathfinding). I'm wondering if just the more pathfinding objects on screen, the less it's able to find a path and stick to it?

I've narrowed down the problem to the pathfinding object triggers. (on path found; arrived, etc) It's not pushing the booleans to the sprites. Not sure why, though - it's literally picking a UID by an instance var.

I'm trying to create a "pathfinding" sprite that can be used and pinned to every enemy that requires it (essentially only ever having ONE pathfind sprite for every enemy, npc, etc. in the game).

For the absolute LIFE of me, I cannot figure out why this incredibly simple few lines of events aren't working:

...and the function it's calling:

For some reason, only one pathfinding object is moving at once. (ie if there are multiple flies on the screen, they all just sit there updating the destX and Y)

Am I missing something?