1) Use SC2Launcher 2.3.1
2) Delete everything inside \Plugins\
3) Copy your AI to \Mods\AI Name\TriggerLibs\
4) Select your AI as Mod in the launcher

Notable Code changes:
1) AICombatDiffFlagCatSpecialHighPrio, etc.
2) c_diffHoldAtIdleChokes, etc.
3) AISetMaxBestAttackersLimit
4) AIDefendTown  => AIDefendWithWave
5) c_PU_Sentry, etc.

Su, after discovering the changes, did you notice if the AI Engine had changes? Does it still use the same states method? How did you initialize the AI and run the states?

would you like to share your AI then?

@SuXue, thx for the tips, it working for me, now I can try all the new blizzard function code  :jig: , just tried the AIMapPathCost ( it help to find the shortest path between point ).
 P/S: The AIExpandDefalut is dead now, try the AIExpand function.
 
@AlsoKnowAs : His method is good, actually. The problem is not because of the launcher but because every native function of blizzard has some slighty change. My advice: rewriting your script from the beginning, which I am doing now from the Blizzard default AI code. Also you can test new function and improved your AI much more.

ptanhkoa,

what I've been saying is that how can you make the  launcher recognize our AI? I've tried launching SC2 Beta with the  latest patch and the default AI (from Blizzard after updating) with  slight modification (adding a line of TriggerDebug) to make sure that  the AI is actually modified, however when I ran the AI with the slight  modification, it shows no sign of changes.

And as you've  mentioned that there are new functions, how can the native.dll from  SC2Launcher 2.3.1 recognizes the new ones that are written by us  ?

Besides then deleting the plugins from the launcher, is there any additional steps that I've missed out because I can't seem to get it work still  .

Edit: ...