{"action":"created","issue":{"url":"https://api.github.com/repos/tastybento/askyblock/issues/132","labels_url":"https://api.github.com/repos/tastybento/askyblock/issues/132/labels{/name}","comments_url":"https://api.github.com/repos/tastybento/askyblock/issues/132/comments","events_url":"https://api.github.com/repos/tastybento/askyblock/issues/132/events","html_url":"https://github.com/tastybento/askyblock/issues/132","id":119363293,"number":132,"title":"Some islands simply won't be added to grid or recognized","user":{"login":"vemacs","id":2669187,"avatar_url":"https://avatars.githubusercontent.com/u/2669187?v=3","gravatar_id":"","url":"https://api.github.com/users/vemacs","html_url":"https://github.com/vemacs","followers_url":"https://api.github.com/users/vemacs/followers","following_url":"https://api.github.com/users/vemacs/following{/other_user}","gists_url":"https://api.github.com/users/vemacs/gists{/gist_id}","starred_url":"https://api.github.com/users/vemacs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vemacs/subscriptions","organizations_url":"https://api.github.com/users/vemacs/orgs","repos_url":"https://api.github.com/users/vemacs/repos","events_url":"https://api.github.com/users/vemacs/events{/privacy}","received_events_url":"https://api.github.com/users/vemacs/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-11-29T14:46:41Z","updated_at":"2015-11-29T15:05:16Z","closed_at":"2015-11-29T15:05:16Z","body":"Ever since I upgraded to 2.9.7.4, I've had a very small amount of players receiving the \"Island protected\" message in their own islands. I looked into it, and when I run `/asadmin info <playername>`, it shows the correct info, but logs\r\n    Player has an island, but it is not in the grid. Adding it now...\r\ninto the console. I run it again, and the same thing is logged.\r\n\r\nHere is the info listed, along with the island coordinates:\r\n\r\n![](https://i.imgur.com/aESfFr1.png)\r\n\r\nWhen I run `/asadmin info` when standing on the island, I get:\r\n\r\n![](https://i.imgur.com/eVmETXV.png)\r\n\r\nWhen I run `/asadmin setrange 200` when standing on the island, I get:\r\n\r\n![](https://i.imgur.com/9QWi7xb.png)\r\n\r\nI compiled my own build of 2.9.7.5, and ran `/asadmin register danieltang924`. It claimed that the island was successfully registered, but it still wasn't added to the grid, and the above commands returned the same results.\r\n\r\nThis is happening to 3 players I know of, with island x,z coordinates of:\r\n\r\n* 0:1600\r\n* 200:9400\r\n* 200:9600"},"comment":{"url":"https://api.github.com/repos/tastybento/askyblock/issues/comments/160421423","html_url":"https://github.com/tastybento/askyblock/issues/132#issuecomment-160421423","issue_url":"https://api.github.com/repos/tastybento/askyblock/issues/132","id":160421423,"user":{"login":"vemacs","id":2669187,"avatar_url":"https://avatars.githubusercontent.com/u/2669187?v=3","gravatar_id":"","url":"https://api.github.com/users/vemacs","html_url":"https://github.com/vemacs","followers_url":"https://api.github.com/users/vemacs/followers","following_url":"https://api.github.com/users/vemacs/following{/other_user}","gists_url":"https://api.github.com/users/vemacs/gists{/gist_id}","starred_url":"https://api.github.com/users/vemacs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vemacs/subscriptions","organizations_url":"https://api.github.com/users/vemacs/orgs","repos_url":"https://api.github.com/users/vemacs/repos","events_url":"https://api.github.com/users/vemacs/events{/privacy}","received_events_url":"https://api.github.com/users/vemacs/received_events","type":"User","site_admin":false},"created_at":"2015-11-29T15:05:16Z","updated_at":"2015-11-29T15:05:16Z","body":"I found the issue, turns out that some older data had assigned single-block islands with coordinates of 200:9601, 200:9602, that stuff. Writing a quick script to nuke all lines that didn't have x,y coordinates divisible by 200 fixed the issue."}}