@hsumi
You are right. I just quickly looked into this:
JavaScript:// This is my code for getting any minimap images:
ImageManager.loadMinimap = function(filename, hue)
{
return this.loadBitmap('img/minimap/', filename, hue, false);
};
// So I use this code from the RMMV core:
ImageManager.loadBitmap = function(folder, filename, hue, smooth) {
if (filename) {
var path = folder + encodeURIComponent(filename) + '.png';
var bitmap = this.loadNormalBitmap(path, hue || 0);
bitmap.smooth = smooth;
return bitmap;
} else {
return this.loadEmptyBitmap();
}
};
So I first thought that RMMV does not take into account deployment paths at this point and that they hid this code in their closed source. But that is not the case because generated maps DO work including the loading of other images like "Overlay.png" that are located in the very same folder.
But:
I was able to force it to work by creating a separate "img" folder with the minimap files in the main directory. The plugin will not find the correct files within the generated "www" folder created during deployment that contains all the other files.
This does seem to fix it... Maybe I just made a stupid mistake somewhere.
I made sure that "Exclude unused files" isn't checked and I verified that the images do get deployed. So this code can load images like "Overlay.png" but not images like "001.png"... So I changed the names from "001" --> "a001" to prevent it starting with a number. Still didn't work.
Of course, there is no option in RMMV to enable the console for deployment and I just found out that the big update to RMMV also broke my
Console Manager plugin so I can't debug it right now.
This is a rather serious bug that you found. However, first I'd have to fix my console manager to debug this and then find the bug in my Minimap plugin. It's probably one or two lines of code but I can't fix it in 30 minutes now so I'll have to fix it, someday... Maybe I ask a friend to look into this for me this weekend but no promises.