For a future subject, I'd be more interested in managing the actual code of any game. How does one correctly handle objects and structures, and the functions that control them? How to separate view from control and model efficiently with lite-c and what code samples are handy to use right away (for example, a linkedlist, hashmaps, garbage collectors...). Handling pointers, preventing memory losses, adding efficiency and optimisation are subjects where I'd like to have a broader view on.
Even trying making a correct division of your code over your files bring issues and nasty problems.

hehe PrenceofDarkness, believe it or not, i'm already working on multiplayer video tutorials. i'm working on several lessons. the goal of that mine tutorial is to teach you how to create fast paced shooter over internet/LAN

i'm sorry i hijacked your thread like this but i though you should know this. i wont have anything against you, making anothere MP tutorial cause more of them is done more people will start programming MP. or you could concentrate on some other area of programming in 3dgs? whatever you choose i wont mind

Thanks for the heads up cerberi_croman. I'll probably go with something else then just so we don't compete.

fair enough

Quoting Joozey.

:highly pseudo-seconded:

If given the option, 'I' would almost certainly choose to read* such material over not doing so.
'I' am roughly familiar with, but not an authority on, such subjects, (and certainly less so in the domain of Lite-C,) otherwise 'I' might attempt to put something together for free distribution.

This might be a good candidate for "new topic" or old topic revival.
(not a guarantee of participation)

do u no what i would like princeofdarkness? i would like a free sample video bout 5-10 min vid of showing the basics of using the engine physics then showing people the advanced stuff like football game or doing the crash physics on a car(i would like that)

hey one question though, for all of you. now it came to my mind...would you like a tutorial where i talk about, and explain the code, add some of it or would you like a tutorial where i write whole code real time?

I think it would be more enjoyable to have you talk about and explain what you are doing rather than watching you type in code ... because if you talk while you type in your code then it will be somewhat tedious to follow the tutorial (after all, it's not a tutorial about typing in code )

Cheers,
Andreas

no you missunderstood me. ofc i will explain and talk all along but do you want me to write whole code or take for example finished game code and explain it and add some small parts of code not to type everything?

1. typing everything?
2. typing little and explaining already created code?

I thought this was prenceofdarkness's thread?