Full Games List
Featured Games
New Games
Reviews
Media
Images
Blogs
Game Updates
Images Feedback Summary
Game Design Highlights
Tutorials
Articles
Scripts
Utilities / Plugins
Resources
Engines
Engine Bulletins
What is Makerscore?
Past Events
Achievements
Misaos
Forums
Post History
Chat
New to RMN?
Full Store List
RMN Music Pack (free)
WICH DO YOU LIKE BEST? 2K,2K3,XP,VX
Posts
Versalia
View playlists
Closeauthor=Strangeluv
Who cares
Just make games
seriously fuck all these designers actually deciding on the important difference in qualities and cuts of silk vs. satin vs. cotton vs. polyester vs. wool that will define their production process and massively impact the finished product
just grab a barrel and some suspenders and you're gold
or something
author=Versaliaauthor=Strangeluvseriously fuck all these designers actually deciding on the important difference in qualities and cuts of silk vs. satin vs. cotton vs. polyester vs. wool that will define their production process and massively impact the finished product
Who cares
Just make games
just grab a barrel and some suspenders and you're gold
or something
Umm...What?
I am starting to like VX more and more.
author=Adon237
Umm...What?
I was pointing out the absurdity of Strangeluv's comment. I can understand the "lol this topic again" attitude but the OP is a newbie to designing, legitimately asking for some advice on which engine to use. Which engine to use is one of the biggest decisions you can make when starting a project, esp. if you have never mak gam before. It seems so trivial to those of us who are more experienced and/or jaded from hearing the same conversation topics repeatedly, but that doesn't mean we need to be obtuse douchebags about it. Dismissing it as "who cares just make games" is quite silly when the actual tools you'll be using to DO that are, again, one of the biggest decisions you make in pre-production.
Your choice of engine impacts your entire production process. If you feel that discussing it is a waste of time, don't bother posting in the discussion.
edit: to reply to the post below without posting yet again: "if you don't have anything nice to say, don't say anything at all" ... not EXACTLY what I was going for but okay I'll take it, but don't expect me to hold myself to that exact quote :B
At first, I though you just told me that posting this topic was completely worthless(it might be) and just told me to stop posting here, but after a couple of times, rereading it, I finally understand what you said. I am kind of getting the "if you don't have anything nice to say, don't say anything at all" vibe from that.
I agree.
I agree.
Strangeluv
2787
1. It is a waste of time, sorry. Especially at this point, when this topic has become a staple of the RM community and just looks bad on the whole.
2. Discussing 100 pages of game design and doing nothing also seems to be the new trend. You have to start somewhere, and you have to brainstorm, yes, but you don't learn by debating on the internet. You learn by actually trying out, experimenting with and experiencing things. Nobody's first project is going to be gold. Game design, like most things, is PRACTICAL as well as theory.
But wearing a barrel and suspenders is much better than debating game design naked for months and creating nothing. It's like my wrting mentor told me - "Writers write." Well, game makers make games. Next time you'll at least have some idea how to improve instead of wondering, "Hmm how do I improve something I've never made lol"
3. The OP did not post the question with respect to any project of his in mind. It was a general question. Maybe if he stated a specific thing he wanted to do, I wouldn't belittle the topic. But no, it's the same topic everytime.
2. Discussing 100 pages of game design and doing nothing also seems to be the new trend. You have to start somewhere, and you have to brainstorm, yes, but you don't learn by debating on the internet. You learn by actually trying out, experimenting with and experiencing things. Nobody's first project is going to be gold. Game design, like most things, is PRACTICAL as well as theory.
But wearing a barrel and suspenders is much better than debating game design naked for months and creating nothing. It's like my wrting mentor told me - "Writers write." Well, game makers make games. Next time you'll at least have some idea how to improve instead of wondering, "Hmm how do I improve something I've never made lol"
3. The OP did not post the question with respect to any project of his in mind. It was a general question. Maybe if he stated a specific thing he wanted to do, I wouldn't belittle the topic. But no, it's the same topic everytime.
Those are all valid points but if it is such a huge waste of time and everybody else is doing it wrong and making you look bad, why are you even here? Why don't you write an intelligent article about point #2 that will be featured and display the "proper" attitude toward game design more prominently, instead of popping into peoples' topics to tell them how pointless they are? A staff member recently enlightened me that just because someone else's design philosophy or tactic is different or inferior to yours does not mean you need to go out of your way to shit on it. If the topic is so pointless and such a bad reflection on the RM Community then you should gloss over it as it is so obviously beneath you and not fruitful to participate in. Belittling other people in your community does not help it look better, either.
I agree, it's the same topic every time and it is stupid and just do some Google-fu already. But I didn't feel the need to stop by just to say that because it would just be shitting on someone else needlessly. posting in pointless topics to inform people that they are pointless is pointless, tonight at 11
Now everybody read Strangeluv's post and absorb the wisdom within it, then go on to peaceably ignore threads you disapprove of while using said wisdom to mak galmes.
I agree, it's the same topic every time and it is stupid and just do some Google-fu already. But I didn't feel the need to stop by just to say that because it would just be shitting on someone else needlessly. posting in pointless topics to inform people that they are pointless is pointless, tonight at 11
Now everybody read Strangeluv's post and absorb the wisdom within it, then go on to peaceably ignore threads you disapprove of while using said wisdom to mak galmes.
LockeZ
I'd really like to get rid of LockeZ. His play style is way too unpredictable. He's always like this too. If he ran a country, he'd just kill and imprison people at random until crime stopped.
5958
author=Fallen-Griever
If you just wanna make games for fun, pick any of the above and work around their inherent restrictions.
In theory this topic would be spent comparing the difficulty of doing this for each maker in turn. Guess that's what I'll do!
- RM95 has mouse support and technically has better graphics than RM2K3, but is unusable. It has serious limitations , and doesn't work right on many modern computers.
- RM2K and RM2K3 give you the easiest time ripping graphics from SNES games. RM2K is turn-based while RM2K3 is ATB. RM2K3 has better support for complex battle events, and a couple other extra features that are so minor you probably don't care about them.
- RMVX and RMXP are more powerful and less user-friendly than 2K and 2K3. They give you the easiest time ripping graphics from 2-dimensional PSX games. Scripts allow you to easily import cool features that *other* people have created, which is awesome, but RM2K3 includes many of these features by default and it can be annoying that you have to go to the extra work to put them in your game. RMVX is somewhat better about this problem than RMXP.
- RMXP is probably better for creating maps than RMVX (due to three layers and unlimited tiles), and RMVX is probably better for creating scripts than RMXP (due to infoboxes). But for a beginner, the biggest difference between XP and VX is, without a doubt, the scripts that other people have already coded for each one. If you want your game to have a specific feature, like a materia system, you need to find out if that script has already been coded in XP and then find out if it's already been coded in VX.
I TRY to make my own scripts, I have only made 1 1/2 so far.
A caterpillar, and I modified a script Versalia posted, to meet my game requirements.
A caterpillar, and I modified a script Versalia posted, to meet my game requirements.
Sorry, my horrid scripting skills will never take me anywhere.
Plus, since you say XP/VX/ all of the Rm's aren't relevant, what do you reccomend I use? I just paid 60 bucks for VX, but...
I feel so stupid now. I can't even script a battle system. :(
Plus, since you say XP/VX/ all of the Rm's aren't relevant, what do you reccomend I use? I just paid 60 bucks for VX, but...
I feel so stupid now. I can't even script a battle system. :(
Hmm.. i make them for fun, but one day, i would like to make a commercial game.
Such a hard decision. If I learn RGSS2 my fun games would be awesome, but if I use a far superior system,I could make a commercial quality game,(maybe)
But....
I am stuck. O:<
Such a hard decision. If I learn RGSS2 my fun games would be awesome, but if I use a far superior system,I could make a commercial quality game,(maybe)
But....
I am stuck. O:<
Darken
3952
Of course, there are far more factors involved than these generalisations, but copy/pasting RGSS takes no more effort than copying an "eventing" tutorial does. Unless you're going to make your own systems, it makes absolutely no difference which RPGMaker you use... except for graphics.
Except in RM2K3 if you want to do a small thing like, change the way equipment is handled, you have to make a CMS which takes forever. In VXP you just... add in some equip mod script, change variables depending on what you want (do you want 1 weapon and 3 card slots? do you want 2 accessory slots? etc.) It's not just copypaste oh I have a game mechanic, it's copy paste oh here is a game mechanic I can modify to my liking without having to make an extra menu or some work around event shit.
Also why would you think making an engine from the ground up is the same as making a battle script for an engine. Do you realize how much effort making an engine is?
Idk I currently use rm2k3 for graphical reasons, but your conception of rmvxp scripting is warped.
