I think what Ello said is right, especially for people who have been using c-script for many years and are now starting with lite-c.

i am just really starting to understand c-script, so the new manual solutions is confusing, because some of them are lite-c and i dont understand why some of my scripts dont work properly. they should be seperated. two manuals. its really not fair to the people who dont wish to go to lite-c. i am a poor man, and i dont have money to convert, and i dont think i should be forced to, after i spent my money on the version i have now.

Alright, so it would be good to have both in one.
I agree with that, but as it is today it is definatly not the best solution.
As there are sometimes Lite-C examples, and sometimes not.

What about making an open documentation project?
(using the wiki)

EDIT:
Ok, I started to port the manual to the wiki and added a link to it on the main page of it.
This is a direct link:
http://www.coniserver.net/wiki/index.php/Documentation

I would really appreciate any hints and any help with this.
Sure it will not replace the "real" manual, but might be a good place to write down some tricks using Lite-C and C-Script how to avoid ugly code or any comments to certain engine functions.

Thanks

Thanks for the new Wiki link. Yes, of course we'll convert all manual examples that are still C-Script eventually to lite-C. However there are several hundreds of them. A full conversion takes its time. Even though usually only a <..> must be replaced by ".." and lowercase must be replaced by uppercase, all the new examples must be tested. I suppose when A7 reaches version 7.10 or 7.20 the manual won't contain any C-Script style anymore.

Thanks, although I find it just confusing enough.