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

Client-Side: Securing Event Triggers

To securely trigger events from the client to the server, we use the SecurityClient.TriggerSecure function. This function checks if the event is in the whitelist or blacklist and blocks triggering accordingly.

How It Works:

  1. Whitelisting: The event is checked against the whitelist. If it’s on the whitelist, it will trigger normally.

  2. Blacklisting: If the event is on the blacklist, it will be blocked, and the client will receive a notification.

  3. Logging: Each action is logged for visibility and troubleshooting.

  4. UI Feedback: You can customize UI feedback to inform players when events are blocked.

Example Usage:

-- Trigger an event to spawn the player
SecurityClient.TriggerSecure("player_spawn")

-- Trigger a non-whitelisted event
SecurityClient.TriggerSecure("malicious_event")
PreviousSecurity Detailed ExplanationNextServer-Side: Securing Event Triggers

Last updated 1 month ago

Was this helpful?

πŸ’…
🌐
πŸ”