Funny effect with ExecuteFunc in AI

Previously I thought that ExecuteFunc just does not work in AI. But that is wrong.
In fact it just looks in the wrong context for the function to call.
That means you can use ExecuteFunc in AI to call functions from the trigger sphere like functions in Blizzard.j and the map script.

Thats is interesting, But I thought you could always call funcs from blizz.j in the ai.

Anyway more interesting would be if there could lead to some trick to being able to call Common.ai functions in the map script.

Question: Can I use gamecache in AI?

Yes, gamecache can be used in AI. In fact it is even the same gamecache as in trigger. That is why I use it for communication between AIs and triggers. Only the string returning gamecache native does not work as usual.

But there is no real way that I can use to communicate in real time (i.e very small wait timer of 0 or so) the cost of a unit is there?

Not that I am aware since the ExecuteFunc bug works in the other way unfortunately so for the price of a unit all that remains is polling and that takes time.

Bleh then its a pipedream wait for them to add the cost triggers into common.j