At 9/15/08 09:10 AM, CybexALT wrote:
At 9/15/08 07:38 AM, xTOXICxEMPIRE wrote:
But yeah, I know what you mean about potential. I always have absolutely epic game ideas in my head, make a menu, do all the storyboarding, plan it out etc, get to the coding and I either can't find any decent tutorials or can't be fucked.
Sounds like you're doing backwards to be honest. You shouldn't come up with an amazing game idea, and then learn how to script it, otherwise you'll get no where. You should read tutorials first. Read all of them, even if they wont help in a game you've planned. Then once you know how to actionscript, you will know what games you will be able to make, and so won't have the problem of coming up with an amazing idea and then find out you can't do it half way through. So basically learn actionscript, then make a game rather than trying to do it at the same time.
Nah, that's the backwards way of doing it.
You're not going to learn how to code properly by just reading a load of random tutorials. You'll put yourself to sleep.
Get a clear idea of what you want, then scour the interweb and work out the best possible way of doing it. Dive in right at the deep end and try to make something you want to make. Chances are the finished product will look nowhere near as good as it did inside your head, but don't underestimate the value of all of that practice. You'll have learned valuable lessons that you can carry on to your next project.
Also, be prepared to rescript your first engine from scratch several times. You won't have any decent ideas for structuring it before you've actually tried to code before, so you'll probably end up having to redo it several times as you learn more and more stuff, with each iteration looking exponentially tidier and more efficient than the one before it.