-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Request for compatibility with rcore_tattoos #67
Comments
Would adding a section to the documents page for people using rcore can apply that themselves be of any use? Eg would be a section saying rcore tattoo issue in the faq section that shows where to apply the event with snippets in the fivem-appearance code |
@FBFezz That could be a solution if there was a place for them to add to, that is the current problem. And one more thing, the more stuff you put in the documentation and people are required to do, creates unnecessary tickets that result in more time spent for us developers than just adding this to the code itself. |
Ill leave it up to @wasabirobby for how he wants it to be done and can go from there |
Alright, but thanks for the idea! |
No Problem, ill try think of other ways in case those ideas don't work |
Hello wasabi, I am dev at rcore script studio, we have been previously talking about a problem with fivem-appearance and our rcore_tattoos script and I have been told to create an issue here.
Our customers are reporting that when they use both of the scripts at once, your fivem-appearance removes our tattoos from their ped. There is a really simple one line fix for this.
Everytime
ClearPedDecorations
is used, tattoos are deleted. Each timeClearPedDecorations
is used, please reapply our tattoos with one of these events, depending on client/server side:From server
TriggerClientEvent('rcore_tattoos:applyOwnedTattoos', playerId)
From client
TriggerEvent('rcore_tattoos:applyOwnedTattoos')
It could also be configurable, something like
Config.ReapplyRcoreTattoos
, but that's up to you.Thanks a lot! 🔥
The text was updated successfully, but these errors were encountered: