NWjs essentially replaces the web browser for running javascript so if you run your game in browser, it's using the browser run instead of NWjs. So the version would not affect your game if you only run in browser.
However, pixi is a js library imported by rpgmaker and so the version of that would affect your game while running in browser.
Thanks that's what I thought, so my improvements on browser were only from the pixi update, and it explain why my game performed better on browser than on my computer (editor) before the pixi and nwjs updates I just made.
So the nwjs update will only impact my finished game if deployed to windows in .exe format right ?
The only way to improve performance on browser is by pixi updates ? (seems like 1.8.9 is the best stable one tho)
You can ignore those warnings, the Audiocontext thing will prevent sound from playing before the player puts any input in the game context frame on browser but it should be fine
For this one I did make it disappear by adding a click condition on my website window, for the "Canvas2D multiple readback" no risk or way to erase it safe too ? I did find a way by adding this where the error shows in rpg-core.js
function init() {
canvas = document.getElementById("canvas");
canvas.getContext('2d', { willReadFrequently: true });
anim_container = document.getElementById("animation_container");
But I'm not sure if it will conflict with Webgl or more..
Tho this warning mention resolve it can improve performance so I'm intrigued.