[3.4 Recap and Beyond]

 

While a list of classes and functions is good for the experienced person who is just looking to remember the function name or param list it does nothing for a new person about showing how to combine them to make some functionality for their game. That's what they care about. How do I make a HUD? How do I make an inventory? How do I make my AI do x? These are the questions that can't be answered with that kind of documentation for a person who may be new to game dev in general.

 

That, is the real problem...

[My artwork for Phobia - Progress]

Look's absolutely not inviting . Realy nice work

[Game Scripting is Hard]

In my opinnion, game ready assets are a good way of making a good and representative mockup of your game when developping it but lack the fexibility to achieve what you have in mind for your final product (haaa this asset is pretty mutch what I want but... it's not exactly what I want). The day I will be happy with my game prototype, i'm going to change the assets and behaviors for my own. It's a longer path to take, but you have something that is original and unique. A game is a work of art. If all games are made with all the same things, there all going to look like they came from the same mixing machine.