08-20-2023, 05:17 PM
(This post was last modified: 08-20-2023, 05:24 PM by DerVVulfman.)
BUMP
to version 1.2
True, only a day has passed, but the Zlib system that creates .png files has been replaced with another. This replacement is based upon those found within utility systems such as MapMaker.
However, the replacement code is a hybrid between the Zlib and MapMaker scripts. While MapMaker's code is able to more quickly create .png files, the generated files cannot load through RPGMaker's cache system. This annoyance was part-and-parcel to how the MapMaker code ended the data blocks within the .png files. So corrections based upon the Zlib edition were made.
Also, the hybrid code includes a little tweak courtesy of yours truly.
It is known to some within the RPGMaker XP community that the 'Graphics.update' command must be executed at least once every ten seconds, otherwise the game engine itself thinks an error in scripting may have occurred. Something like an endless and recurring loop would cause such an issue. And if one was to execute either Zlib or the PNG creating system for extremely large graphics (imagine a 500x500 map), it could take much longer than 10 seconds depending upon the PC. Obviously, the system would shut down and exit.
The hybrid which I provide includes a counter of sorts, actually looking at how many iterations have passed during the creation of the .png bitmap, and execute Graphics.update on a fairly regular (but quite spaced apart) basis. This would avoid the issue with the Game.exe thinking that it has run into an endless loop, and allow it to function even with massive image files.
* * *
Due to the ZLib system being replaced, the use of the SYSTEM_MODE variable within the configuration page no longer exists. This latest edition no longer has this configuration variable. If you already have defined your configuration page, there is no worry as the elimination of SYSTEM_MODE would not hamper your setup.
* * *
Just for kicks, I added the timed 'screen-saving' feature into Scene_Battle. While using the default [Call Save Screen] built into RPGMaker XP kicks you out of battle and into the Field Map (ugh), someone may be inventive enough to find a way to save their game while in combat. For this, I added screen shot capability.
So no, it does not save your games IN combat. But it will generate the screenies for someone who DOES come up with such a feature.
So no, it does not save your games IN combat. But it will generate the screenies for someone who DOES come up with such a feature.