![]()
Okay so you have your resources now, even if you won't use all of them it is a good thing to download and archive as much as you can, making a resources folder on your computer for everything to be placed in allows easy access to resources that you personally prefer and cuts down waiting times for sites to load, depending on your connection speed of course.
Alright, so everything should be in order now, an organised workspace, plenty of resources and new ideas for your game.
We can't begin yet...
There can't be a game made without appropriate knowledge how RPG Maker 2000/2003 works, it is strongly advised that before you even begin to consider making a game, you look through the program's Help File since it is more useful than any tutorial or template.
RPG Maker focuses on 3 main functions, these are:
| Switch Operations Variable Operations Fork Conditions/Conditional Branches |
Anything mildly complex that can be made with the program is based around these 3 functions, they are an important thing to learn but when you have, adapting other functions of RPG Maker to them can be what provides that added piece of structure to make your game more enjoyable to play.
Extensive information is provided on each of these 3 functions and so it should be noted that expecting to grasp the concept of it all may result in disappointment as a lot of the operations require implementation before a more thorough understanding of how they work is achieved.
Now it's time to begin, however...
Practice makes perfect, starting up your new game project with newly developed knowledge doesn't necessarily mean that you are ready to make a game, a lot of new developers make the mistake of diving in and sorting things out within their main game project, Custom Menus and other systems similar to them need to be able to adapt do your game's extra settings, they can very easily trap you if you aren't organised enough.
It is always a recommendation to start a new side project which you can create all of your systems in, this is a more dragged out process because it can end in about double the work to begin with, but in the grand scheme of things it is a very successful work-saving procedure that should become habitual, solely because you won't have to go back to fix things up later on.
When you feel you have enough of an understanding to implement things into your own game, that is when it's time to throw it over...
Starting the system again from scratch is always a better way to go, a lot of crucial errors get weeded out upon every redesign and new skills can be acquired that were not known beforehand.
You learn from experience, so experience as much as you can.
Now you're set
By this point your knowledge of RPG Maker should be quite higher than before, provided you studied up and practiced hard, everything from here on is past the startup phase and comes down to your own judgment on how you approach project construction.
Good Luck!
Carius