Author Topic: Requests for technical documentation  (Read 1445 times)

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Requests for technical documentation
« on: 03 Oct 2016, 12:16 »
I am going to write several articles in the repository's wiki (https://github.com/adventuregamestudio/ags/wiki) to pass my knowledge of engine's internal work and procedures we followed in the past (like preparation for release).
Probably the few ones that already exist there need to be reworked too, because they were written as me and JJS were researching the engine for the first time ourselves.

Please leave your requests on which articles would you like to see. If I actually have that knowledge, I will try to find time and write about it.


Current progress:
Public release: procedure
Engine data structure restrictions
« Last Edit: 06 Oct 2016, 19:44 by Crimson Wizard »

JanetC

  • Mittens Serf
    • JanetC worked on one or more games that won an AGS Award!
    •  
    • JanetC worked on one or more games that was nominated for an AGS Award!
Re: Requests for technical documentation
« Reply #1 on: 31 Oct 2016, 17:20 »
How to rebuild libraries is always good, I really got tripped up on that one.

Crimson Wizard

  • Local Moderator
    • Best Innovation Award Winner 2013, for spearheading the AGS 3.3.0 project
    • Lifetime Achievement Award Winner
    • Crimson Wizard worked on one or more games that won an AGS Award!
    •  
    • Crimson Wizard worked on one or more games that was nominated for an AGS Award!
Re: Requests for technical documentation
« Reply #2 on: 31 Oct 2016, 17:55 »
How to rebuild libraries is always good, I really got tripped up on that one.
Which libraries?