I've been reading through the 20+ pages that have been posted in here since I discovered this thread yesterday and I have a couple of thoughts:
Several posts hoping that this new maker is somehow 100%, or nearly 100% backwards compatible with older projects
I should hope this would be basically impossible. If this new maker was such an incremental upgrade that your MV scripts, and events, and whatnot worked 100% out of the box simply by converting the project, there'd be no reason at all to call this a new maker, and it would've been better served as an 'update'.
People hoping this has 3D involved somehow
The screenshots pretty much show that's not going to be happening, unless it's some implementation of the babylon script (like the MV3D plugin), which would be cool. I get that some people want to move on to a 3d engine of some kind, but lets face it, if you're trying to make a 3d game, you should be using unity or something similar. This maker is designed for a novice, and can be extended with plugins, sure, but there's a certain limit where it's no longer novice friendly. I already have trouble making 2d sprite graphics, I can't imagine trying to draw new resources in 3d.
People who want JS to be replaced with C# or C++ or whatever.
I think at this point it's been basically confirmed that we're still using JS here, and thank god for that. See the above message about accessibility. If they moved to a more advanced language, like C#, it'd be a lot more difficult for novice programmers to learn, and get into for sure. I think that JS is the perfect combination of simplicity and power, and is perfect for RPGMaker in that regard.
People who want entirely new battle systems built in, with no plugins
I get it, you want a tactical system, or an ABS. Why not both? This goes back to the accessibility thing above, though. If one or both of those are included by default, it just adds extra layers of stuff to disable if you're not using it. People have been doing ABS systems since RM2K using events, and plugins really make that a lot easier nowadays. The fact is, though, that it's preferable for built-in systems in the engine to be used by the majority of users. Not everyone is making an ABS game. Not everyone wants a tactical battle system, and I don't want three tabs in my database exclusive used for ABS or TBS stuff that I have to manually delete when I make a new project to save on the 100's of MB of resources those things are probably sticking into my new project.
Things I'd personally like to see:
- Plugins that allow modification to the database, or to the maker itself
- Non-lame dual wielding implementation (or not, y'know, a guys gotta eat.)
- Ability to show actor busts or sprites in front view, and show animations over them
- Have weapon images based on the weapon (from the database), not on the wtype without a plugin
- more robust generator/parts
I'll be keeping my eye on this though. My interest has been piqued, despite not actively working on my own project in some time.
