RMMV Changing the opacity for a specific window in battle

[Kokonaugt]

Hey! I'm trying to remove transparency from all the assets in my games (or as much as possible) : I managed to make all of the menu windows that I know of opaque, except this very specific one that appears during attacks in battle.

Do you know where I could edit the code to make it opaque once and for all, or if a specialized plugin could help me with this?

 

[slimmmeiske2]

I've moved this thread to Plugin Requests. Please be sure to post your threads in the correct forum next time. Thank you.

 

[caethyril]

You could try sticking this in a .js file (e.g. in Notepad, Save As > File Type: All Files, Filename: whatever.js) and importing as a plugin (untested):

Window_BattleLog.prototype.backPaintOpacity = function() {
    return 255;  // originally 64
};

 

[Kokonaugt]

You could try sticking this in a .js file (e.g. in Notepad, Save As > File Type: All Files, Filename: whatever.js) and importing as a plugin (untested):

Window_BattleLog.prototype.backPaintOpacity = function() {
    return 255;  // originally 64
};

Thank your for your answer, I managed to do it yesterday evening after I figured out the window was called "BattleLog". What I did is change the line you're talking about in rpg_windows.js.
Is there a reason to rather create a plugin for this, or is it alright to just edit the code in rpg_windows.js like I did?

 

[caethyril]

Thank your for your answer, I managed to do it yesterday evening after I figured out the window was called "BattleLog". What I did is change the line you're talking about in rpg_windows.js.
Is there a reason to rather create a plugin for this, or is it alright to just edit the code in rpg_windows.js like I did?

The in-game effect should be identical.

Editing rpg_windows.js directly can cause unnecessary confusion if, at a later point, you're looking for help on some problem but are using an edited version of that core script file. (Updates to the core scripts could also be an issue, but RMMV isn't receiving any more updates so no worries there.)

Making your edit(s) into plugin(s) means they can be tracked easily and turned on/off via the Plugin Manager if you need to do some debugging or change your mind about a feature.