Type of bug

Other unexpected behaviour

/ess version output

[20:52:08 INFO]: Server version: 1.17.1-R0.1-SNAPSHOT git-Paper-119 (MC: 1.17.1)
[20:52:08 INFO]: Brand version: Paper
[20:52:08 INFO]: EssentialsX version: 2.19.0-dev+221-1556b91
[20:52:08 INFO]: PlaceholderAPI version: 2.10.10
[20:52:08 INFO]: LuckPerms version: 5.3.47
[20:52:08 INFO]: Vault version: 1.7.3-b131
[20:52:08 INFO]: DiscordSRV version: 1.23.0
[20:52:08 INFO]: EssentialsXChat version: 2.19.0-dev+221-1556b91
[20:52:08 INFO]: EssentialsXSpawn version: 2.19.0-dev+221-1556b91
[20:52:08 INFO]: Economy Layer: None
[20:52:08 INFO]: Fetching version information...
[20:52:09 INFO]: You're running the latest EssentialsX dev build!

Server startup log

https://gist.github.com/freddyheppell/db35090c7b461843d0a01b4b352872f0

EssentialsX config files

https://gist.github.com/freddyheppell/db35090c7b461843d0a01b4b352872f0

Error log (if applicable)

No response

Bug description

For some players, running /home says they have no homes, despite them having homes in their data file. But, their homes are autocompleted when typing the /home command.

Steps to reproduce

1. A player runs /home to view their existing homes
2. The player runs /sethome test to create a new home
3. The player runs /home again

Expected behaviour

Running /home should show the homes that exist in their data file. Running /home again after /sethome should include the new home too.

Actual behaviour

Both times they are told Error: Player has not set a home. However, both pre-existing home and the newly set home are shown in the autocomplete menu. Several players have this issue.

Another player (whose datafile is here), does not experience any of these issues.

This happens when the player has one or more homes in a dimension that has been reset.

Can confirm. A player is having this issue and its pretty annoying.

Can't say if its due to a world reset, I haven't done any world resets since Jul 1, and not created any other worlds then delete after.

Confirmed by #4240 (comment)

Found out some of the worlds looks like "176a8ad6-aa96-4459-83e7-0be437ec3049" which causes the issue "player has not set a home" but I never created such world. How EssX determines the correct world? That UUID named world should bring to the "world" which is somewhat confusing as hell :thokingintensifies:

EDIT: Noticed I posted my message in the PR which I marked as off-topic