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

target/doorlock HasGroups issue #170

Closed
Alexscr1pt opened this issue Oct 29, 2024 · 1 comment
Closed

target/doorlock HasGroups issue #170

Alexscr1pt opened this issue Oct 29, 2024 · 1 comment
Labels
wontfix This will not be worked on

Comments

@Alexscr1pt
Copy link

ox-target/ox-doorlock - HasGroups check for access to features is making it so that for jobs, you have access to all doors/interactions of all jobs you have regardless of being on/off duty rather than pulling what your active job is from player.jobs section of SQL

@Ehbw
Copy link
Member

Ehbw commented Jan 20, 2025

utils.hasPlayerGotGroup check for both ox_target and ox_doorlock are handled by the framework bridges. Which are currently ND, ox_core, qbox and ESX. If your using an unsupported framework or standalone these checks will always return true

@Ehbw Ehbw closed this as not planned Won't fix, can't repro, duplicate, stale Jan 20, 2025
@Ehbw Ehbw added the wontfix This will not be worked on label Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

2 participants