Peer pressured badly to switch engines?

[JayRay]

XP never fixed the fact that large sprites disappear from the game screen if the one tile at the base of their sprite goes off screen... You have to add a script to fix that.
XP never fixed large sprites keeping their Y-priorities on a map, you have to add a script for that.

Simply, NO Engine is perfect in all methods. So people make scripts, plugins, and fix them for their specific preference.Yes, plugin, fixed - five minutes and done. Hell, it took me all of 30 seconds to find the plugin for that audio 'issue' (That I never experienced myself) on Google.

Also, I say negligable, because just like XP has preloader scripts, MV has Preload_Cache! I use it all the time, loads the music, graphics, and all I need before I even enter a scene. JUST like preloading was done with XP...


But let's address something I'm seeing as a theme here. You hate on a lot of stuff, simply because you're stuck to YOUR way or no way.

I posted a simple event system that was drag and drop for RPG Developer Bakin, the method that allows text files to simply be dragged and dropped between projects and you came back with. "I would have to see it in English." You literally dissed a Japanese engine's format because you didn't understand its capabilities.. I talked about Bakin in the engine discussion, and you came across with just - well, I'm going to come out and say it. negativity.

 Does this engine feature any kind of programming language?
Even Warcraft 3's engine had something like that. 
Is it stable? Or buggy? Because in WC3 the engine couldn't handle pointers properly for some weird reason, and people always warned fellow users about optimizing events and resources.

Well, a PC or laptop with Win10 and 8 GB RAM serves as a bare minimum for decent performance for Win10 consumes the first 4 GB entirely. I hate when engines become real resource hogs. 

 I wouldn't use it unless it could run on Win8 as well.

Stop being a hater on everything, man.

Update: Just in note... The basic tileset from XP is 8 colums of 13 rows (01-Grassland...)
An MV Tileset for the B is 8 columns of 32 rows, and there's 4 of them (B,C,D and E) for 128 total tile rows.