RPG Maker MV 1.3.3 Update

Hey everyone, the latest version of RPG Maker MV is here!


We would like to remind everyone to make sure to do the following steps before updating to ensure that when the update happens so your changes won’t be overwritten:

• Make a backup of your Generator folder if you edited it. If you already upgraded from 1.2.0 this is unnecessary.
  
• Replace BGM files if you got it from 1.3.0. 
  

If you have an old project that needs updating, do the following:

• Make a backup of your project.
  
• Create a new project or go to the NewData folder in your RPG Maker MV root (where MV is installed) folder. 
  
• Copy the new js files (RPG*.js and Libs Folder) and replace the one in your old project. DO NOT COPY plugins.js or it will replace your plugin settings.
  
• Copy index.html files to your current project.
  
• It should now be updated!
  

Download Links (1.3.3)


Update Only


Latest Full Installer


Download Links (1.3.2)


Update Only


Latest Full Installer


Reporting Issues





Script Changelog


http://yanfly.moe/2016/10/20/rpg-maker-mv-1-3-2-update/


Editor Fixes

• Character Generator JSON Save and Load is fixed.
  

RPG* Updates

• Fix to the Skill owned condition in Event Condition
  
• Fixed some crashes in mobile play
  
• Fixed to the Scroll Text event command
  
• Pixi Bug: Unnatural Tile Scaling
  
• Pixi Bug: resolution is not defined
  
• WebGL Blend Mode: Overlay not working on certain features
  
• Character Generator：ID can now not be sequential, and qXXX can be used for ID too
  
• Fix to the damage popup when drain skill is reflected
  
• TilingSprite Scale Bug
  
• Fix to prevent negative value to be entered in Attack State
  
• Support for Direct Input Controllers (not ALL controller are supported)
  

Plugin Updates

• Fix to some Kadokawa scripts so that their files are not removed by the "Removed unused files" in Deployment
  
• BattleVoice.js
  
• Foreground.js
  
• TinyGetInfoWnd.js
  

aiii thank you so much we've been waiting for it ouo 

So uhm. The Charater generator cannot save or load .json files anymore?


Started a new project before I update the old ones, so haven't fiddled with anything. In other words, this problem is in a new project updated to 1.3.2.


Its the same with the old projects though.


Sorry if it's something painfully obvious.


Oh and thanks for the update! Nice to see MV getting better and better :)

nooooo are all the plugins going to break again  ;_;

It shouldn't unless they did something unique.

Oh that's good! I guess I have no room to complain and should be glad they're continuing development instead of letting it rot or something.  :D

Uploaded it.  Just to be certain...all Updates resets RTPs?  Because... well I am wondering how many times I risk flushing my own graphics...  Kinda!  (I wonder also the average of updates per new versions of RPGM out of curiosity!  ;)  )

Is there any risk to install the update if i own the steam version?

Steam is automatic :)

Does that means it just crap out automatically the BGM folder and generator one? (on Steam?)

RPG Maker Updates don't affect your projects. It has to be added manually by you. The first post tells you the details.


This includes the rtp.

My goodness, good job guys! Updating now!!

Mine still says 1.3.0, shouldn't i be worried?

I updated and while all the plugins i've used are in my plugin folder they are gone in game.  Do I have to add them and fix there settings again?

I don't see anything about the memory leak issue, was this addressed with this patch at all?

This is why in the first post we said, 

• Copy the new js files (RPG*.js and Libs Folder) and replace the one in your old project.
  

RPG*.js and Libs folder only. If you replaced plugins.js, you have to reset them. I hope you did backup............




It means that your memory leak is related to your resource handling. There is a fix for memory issues.

I misread and presumed it was the full js section.  At least I backed up this time, wouldn't mind but I've updated twice before.  Thanks dude, off to fix it I go.

Someone named Andar on here had mentioned that a final 'official' fix for internal memory issues was possibly being released with 1.3.2. I take it that was not included with this one.

There is a fix for memory issues here and the performance can be seen. Again, make sure to recheck all your resources and see how much memory it is eating. No matter how much optimization you do from code, if the resources themselves are not optimized, there is a limit to what we can do.

Thanks for this post Archeia! and the update. You guys are super!