I just wanted to thank all on the forum who've hopped in to answer when I have a question! I'm always reminded how much more helpful dedicated old school forums are compared to things like reddit. Honestly, if I didn't feel like I had a reliable place for guidance with AGS, I'd probably lose steam and stop. So thank you, really! :-D
I've been trucking along with my game. It was just the main controls and text I needed to sort out. Everything else is relatively clear between the manual and tuts. It'll be a while before I get to the next point that I already know I'll need to ask about, but I know you'll be here ready to drop that knowledge when I do!
That's all I wanted to say but I don't think I can post a thread here that isn't a question so I thought of one. Is compatibility an issue with modules? I'm not looking to use any this time around since this is meant to be a learning experience where I script as much as I can from scratch.
But I do wonder if they're made in a way where using a different version of AGS could "break" them? Or would it just be if script in the modules becomes obsolete?
The script may be version specific, but currently AGS is backward compatible, which means that you can enable old script functions. This is done in General Settings -> Backwards Compatibility section.
https://adventuregamestudio.github.io/ags-manual/GeneralSettings.html#backwards-compatibility
If there are only few old functions used, they may also be replaced with the newer alternatives using following table:
https://adventuregamestudio.github.io/ags-manual/ObsoleteScriptAPI.html
Ah, cool! Thanks so much! That table is a great resource for keeping things current. Modules really do seem useful. A lot of things I considered doing, there were modules for. I just figure if I'm gonna learn, I might as well go full in, but I'll certainly make use of one if I decide to do something that would just be a nightmare for a newbie without it.
You can also use them as a learning tool, after they're just AGS code. ;)
True! (laugh)