> For the complete documentation index, see [llms.txt](https://ayznnn.gitbook.io/waveshield-v4/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ayznnn.gitbook.io/waveshield-v4/troubleshooting/common-false-bans/trigger-client-server-events.md).

# Trigger Client/Server Events

*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)

```lua
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.

<figure><img src="/files/RaLKVp7JubVJdu1uwur5" alt=""><figcaption><p>Configuration Panel</p></figcaption></figure>

{% hint style="danger" %}
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**](https://ayznnn.gitbook.io/waveshield-v4/troubleshooting/read-this)
{% endhint %}