Jailing of someone who is offline failed

[mormoon]

Jailing a person whilst offline seems to work like expected however after logging back in, that particular person is NOT jailed. We did some further testing and we found out that if you add the -t 888d parameter the command works as expected. There is a peculiar thing that the jailed person cannot break blocks. After re-logging the client the person that is jailed is able to break blocks again.

On a side note we found out that if a person is jailed with an infinite amount of time (0 mins), the person can bend the rules by escaping(+10m) or breaking a block (+1m). Not sure if this is the desired result of jailing someone indefinitely.

[10:22:53] [Server thread/INFO]: BasicallyiK1ll lost connection: Disconnected
[10:22:53] [Server thread/INFO]: BasicallyiK1ll left the game.
[10:23:28] [Server thread/INFO]: mormoon_nl issued server command: /jail BasicallyiK1ll -j tree -a -r Irritant -i
[10:23:28] [Server thread/INFO]: BasicallyiK1ll has been jailed forever.
[10:45:49] [User Authenticator #11/INFO]: UUID of player BasicallyiK1ll is f2558f75-d5e0-4a10-b7c7-188654bc101c
[10:45:49] [Server thread/INFO]: BasicallyiK1ll[/195.241.253.179:61509] logged in with entity id 42462 at ([towny4]-1560.5184999930248, 57.0, -1021.0410051007091)
[10:45:50] [Craft Scheduler Thread - 595/INFO]: BasicallyiK1ll has the following notes:
[10:47:06] [Server thread/INFO]: BasicallyiK1ll issued server command: /kill
[10:49:41] [Server thread/INFO]: BasicallyiK1ll issued server command: /kit

[graywolf336]

Interesting, i haven't had any issues on my server with offline players.
Which storage system are you using? Which version are you using? Can you
link to your configuration?
On May 13, 2015 7:00 AM, "mormoon" notifications@github.com wrote:

Jailing a person whilst offline seems to work like expected however after
logging back in, that particular person is NOT jailed. We did some further
testing and we found out that if you add the -t 888d parameter the command
works as expected. There is a peculiar thing that the jailed person cannot
break blocks. After re-logging the client the person that is jailed is able
to break blocks again.

On a side note we found out that if a person is jailed with an infinite
amount of time (0 mins), the person can bend the rules by escaping(+10m) or
breaking a block (+1m). Not sure if this is the desired result of jailing
someone indefinitely.

[10:22:53] [Server thread/INFO]: BasicallyiK1ll lost connection:
Disconnected
[10:22:53] [Server thread/INFO]: BasicallyiK1ll left the game.
[10:23:28] [Server thread/INFO]: mormoon_nl issued server command: /jail
BasicallyiK1ll -j tree -a -r Irritant -i
[10:23:28] [Server thread/INFO]: BasicallyiK1ll has been jailed forever.
[10:45:49] [User Authenticator #11
https://github.com//issues/11/INFO]: UUID of player
BasicallyiK1ll is f2558f75-d5e0-4a10-b7c7-188654bc101c
[10:45:49] [Server thread/INFO]: BasicallyiK1ll[/195.241.253.179:61509]
logged in with entity id 42462 at ([towny4]-1560.5184999930248, 57.0,
-1021.0410051007091)
[10:45:50] [Craft Scheduler Thread - 595/INFO]: BasicallyiK1ll has the
following notes:
[10:47:06] [Server thread/INFO]: BasicallyiK1ll issued server command:
/kill
[10:49:41] [Server thread/INFO]: BasicallyiK1ll issued server command: /kit

—
Reply to this email directly or view it on GitHub
#69.

[mormoon]

[15:55:35 INFO]: Jail Version: 3.0.0-SNAPSHOT-b182
[15:55:49 INFO]: This server is running CraftBukkit version git-Spigot-870264a-0a645a2 (MC: 1.8.3) (Implementing API version 1.8.3-R0.1-SNAPSHOT)
[15:55:49 INFO]: Checking version, please wait...
[15:55:49 INFO]: You are running the latest version

Running Mysql as storage system.

Link to configuration: http://pastebin.com/XHeWxv6T

[graywolf336]

When you jail someone offline, how long does it say they're jailed for?

[graywolf336]

I have not been able to replicate this issue using the exact same command (username and jail names changed) as was stated in the first post. If you're still having this issue, please try the latest build and then report back after testing it.