Troubleshooting

Troubleshooting

AMAI does not appear in game

• Install into a copy of a .w3m or .w3x map and select that exact copy in Warcraft III.
• Make sure the chosen script set matches the game version.
• Move maps out of Program Files or another UAC-protected directory before installing.
• If using local files, verify the registry/defaults setting and the correct Scripts location for the game version.
• For official maps on Warcraft III 1.30+, extract writable copies from CASC storage first.

The AI stalls at a tech tier

Custom melee maps must use the Melee (Latest Patch) data set. For custom units or altered prerequisites, update the chosen version's StandardUnits.txt and related tables, rebuild, and reinstall.

Very old maps may need to be opened and saved in a newer World Editor for full player-count support.

Commander does not open

• Install with Commander mode (1), not mode 0.
• Press Esc or type -cmd.
• Lua maps support only the startup language/game-mode selection. Convert the map's script language to JASS for in-game Commander commands.
• Scripted maps can conflict with the replacement Blizzard.j; disable Commander if the map depends on its own game script.

Installer reports missing scripts

Keep the release's Scripts directory beside amai-installer.exe. If building locally, compile the required target before running or packaging the installer.

Installer cannot modify a map

Close editors or games using the map. Work outside protected folders and check that the file is writable. An MPQEditor error code 5 normally indicates a permissions/UAC failure.

Large games lag or crash

AMAI performs more script work than Blizzard's AI. Very high player counts can exceed Warcraft III's per-frame script capacity. Use optimized scripts and reduce the number of computer players. The source scales some job intervals with player count, but it cannot remove the engine limit.

Warcraft III 1.29–1.31 problems

These versions are known to interfere with AI chat and hero skill learning. Upgrade to a current Reforged release or use a supported classic version when possible.

Strategy or profile changes have no effect

1. Confirm that you edited the same version/race you install.
2. Compile that version after saving.
3. Install the newly generated Scripts output into the map again.
4. Lock the strategy/profile in Strategy Manager to remove random selection while testing.
5. Check compiler output for malformed tabs, uppercase booleans, spreadsheet-added quotes, invalid identifiers, or a function called before it is defined/imported.