
Last week I ran into a completely new problem, which may be interesting to mention here.
As part of development, I have always had a number of additional Unity projects for experimentation. Trying things in isolation usually means that A) I can assess a new system or function by itself first, which tends to be easier to implement and shows me how it would work without competing mechanics, and B) means that any problems I create (trial and error tends to lead to quite a bit of error) stays contained within its own project, and I don’t end up breaking the main game with it. Or so I thought.
Last week, I ran some experiments on the pathfinding plugin Path to Prosperity uses, seeing if I could optimise performance and improve the way units run toward each other at the start of combat. As usual, I set up a new project, imported the third party pathfinding tool, updated it, and worked on it for a little while. Unlike usual, I found that the update had broken the pathfinding in the regular Path to Prosperity project when I switched back.
There is no obvious reason to me as to why this would happen. Files should not be shared between the two project folders, and updating one should have no effect on the other. Fixing it was not straightforward either. Where usually rolling back any changed files, or biting the bullet and updating the main project as well should be easy fixes, neither of them worked in this case. There are a few more ideas I have for how to diagnose the problem and try to fix it, but this was a curveball I certainly wasn’t expecting.
I will keep you updated.
Until next week!