EssentialsX

EssentialsX

Bukkit Plugins
2M Downloads

Unlimited command breaks userdata

iGuillem opened this issue ยท 3 comments

commented

Information

Full output of /ess version:

<!-- Server version: 1.14.4-R0.1-SNAPSHOT git-Paper-186 (MC: 1.14.4)
[21:27:42 INFO]: EssentialsX version: 2.17.1.15
[21:27:42 INFO]: PlaceholderAPI version: 2.10.3
[21:27:42 INFO]: PermissionsEx version: 1.23.4
[21:27:42 INFO]: Vault version: 1.7.3-b${env.TRAVIS_BUILD_NUMBER}
[21:27:42 INFO]: EssentialsXChat version: 2.17.1.15
[21:27:42 INFO]: ChestShop version: 3.10-SNAPSHOT (build 157)
[21:27:42 INFO]: EssentialsXProtect version: 2.17.1.15
[21:27:42 INFO]: EssentialsXGeoIP version: 2.17.1.15
[21:27:42 INFO]: EssentialsXAntiBuild version: 2.17.1.15
[21:27:42 INFO]: EssentialsXSpawn version: 2.17.1.15
[21:27:42 INFO]: Estas ejecutando plugins no soportados! -->

Server log: https://gist.github.com/iGuillem/9c4f00a4f4c7de78fa87cc93739c139a

EssentialsX config: https://gist.github.com/iGuillem/3180f8b703b41d0b2b8bf68adc9d1dfc

Details

Description

The player's file gets corrupted

Steps to reproduce

type /unl glass and hours later, when the player joins the server the file is corrupted

Expected behavior

Screenshots

commented

Can you give more exact steps on how to replicate this? How exactly is the player's file corrupted, and what actions did you take in what order in order to have this occur. Please try to test it again and provide screenshots.

commented

The player executes the command /unl glass (or any id 1.14)
Then I restart the server and when the player enters, this appears in console https://gist.github.com/iGuillem/9c4f00a4f4c7de78fa87cc93739c139a
I don't remember if the player disconnected before restarting or if he was ejected on restart
I don't know what other screenshot I could show

commented

Ah yes, I see. Now able to replicate on the same version of Essentials and Paper as you have. It seems not to matter whether the player left the server or not, as simply restarting the server seems to trigger the issue. Interestingly enough, it didn't seem to happen for me on 2.17.1.5, but when I did update to 2.17.1.15 it did occur. Either way, it's broken in the latest version so that aught to get checked out.