RPGMaker MV

[Animebryan 139]

This new MV version sounds good, but the people that are currently working in their games can't convert the graphics to RMMV. It's been just 3 years since RMVXA and they stopped using Ruby to use Javascript... I guess I'll use MV for the sequel. This community will still support VX Ace after RMMV's release, right?

Actually, nobody knows for sure whether or not we can import VX/Ace styled RTP graphics to it yet. There's talk about being able to use any custom tile size either naturally or through a Plug-in. Also, for the record, it's actually been about 4 years since VX Ace's release. As for this site supporting VX Ace afterward, you have nothing to worry about. Even amerk himself said he's hesitant about switching over. Considering that most scripters here are so used to Ruby/RGSS that may or may not know javascript means the transition to MV will be a somewhat slow & steady process. VX was ditched because Ace was simply a 'superior' copy of what it was, where in the case of MV being vastly different means a lot of people will continue to use Ace while getting used to MV.

Edited August 23, 2015 by Animebryan

[Rikifive 3,411]

Well, for the record, Yanfly announced that he was gonna start a new scripting system for MV (which he's probably working on right now). It also wouldn't hurt to start brushing up on javascript ahead of time. After all, RMMV isn't gonna write it's own scripts (Plug-ins) for itself, those who already know or just now learning javascript are the ones who'll set the stage for new features & such. Heck, Yanfly was already working on RGSS3 scripts back when just the Japanese version just came out, so I trust he'll be ahead of the game when it comes out.

Well, I'm not using Yanfly's scripts that much, so there's no big difference. Also - I'm currently working on a project - and it'll take ~more than a year to complete - No way I'm going to start everything all over again.

Perhaps I'll consider using MV for next projects (at least 2 years later), but for now I have everything I need.

[Tsarmina 2,612]

I think mostly it'll be a matter of time before the resources/scripts/etc market for MV will really start growing larger. The thing is, we've had Ace for so long now that over time the amount of RTP-styled tiles, portraits, and RGSS3 scripts have built up to make a rather large web of what we can do from the basic engine. Since MV looks like it might have a different style, of course it'll take a long time before the expanded content that inevitably comes with new makers will follow.  

 

The speed at which these assets will come out is also related to how useful MV is from the base package XD But they will with time. You can guarantee there'll be people making MV RTP games, and then someone's going to want to make their game nicer and make assets, and from there on out MV will steadily grow more resources. I'm just wondering how fast it'll be. :x

[Rinoazelda 287]

I think mostly it'll be a matter of time before the resources/scripts/etc market for MV will really start growing larger. The thing is, we've had Ace for so long now that over time the amount of RTP-styled tiles, portraits, and RGSS3 scripts have built up to make a rather large web of what we can do from the basic engine. Since MV looks like it might have a different style, of course it'll take a long time before the expanded content that inevitably comes with new makers will follow.

 

The speed at which these assets will come out is also related to how useful MV is from the base package XD But they will with time. You can guarantee there'll be people making MV RTP games, and then someone's going to want to make their game nicer and make assets, and from there on out MV will steadily grow more resources. I'm just wondering how fast it'll be. :x

 

As fast as snails slide?!

[Arrpeegeemaker 136]

 

 

I hear that, I've put a lot into using Ace and learned most of what I know about the maker on it. I didn't start using RPG Maker until VX was out for a few years, and Ace is when I started to get serious. 

I will be getting MV, but I will by no means be abandoning Ace or anything I'm working on with it. Just like the other makers to for users who've been on longer, XP and VX still have a lot of value to me, as I spent a lot of time using both, and Ace will be no different. 

 

 RK5 you'd better make games on MV, too. And I'm watching you're progress bar, and I will be playing your Ace game when it's ready. Although I have to admit I know absolutely nothing of MLP

MVMLP ^^ One day

[Rinoazelda 287]

 

 

 

I hear that, I've put a lot into using Ace and learned most of what I know about the maker on it. I didn't start using RPG Maker until VX was out for a few years, and Ace is when I started to get serious. 

I will be getting MV, but I will by no means be abandoning Ace or anything I'm working on with it. Just like the other makers to for users who've been on longer, XP and VX still have a lot of value to me, as I spent a lot of time using both, and Ace will be no different. 

 

 RK5 you'd better make games on MV, too. And I'm watching you're progress bar, and I will be playing your Ace game when it's ready. Although I have to admit I know absolutely nothing of MLP

MVMLP ^^ One day

 

 

I will only get MV 2 years after it's release.

[Rikifive 3,411]

I hear that, I've put a lot into using Ace and learned most of what I know about the maker on it. I didn't start using RPG Maker until VX was out for a few years, and Ace is when I started to get serious. 

I will be getting MV, but I will by no means be abandoning Ace or anything I'm working on with it. Just like the other makers to for users who've been on longer, XP and VX still have a lot of value to me, as I spent a lot of time using both, and Ace will be no different. 

 

 RK5 you'd better make games on MV, too. And I'm watching you're progress bar, and I will be playing your Ace game when it's ready. Although I have to admit I know absolutely nothing of MLP

MVMLP ^^ One day

Yeah, I'll never leave Ace, but perhaps I'll work on MV too someday. We'll see what future will bring to us. =] but for now... -

I'M GONNA ACE FOREVER, DON'T YOU EVER FORGET! XD

Why, thank you!

To be honest I'm planning to make more MLP (or not- we'll see) games, but this time it'll be more focused on story - not an RPG game - I'm having one touching story on mind - it seems REALLY good, but I'm not sure how it'll turn out, so... perhaps this'll be done in MV? Who knows. =P

 

I will only get MV 2 years after it's release.

Kinda like me - I'll wait for scripts and for some occasion. Also acquiring MV doesn't depend on if I want to use it or not - different currency is really a pain. Why I'm not that hyped of it is because I think I'll be not able to afford it, considering I'm wasting my life completely right now, if you know what I mean. I think I'll regret that in the future...

I only hope i'll be able to at least finish my current project... I only hope for it... Time is going fast, really fast and I'm slowly getting myself into a trouble...  didn't meant to bring that all up, forget 'bout that - At least I'm having fun right now! That's how irresponsible man looks like! =)

[amerk 1,122]

I'm not a scripter, so I can't say with certainty the ease or difficulty of converting scripts. With the current Ruby system, each maker has had to have scripts rewritten. Some have worked okay with all versions, some only require minor tweaks, and some had to be either be done from the ground up or scrapped and made into an entirely different version. But... typically, it would seem a scripter well versed in an earlier version was pretty good at handling the newer ones, and as a result we were able to get scripts fairly quick with each new installment.

 

I'm not sure if the same can be said for JS. I hear it's much easier to learn, so there's that for those who were looking in getting into script writing, but I imagine it will still take a bit of learning curve to abandon the "same old same old" we've become accustomed to. We may not see scripts pour out for a good while with MV, and that may be what holds people back the most in jumping ship into investing in a whole new maker.

 

On the other side, the long run benefits will outweigh the short term, because it's very doubtful that EB would ever reverse course and go back to Ruby once JS has been implemented. Whether or not MV starts off on shaky grounds remains to be seen, but future updates and implementations should go much more smoothly.

[Kayzee 4,032]

I'm not a scripter, so I can't say with certainty the ease or difficulty of converting scripts. With the current Ruby system, each maker has had to have scripts rewritten. Some have worked okay with all versions, some only require minor tweaks, and some had to be either be done from the ground up or scrapped and made into an entirely different version. But... typically, it would seem a scripter well versed in an earlier version was pretty good at handling the newer ones, and as a result we were able to get scripts fairly quick with each new installment.

 

I'm not sure if the same can be said for JS. I hear it's much easier to learn, so there's that for those who were looking in getting into script writing, but I imagine it will still take a bit of learning curve to abandon the "same old same old" we've become accustomed to. We may not see scripts pour out for a good while with MV, and that may be what holds people back the most in jumping ship into investing in a whole new maker.

 

On the other side, the long run benefits will outweigh the short term, because it's very doubtful that EB would ever reverse course and go back to Ruby once JS has been implemented. Whether or not MV starts off on shaky grounds remains to be seen, but future updates and implementations should go much more smoothly.

 

JavaScript is sort of... weird. It doesn't actually have classes the same way Ruby or most object orientated languages do... instead it uses prototypes. I guess it's kind of the same thing but it has a completely different structure to what people working with Ruby might be used to. I honestly have no idea how most large libraries actually work in JavaScript because I have not worked with it beyond simple webpage stuff. JavaScript is pretty neat though, I think it has a lot of the same kind of stuff with closures and other functional programing structures as Ruby can, but I don't like the syntax as much.

 

So basically, in my opinion as a scripter, JavaScript will probably turn out to have a steeper difficulty curve then Ruby, but I am really not completely sure. It might end up being easier for simple things, but that depends on how the default scripts are set up. I am not sure how well aliases will work, but considering everything in JavaScript, even functions, are just stored in variables, they shouldn't be hard to do. My own experience with is that JavaScript can get very very messy pretty easily, but we will just have to wait and see.

Edited August 24, 2015 by KilloZapit

[PAC918 13]

I'm planning a second release. Just like The Last of US did for the PS4. A remastered edition. 

[Traverse 144]

Kinda like me - I'll wait for scripts and for some occasion.

 

There are no scripts, there are plugins now. While some might say that there's little functional difference, it occurs to me that running script calls from an event may now be no longer possible in RMMV. It also depends on how the default system is structured but there is the possibility that plugin compatibility is going to be a whole lot lower than script compatibility, if the system is coded in such a way that many overwrites are necessary in order to implement changes.

 

So it goes without saying that none of the scripts from XP-VX-VXAce are going to be usable in RMMV. In any way. And "porting" the existing scripts is probably not so much going to be "porting" as "rewriting", since not only is JavaScript fairly dissimilar to Ruby, but the structure of the engine is almost certainly going to be very different from the previous makers (in part due to how different JavaScript is from Ruby).

 

I doubt many old scripters will be keen on rewriting their scripts*. You'll just have to pray that some part of the larger community of JavaScript coders take enough interest in the engine to make new plugins that do what the old scripts did.

 

*And yes, I know Yanfly seems keen, but he's probably one of the exceptions to the rule (if he's not being paid by Enterbrain). Same deal with Archeia and their Luna Engine port.

Edited August 24, 2015 by Traverse

[Arrpeegeemaker 136]

@ Traverse: I get the feeling that you have the most up to date information of the people posting here, you seem to have done your research well. But man, you are really bringing the reality hammer down on me right now! (I'm not criticizing you, of course I would want the most real and up to date information) You bring up really good points about the Java aspect, I know it's already been mentioned but still...you're right, a lot of what we know is going to probably go out the window. 

 

I think part of me is thinking it's going to be largely the same,, in my head I treated it like VX----> VXAce----->VXAce+     When really it's going to probably be drastically different in a lot of ways that I might not warm up to instantly. I guess I'm counting on Enterbrain to keep the heart and soul of what RPG Maker collectively is to us all at it's core. 

 

After reading your post above, especially the part about all of these scripts having to be rewritten in a different language...

I think now what I hope for the most out of MV is that the community that builds up around it will be strong like this one. I've said it before, RPG Maker is the only thing I know of that, instead of calling a customer support line you hit the forums and ask the users. Sure, many different things have forums that people bring questions to, but RPG Maker has a unique kind of community, because everyone is in it to give something in some way, even if it's only 'giving' your game to the community. 

 

I realize now a lot of people who've pounded out years of RGSS aren't going to want to essentially start all over again. Some will, sure, but I think I've been naive with my anticipations. So I guess here's to the future community of MV, may it's resources be vast and it's tutorials plenty. 

 

 

*Update* Dear God, btw I wrote this first thing after getting home from work and relaxing, and MAN I sound like a soft serve vanilla ice cream cone served on a giant marshmellow. Like I read, watched the movie of and ate a copy of the Notebook and then had a fight with my cats and cried for three hours before writing it. 

 

Shows you how happy I am to be off of work. @ Traverse: Sorry if it seemed like I'm virtually brown-nosing, I'm friendly, but not that friendly. I'm a cat person. In my heart, I think all cat people truly hate people. But not cats ^^

Edited August 24, 2015 by Arrpeegeemaker

[Traverse 144]

Oh, I apologize if I came off hostile, I wasn't directing all of my post towards you specifically - just as a general comment to everyone who was wondering if scripts from XP/VX/Ace might be easily usable in MV.

 

But no, I'm actually not the most informed and up-to-date of the people posting here. That honor would have to go to Archeia (who I don't think has made any posts here beyond the first page). Sadly, as she's an actual beta tester for RMMV, she's bound by a non-disclosure agreement and can't really say anything that hasn't already been released by EB/approved by their PR people.

 

However many other beta testers who've posted here too, I can safely say I'm not one of them.

[Arrpeegeemaker 136]

Oh I didn't mean it like that lol I was saying bringing the hammer of reality down like 'making me realize something' but in a big way. I guess my wording was weird. I would have loved to beta test MV, but I have literally no qualifications whatsoever. 

 

I'm starting to think I might get on board with the 'wait a while' people when it comes to MV. It is gonna be a while before I'm done with anything I'm committed to on Ace, anyway.

[+ Takeo212 1,079]

Due to financial stuff, I personally don't see enough new content with MV yet that would encourage me to pay full retail price for it yet.

I got ACE during a HumbleBundle deal a while back and even paying full price for something I only intend to use as a side project/hobby made me sad.

I really wanted it - just rent, bills and food comes first lol.

 

I am really interested in the side view system it will apparently have, as well as the RTP built in. I'm sure Ace RTP can be used if you convert it yourself, just like how we can use XP tiles if you manually convert them. I'm more interested in new content.

 

I'm unsure if I should even study up on RGSS3 anymore due to the Javascript now. Ruby was something I wanted to learn - i even stopped caring the college because I simply wanted to learn Ruby and make games.

 

I might be with alot of other people though - I really want to own MV, but with projects already in progress, it'll be wise to buy it later when support and content is available and not straight away for either; MV not to be used due to current projects, or current projects gets neglected/abandoned for new MV projects.

[Kayzee 4,032]

I really think the VX Ace community should consider making a open source version of VX Ace the same way people did with RPG Maker 2003, but we will have to see how MV works out.

[+ Retired 274]

I really think the VX Ace community should consider making a open source version of VX Ace the same way people did with RPG Maker 2003, but we will have to see how MV works out.

 

Those people have no useable version and started in 2010. They even recommend that you just buy 2003 because its legal to purchase in the West now.

[Tsukihime 1,489]

I really think the VX Ace community should consider making a open source version of VX Ace the same way people did with RPG Maker 2003, but we will have to see how MV works out.

I'm not sure how useful that would be. If MV works well and the only thing that's really lacking are input methods, we can just fill in those blanks with separate tools.

 

Given that it will use javascript, it should be much easier to build tools on top of it since there's no need to deal with ruby-specific things like its serialization method.

[amerk 1,122]

 

I doubt many old scripters will be keen on rewriting their scripts*. You'll just have to pray that some part of the larger community of JavaScript coders take enough interest in the engine to make new plugins that do what the old scripts did.

 

 

 

The same may even be said about the game developers. I do realize this is similar to the naysayers who were bent out of shape about staying with VX when Ace came around because Lord forbid they buy another maker when they could already do the same with VX, even if they had to use the faulty SwapXT tile swap script.

 

But there is a big difference between the changes that happened between VX and Ace than what appears to be happening between Ace and MV. Don't get me wrong, the few changes we have seen with MV are definitely important (higher resolution and multi platform for one), but it still doesn't look like a huge impact over Ace than what Ace had over VX, especially when, all things considered, these things should have been offered to Ace from the beginning.

 

While it remains to be seen how much we really know and how much has changed, from a cursory glance at the topics and the site showing off MV, we still appear to be having issues with auto layering, mapping is still confined to a grid (when I would have loved for a more in-editor parallax tool), the potential of previous resources from XP, VX, and Ace may not automatically work with MV without some effort and elbow grease to reformat them and probably repaint some of the pixels (which may render a lot of the current resources as useless to people without the know how), and all of this on top of added features many can already do (with scripts) in Ace.

 

At the very least, adding JS to Ace from the get-go would have made Ace that much better of a buy, because it would have stood out amongst a sea of other changes going on at the time. A lot of people seemed to have purchased Ace for the default changes between VX and Ace alone rather than the upgraded RGSS language, and by the time they got through absorbing all that Ace had to offer, scripts started to trickle in.

 

But from reading comments here and abroad, the changes going on between Ace and MV may not be enough to drive people to open their wallets like they did with Ace, especially if they feel the changes don't have quite the impact that Ace had over VX, even while replacing Ruby with JS.

 

I'm glad EB is finally rolling with these changes, but it's a bit of a wonder why they weren't done sooner, and if it may be too late when other game makers have had a leg up on such features for the past few years. Again, time will tell.

[Traverse 144]

I don't know how many people opened their wallets for Ace but the fact that Ace was released on, from what I can tell, many more distribution channels than VX (Steam and Humble Bundle, ect.) would probably have played a fair part in its success.

 

Feature wise, I'd equate the jump from Ace to MV as similar to the jump from 2k3 to XP. In both instances, Enterbrain changed the core coding of the engine and there was a clear jump in quality and format of resources used (at least in the RTP), with minimal features lost. In the transition from 2k3 to XP, I don't think I'd be wrong to say that more than a few users of 2k3 were hesitant to open their wallets for XP - I'm inclined to believe that much of the XP crowd were fresh blood. I could be wrong, I don't have any statistical evidence to back it up, just a feeling I get from the old flame wars between those who fervently condemned the users of non-official-English makers and ones who used to use said makers around the time XP got localized.

 

Similarly, I wouldn't be surprised if the bulk of MV users will be new meat. There are going to be Ruby coders, people who've already invested in Ace or other makers and those who just don't have the resources to meet the new resource format/code JS losing interest. On the other hand, the new features MV does have are certainly going to attract mobile developers and the multitude of JS coders.

 

I'm not going to bring VX anywhere into the picture here - VX was the first maker where Enterbrain unashamedly dropped a whole bunch of features with no easy substitute, the reason for which still utterly eludes me.

[Squires 35]

I think the only thing I'm digging is the 32x32 icons. I'm always frustrated when I accidenally forget the VX Ace dimensions for icons. 

Although, I've spent too little time in XV Ace to lose that much switching engines (Or upgrading, in that matter?).

[Rinoazelda 287]

What does MV stand for?

[Rikifive 3,411]

Probably Mobile Version.

[Rinoazelda 287]

If EB did a way to export Ace games to Mac and Android using MV, I would buy it day one.

[YamiKitsune 23]

I just hope I don't have to make an account on another community forum. I have alot of friends here and re-adding them all would be so tedious.