<a href='
http://www.phylomortis.com/html/rmxpblog.html' target='_blank'>Proof</a> that even RPGMaker
is not perfect. This guy used a 733MHz computer, and at a mere 640x480 resolution, the game ran at 8-9 frames per second. Even the Toolkit runs faster than that on a Pentium 100MHz at the same resolution!
I personally like this comment...
Ojima also imagines resource sites carrying scripts for all to use, so that scripts aren't just the domain of the advanced user.
I'm skeptical.
LMFAO! Didn't we have resource sites FOUR YEARS AGO! Laughing
I do realize that there are RPGMaker resource site out there, but I found if funny that the reviewer said he was skeptical, and that one of the authors of the software said that he "imagined" them, as if it was part of his vision for the future or something.
This was also funny...
I'll explain how to do a transition now. A transition is actually accomplished by using two commands 'Prepare Transition' and 'Execute Transition'...
Prepare Transition
Teleport (Fading off)
Execute Transition
Er, couldn't they have accomplished the above just by using one command?....such as...
#Transition("teleport")
So much for their team of programmers...here's more...
Picture limit of 50; variables can only be 8 digits long; names are only 16 characters long;
Many commands were removed that used to be in RM2k, which makes the "more advanced software" actually less advanced in some respects.
This dependence on RGSS may actually be advantageous to Enterbrain. If future RPG Makers rely more and more on the common RGSS base rather than native code, it might decrease development time while providing extensibility and functionality. Enterbrain would do well not to leave people who want a simpler program in the cold, though.
Oooo, slap in the face for RM2kers! One of the biggest things that they try and throw at us is how much RPGCode is pushed with the TK, and now the same thing is happening to them.
Cool New Feature: You can preview your messages. If you press F2 in the Input Message window, you will be shown how your message will look in-game.
This feature was added so long ago in the TK, I can't even remember which version it was in....
A new conditional branch 'Button Input' was added. If a button is pushed, that button's number is put into a variable. If this branch is used, the event waits for input. This is much like RPG Maker 2000's 'Wait Until Key Pressed' option, but it's not waiting for a specific key. Rather, if any key is pressed, the event advances.
Whoa! The TK3 team should get on those features! *COUGH*