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] - esx_core - ESX.PlayerData.name retunr nill #1386

Closed
DyroS3 opened this issue Aug 5, 2024 · 1 comment · Fixed by #1388
Closed

[Bug] - esx_core - ESX.PlayerData.name retunr nill #1386

DyroS3 opened this issue Aug 5, 2024 · 1 comment · Fixed by #1388
Assignees
Labels
bug Something isn't working

Comments

@DyroS3
Copy link
Contributor

DyroS3 commented Aug 5, 2024

Describe the bug
When trying to use ESX.PlayerData.name, the return value is nil

To Reproduce

RegisterCommand('ESX.PlayerData.name', function(source, args, raw)
  local ESX = exports['es_extended']:getSharedObject()

  print('ESX.PlayerData', ESX.DumpTable(ESX.PlayerData))
  print('ESX.PlayerData.name', ESX.PlayerData.name) -- retrun nil
end, false)

Screenshots
image

Debug Info (please complete the following information):

  • OS: Windows
  • FiveM Artifact: 9214
  • ESX Version: 1.10.7

Additional context
When I look at the values printed by ESX.DumpTable(ESX.PlayerData), I see that there is no name header, and when I look at the kernel I see that server - main.lua finds that userData does not have a value for name. Is ESX.PlayerData.name being dropped?
image

@DyroS3 DyroS3 added the bug Something isn't working label Aug 5, 2024
@DyroS3 DyroS3 changed the title [Bug] - esx_core - ESX.PlayerData.name [Bug] - esx_core - ESX.PlayerData.name retunr nill Aug 5, 2024
@Gellipapa
Copy link
Member

@DyroS3 Hi! Thanks for report problem. I corrected it, the error was that there was a refactor and the name value was not entered and therefore the player data was not received.

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
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants