Closed Luashine closed 2 years ago
Hell yeah I won't say no to gratis documentation! I assume we should simply use one common.ai
file and not split it up like common.j
But I'm open for any kind of suggestion or request for help.
If you say yes, I'll commit it as a single common.ai.j
file in first commit and then add his docs.
Let's use common.ai
I think. There already is a common.ai file in here with all the non-common-ai usable natives. I would simply replace the file and add the old and the new documentation.
Is the @commonai
tag used/unused, what should I do with it?
Is the
@commonai
tag used/unused, what should I do with it?
I'm currently using it to signify that a native was defined in common.ai but still is usable if you import into your war3map.j So I'm open to change that tag if anyone got a better name but for now I would simply just tag the same natives, that is natives which work in a normal map script.
With moyack's permission I wanted to move the few previous contributions remaining on his website to here. There's one minor problem: Starquizer dedicated most of his work to the AI natives. These aren't tracked by this jassdoc.
Would you add it? Attached version 1.33.0.19203 (changed file extension due to github restrictions) common.ai.txt