Fix the problems maps hit most
Each guide covers what you see, why it happens, how to fix it by hand and which of our rules catch it. Written from our lab notes, with the sources linked.
Map crashes on the loading screen
The game closes during or right after the loading bar. The usual causes, in the order to check them.
Old map stopped working after a patch
Maps from 1.26 and earlier break on newer builds for a handful of known reasons.
Script errors on 3.0: names that clash with new natives
3.0.0 added natives with common names. Maps that already used those names stop compiling.
Players desync at the same moment every game
A desync means the clients disagree about the game. Find the code that runs differently on each machine.
Lag that builds up over a long game
Frame rate falls after 30 to 60 minutes. Usually it is leaked points, groups and effects.
The World Editor can't open the map
Missing trigger functions, invalid object IDs, damaged archives and crashing imports.
Map too large to host or download
Size limits by patch, and how to slim a map without losing what matters.
Imported model is invisible or a checkerboard
Texture paths, model paths, animations and file names: what makes custom models vanish.
The map loads, but nothing starts (or it freezes)
The operation limit, endless loops and UI created too early.
Lua map errors: FourCC, the percent sign and integers
Three mistakes that stop Lua triggers or crash the editor, and their one-line fixes.
Reading War3Log.txt: what matters and what to ignore
Most lines are noise from the game's own files. How to find the ones about your map.
Problem not listed?
Ask on the Discord with the map link and what you see. Common answers become new guides.