Just a nameless weakling
- Jan 2, 2014
- Reaction score
- First Language
- Primarily Uses
Maybe RM should just hire you guys as well
Plugins can, during local runtime, write to and create files on disk. Some of my MV plugins made index files to be used in published games that might run on a server and not have access to the file-system, instead referencing the index file to figure out where the files it should load were found. And example would be the preload manager plugin.I think it would be easy if plugins aren't marking static paths as required assets.
What I'm more concerned with is when the filenames are specified by users, or the filenames are generated dynamically at runtime. Not much you can do there in general
I don't mind partial chibis, like the Dark Fantasy "tall" character style. In fact, I think it looks great and still captures that oldschool FF nostalgia. The standard-sized RM chibis though? They're too squat and as such, much of the details for their clothing, motions, etc is lost because of that. They're like all head.People bashing on the tiny PCs fighting big battlers.
Personally I don't mind it myself given I'm a fanboy of the old games though I wish they would make it a tad easier to put in large sprites or more frames for battle.
An "Either or" option is all I'm asking for.
Not as easily replaceable. Well at least I don't think so. It's a tad annoying/hard to keep within the 64x64 sprite box.I don't mind partial chibis, like the Dark Fantasy "tall" character style. In fact, I think it looks great and still captures that oldschool FF nostalgia. The standard-sized RM chibis though? They're too squat and as such, much of the details for their clothing, motions, etc is lost because of that. They're like all head.
Since MZ didn't move on from that atrocious style, I guess I just have to hope that the next RM after MZ finally does. They're easily replaceable though, so at least we have that.
The tkool guide on writing plugins actually covered this:The fact is that the problem of copying RTP to the project folder remains. The problem is that the function exclude unused resources can also exclude resources used by plugins. Which makes it impossible to use it together with file encryption.
And this cannot be fixed. To prevent this from happening, all the resources in the plugins must be indexed, but no one is doing this and most plugins do not specify these parameters. Which leads to the fact that resources are considered unused.
The challenge with specifying them static like that is that what if you let the user select assets via plugin configuration, as is possible with the plugin param type specifications? You can solve this -- as I mentioned briefly -- as a plugin developer by writing these dynamically to an included plugin file during playtest using node's filesystem commands, however. I might make a tutorial and a minimal code snippet once MZ releases; I've done this in MV already for a personal plugin.The tkool guide on writing plugins actually covered this:
If you are loading images directly in your plug-in, you may find that you want to exclude the unused files if you check Exclude unused files when performing the deployment.
・Image_1.png in the img/pictures folder
・Image_2.png in the img/system folder
-Img/example folder image_3.png *
Is the code to refer to each.
let b1 = ImageManager.loadPicture("image_1");
let b2 = ImageManager.loadSystem("image_2");
let b3 = ImageManager.loadBitmap("img/example/", "image_3");
*This is an example of specifying an example folder that does not exist by default due to the plug-in description.
However, the image will be deleted as it is.
If the image file to be used is fixed, please describe the required file after @requiredAssets.
* @requiredAssets img/pictures/image_1
* @requiredAssets img/system/image_2
* @requiredAssets img/example/image_3
In MV, '@require 1' also requires the '@dir' parameter to work. That is, you must hardcode a directory, which keeps it from being useful for a general-purpose 'include this in the compile' plugin.I'm not sure about MZ, but assuming it's like MV, there's the "@require 1" setting for that case.