My players have recently discovered a couple of connected chunks that are "semi-protected"; the chunks are not near the world spawn's location, though the chunks are near the world's old spawn. I have set the world's spawn through both the base minecraft cmd and the multiverse cmd, but to no avail.
Currently, I am running a Spigot 1.8.3 server on a RaspberryPi2. I am using Multiverse-Core/NetherPortal, PermissionsEx, ModifyWorld, and ChatEx.
This problem began on a Spigot 1.8 server with no mods running, persisted into running the server with the mods listed, and into the updated Spigot 1.8.3 server.
Update 3/11/15: After some more testing with the server, myself and a player, I'd like to update the problem.
My server's Pex runs three types of groups: default, and Admin. The permissions file looks like this:
The players can destroy blocks, but cannot place them in the specific area.
Doing debug tests with PermissionsEx toggle debug cmd yields that a player in group default has the following:
Server log
[19:26:16] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.dirt', regex-matched a value of true from modifyworld.* (CACHE MISS)
[19:26:17] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.destroy.dirt', regex-matched a value of true from modifyworld.* (CACHE MISS)
[19:26:21] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.dirt', regex-matched a value of true from modifyworld.* (CACHE MISS)
[19:26:21] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.place.dirt', regex-matched a value of true from cache.
Doing debug tests with PermissionEx toggle debug cmd yields that a player in group admin has the following:
Server log
[19:47:46] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.grass', regex-matched a value of undefined from cache.
[19:47:47] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.destroy.grass', no match found (CACHE MISS)[19:47:51] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.dirt', no match found (CACHE MISS)
[19:47:51] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.place.dirt', no match found (CACHE MISS)
Furthermore, after even more testing, we found that even if the other player has a rank of Admin, he still cannot place blocks in the area, though he can break them. If my permissions are changed at all, I can still place and destroy.
Given this, I don't see how it could be a permissions related issue.
I have also used MCEdit to delete the chunks, hoping the error was in the chunk files, but this did not change the issue even after the chunks were regenerated.
Currently, I am running a Spigot 1.8.3 server on a RaspberryPi2. I am using Multiverse-Core/NetherPortal, PermissionsEx, ModifyWorld, and ChatEx.
This problem began on a Spigot 1.8 server with no mods running, persisted into running the server with the mods listed, and into the updated Spigot 1.8.3 server.
Update 3/11/15: After some more testing with the server, myself and a player, I'd like to update the problem.
My server's Pex runs three types of groups: default, and Admin. The permissions file looks like this:
groups:
default:
options:
default: true
prefix: '&6(Guest) '
message-format: '%prefix &7%player: &f%message'
rank: '4'
permissions:
- modifyworld.*
- -movecraft.*
- -minecraft.command.*
- -multiverse.*
- chatex.allowchat
- chatex.chat.*
Member:
options:
prefix: '&4(Member) '
message-format: '%prefix &7%player: &f%message'
rank: '3'
permissions:
- modifyworld.*
- -movecraft.*
- -minecraft.command.*
- -multiverse.*
- chatex.allowchat
- chatex.chat.*
Admin:
permissions:
- modifyworld.*
- minecraft.command.*
- movecraft.*
- multiverse.*
- chatex.allowchat
- chatex.chat.*
- permissions.*
options:
prefix: '&2(Administrator) '
message-format: '%prefix &7%player: &f%message'
rank: '1'
schema-version: 1
The players can destroy blocks, but cannot place them in the specific area.
Doing debug tests with PermissionsEx toggle debug cmd yields that a player in group default has the following:
[19:26:16] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.dirt', regex-matched a value of true from modifyworld.* (CACHE MISS)
[19:26:17] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.destroy.dirt', regex-matched a value of true from modifyworld.* (CACHE MISS)
[19:26:21] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.dirt', regex-matched a value of true from modifyworld.* (CACHE MISS)
[19:26:21] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.place.dirt', regex-matched a value of true from cache.
Doing debug tests with PermissionEx toggle debug cmd yields that a player in group admin has the following:
[19:47:46] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.grass', regex-matched a value of undefined from cache.
[19:47:47] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.destroy.grass', no match found (CACHE MISS)[19:47:51] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.interact.dirt', no match found (CACHE MISS)
[19:47:51] [Server thread/INFO]: [PermissionsEx] User Player checked for permission 'modifyworld.blocks.place.dirt', no match found (CACHE MISS)
Furthermore, after even more testing, we found that even if the other player has a rank of Admin, he still cannot place blocks in the area, though he can break them. If my permissions are changed at all, I can still place and destroy.
Given this, I don't see how it could be a permissions related issue.
I have also used MCEdit to delete the chunks, hoping the error was in the chunk files, but this did not change the issue even after the chunks were regenerated.