Closed KraXen72 closed 3 years ago
The "source" of this warning is in Krunkers code. Not much we can do about it except hiding it or nulling out the caller.
The reason why this error shows up on idkr, is because we re-bind the original console
object from Krunker:
https://github.com/Mixaz017/idkr/blob/master/app/preload/global.js#L157-L158
That warning happens on every client and on every browser. It's just hidden.
oh, interesting. i know that krunker disabled console logging (which is not a particualrly nice thing to do), and i didn't think reenabling was possible but here we are? anyway thank you for clarifying. i'd just suggest binding the old console to some custom object that only idkr uses so krunker doesen't have the console but idkr does
What. Krunker logs are as important as idkr logs.
there are 10 console warns every second which slows down the client a lot on latest master.
i temporarily fixed it by adding
console.warn = () => {}
but that's not a real solution. please fix the source of this warn. thanks