onClientDebugMessage/onDebugMessage recognize level 4 as 0

[srslyyyy]

Describe the bug

As in title.

Steps to reproduce

outputDebugString("test", 4, 255, 255, 255)

-- client

function onClientDebugMessage(debugMessage, debugLevel)
    iprint(debugMessage, debugLevel)
end
addEventHandler("onClientDebugMessage", root, onClientDebugMessage)

-- server

function onDebugMessage(debugMessage, debugLevel)
    iprint(debugMessage, debugLevel)
end
addEventHandler("onDebugMessage", root, onDebugMessage)

Version

r22489

Additional context

Level 4 was added in #1167

Relevant log output

No response

Security Policy

• [X] I have read and understood the Security Policy and this issue is not security related.

[TracerDS]

Hmm, looks like level 4 calls LogCustom which calls LogString with level = 0