Projects
| AGS Documentation | AGS Manual | weblinks to tutorials, wiki etc. |
|---|---|---|
| Cerno | One of the big hurdles I had to clear when starting out with AGS was the realization that despite its professional and highly mature looks, there are a number of issues under the hood that need to be resolved through scripting. The main problem for me as a beginner was to realize that some functions that I assumed would be supplied out of the box for a great-looking tool like that had in fact to be written manually. Sometimes it was not very clear what exactly was supplied by AGS and what I had to script myself. Now, one thing I think could greatly smooth this process for the beginner could be a link [b]"further reading (www)"[/b] under the more important topics of the manual. These links will lead to special wiki overview pages which themselves lead directly to wiki entries dealing with the issues in more detail. This could be about supplying script snippets or just more in-depth explanation about e.g. the pitfalls of blocking actions ("how do I start a dialogue after a scripted scene?"). Another thing I would find helpful is a short list of what works, what doesn't, and what could be solved better differently. To populate the corresponding wiki pages it might be a good idea to look through the forums or even better ask the regulars for questions that have been asked more often. It would even be possible (but probably overkill) to search the forums for the commands in the manual to find issues that confuse people. Is there a policy against weblinks in the manual or would this be a possibility? What I like about the current manual is its brevity. You can read it through and get a good overview over all the functions without becoming too bored with details. Unfortunately the devil is in the details after all and for me personally, some more information would have helped me stumble less in the beginning. | |