suppress warnings/errors

[Bonsai]

Hey Peeps,

is there are way to suppress warnings and errors, so they don't show up in the debuglog?

I have a resource that is producing a lot of errors, but those errors are not important and not fixable (map scripts).

But they are spamming my debuglog too much so actual problems might be missed.

Is there something like that?

Bonsai

[Captain Cody]

Any error is fixable, what's the issue?

[Bonsai]

Any error is fixable, what's the issue?

Well surely they are fixable, but its not my business.

As I said, its maps scripts that are loaded and executed, I cannot fix them all

[Captain Cody]

Well in that case, try just debugscript 1

[John Smith]

Try cancelling onDebugMessage if specific conditions are met. (not sure if it'll work, just guessing)

edit: won't work.

[AlexTMjugador]

The only thing you can do to effectively hide errors and warnings which originate from scripting errors is making your own debug view, hiding the default one and control which messages do you want to be output to the new debug view by using the onClientDebugMessage event.

However, if that warnings and errors are caused by explicit calls to the outputDebugString function, you can disable that function (providing that scripts don't call it in a hacky manner, or overload it with another name) by using addDebugHook:

local targetResource = getResourceFromName("resource-name") 
  
local function disableDebugOutput(sourceResource) 
    if sourceResource == targetResource then 
        -- Don't call the actual function if the call is from the resource we want to block 
        return "skip" 
    end 
    -- Otherwise, continue normally 
end 
addDebugHook("preFunction", disableDebugOutput, { "outputDebugString" }) 

Keep in mind that addDebugHook and any other approaches to hide that warnings are not designed with performance and retail use in mind, so it is not a good practice to just hide the errors in the script. Fixing the errors which cause the debug spam is the thing that should be done instead.