Replies: 1 comment 1 reply
-
2.17.1.9 is a very old EssentialsX version. Migration instructions are provided in each subsequent release changelog.
Could you verify whether players have the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
To preface: Server plugins was migrated from Essentials 2.17.1.9.
plugins/Essentials
and most flat files within it are from that version. I did follow migration guide as to 'delete' the config.yml and let EssentialsX recreate it. I did not see that EssX has changed any of the userdata files at all, as in there has been zero change to the modified timestamps.Server dump available here: https://essentialsx.net/dump.html?id=5c6bb3833a024e89890b39cc11c5beda
I have enabled the 'let essentials hook teleports' setting in config.yml to no avail.
In the older version of Essentials, there was a
lastlocation
object which stored the player's last position, be it from teleport, or death. I believe this data was used by Essentials for the/back
command. This doesn't seem to be getting populated since updating to EssX, and for the one user who already has one (myself), thelastlocation:
object isn't being updated at all.Below is the UUID.yml for
plugins/Essentials/userdata/
for myself:As an asside, the only worlds available are titled
hawknet
,hawknet_nether
andhawknet_the_end
, the worldskyworld
in thelastlocation:
object was from my MC 1.14.4 server, and controlled by Multiverse which is not present on this server.Beta Was this translation helpful? Give feedback.
All reactions