Anti trigger event protection
Last updated
Last updated
Make sure that you started the event protection resource as first resource in server.cfg, above your resource list.
Make sure to create a backup of your resource before you use this command in order to recover it.
In case the command for adding event protection to the resource does not work properly for you or you want to protect only some events from the resource, you can also add the event protection manually. To add event protection manually you have to replace in your server scripts from the resource the AddEventHandler with SecuredEventHandler for all events you want to protect and add in fxmanifest the following lines:
The raceventprotection command is no longer working on the latest server artifacts. In order to make it work, you must temporarily turn off your server and switch to an older artifacts version where the command is still supported, for example the Last Recommended (7290). After you switched to an older artifacts version, run the command to install event protection on all your resources where you need the event protection. After you added the event protection to your needed resources, you can revert back to the latest artifacts version. If you do not want to change your artifacts and then revert to your initial artifacts, you can do the process of adding event protection manually.