Add Discord User ID argument to onPlayerConnect when Discord RPC is connected

[simoofficiel]

Is your feature request related to a problem? Please describe.

No

Describe the solution you'd like

I would like to request an enhancement to the server-side onPlayerConnect event.

Currently:

onPlayerConnect(playerNick, playerIP, playerUsername, playerSerial, playerVersionNumber, playerVersionString)

Proposed:

onPlayerConnect(playerNick, playerIP, playerUsername, playerSerial, playerVersionNumber, playerVersionString, discordUserId)

When Discord RPC is connected and the Discord User ID is available, discordUserId should contain the player's Discord User ID.

If Discord RPC is not connected or the ID is unavailable, discordUserId should be nil.

Describe alternatives you've considered

Example:

addEventHandler("onPlayerConnect", root, function(playerNick, playerIP, playerUsername, playerSerial, playerVersionNumber, playerVersionString, discordUserId) if discordUserId then outputDebugString("Discord User ID: " .. discordUserId) end end)

Additional context

Possible use cases:

• Discord account linking
• Whitelist systems
• Connection logging
• Discord integration
• Server security systems

For backward compatibility, the new argument should be added at the end of the existing arguments so existing resources will continue working without modification.

Security Policy

• I have read and understood the Security Policy and this issue is not about a cheat or security vulnerability.

[iManGaaX]

Discord user IDs are fetched on the client-side, whereas onPlayerConnect is a server-side event.

[Rilot06]

It would be completely insecure, discord user ids are just what the client says they are, it's not an actual server authentication, should never be used for any type of security/auth.
Sending it as an official server side event argument would falsely hint that it's a secure id, I don't recommend this being implemented.

[Fernando-A-Rocha]

See what mta neon did for server side identity