Content

• Tips
• Warnings

1 Learn a programming language. C / C ++ is the most popular as well as the industry standard, but if you are new to programming you might be better off starting with Python. http://www.sthurlow.com/python is a very useful Python programming guide for beginners. Also, find a handy game engine like “RPG Maker” or “Torque”. This can be helpful if you don't know programming. However, learning programming may be the best option for the future.

2 Come up with a game. Once you have decided on the story in the game, move on to more detailed moments of the gameplay. The more specific your plan is, the easier it will be to implement it. * Create a plot for your story. For example: Will Sally find the key to the second door by chance, or will she have to complete Dr. Miller's mission to find a ladder and climb a tree to find the key?

• How will the characters move, using the keyboard or mouse? Will cheat codes be used?

3 Collect your resources. Collect or create all the textures, sprites, sounds, and models you need for your game. You can find a large number of free resources on the internet, so take a look around. http://www.onrpg.com/contentid-4.html is a very helpful guide to sprites.

• To create sprites, you have to learn pixel art. There are many tutorials on this topic on the Internet.

4 Select an engine. Building a game engine can be challenging, especially if you're new to programming. Try using an open source engine first. They are free, and at the same time you will understand how the engine should look like.

5 Create game scripts. Scripting is one of the last steps in creating a game. The script tells the engine what to do and when. If you are building your own engine, then you will have to create your own scripting language that your engine can understand. If you used an open source engine, then most likely the scripts are already present in this assembly.

6 Test your game. Now, you can look at the results of your hard work. Play your game, do everything until your computer and you turn blue. Find all possible “bugs” (problems) and fix them before you release the game.

7 Release your game. This part is completely up to you. If you are planning to sell your game (and you have not used one of the open source engines), then you are in the process of protecting your copyrights, trademarks, and so on. Or you can release it for free (open source) for others to learn.

Tips

• If the game is going to be online, make sure to use encryption! Hackers will easily take it away if you don't.
• Start small and build on. Don't add things like special effects until after you've set up the basic structure of the game.
• Always remember that you have to create games, not engines. Focus your efforts on the game, not the engine, and don't add unnecessary features just because they “might” come in handy or “would be great to have” in the future.
• Write the things that * * need now * * instead of the things you “might need”.
• Making and developing a game can be tough. If you feel stressed that one part of your game isn't working, take a break. Don't turn what you love into your enemy out of haste.
• You don't have to reinvent the wheel. If a library exists that does what you want, then don't create your own.

Warnings

• If you plan to sell your game and do not use your own engine or work, make sure you have permission from the creators to avoid potential problems.