Codex Studios
Visit our Tebex StoreOur Discord
  • ๐Ÿ‘‹Welcome to Codex Studios
  • Overview
    • ๐Ÿ’กAbout Us
    • โœจOur Features
  • ๐Ÿ’…RedM-Scripts
    • ๐ŸŒ[Codex Studios] : Core
      • Client Side
      • Server Side - CodexCore API
      • Config
      • ๐Ÿ“ Client Side (clientside.lua)
      • ๐Ÿงพ Server Side (serverside.lua)
      • ๐Ÿ›ก๏ธCodexCore Security Module
      • ๐Ÿ—’๏ธSecurity Detailed Explanation
      • ๐Ÿ”Client-Side: Securing Event Triggers
      • ๐Ÿ”’Server-Side: Securing Event Triggers
    • ๐Ÿ’ช[Codex Studios] : Trust Level
      • Client Side
      • Config
      • SQL
  • ๐Ÿ“ฆ[Codex Studios]: Supplies System
    • Client Side
    • Server-Side Town Supplies
    • Config
    • ๐Ÿช›Examples and Commands
    • Sql Updated
Powered by GitBook
On this page

Was this helpful?

  1. RedM-Scripts
  2. [Codex Studios] : Core

Server-Side: Securing Event Triggers

The server-side script handles event registration, rate-limiting, permission checks, and global event guards (whitelist/blacklist).

How It Works:

  1. Rate Limiting: Controls how often an event can be triggered by the same player within a specific time period.

  2. Permissions: Ensures only players with the right permissions can trigger sensitive events.

  3. Event Guard: Blocks events that are blacklisted or not in the whitelist.

Example Usage:

-- Register a secure event
Security.RegisterSecureEvent("player_spawn", {
    rateLimit = { maxCalls = 5, perSeconds = 10 },
    permission = true,
    log = true,
    handler = function(source, ...)
        -- Event handler logic for player_spawn
    end
})

-- Trigger a secure event (client-side will automatically be checked)
TriggerEvent("player_spawn")
PreviousClient-Side: Securing Event TriggersNext[Codex Studios] : Trust Level

Last updated 1 month ago

Was this helpful?

๐Ÿ’…
๐ŸŒ
๐Ÿ”’