I thought I’d give a little update on the update. I feel a bit bad about it taking so long to get done, but know that it is not because I am not working on it. In fact it was pretty much done a couple of weeks ago when I suddenly found a much better way to store and use edges for pathfinding.
I had my mind set at that point not to be tempted to add any new features to this update and just get it done, but I felt I had to make an exception in this case. I had already made changes to the way edges are handled at this point, so any users who wanted to update would need to update this part of the toolkit in any case.
However, since I know I would then be changing this part of the toolkit again in the following update this would mean any users would have to modify their projects twice. Therefore I’m implementing my latest ideas already in the next update.
This will make pathfinding even faster and will be a lot easier to work with. It also looks a lot cleaner and takes a lot less space. To give an example this is one of the new toolkit functions before my newest changes to edge arrays (this you will now never have to see again):
Here is the same function with my new solution for handling edge arrays:
I hope you can agree that this is a worthwhile excuse for delaying the update a bit 
I’ll try to get it in your hands as soon as I am able.