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)
RMVX AND YOU
Posts
Lennon
88
Lennon
View playlists
CloseAccessory slots, menu shots, all neat little things but not essential.
I'd like to go back to my previous argument and say that this is essential if you wanted your game to have things like this. IE you can make your game more like the game you wanted to make, and not the game the engine dictates that you should make.
What you're doing is just going NO NO NO when someone makes a completely legitimate argument for why VX is better than 2k3.
Darken
3952
I'm sure doing that would be completely different from what you did. No; what you did was patently different... ON THE INTERNET.
Where did I say I was doing anything different? I just want end the use of A SHITLOAD of quotes between me and you.
All those neat things are not essential? Bro I think you need to understand that they are valid gameplay mechanics, the act of being able to press escape and see all the options (like sidequest shit, skill trees, materiawhatever) in one area for the player makes the game a lot more convenient. Also the equip feature is pretty essential for my game since it's primarily about rune collecting and rune combos 2k3 has an equip category for each slot (meaning I'd just be limited to one rune slot, eliminating any chance of 'combos'. In-game screen shots? You mean the ones where you wander around the map? No I have not developed that part of the game yet as I am just designing the battles and how the game actually works. I just thought I'd show off some things you'd never see in a 2k3 default menu.
As for the title screen thing, you wanted the title screen to look good, you wanted to make the title screen look different. You can only control how it looks (and even then you're limited to a single image) and cannot control how it functions. Yeah you can live with that limitation, but I don't think you can live with an RTP cloud title screen either.
you need to alter and jump through hoops to do anything well in 2k3
You are losing if you think this is my intent. "You need to alter and jump through hoops to do anything different in 2k3." is more like it, but inb4 "different doesn't mean better" argument.
Nightblade
2723
post=107193Accessory slots, menu shots, all neat little things but not essential.I'd like to go back to my previous argument and say that this is essential if you wanted your game to have things like this. IE you can make your game more like the game you wanted to make, and not the game the engine dictates that you should make.
What you're doing is just going NO NO NO when someone makes a completely legitimate argument for why VX is better than 2k3.
There seems to be a big misunderstanding here; so I guess I'll have to spell it out since I didn't make it obvious enough. I was suggesting people learn XP over VX - I was not suggesting 2k3 was superior in every way, nor was I suggesting there is nothing at all wrong with 2k3.
You are losing if you think this is my intent. "You need to alter and jump through hoops to do anything different in 2k3." is more like it, but inb4 "different doesn't mean better" argument.
If you actually did not agree with karsu's assessment, then you can disregard the previous post.
All those neat things are not essential? Bro I think you need to understand that they are valid gameplay mechanics...
http://rpgmaker.net/games/272/images/6140/
WHAT!? AN EMPTY SLOT!? FUUUUU... Alt +f4.
You were stating UI niceties as something game breaking. I am not disputing it is nice; I was just saying that it's not exactly a deal breaker to a lot of people. It may be essential to you; but to a lot of people... Well, there are other things to consider.
As for the title screen thing, you wanted the title screen to look good, you wanted to make the title screen look different. You can only control how it looks (and even then you're limited to a single image) and cannot control how it functions. Yeah you can live with that limitation, but I don't think you can live with an RTP cloud title screen either.
The cloud title screen is a completely different limitation... It is also completely irrelevant. What was the point you were even trying to make here?
Darken
3952
post=107198
The cloud title screen is a completely different limitation... It is also completely irrelevant. What was the point you were even trying to make here?
Making your games functionally different is just as important as making it look different.
WHAT!? AN EMPTY SLOT!? FUUUUU... Alt +f4.
Yup way to ignore my menu convenience and Rune Equip/Combo system not possible in the 2k3 default menu.
I was suggesting people learn XP over VX - I was not suggesting 2k3 was superior in every way, nor was I suggesting there is nothing at all wrong with 2k3.
Woah woah woah, back up the internet debate truck. What was the last page of arguing for?
Nightblade
2723
Woah woah woah, back up the internet debate truck. What was the last page of arguing for?
Can someone here show me an RMVX game that doesn't use some form of RTP? An actual map please.
Wasn't sarcasm incidentally: it was an actual question.
If you want to keep pestering people into upgrading, I would suggest RMXP.
There are many articles out there referencing the key differences between RMVX and RMXP; some have described them as nitpicks; others have used a more colorful way of describing it. Use what you need to use, and use what you're more comfortable with.
Personally: I use 2k3 for my current project because it does what I need it to do, and I'm more familiar with it (A few other things would have been nice, but the additions I would have wanted aren't worth the transition time for me). For one of my next projects, I'll have to move on to RMXP... depending on how mode 7 works for it of course... But that's a discussion for another day.
Personally, I stick to using RM2K(3) and playing games with those engines because both RMXP and RMVX perform like ass on a computer that supposedly adequately meets its system requirements. Shitty code? Totally, Enterbrain.
I might try and get into RMXP and RMVX if I upgrade to a machine with a dual core CPU, 4 gigs of RAM, and a great video card. I'm not upgrading just for RPG Maker, though.
And for those with a bad sense of humor, the second paragraph is sarcasm aimed at aforementioned shitty code.
I might try and get into RMXP and RMVX if I upgrade to a machine with a dual core CPU, 4 gigs of RAM, and a great video card. I'm not upgrading just for RPG Maker, though.
And for those with a bad sense of humor, the second paragraph is sarcasm aimed at aforementioned shitty code.
Lennon
88
post=107232
Personally, I stick to using RM2K(3) and playing games with those engines because both RMXP and RMVX perform like ass on a computer that supposedly adequately meets its system requirements. Shitty code? Totally, Enterbrain.
I might try and get into RMXP and RMVX if I upgrade to a machine with a dual core CPU, 4 gigs of RAM, and a great video card. I'm not upgrading just for RPG Maker, though.
And for those with a bad sense of humor, the second paragraph is sarcasm aimed at aforementioned shitty code.
I'd say its a case of shitty PC, not shitty code.
All of Enterbrain's default code has shit in its gears.
Good thing you can change RMVXP's code to not suck.
Good thing you can change RMVXP's code to not suck.
post=107198You are losing if you think this is my intent. "You need to alter and jump through hoops to do anything different in 2k3." is more like it, but inb4 "different doesn't mean better" argument.
If you actually did not agree with karsu's assessment, then you can disregard the previous post.
I assume you mean this:
Considering all the huge and time-consuming inconveniences anyone using rm2k3 has to deal with to do anything remotely creative beyond the engine's intended purpose
Bold for clarification. My criticism of Rm2k3 has nothing to do with the ability of the game creator, but the apparent disdain for RMXP/RMVX despite their ability to overcome many of the limitations that cannot be avoided in rm2k3. Such as a battle system that is broken beyond repair. Not so different from your complaints about a borked tiling system.
I play (and finish) far more rm2k and rm2k3 games than most people, including most rm2k/3 users themselves. I would've played the final version of Demon Legacy had I not run into a critical error within the first ten minutes. Why would I do this if I just hated them all?
I simply reserve the right to criticize the maker and the mentality of those who use it, however - just like you do for RMVX users.
post=107234If only that were the case.post=107232I'd say its a case of shitty PC, not shitty code.
Personally, I stick to using RM2K(3) and playing games with those engines because both RMXP and RMVX perform like ass on a computer that supposedly adequately meets its system requirements. Shitty code? Totally, Enterbrain.
I might try and get into RMXP and RMVX if I upgrade to a machine with a dual core CPU, 4 gigs of RAM, and a great video card. I'm not upgrading just for RPG Maker, though.
And for those with a bad sense of humor, the second paragraph is sarcasm aimed at aforementioned shitty code.
As it stands though, I have a machine with Pentium 4 2.66GHz CPU, 512MB DDR RAM, and a GeForce 6200 PCI video card and both XP and VX run like crap. There was also no performance increase when upgrading from my old machine which had a Pentium 3 966MHz, 512MB of RAM, and an ATI Radeon 7000.
The apparent lack of hardware rendering support (Software rendering? What age do we live in?) in the code of XP and VX eliminates the video card from the equation, and the extreme upscaling in the CPU obviously did nothing to alleviate the problem even though the CPU should be the bottleneck assuming software rendering is used. RAM could possibly be an issue, but if XP and VX require 1GB+ RAM to just run without choking, I'd say that's a case of terrible code and bloat.
Nightblade
2723
Bold for clarification. My criticism of Rm2k3 has nothing to do with the ability of the game creator, but the apparent disdain for RMXP/RMVX despite their ability to overcome many of the limitations that cannot be avoided in rm2k3. Such as a battle system that is broken beyond repair. Not so different from your complaints about a borked tiling system.
"Beyond repair" I like that part because it is completely exaggerated. But carry on; please.
I play (and finish) far more rm2k and rm2k3 games than most people, including most rm2k/3 users themselves. I would've played the final version of Demon Legacy had I not run into a critical error within the first ten minutes. Why would I do this if I just hated them all?
And what was the critical error, might I ask? If you're trying to make a point about this being rm2k3's fault, you're doing a poor job of it; as such a thing can happen with any engine RPG maker or otherwise. Want some proof? Go to the technical support forums for any variety PC game.
I simply reserve the right to criticize the maker and the mentality of those who use it, however - just like you do for RMVX users.
Fair enough, I'll continue to wait for someone to make an RMVX game worth a shit. Darken seems to be getting there. Only time will tell.
"Beyond repair" I like that part because it is completely exaggerated. But carry on; please.
Disproportionate value for stats, an insanely slow ATB bar, battle event commands that use a skill if you go into the skill menu select a skill and cancel, terrible methodology for turn counting that makes poison and regen outrageously powerful and makes other buffs and debuffs less powerful if the party or enemy party is simply larger.
I could go on, but I will refrain. If you want even more tidbits about rm2k3's broken battles, just ask GRS. He spent eons trying to make the battle system not miserable.
And what was the critical error, might I ask? If you're trying to make a point about this being rm2k3's fault, you're doing a poor job of it; as such a thing can happen with any engine RPG maker or otherwise. Want some proof? Go to the technical support forums for any variety PC game.
Way to jump the gun. I was seriously just saying I would have played it if it didn't crash. Should I make a screencap of it, go into Photoshop and type in the text "HIGH QUALITY" to get the point across?
At least on the whole "slow ATB bar" thing, that's to do with the user inputting values for AGI which are too far different between the combatants and/or fellow party members; larger the difference the slower and/or faster the ATB bar. I personally never found the ATB bar to be a nuisance.
I agree that RM2K3's battle system has other legitimately annoying problems, though. The horrible method of counting turns is but one thing I never really understood why it was done in such a way.
I agree that RM2K3's battle system has other legitimately annoying problems, though. The horrible method of counting turns is but one thing I never really understood why it was done in such a way.
post=107248
At least on the whole "slow ATB bar" thing, that's to do with the user inputting values for AGI which are too far different between the combatants and/or fellow party members; larger the difference the slower and/or faster the ATB bar. I personally never found the ATB bar to be a nuisance.
Biggest difference is if the party comes in three or four. If there are four party members it is almost always extremely slow.
And if the party goes somewhat quickly, monsters only get in an attack every two or three full PC turns.
post=107250post=107248Biggest difference is if the party comes in three or four. If there are four party members it is almost always extremely slow.
At least on the whole "slow ATB bar" thing, that's to do with the user inputting values for AGI which are too far different between the combatants and/or fellow party members; larger the difference the slower and/or faster the ATB bar. I personally never found the ATB bar to be a nuisance.
I never found that to be an issue for me, let alone have it happen.
Maybe it's the way I use the AGI stat, but having played games where the ATB bar was extremely slow/fast and/or had weird AGI to compensate, I've more or less come to the conclusion the majority of ATB problems lie with the user misunderstanding how AGI influences the ATB bar, rather than the RM2K3 DBS.
Because I really want to have to make a game with 10 ATK, 15 MGC and 500 SPD at L1.
People actively quote my projects.
Fair enough, I'll continue to wait for someone to make an RMVX game worth a shit. Darken seems to be getting there. Only time will tell.
People actively quote my projects.
