If you are not playing campaign/UMS maps than you can just continue and ignore the warning. When BWAILauncher compiles the selected AI scripts, it loads its default aiscript.bin and bwscript.bin (located in Libs/MPQ/scripts/), and puts the compiled scripts into them, so as to keep all other default ...

Very interesting read, and some great work your doing there!

Thanks for the heads up!

The first issue will depend on the GRP, but I'm guessing most will be the same issue: being compiled slightly incorrect. The one you uploaded has frames with some pixel lines that are wider then the GRP so I reject it. The fix of course is just ignoring the extra pixels instead. To do this open GRP....

I believe there is a Firegraft EXE edit to fix that glitch (i believe its called something along the lines of "idle worker glitch" or something), and that is the reason Entropy 3 works.

Well at the moment I have no idea why it would be crashing, but one thing to note is that the AI's included in BWAI Launcher don't improve the campaign AI (or at least they don't improve a lot of the maps, which have their own specific AI's), so there is no reason to play the campaign with BWAI Laun...

Try following and replace Chaos Launcher with the high res launcher.

I don't know why your thing is crashing, but I know some about the Type's. Afaik the Type only defines how many of the header items (things between .headerstart and .headerend, other then IsId and Type) are included. The possible header items in order are: Init Death GndAttkInit AirAttkInit Unused1 ...

Wait... The scripts in the backup are the selected ones? Then you selected the wrong mpq in step 4, you were supposed to choose the patch_rt.mpq not the backup patch_rt.

[quote name='Taranok' date='01 January 2012 - 05:05 PM' timestamp='1325455506' post='10556'] I followed the instructions to link it with Chaoslauncher. I closed and reopened BWAILauncher. I hit OK with the selected AIs. It launched Chaoslauncher, and then I hit start from Chaoslauncher and Starcraft...