@Ironhide92 The actual error messages are logged in the debug.txt file, it would help if you quoted some of them or attached your file. However, some of the error messages logged do not contain enough data for
@Daedolon to effectively debug them, so don't get your hopes up for a quick fix. Most of the messages I see are not related in any way to what I'm doing. Instead, most of them are caused by the AI trying to get the girls somewhere but failing to do so. Fortunately, those error messages are only slowing you down, not making the game unplayable - they disappear from the screen after a few seconds.
@Daedolon It would help you a lot if you could log some info about the context where the error messages occur. The whole stacktrace would be best but it would cause the debug.txt file to explode in size. On the other hand, it's not enough to log the source code location, however, as the actual bug might be caused by the code calling the function. Adding more non-error log messages at different code levels might help here, although there's also some danger of log file explosion. You can mitigate it a bit using some global flags. Say the pathfinding code raises an error that it can't find a route somewhere. Let it also enable a global flag - which the AI code will check - to log the girl's name, location, and what she's trying to do. Next time the error occurs, you know much more about its context and you have a starting point for debugging. Such a flag could be created as disabled, never written to or read from the save file, and never cleared - basically, once you trigger it, it stays enabled until you quit the game.