DEVELOPMENT METHODS:WHICH ONES ARE YOUR FAVORITES?

Now that I think of it, I forgot to share some of my methods. I did realize a few things while trying out various engines and here is a list that could shed some light on things.

• Use Resource Conventions

Sometimes, when you get an abundance of resources, its best to categorize and name them according to their type. Usually in RPG Maker, you'll have the standard folders such as "Music" and "Battle", but what lies within can be files with generic names that help alphabetize based on origin. For example, if you want to categorize characters, rename the string to char_(instert name here).

Same thing applies in Game Maker. It's VERY important to use what we call "Resource Conventions"(RC). This is a simple tactic to separate each type of item. For example, we have sprites(spr),objects(obj), and background(bg). Depending on your game, this can make your database look very good and clean so that you never get lost. Before, I did not use RC to my advantage,so my database looked like spaghetti.

• Please plan

From experience, I can say this. Planning is very important. Its common sense, but when you first start out, its simply an idea. No one knows what may happen to their projects as they grow, and as our minds and experiences grow, so will our projects. New ideas come in like a tidal wave and we're like "ooh, I want to put this and that in there" and you'll be that way until the project begins to be all over the place. When it gets to this point, you're wondering where it should go from here..."Cancellation" or "Scrapping"? Before you begin a new game, please plan. Plan out EVERYTHING, it will save you a ton of time in your precious life.

• Never EVER forget to back up!

I absolutely cannot stress this enough. Back up your projects on a regular basis. Once a week at the very least. No one knows what could happen to their projects at any given time. Computer crashes, corruption, missing flash drive, etc. I've lost projects before to a corrupted flash drive. At that point I had done so much work, I wondered if it was even worth starting over.Send out copies to your online storage services, store on flash drives and do whatever you can to make sure your work is infinitely available. The last thing we want is a project to not make it out of the oven.

• Keep variables organized

When you create a project, it will 9/10 use custom variables to make your unique systems such as Banks,Time Spent, etc. When making a set of variables that you know will grow to be abundant, its wise to categorize them so you won't get lost when you'll need to look back for them.

• Add commentary as you code!

This is an extremely important one! I cannot stress enough that commentary will save you mounds of brain power and stress. When you code something, you'll have to keep track of what it does and how your systems work. By adding lots of commentary on your events, you'll never get lost and wonder what does what anymore. Sometimes, its best that you take a break from your projects, but not TOO long.Days can become weeks, weeks become months, and so on. If you don't add commentary, you'll come back and be like "I forgot what this stuff does". But, if you do add commentary, you'll be able to read it and immediately know where to pick off from.

• Work smarter, not harder

When working, you'll want to find the most efficient way possible to do something. There are LOTS of ways to get to the same goal. Everyone codes a little differently and depending on your level of knowledge, you can create some awesome stuff. After getting the gist of what your program can do, you'll find the wittiest way to do things. In fact, depending on what this method is, you could cut your workload in fractions.

For example, instead of making a parent object in my projects, I simply copied the object and did some stuff to it. That's wrong. You want the parent object to set the standard for the kids. Each "kid" shouldn't have their own programming.They can inherit their events and add some code to become original though. Your dad may be a doctor, but the next kid wants to be a doctor that can play basketball XD.

• Don't be afraid to ask for help

Some developers can often have a sense of pride and idea that they can always do everything on their own even if they don't know what the heck they're doing.Realistically, there is always going to be someone smarter than you. Game developers always learn from one another because we are all on different skill levels and have our own special talent(s). Heck, that's why were here right? If you think about it, we're all one big team trying to help one another improve. Without one another, we'd be wondering on how to do things for years, when someone could have taught you in a couple days. Always, ALWAYS be open to learning, getting help, and receiving feedback on your content. It will save lots of time on your end. You wouldn't believe how happy I was when I first saw codes work that I thought would be "hard to learn".

• Picture what's happening before you test and test lots

As we all know, testing takes a LONG time. I can't even begin to explain how important it is to test. As your projects become more ambitious, so will your load times, bugs, test times,and content. When you are coding an event, always imagine it as you're coding. There are many games I've seen that made me think "did the developers even test this thing"? So, I advise that you test and test lots. Depending on the game type and content, more tests may need to be run. Since RPG Maker games do not require things such as gravity, you won't have to worry about nasty collision detections and stuff. Also, when you finish a game, you most likely will not be aware of every bug, so don't be shy on letting others play your game so they can help you out with that.

• If you're in a team, stick to your forte(s)

Lets face it, we've all thought what it would be like to make our projects by ourselves, hence why we often start off doing so. If you aren't good at something then you have two choices; get help or learn it yourself. But, by the time you've become a jack of all trades, you'll realize that things would have gotten done faster and more efficiently if you had someone who specializes in an area. Being a one-man team is a challenge especially if your project is 100% original.Its rare to be the composer,artist,programmer,tester,and marketer all in one. There are a vast variety of talented people here and around the world that you could reach out to. A simple cry for help could save you months, even years of time.

author=Marrend
I usually make a folder in my computer for projects that I work on. The last couple of projects, I split up things into sub-folders. For example, all the scripts I'm using, generally in an unmodified version, are in a "scripts" sub-folder. Same with music and graphics. Writing, such as the game's dialog, plus any random notes that I think might be useful, tend to be in the base directory.

I must admit, I don't always make comments in the scripts I write. Or make any kind of notes on how it can be used, if I'm okay with other people using it (I usually am, though), or that I even made it. Maybe not the best policy!

Now, that is something I haven't thought of. Keeping lots of notes of dialogue would prove to be very useful so you aren't infinitely thinking about new concepts in the storyline.

And yes, commentary would be best especially if the script is "Free to use". Its important to sign your work and let people know who made it so you'll receive credit for it. The last thing you want is for someone to steal your work and claim it as their own. Believe me, I've seen it happen. People will steal scripts and say its theirs. As long as it doesn't bother you, its fine. But, I would update that policy. Small codes is one thing, but entire scripts need credit of some sort(at least IMO).

Usually at the beginning or end of scripts, you'll put "(script name) created by (user). Please give credit if used". Or if you don't care about credit simply put "no credit needed".

You both are absolutely correct.Its wise to plan, but not so much that your game is simply a dream and you never implement it into an engine.

Years ago, I started a project with absolutely no knowledge of how to even begin making a game, I just simply played them. What people need to know is that as you play each and every game, you are becoming a developer inside. You will begin to notice things you do or don't like, errors, good and bad game design,etc.

I've remade my "flagship" project SEVERAL times as time went along. When new ways of handling code came to mind, or a new concept was introduced, it would result in going back and remaking codes to adapt to the new concept. For example, in Game Maker, I had 2 sprites for every character,monster, and NPC. There was a left sprite and a right sprite. As dumb as I was at the time, I didn't know that you could just make one sprite,set the origin, and flip the sprite with codes. With that done, I had easily cut the resources in half, but I had to spend several days reprogramming the database to cater to this new style. Of course there is a difference between not knowing and not planning, but unfortunately, I did both XD.

Planning is what leads to success and much less time will be spent wandering the desert and more time transferring your imagination into works.

Great job with this! Thanks for sharing that. Its great to think of your database as a binder. Everyone remembers dividers right?



Link makes a valid point as it should indeed look like the one on left. This form is something that should not be pushed aside.For example, a form I use for platformers is

-World 1
+Stage_001
Stage_001_a
Stage_001_b
+Stage_002
Stage_002_a
Stage_002_b
+Stage_003_Boss