🌊
WaveShield v4
  • GETTING STARTED
    • 🤝Redeem
    • ⚙️Installation Guide
  • documentation
    • ❓How To
      • 🎫Bypass Staffs
      • ⛔Unban
    • ⚙️Configuration Settings
      • 🌳Objects
    • 💻For Developers
      • 👉Exports
      • 🗑️Event Handlers
    • 🤖Commands
  • Troubleshooting
    • ➡️READ THIS
    • ⚠️Common Issues
      • Black Screen/Infinite Awaiting Scripts / Errors after installing WaveShield
      • Server crashing at startup / A Script is not starting
      • A Script is not working properly
      • FPS Drops / Loss
      • I get other ban than mine
      • Input Boxes limited to 2 characters
    • 🙅Common False bans
      • Trigger Client/Server Events
      • vMenu
    • 📈Performance Issues
Powered by GitBook
On this page
  1. Troubleshooting
  2. Common False bans

Trigger Client/Server Events

PreviousCommon False bansNextvMenu

Last updated 16 days ago

If you are experiencing false ban issues related to our automatic event protection, here's how to fix them so you can use this awesome feature.

  • Make sure you don't use any other type of "event protection", "anti-trigger", etc. You'll need to remove the resources that interfere with the event system (or disable the option if you can).

  • Make sure you have no code at all that overrides the TriggerEvent, TriggerServerEvent & TriggerLatentServerEvent functions, that will also need to be removed, here is an example of what it can looks like.

  • Make sure you have not ignored the script in the config (you must not)

TriggerServerEvent = function(eventName, ...)
    return TriggerServerEvent(eventName, ...)
end;
  • If you still have this issue after you checked this, then you will probably need to whitelist the event because your script is surely made in C# or JS and WaveShield event protection is only working for LUA scripts at the moment.

PLEASE IN ANY CASE DON'T ADD THE SCRIPT THAT CAUSE THE ISSUE TO THE IGNORED SCRIPTS BUT FIX THE PROBLEM THROUGH THIS PAGE. For more informations,

🙅
please read this
Configuration Panel