RPG Maker MZ 1.4.4 Patch Notes

Archeia · 2022-02-25T17:51:48+0900

Hello RPG Makers! The latest update, Version 1.4.4 is live! Thank you for using RPG Maker MZ. As always, we appreciate your support! We hope you are enjoying it so far. Download Link: Download here! Bug Fixes Implemented a countermeasure to the problem that may cause the NW.js process to not terminate normally in Windows environment. Fixed an issue in which the cursor position would move to a different page when any frame was selected in “Create MV- compatible data” and the frame was deleted while editing the frame view. Fixed an issue in which events would appear at unintended coordinates after switching maps and loading events with “Autorun” events. Fixed the problem of "File name "None", Volume 90%, Pitch 100%" when "Play SE" is edited in ”Set Movement Route”. Fixed an issue in which fade-in was not performed when loading data if the project data had been changed. How to update your project(s): Create a backup of your project or only its data and js folders. Updating can sometimes cause your project to break so this is for the safety of your hard work! Update your project by going to the Main Tool Bar -> Game -> Update Corescript option. Latest Corescript version: 1.4.4 Known issues for 1.4.4 There is an issue where the game does not automatically close after executing Enemy Group -> "Battle Test". Please close with "X". Restore main.js to a previous version (update the core script).

● ARCHIVED · READ-ONLY

Started by Archeia Feb 25, 2022, 08:51 AM 32 posts Page 2 of 2 View original ↗

Jams

#21 Apr 29, 2022, 02:51 AM Source

On 1.4.4, Player transfers with no fade flashes the sprite sheet on the screen before the transfer completes. This does not occur on 1.4.3.

Additionally, the icon for the menu in the upper right flashes for a second as well. Though the latter issue is regrettable, I can just disable it. However, the former prevents me from upgrading my core.
Saliacoel

#22 May 14, 2022, 11:30 PM Source

Cool update, but I'm getting random crashes.
Not funny.
rayminator

#23 May 15, 2022, 12:14 AM Source

Saliacoel said:
Cool update, but I'm getting random crashes.
Not funny.
what were you doing before it crashed?

it crashes on me when I'm adding pictures.
Saliacoel

#24 May 15, 2022, 02:32 PM Source

rayminator said:
what were you doing before it crashed?

it crashes on me when I'm adding pictures.
Yes, now that you say it..
It crashes when I click on the button pick the picture in Show Picture.
rayminator

#25 May 15, 2022, 02:59 PM Source

Saliacoel said:
Yes, now that you say it..
It crashes when I click on the button pick the picture in Show Picture.

it has been reported already just to wait for the next update

here is what you can do for now is to add a few images then close window and save then repeat
Synchromystic

#26 May 20, 2022, 02:06 AM Source

Not sure if my problem is related to what everyone is talking about here, but I just posted this in its own thread a while ago, since I couldn't seem to find anything relevant with my search results... Perhaps not entirely relevant since this began while I was using 1.4.3, but this is what I'm experiencing:

I've been dabbling in MZ for Mac on and off for about a year now, no type of coding knowledge whatsoever so any replies to this will have to be dumbed down pretty good for me to grasp them... But I was creating a few scenes earlier today, everything was working fine and then I added one more line of dialogue to a scene I was working on, hit the "playtest" button, and it immediately crashed. It threw up an "nwjs quit unexpectedly" error and asked me if I wanted to reopen it, but my response doesn't change what happens next: The play test window continues to try to load for a second, then gives the error message again and closes.

The editor and everything is still working just fine, I was using version 1.4.3 and tried jumping around to other versions - including the newer 1.4.4 - and nothing seems to change. I deleted the event that I had finished making just before the problem first occurred, so that my game's situation is exactly as it was when it was working, but I still can't play test. What the heck happened, and how do I go about addressing this?
Andar

#27 May 20, 2022, 11:35 AM Source

@Synchromystic if I remember correctly, the playtest uses a reduced variant of the chromium engine.

if you have the chrome browser installed and either updated it or changed its settings, those changes would then be added to the chromium engine of the playtest function automatically - and I know that chrome has some more critical default settings where it blocks "websites" that it believes to be infected - and that can cause problems with local HTML-games as well.
Synchromystic

#28 May 20, 2022, 01:20 PM Source

I've never used Chrome, and hadn't updated anything on my system in a while, so I doubt that would be the issue.
skatefilter5

#29 May 27, 2022, 05:17 PM Source

random crashes occurs where I try to add new tilesets.
Synchromystic

#30 May 29, 2022, 03:29 PM Source

Update on the nwjs error I mentioned above:

It seems the Visustella Core Engine plugin was to blame, but I was fortunate enough to stumble upon a fix. For some reason, the plugin's default settings make play testing absolutely impossible on all of my Mac systems... In order to get it to function at all, you MUST go into the Screen Resolution Settings, find the option that says "For MZ 1.3.0+?" and change the value to "True" and then it will start right up.

Extremely simple solution, but somebody really should do something about this because we're given no indication at all that this problem is going to occur by default, and I seriously doubt anyone who is jumping in to MZ at this point is going to start off by rolling back to an earlier build where the error won't occur.
Andar

#31 May 29, 2022, 03:57 PM Source

skatefilter5 said:
random crashes occurs where I try to add new tilesets.
then you're doing something wrong.

the only way a picture can crash the game is when the filename for that picture breaks the networking rules.
so remove all spaces and all special characters and it should work.
skatefilter5

#32 Jun 19, 2022, 06:25 PM Source

Andar said:
then you're doing something wrong.

the only way a picture can crash the game is when the filename for that picture breaks the networking rules.
so remove all spaces and all special characters and it should work.
ok