Saving/Loading, Cutscenes, and AI

#1 Saving and Loading must be done in code, mainly because you know what your game's scene objects and states are. Those are what you need to read/write to a "save file". Kind of a like a mission file, but more concise and related to directly manipulatable objects.

Are you talking about mini-movies using in-engine graphics or using a video file?

AI is script intensive as well since behaviors must be scripted.

#2 You do not have to code Saving and Loading in C++, I did it in script back when I didn't know C++ at all and it worked fine.

AI does not have to be script, either. (I did mine in C++) But those are good guidelines. :)

#3 Actually, using fileobjects in TS is not hard as long as you know what data you need to save and update. If you want to pack and encrypt that data, then you'll have to do it in C++ with an external library. I'm a complete idiot when it comes to AI, though. But I know of several scripting and C++ solutions of varying quality and measure. It just depends on what you need. If you are making a basic platformer, then your AI requirements will not be heavy, but if you are making a tactical shooter...well, then it gets sticky.

#4 Well your ai will need sensors, if you dont already know about them use raycasts and radius search.

#5 Thanks guys, that helped!