Discussion in 'RPG Maker MV Software Updates' started by Archeia, Nov 24, 2016.
@Jonforum: Saw that but you need to use "use strict". It's causing a lot of issues.
Issues like what? If it's throwing errors, then it's pretty much trying to warn you that you're doing something dangerous.
yeah it's not throwing any issue here neither.
on a side note
we can forget ES6 will be use in MV because most features aren't yet implemented in Browser
@nio kasgami Modern browsers support about 95+ % of all ES6 features. What nade you think most features were not supported? The problem is mobile devices and outdated browsers, if you want to reach all platforms and a wider audience you need to transpile your code to ES5. I would love to see ES6 in MV too, it would be a great next step and when browsers finally support ES6 modules, plugins will be a whole new story.
I highly doubt that browser will ever support the ES6 modules evers but that's another story.
Plugin will be mostly editing ES5 because you technically can't edit a class without using the prototype ways.
ES5 is fine. It's a little lengthier than ES2015 without all the syntax sugars, but it's perfectly fine for gamedev.
Perhaps in the next RM iteration.
Let's check the ES6 Table and reconsider if it's worth it. Notice the mobile section...
Wow, that's full of reds for mobile
Supporting modern browsers in anything is not typically a problem, but you very rarely make anything exclusively for the newest line of products (be it graphics cards for native games, or web browsers for MV). There's always going to be backward compatibility involved because you can't expect everyone to shell out money in order to be able to play your game. Sure, updating a web browser is free, but that still doesn't mean people will do it. People are notorious for not updating things. Look at Java, for example. How often do people just close the update prompt window instead of just updating it to make it go away? And making the user perform more steps to be able to use your product is a quick and easy way to lose audience interest fairly fast.
Supporting legacy browser is not exactly an issue with MV, as games come bundled with their own - compatible - browser. However, I would not consider rewrite of MV to ES6 to be worthwhile at this point.
This is precisely why i mentioned transpiling. I dont expect many people to have latest browsers and technology. I only mentioned ES6 compatability because Nio thought most browsers dont support it when in fact most browsers including a few older versions support over 90% of ES6, the largest problem is mobile browsers and support. It would be awesome to start using all features, I could care less if MV rewrites it or not because I can start writing ES6 either way and it still work find as long as i transpile and dont use modules.
I'd rather have code I can understand in ES5 than the crap that comes out of a transpiler.
Lol it is definitly ugly, you will always have the main ES6 file though , just when its ready to be released and you want full compatability you can transpile it. Right now though most features work with nwjs so you dont need to transpile it for testing and even if you did sourcemaps will have you covered. I only wrote one plugin with ES6 and it was pretty fun but as you mentioned its easier and more manageable to have readable ES5 code.
peoples are lazy and want to have straight forward for when it's about game dev and I can say ES5 transpiled code is annoying and peoples doesn't want to have to install or learn how to compile their code.
you will see how peoples are lazy.
Oh, nothing serious. JShint was yelling that stuff like $gameMap wasn't defined. Searched how to exclude
RM objects for a while but found nothing so I just gave up to use strict mode x).
That's so unfortunate. I would love to use ES6 arrow functions.
Any word on the updates with the Child generator options? How about the music/graphic errors?
Child Generator is DLC if that's what you're asking.
I don't know what you mean by music/graphic errors.
I asked and this is an intentional design choice. Now it's upto KDKW if they want to enable it.
Separate names with a comma.