it is up to the AI dev to decide that. if it is useless for him, he can ignore it.
i extended documentation for the event now, will commit soon.
i am always happy if people do such stuff on a spring fork, i will merge it in then. some AI devs did that already.
i know that it is not nice to have to use an API which is not well documented. but keep in mind, that i did not write the API either (i just rewrote it). You already know how many functions there are in the AI callback, and then there are also events and commands. I already added a lot of docu, and some others helped too, but i will not go through all the functions, events and commands, and check all the code paths behind them and all stuff they depend on to find every little detail that could be of interest to an AI dev, and write it into nice comments. i guess you understand that

i do not use these functions myself, so i do not know which are unclear documented.
Whenever you investigate the inner functioning of a function, because it does not act according to its documentation, please document it right, and give it to me (as said, best through a git fork of spring).
so next time someone uses it, he does not have to go through the same process again.
also, besides the Lua interface maybe, this si already the most well documented part of the engine
