[Bug] playerConnecting setKickReason

[xHamish]

Summary

Setting the kick reason inside of the playerConnecting event to nil will crash the server.

here is the code used

AddEventHandler("playerConnecting", function(name, setKickReason, deferrals)
    setKickReason(nil)
end)

Issue type

Server

Repro rate

Always

Server build version

b139 w32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Inside of a playerConnecting event use the second provided parameter (setKickReason) and provide a nil reason

Expected Behavior

Server shouldn't crash and instead just kick the player with a blank or empty message.

Actual Behavior

Server crashes

Evidence

No response

Additional Context

No response

[wolfram-cfx]

Thanks, we are looking into this.