... Of not failure.
Had an idea, implemented it, and it didn't work. Actually made performance worse. Could go in and tweak it around a little bit and try to change it into something that is just as useful, but at this point it's not really worth trying to salvage at this time.
So hooray time lost on that solution. Now it's time to lose time on other solutions!
Just kidding. I'm going to ignore motion between nodes in a path and focus solely on the nodes in the path now. That last bit was a moonshot in order to save processing power. Now we're just back to content variety and maybe poking at the movement functions to maybe save a couple cycles here or there. No guarantees there, though.
