-
-
Notifications
You must be signed in to change notification settings - Fork 749
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
[Bug] - es_extended - After relog, player are not recognized as dead #1323
Comments
@lush0n3 Hi! We fixed this issue 1.10.4. I deleted my core and copy and paste 1.10.5 and works perfectly. |
Previously this was a bug, it was recommended that you re-download and copy 1.10.5 and it should work. |
I will update again, I am on the latest version of all repositories and it is not working correctly, do you use multicharacters? |
Video Showcase: https://streamable.com/bcllz3 |
Hi! @lush0n3 Thank you for your response. I will try again setup in txadmin. |
@lush0n3 Previously this was indeed a bug but it has been fixed and I can't cause the problem. Is there any error message client or server console? Is the state of death saved in a database? |
Yes, I am using the official version with the latest changes. https://github.com/esx-framework/esx_ambulancejob I did a review of all the scripts that interact with access and everything is correct Everything you mention is fine, since I updated the extended this started happening. |
@Gellipapa If you switch with forcelog or log out and open the game between a dead and a living character the problem occurs, or when you log out dead, at least that's what's happening to me. I don't know if this is associated with the "isDeadState" function But do what I say, log out with a dead player, then log in with a live player, log out and log back in with the dead one, at least that's how I get the error. Thanks in advance for your time |
@lush0n3 Hi! I tested your descriptions, and it's works. Video: https://streamable.com/2ge2lx I don't quite understand why it doesn't work for you, we need to do more testing. |
Hello again, I found out which script is giving the problem. illenium-appearance: https://github.com/iLLeniumStudios/illenium-appearance Apparently it triggers an event after all the ESX events and revives the player, leaving them dead but unable to send dispatch. I don't know if the same thing will happen when using fivem-appearance but I will continue testing and looking for the problem. |
@lush0n3 Hi! Thanks, let us know what you find out and we'll see how we can help you fix the illenium if that is indeed the problem. |
Hello i have the same issue, when i relog i dying i use the last version of esx legacy |
@Minimalistic09 Hi! Do you use illenium appearance? |
I tried a lot of things and none of them worked, so I went back to the previous. I mean, I didn't update the file -> \es_extended\client\main.lua (1.10.4) |
I also have this issue, fresh installation of es_extended 1.11.3 and disables multicharacter and identity |
Describe the bug
When player dies and does reconnect, he's not recognized as dead and dead player cannot call for emergency services also can't see respawn/bleedout timer.
To Reproduce
Die
Quit game
Connect back to game
Player won't receive option to call for emergency or see timer until respawn.
Debug Info:
Expected behavior
Upon connection, the player should appear dead again, but appears lifeless, lying on the ground and without the possibility of calling emergency services, nor the possibility of being revived by another player.
Screenshots
Debug Info (please complete the following information):
The text was updated successfully, but these errors were encountered: