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

[Bug] - es_extended - After relog, player are not recognized as dead #1323

Closed
lush0n3 opened this issue Feb 22, 2024 · 16 comments
Closed

[Bug] - es_extended - After relog, player are not recognized as dead #1323

lush0n3 opened this issue Feb 22, 2024 · 16 comments
Assignees
Labels
bug Something isn't working

Comments

@lush0n3
Copy link
Contributor

lush0n3 commented Feb 22, 2024

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
image

Debug Info (please complete the following information):

  • OS: Linux
  • FiveM Artifact: 7290
  • ESX Version: 1.10.5
  • Multicharacters
  • illenium-apperance
@lush0n3 lush0n3 added the bug Something isn't working label Feb 22, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in ESX Roadmap Feb 22, 2024
@Gellipapa
Copy link
Contributor

Gellipapa commented Feb 22, 2024

@lush0n3 Hi! We fixed this issue 1.10.4. I deleted my core and copy and paste 1.10.5 and works perfectly.
image

@Gellipapa
Copy link
Contributor

Previously this was a bug, it was recommended that you re-download and copy 1.10.5 and it should work.

@lush0n3
Copy link
Contributor Author

lush0n3 commented Feb 27, 2024

I will update again, I am on the latest version of all repositories and it is not working correctly, do you use multicharacters?

@lush0n3
Copy link
Contributor Author

lush0n3 commented Feb 27, 2024

Previously this was a bug, it was recommended that you re-download and copy 1.10.5 and it should work.

I updated everything and it still doesn't work, like I said before I'm using multicharacters.
image

@lush0n3
Copy link
Contributor Author

lush0n3 commented Feb 27, 2024

Video Showcase: https://streamable.com/bcllz3

@Gellipapa
Copy link
Contributor

Hi! @lush0n3 Thank you for your response. I will try again setup in txadmin.

@Gellipapa
Copy link
Contributor

Gellipapa commented Feb 27, 2024

@lush0n3
I did a complete new installation with multicharacter and it works for me. Are you sure you are using the official esx_ambulancejob?

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?

@lush0n3
Copy link
Contributor Author

lush0n3 commented Feb 27, 2024

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.

@lush0n3
Copy link
Contributor Author

lush0n3 commented Feb 27, 2024

@Gellipapa
I found the problem or at least what causes it.

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

@Gellipapa
Copy link
Contributor

@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.
There is a bug that forcelog does not reset ambulancejob timer but that is another bug.

@lush0n3
Copy link
Contributor Author

lush0n3 commented Mar 21, 2024

@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. There is a bug that forcelog does not reset ambulancejob timer but that is another bug.

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.

@Gellipapa
Copy link
Contributor

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

@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in ESX Roadmap Apr 13, 2024
@Minimalistic09
Copy link

Hello i have the same issue, when i relog i dying i use the last version of esx legacy
any know how fix it?

@Gellipapa
Copy link
Contributor

@Minimalistic09 Hi! Do you use illenium appearance?

@lush0n3
Copy link
Contributor Author

lush0n3 commented Apr 19, 2024

Hello i have the same issue, when i relog i dying i use the last version of esx legacy any know how fix it?

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)

@cipherbullet
Copy link

cipherbullet commented Nov 22, 2024

I also have this issue, fresh installation of es_extended 1.11.3 and disables multicharacter and identity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

5 participants