HotFix for #1764

The way I fixed this is by allowing the paths to be loaded at server boot even when the config option is set to False. 
My preferred fix would be to not start the AI timers at all if the config is false.  However, in that case the NPC would need to be reloaded should a GM //set the option at runtime, and the paths would also need to be loaded at that time.
With this fix, if a GM uses the //set command to enable the walker npcs during runtime, the NPCs will just start walking as soon as their timer fires.
This is not very clean, nor very efficient, but it required the least amount of work, fixes the crashes, and has the above advantage of dynamic setting with no additional overheads...

PLEASE MAKE A MORE PROPER FIX!!

L2_GameServer_It/java/net/sf/l2j/gameserver/GameServer.java

@@ -334,8 +334,8 @@ public class GameServer
 
 		
 //		L2EMU_ADD by Rayan. L2J - BigBro
-		if(Config.ALLOW_NPC_WALKERS)
-			NpcWalkerRoutesTable.getInstance().load();
+		//if(Config.ALLOW_NPC_WALKERS)
+		NpcWalkerRoutesTable.getInstance().load();
 		//L2EMU_ADD by Rayan. L2J - BigBro
 		
 		RecipeController.getInstance();