THE MAJORITY OF AI PROBLEMS WITH AI ENCOUNTERED ON WINDOWS VISTA/7 ARE CAUSED BY UAC.
IF YOU ARE HAVING AI PROBLEMS UNDER VISTA/7, READ THE FIRST ENTRY UNDER VISTA-RELATED PROBLEMS BEFORE POSTING.
ALL PLATFORMS:
Problem: Receive message "cannot read .\AI\AI.lua. there is no such directory or file" when attempting to use homun, or "cannot read .\AI\AI_M.lua. there is no such directory or file" when attempting to use merc.
Solution: Your default RO AI is missing or has become corrupted, OR you're having Vista/Win7 UAC problems (See below section)
Download the basic AI from here: http://downloads.iro.../Default AI.zip
extract it, and copy the following files from the AI folder in the downloaded default AI into your AI folder:
AI.lua
AI_M.lua
Const.lua
Util.lua
Problem: Receive error messages upon attempting to use custom AI in game, but not an error referring to callback.lua. If you are running vista or windows 7, and the AI is installed correctly, see the problem in vista section.
Solution: The custom AI is not installed correctly, or was supplied in a non-working form by the author of the AI.
Ensure that you have the lua files inside the USER_AI folder, not inside a folder within the USER_AI folder.
Your AI and USER_AI folders should look something like this:
Problem: Receive error message(s) when attempting to use custom AI configuration program.
Solution: If the error messages refer to .Net, VB, or runtime, or specify a missing .dll file, you are missing a required runtime library.
The AzzyAI control panel requires the microsoft .Net framework, available at:
http://msdn.microsof...k/bb264589.aspx
Other AI control panels may require the same runtime libraries, or a different one - review documentation or contact the author of your AI.
VISTA/7 SPECIFIC PROBLEMS:
These usually occur under Windows Vista and Windows 7, when User Account Control is enabled and RO is installed to the default installation location, C:\Program Files\Gravity\Ragnarok Online.
Problem: Custom AI is installed properIy, but still behaves as if it was the default AI. No amount of changes made in the USER_AI folder seem to effect AI behavior.
Problem: Receive error "./AI/USER_AI/AI.lua:3: could not load package './AI/USER_AI/callback.lua' "
Problem: AI is installed correctly, and is working, however, no amount of changes made using the GUI effect the behavior in game. Making changes directly to the config files may or may not work. Or, AI is installed correctly and working, and changes made using the GUI effect the behavior in game, but manually changing the config files does not change the behavior of the AI.
Problem: Receive error "cannot read .\AI\AI.lua. there is no such directory or file" or "cannot read .\AI\AI_M.lua. there is no such directory or file", however, AI.lua and AI_M.lua exist in the AI folder.
Explanation: Vista and windows 7 place special protections on the program files folder (and all subfolders) as part of the User Account Control (UAC) functionality. Vista/7, with UAC enabled (the default setting), changes made by programs (instead of the user) will be made to a virtualized directory ("UAC Virtualization") within the user space, even if the program has permissions to write to program files.
Some versions of the client came with a defective AI which produces the callback.lua error - in this case, the defective file will be the one that gets preserved by vista's stupidity.
Because of these protections, settings saved by the GUI can be piped to the virtualized directory while the game is looking at the non-virtualized directory, or vise-versa.
Solution 1: Move the ragnarok online folder to another location on the C: drive - i recommend making a folder C:\Games\Ragnarok . Delete the AI folder and restore the default AI from the link above. Reinstall the AI.
Solution 1b: Failing that (it is quite possible that just moving RO will not work), uninstall RO, and reinstall it to C:\Games\Ragnarok.
Solution 2: Disable UAC (User Account Control).
http://www.howtogeek...er-account-c...
You may have to delete the USER_AI folder, and then make a new USER_AI folder, and install the AI into that.
Problem:
AI Configuration program for MirAI or AzzyAI gives an error message, saying that files cannot be found, or that access to files was denied.
Solution:
The AI configuration program must be run as administrator. This may not be necessary if UAC is disabled.
AI BEHAVIOR PROBLEMS:
Problem:
AI generally, with some features working and others not (AI is definitely custom AI, but not doing what it should) after switching from another AI.
Solution:
Delete all files in the USER_AI folder, including those from any previous AI's used, and reinstall the AI. Simply copying all the files for the new AI over the old ones should work, but i keep getting reports contrary to this. May be a vista/7 related issue.
Problem:
Tactics or monster specific behavior does not work for mercenaries.
Solution:
The client does not provide the facilities for mercenaries to identify different kinds of monsters. Some AIs, including AzzyAI, can differentiate between "natural" monsters and those summoned by some unnatural effect (mobs summoned by other monsters, alchemist flora and plant cultivation. Some AIs also attempt to detect 'herb plants' in order to avoid wasting time attacking them.
AzzyAI supports a very awkward workaround as described here: http://forums.playra...w.asp?tid=15857
Problem:
Mercenary bugs out after using bowling bash.
Solution:
This was a bug that occurred with version 1.27-1.281 of AzzyAI. Upgrade to 1.282 or later.
Problem:
After teleporting, player is sometimes disconnected.
Upon reconnecting, the mercenary immediately leaves.
Explanation:
Mercenary Actor ID's change every time they spawn (which occurs on teleports and map changes).
Because the Actor ID is a part of the packets sent by the client to control the mercenary, latency can result in the following problem:
If a player teleports, and the merc attempts to do something before the server receives the teleport packet, it is possible for the player to have teleported (giving the merc a new Actor ID) before the server receives the "merc do-something" packet sent before teleporting. This packet will refer to an incorrect Actor ID. Since it is not supposed to be possible for the client to send such a packet, the server assumes that the player is using an illegal client or AI and punitively disconnects them and ends the mercenary contract.
Solution:
Don't teleport while lagging if you are using a mercenary, or put the mercenary into standby before teleporting. Yes, we all know this is a major hardship, but that's what happens when the developers try to "punish" players for doing something that should be impossible (ex: DC on moving while talking to npc, AV bug, etc). It is also worth noting that even when lagging, most players will not encounter this bug.
Edited by DrAzzy, 02 February 2011 - 08:54 AM.
