Skip to content
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

Open
horejsiladislav opened this issue Mar 15, 2023 · 5 comments
Open

Request for compatibility with rcore_tattoos #67

horejsiladislav opened this issue Mar 15, 2023 · 5 comments

Comments

@horejsiladislav
Copy link

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 time ClearPedDecorations 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! 🔥

@FBFezz
Copy link
Collaborator

FBFezz commented Apr 16, 2023

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

@horejsiladislav
Copy link
Author

@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.

@FBFezz
Copy link
Collaborator

FBFezz commented Apr 19, 2023

Ill leave it up to @wasabirobby for how he wants it to be done and can go from there

@horejsiladislav
Copy link
Author

Alright, but thanks for the idea!

@FBFezz
Copy link
Collaborator

FBFezz commented Apr 19, 2023

No Problem, ill try think of other ways in case those ideas don't work

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants