The teams are making progress. It may seem slow at times, but it is happening. I am really pleased with it, and I hope that you are too. Look how far you've come from the beginning of the year.
Don't get bogged down and depressed because you can't figure out a piece of coding. Sometimes it takes a couple of days to get it to work. Look at your accomplishments. Review your game ideas. Make sure you are not making a quiz for your players. Make the game interactive; make it something that would be fun for you to play while also learning the material.
I know at times it gets frustrating when sites are blocked and you can't seem to find what you need. But, there are other sources for what you need, and we can work around it.
Keep up the good work. Look toward the goal of finishing your game. After all, you are creative and intelligent and have all the tools you need. You CAN do it!
Game Design and BCA
Friday, February 18, 2011
Wednesday, February 9, 2011
Action Script
So, you have your game idea and your symbols are in the library and you're ready to put the game together. Where do you start? Good question.
If you've completed the lessons on the wiki, you have some idea about the kinds of things you can do in the game with your coding--at least the basic kinds of code. You don't have to start from scratch and write it all. You can copy the code and then substitute your symbol names in some of the code if it does exactly what you want to do. That's a start.
It's a good idea to have a description of what the code is doing included as well. You might think that you will remember, but chances are you won't. It just helps later on when you come back to the code and you can just read it in plain English.
Break your task into small sections and work on one section at a time. If you plan a major feat, chances are you are going to make a small mistake and that will cause you a lot of grief and you'll wished you'd worked a little section at a time. It just makes better sense. You know that a bracket or a comma or a semi colon left out can cause your coding to fail to work. Why risk it?
Do a little bit. Watch it work. Pat yourself on the back. Then go on to the next challenge with your self confidence a little bit higher than it was when you started. If you do this every day, before long, you will have accomplished a great deal of work on your game.
If you've completed the lessons on the wiki, you have some idea about the kinds of things you can do in the game with your coding--at least the basic kinds of code. You don't have to start from scratch and write it all. You can copy the code and then substitute your symbol names in some of the code if it does exactly what you want to do. That's a start.
It's a good idea to have a description of what the code is doing included as well. You might think that you will remember, but chances are you won't. It just helps later on when you come back to the code and you can just read it in plain English.
Break your task into small sections and work on one section at a time. If you plan a major feat, chances are you are going to make a small mistake and that will cause you a lot of grief and you'll wished you'd worked a little section at a time. It just makes better sense. You know that a bracket or a comma or a semi colon left out can cause your coding to fail to work. Why risk it?
Do a little bit. Watch it work. Pat yourself on the back. Then go on to the next challenge with your self confidence a little bit higher than it was when you started. If you do this every day, before long, you will have accomplished a great deal of work on your game.
Subscribe to:
Posts (Atom)