Ok, guys, thank you very much for all your great help!
Anyway, I found a way to debug my AI scripts and also discovered some other related things, maybe this could be helpful for someone else, so let's try to summarize:
- AI scripts cannot use functions from blizzard.j, but can use functions from common.j. If you need to use a function from blizzard.j, you will have to copy and paste it to your .ai file, and probably loose your mind before you find and copy all other necessary parts too (like global variables, helper functions, etc, etc) and finally make it work.
- There is also the common.ai file which contains functions used by AI scripts, but which cannot be used by triggers.
- It proved that finding these three files on the net is not such an easy job. If you need them, I can post here if that is allowed by forum rules.
- The easiest way (as far as I know at this moment) to debug your AI is to use DisplayTimedTextToPlayer(Player(observer),0,0,seconds,message), where observer is the slot number minus one of your player (either who you control or the observer). Messages are not only displayed on the screen, but in the Message Log (F12) too.
- Many functions that can be used in AI scripts (and which compile successfully) simply do not work. The most notorious example is the I2S function, which returns empty string instead of the string representation of a given integer.
That should be enough from me for now according to the interest my posts get here.
Looks to me like Blizzard made very sloppy programming environment for users, and that it is the main reason why they do not provide any support. Good luck!
