fix(es_extended/client/modules/death): fix death thread on first spawn#1592
Merged
Conversation
Arctos2win
approved these changes
Jan 10, 2025
Meyndflay
pushed a commit
to Meyndflay/esx_core
that referenced
this pull request
Jun 9, 2025
fix(es_extended/client/modules/death): fix death thread on first spawn
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR aims to address an issue where the death thread would not start on first spawn when using certain third-party multichar systems. This is not directly an issue with ESX, but more the result of those multichar systems triggering esx events in the wrong order.
PR Checklist