[RELEASE] rbSafeEvents (PROTECT YOUR SERVER) [PAID]

FiveM Resource Development & Modding Releases
,
1

RBsafeevents
RBsafeevents960×540 38.2 KB

What does this do? :thinking:

This adds a layer of security to your server events, after checking them, it evaluates if the event is real or not.
With this script, you can detect almost every cheat that tries to use events.
For now, lenue can’t bypass the script in any way.
It’s time to put those event blockers away!

Why should you use rbSafeEvents? :closed_lock_with_key:

Cheats and menus are evolving as fast as they can, if you still encrypt your scripts so people can’t get your triggers, that’s not enough, cheaters are getting events and their data through event loggers.

Feature list :heavy_check_mark:

  • Protect your client->server events!
  • Optimized
  • Standalone

To do :hammer:

  • Make a better and easier installation (it’s already easy but I want it even better)

You can PreviewđŸ“· & BuyđŸ”„ it!

ps: installation included on download
Code is accessible No (escrow)
Subscription-based No
Lines (approximately) 500-1000
Requirements nothing
Support Yes
1 Like
2

How does this actually work?

1 Like
3

Well, i can’t really tell the technical parts but, we’ve created tool that verifies the authenticity of the event with the help of a key and a “token” (not FiveM tokens, our own token).

If you need any help or if you have questions about the script you can always come to our support dc server and we will help you!

4

The token has to be saved somewhere client side, that means there is a way someone can easily get the token.

Also I think it is almost similar as Salty Token, just escrowed.

Can you post the installation guide here? Just want to check how to install before buying.

1 Like
5

It’s not like Salty Token, it’s not just a “token”, every trigger has a different “token” and that token its only valid for 1 time use, and if you try the same token on other server it will be invalid.

How to install rbSafeEvents on other scripts:

  1. Choose the script you want to protect

  2. Change his fxmanifest.lua or __resource.lua: → Screenshot by Lightshot

  3. Change your’s RegisterServerEvent
    3.1 Old → Screenshot by Lightshot
    3.2 New (a new argument is being passed, it’s the player ID!) → Screenshot by Lightshot

ps: the token is not always the same because they are calculated on the go

Edit1: ps part

1 Like
6

Is it still being triggered using TriggerServerEvent?
and is it possible to Trigger an event From server side to server side?

1 Like
7

Yes, you don’t need to change nothing on the client side!

Actually i didn’t think about that till now.

Just pushed an new update to escrow:

  • Now you are able to trigger events SERVER->SERVER but source will be nil
  • Better error manager
8

Everything seems smooth now

1 Like