Gamedev Lounge 0010

[Hoeloe]

What I mean by that is twofold. Firstly, Actionscript is a rather low-powered language, meaning your design of core elements of your game is often forced to work around it (design influence is mostly here).
Secondly, I consider game design as a multi-levelled process. The design is not just limited to graphic design and level design, etc., but also in algorithm design and code design. Badly designed code can ruin a game just as much as bad level design, if not more. Note that code design is not necessarily the code itself, but more the layout of the code. For example, in an OO language, this might be as simple as deciding which class files you will use, and where your inheritance will be, etc.

Now, Actionscript is not a great OO language. It's more like an OO/Procedural hybrid, making the design of it's code very different to other, pure OO languages, even if certain aspects of the code itself may be very similar. I know that AS has improved on the OO front since the move from AS2, but the setup is still very different, if not because of that, then because of other odd quirks.

Does that clear things up a little?