Making a quick game...worth it?

[SirCumferance 28]

I have been fiddling with the RPG Maker series since Don Miguel, but never actually finished a working game. My excuses were varied from, 'Oh, a new engine, lets start over' to 'Just one more script'

Thing is, I want to actually just make a quick one, spit it out there and there, its done but I dont want to be known as 'that guy'

 

So tell me, is it ok to make a quick, not polished game just for the sake of getting it out there and in doing so, could I remake that game later with more polish? 

 

Thoughts?

[Wren 179]

That's a complicated question.

 

If you want to complete a project for the satisfaction of completing one, then do so, but if you want to showcase your skills and perhaps join a development team to work on a larger grander project, then putting the most polished and interesting project forward, even if it isn't complete, would probably be a better use of your time.

 

If you just want to work on your own project, creating the game you want to create, then don't be concerned with how long it takes, stay true to your vision and work at your own pace, maybe one day you will finish that project.

 

In any case, I have enjoyed your involvement and contributions to the community, so no matter what path you choose, I hope you will continue to share your progress and your thoughts via these boards.  Good luck, Sir!

[TheoAllen 830]

There is nothing wrong with making (quick) game. I was been perfectionist back then and I never finished a single game. But when I wanted to test out my battle system, I forced myself to make a quick game. It didn't matter if I use the full RTP and such, my aim is just to make a game and tested out my battle system.

 

You know what? I learned many things such as how to balance the game, how to design level, and how to effectively use the switches, variables, and scripts (and also began to realized some of my scripts were really troublesome if used in real game development). You can polish your game later after you finish the game. Many of my friends got stucked on polishing the game than making the game itself. And as the result, they never finished it.

[amerk 1,122]

There's a large difference between playing a quick game and developing a game quickly.

 

The first is perfectly fine. I tend to favor 3 to 5 hour RPG Maker games much more than the 15 to 20 hour ones do to time constraints on my busy life.

 

The second can only be accomplished if you've had the experience to do so, and even then it's not advised. Throwing together a game quickly without much thought of what's going into it will show (especially if you don't have any experience), and once you put it out on the forum, it will be open for scrutiny and (in some forums) even ridiculed.

 

As for "not polished", definitely going to advise you against it. It's one thing not to have the full manpower or desire to make a huge game, or even the experience to make a very polished game, but to intentionally throw a game out there (or spit it out, as you say), and think that's it, no polish, that just shows laziness. If you do that, then you need to be ready for all the negative comments you'll get as a result.

[SirCumferance 28]

ALL valid points and I have heard everything said (and not said). I will finish up my 'quickie' but put a little more polish on it. Ridicule I can handle as long as peeps arent talking out their ass and I am always open for criticism, its how we improve.

 

Thanks again for the advice and the awesome words of encouragement, it helps.

[privateer 1]

I actually understand where you're coming from Sir, I've also been around since the day of Don Miguel. What all the others have mentioned prior to me are all valid reasons. From my experience, I started from the school of thought that wanted a completely polished game, and struggled with the many things that you have also struggled with, I'm sure many that touched the RPG Maker series have struggled with the same experiences.

 

However, somewhere along the line, for no reason, I made a quick and simple game just for the sake of making it. I found that it allowed me to focus on what I wanted in the game. I never released the small game, but actually used it as a springboard into developing a complete and well polished game.

 

It really does depend on what you're trying to accomplish. I, myself have released two games so far, but I often find myself polishing up the previous project for the next game in the series. This leads to new improvements and a better experience from my players when they pick up the latest game.

 

Good luck Sir, and I hope that even if I didn't answer your question, that one of the previous posters did.

[RavenBlueIndigo 121]

My opinion on the matter is, it's fine to release a game quickly, as long as you do it competently and it still comes off as good. Do not sarifice quality. Give it the treatment it deserved. I made a game in one month before, but I was working near constantly almost 24/7 on that, and I was commited to it, and it didn't come out half bad. I mean, I wouldn't place it among the greats of RM games, but it was still pretty good, and alot of friends/random people I sent it to seemed to like it. One person is even gonna replay it on a stream one day.

[paralistalon 2]

I think it's fine to make a quick, unpolished game. It will give you experience and may give you some needed motivation to improve it. The game may be ridiculed, but if your next game is great, I feel that people will judge the game and not the developer. If your game does suck in the end, then just don't have the audacity to charge money for it or claim it's amazing... maybe just ask for some honest criticism so you know what to do better. Personally, I would rather focus on making a great DEMO of a game than releasing the final package all at once.

Edited September 26, 2014 by paralistalon

[kazutazu 0]

You'd have to balance it out between scripts/features/etc and time/progress/work. Best thing to do right now is to plan the game out right now, more specifically the scripting part. As for engine, stick with rpg ace for your first game. Once that's done you can get started on the other parts of making your game, ie art, story, so on. I've been there before, always looking for scripts and always trying to add more stuff. It's an ambitious undertaking, but definitely not the only important factor in making a game. As i mentioned before, make a list of things you want in-game, and work from it through that. As for making a quick game, i think that's a great idea. Making a non-time consuming and small game is a good source for feedback and results. Whether it turns out good or bad, it'll be valuable experience for the 'big' game you're planning later on.