When searching through the manual there are often situations where there's either just the Lite-C version described (e.g. Views) or only the C-Script version (e.g. portal_x).
It's a mess! Maybe it would be better to either finally get rid of the C-Script stuff officially or split the manual up into two parts.
I wonder how newcomers can work with the manual currently - it must be very depressing to get different working and non working information (depending on which script language you use) all the time.
I know, this is a lot of work, but currently the manual can be pretty confusing at times.
Re: Lite-C vs. C-Script
[Re: FBL]
#166917 11/11/0712:0411/11/0712:04
i dont agree in having two separate manuals, because sometimes you know how you did it with c-script and its cool if you find the lite-c version there, too. this is mostly the case but it should be everywhere, thats true
Re: Lite-C vs. C-Script
[Re: ello]
#166925 11/11/0723:2111/11/0723:21
Found it very confusing too sometimes! I think if there is no more changes made to C-Script why not remove from the manual and put it another CHM. Right now the manual claims it is Lite-C syntax, but everything is mixed. Also fixing the many syntax errors, adding more examples on the new engine features would be nice.
I would not mind if C-Script and Lite-C are inside the same manual, but then it should be made clear what is what. Right now it's done with either a comment or with color green/red. Not always though..