-
-
Notifications
You must be signed in to change notification settings - Fork 740
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
[Feature Request] - es_extended - Better handling of getting entity type #1308
Comments
this is set to 300 to allow wiggle room. |
I understand why it's locked within 300 units, but I still believe If you consider second option to bring more issues ( i assume statebags would be the problem here and entity ownership ), then you may close this issue |
what is your usecase for spawning vehicles outside of onesync range anyway? |
Generally, in most cases it's fine if the source is within 400 units, but there was a case where I needed to create entity far from the entity, which was then tracked on the map etc. Very speecific, however I thought it'd be good idea to mention it as it's not really handled at all atm |
For that, id recommend putting a blip where it would spawn, |
@mikigoalie Hi! As @Mycroft-Studios said you can do this, you manage the whole process server-side and update the coordinate from the server and send it back to the client. |
There is small overseen issue with getvehicletype RPC
esx_core/[core]/es_extended/server/onesync.lua
Line 91 in 7c59848
Currently, if there are no players near given coords, the function will fail without proper handling. I suggest to pass the rpc to any other random player or cache it until someone appears nearby.
Use case should be self explainatory, but: Creating a vehicle in onesync zone with no player will result in an error.
The text was updated successfully, but these errors were encountered: