A Tip for Ultra Noobs

[DarkprinceVI]

An interesting way I've found in the endeavor of learning Rpgmaker is the use of others games.

If you want to learn how someone does something event or script wise you can sometimes download their project files with their games on Rpgmaker.net

Doing this always helps me with map planning and overall framework of the game.

Tis all. Super simple

 

[Sausage_Boi]

It is a good way to learn, and one I have used many times! There are even a few tutorials that are made like games that are super fun to use and learn.

 

[Susan]

If you are talking about ultra newbies, the first thing they really should do is read the manual and the tutorials.

After that, they can download unencrypted games to see how people create their games.

And just for more information, there are actually unencrypted games available in this site as well. The main website even has the official XP and VX Ace sample games. Both of which are unencrypted. ^^

 

[Andar]

Besides that, the very first step for ultra-noobs would be to play some RM games to learn what can be done with it instead of just going ahead - and they might want to follow the link in my signature - it guides you not only to tutorials but also to some of those sample games to look at.

 

[DarkprinceVI]

The thing I've learned about ruby however is that if you learn scripting anything possible.

My biggest tip would have to be

LEARN RUBY especially RMs version.

However you can still make a really good game with skilled mapping, plot, npcs, good eventing and other arguably easier things

 

[Susan]

You see, there is nothing wrong with the advice that you are giving.

A lot of people are doing what you are advising.

The problem here it, you are giving 'tips for ultra noobs'. When you say that, it makes me think of people who just received the engine and have no idea what can be done with it.

Telling them to go ahead and open RM games to check out the eventing and play with the scripts is fine, but only after they learn and understand the basic things. That is why Andar and I are saying that you should check out the tutorials first.

 

[Sausage_Boi]

I guess it depends on the person. I downloaded the trial version and played with it for a few days before I ever got into a tutorial. It was nearly a week before I opened the RMVXA school tutorial/demo.
And I only recently (within the past week) opened up the manual, to read a little bit about auto-tiles. Otherwise for me, I really prefer to experiment, and get as far as I can before I seek assistance from people more knowledgeable. 

To each their own, I guess. 

 

[MisterTorgue]

I would say ultra noob it is a case of starting from the very basics, reading the helps, the tutorials before thinking about doing anything.

After that play some sample games, only play them, get the feel for what is in a game, the details e.c.t.

After that open the sample projects and see how they do different things, how they get characters to talk, and such.

Going into games straight away, you are more firefighting your knowledge of you see something and will be like "how does that work".

Where if you ready tutorials e.c.t. first, you will have an idea, when you see how it works it will all click into place.

Once you have done all this, create a test project, do some mapping, see what looks good and what doesn't.

Create some simple events for talking npcs, door switches e.c.t.

(Post mapping up here as people can tell you what to do to improve your mapping skills)

I remember learning RPG Maker 2k3 <3

But yeah, with this, after you've done the above, you are in luck, you literally have the most helpful community and admins on the internet all in one forum!

I honestly couldn't have learned anywhere near as much as I have since I bought VX Ace if it wasn't for everyones help

 

[Celianna]

Moving to general discussion.

 

[whitesphere]

Really the best approach varies with the person.  When I purchased RPG Maker, I started tinkering around with it.  In retrospect it would have been very useful to go through the tutorials since I spent awhile trying to figure out basic things with mapping.

Sample games are also a good idea, since they do give you an idea of what can easily be accomplished with RPG Maker, but I don't think someone who just purchased RPG Maker would benefit from examining the sample game, until s/he learns the basics of the toolkit.

Now I agree it's highly useful to PLAY the sample games, while learning the basics, so you get a feel for RPG Maker's capabilities.

And, of course, these forums are extremely helpful once you understand the basics.  The active community is probably the biggest benefit to RPG Maker versus other RPG building tools.

 

[amerk]

An interesting way I've found in the endeavor of learning Rpgmaker is the use of others games.

If you want to learn how someone does something event or script wise you can sometimes download their project files with their games on Rpgmaker.net

Doing this always helps me with map planning and overall framework of the game.

Tis all. Super simple

You make it sound as if nobody here plays the games that are built on the very editor they are using. But in reality, RPG Maker games is almost all I ever play anymore, having grown tired of the direction consoles have gone.

But your point is sound, even for the veterans. I can't recall the amount of events I've studied to learn new things. When I first started using the program, I remember trying to create an event that could only be read in front. I created all sorts of switches to go on/off for this thing and wound up with an uplayable mess. Then I started playing a game and was surprised that you were forced to go up or down stairs facing the stairs and you couldn't do it from the sides. I looked at the event, and discovered the beauty of conditional branches, variables, and playing events based on a faced direction.

 

[TheoAllen]

Script is sacred place. You might won't believe that I played RM since 2008 and until 2012, I was afraid of using any script. Just by reading its manual, I got headache. I would say, get the basic idea of the editor itself. What is event, what are the switches, variables, etc. It could by looking at avalaible tutorials or looking from someone's project.