Remove "access denied" console print

[nta]

@Keyinator

The Any update on this? was not meant as Has there been any progress since this week? but rather due to the fact that my original post was lacking a lot of information which I then updated. I wanted to make sure that the problem has (just) been acknowledged with the further information I provided.

Right, and this is understandable. I believe no acknowledgment was posted mainly because the actual request itself wouldn’t be implemented, and as such said acknowledgment (“this has been noted but won’t be implemented in this way”) could lead to a negative response in return (“why don’t you implement this simple thing? it’s so annoying”).

Not responding indeed was a bit open to interpretation, too, though. A ‘Noted.’ could’ve worked but could also have been too… empty.

@Keyinator

My main concern was that I use the console as a first way of checking for any unwanted discrepancies from expected server operation (script errors, etc.).

… which is in itself a different issue yet again, see also the long-standing todo entry of an ‘issues tab’ of sorts being needed so that there’s a more persistent and structured place to show anything actionable.

@Keyinator

I’ll look into how we can use them

Updating to a newer server version should be enough to use such, the default is to not print any output from client-forwarded commands, assuming that’s what is causing these prints.