Locked Players can't rejoin for a long time!

[caoli5288]

Locked Players can't rejoin for a long time!

[caoli5288]

Server and plugin version?

[helptiger]

server: 1.8.3 and 1.8.7; plugin: 1.1.2 from Spigot and 1.1.3 from here

[caoli5288]

Any server lag or crash before lock data?

[helptiger]

no, absolutely not
tested with 3 different MySQL Servers

[caoli5288]

Any error output?

[helptiger]

no

[helptiger]

for me it seems that the unlock process is not fired correctly

[caoli5288]

I have no idea yet, I will test it this weekend.

[Dummyc0m]

You could test it, if you set your player (must be offline) manually to online in the MySQL table (column Online = 1) and then try to join the server.
What?

[caoli5288]

I really found no problems in testing.
I switched the server more than 100 times and not one failure.

[helptiger]

Hmm, but have you also tested what happens if a player is locked? For me the bug hides in the unlock process. That could be the UnlockTask.java or related. The simplest way to test is to manually set the player online to 0 in the db and than try to join. So again, what happens after a player is locked.

[caoli5288]

I know it will locked 5 mins.

[helptiger]

So, is it possible to reduce this time or make it configurable?

[Dummyc0m]

The plugin saves a player every 3 minutes i suppose, so 5 min lock is alright.

[Cnly]

Hmm, but have you also tested what happens if a player is locked? For me the bug hides in the unlock process. That could be the UnlockTask.java or related. The simplest way to test is to manually set the player online to 0 in the db and than try to join. So again, what happens after a player is locked.

UnlockTask.java is only used in an infrequent case where a player quits the server fast enough after joining to unlock the locked data, which was locked during its data's being loaded.

So, is it possible to reduce this time or make it configurable?

Which time do you mean?

[caoli5288]

Close. You can test the new /psql send <who> <target_server> command. If any problem please open a new issue.