was not safe for net

[imsnaily]

So basically you can crash a server spamming TriggerServerEvent of the server events as playerDropped, playerJoining, explosionEvent, etc...

If there's a good amount of resources that handles that events the server will just crash. It could be a nice thing to like "whitelist" this events and prevent from using them on TriggerServerEvent

[tens0rfl0w]

I'm curious if you actually managed to "crash" a server with this method, as testing this on a loaded server had no impact at all. (If you did, you could provide your crash dump.)

Dropping this event client-side wouldn't make much sense as someone who would abuse this would already be able to execute arbitrary code. (Also the event handlers like playerDropped can be registered as network events per script, so blocking this could result in broken scripts, though usage is unlikely due to the prints 'monitor' and other stock resources produce.)

Blocking those certain base events would still leave all other custom events open for this kind of approach. (Server frameworks have a lot of those generic event handlers.)

Still curious if you managed to "crash" a server with this, as the dropping of such events should be lightweight.
For reference the lua implementation just drops the packet and doesn't process it at all (per script):

fivem/data/shared/citizen/scripting/lua/scheduler.lua

Lines 162 to 167 in 47adce0

	if not eventHandlerEntry.safeForNet then
	Citizen.Trace('event ' .. eventName .. " was not safe for net\n")
	_G.source = lastSource
	return
	end

[Zydson]

It won't crash, only will heavily load on CPU, also seems like you are running localhost so you don't get kicked for network event overflow. Normally you could not spam events every 0ms without getting kicked.