You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 25, 2023. It is now read-only.
can you help me make disable melee (like punching) on rank 1, bcs i dont want new player punching everybody on the server D:
i made a thread that check player's rank and if its under 2, it will use disablecontrolaction native, it works if the player has relogged after he registered new character.
the problem is if a new player register on the server freshly, the thread isnt working (its like it give nil value when checking player's rank or smthing else is making it not working) and this new player can still punch until he relogged from the server
The text was updated successfully, but these errors were encountered:
I'll have to investigate further. This script listens for the 'QBCore:Client:OnPlayerLoaded' event which is fired whenever a player is loaded in whether it's a current or new character.
Right, I tried this on a fresh install with the QBCore recipe and loaded in as a new and current character and I can't reproduce the bug you're experiencing.
Are you using the standard qb-multicharacter?
Are you using the latest version of xperience?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
i use qb
can you help me make disable melee (like punching) on rank 1, bcs i dont want new player punching everybody on the server D:
i made a thread that check player's rank and if its under 2, it will use disablecontrolaction native, it works if the player has relogged after he registered new character.
the problem is if a new player register on the server freshly, the thread isnt working (its like it give nil value when checking player's rank or smthing else is making it not working) and this new player can still punch until he relogged from the server
The text was updated successfully, but these errors were encountered: