Open 2.1.0: [2.1.3] Spawn Protection

[DragnMaw]

Version:
2.1.0

What is the bug:
The Spawn Area zone is no longer protected from players since updating from 2.1.1. Not sure if its only affecting the server I am running, or if on all servers.

Mod & Version:
FTBUtils-1.7.10-1.0.11.1

Paste.feed-the-beast.com log:


Can it be repeated:


Known Fix:

 

[lenscas]

I believe that spawn protection is a vanilla feature, look in the server.properties file(or whatever it was called, its that file that you use to set whitelist on/off commandblocks on/off and some other things)
Here you should be able to increase or decrease the spawn protection

 

[DeathOfTime]

What is the bug:
The Spawn Area zone is no longer protected from players since updating from 2.1.1. Not sure if its only affecting the server I am running, or if on all servers.

Mod & Version:
FTBUtils-1.7.10-1.0.11.1

I believe that spawn protection is a vanilla feature, look in the server.properties file(or whatever it was called, its that file that you use to set whitelist on/off commandblocks on/off and some other things)
Here you should be able to increase or decrease the spawn protection

The Spawn claim uses the exact same size as the spawn protection that is set in server.properties. If you set "spawn-protection=0" in server.properties it will completely disable the spawn claim.

I found this out when I thought it would be alright to set the spawn protection to zero now that FTB Utilities would be handling that area as a claim. I set set it back to the default sixteen once I had figured out the claim was based on the server properties setting.

Tested in FTB Infinity v2.1.2
***
Then I remembered that spawn protection and quicksand don't mix. I quickly went around the spawn claim and dug up all the quicksand.

 

[DragnMaw]

Spawn Protection was still set to the default of 32, but I tried increasing it in the server.properties to 64, and the area still isn't protected.

 

[DeathOfTime]

Spawn Protection was still set to the default of 32, but I tried increasing it in the server.properties to 64, and the area still isn't protected.

The default setting for spawn protection in server.properties is 16. As far as I am aware it has always been 16. It may be able to be set to more, or less. Yet the default is 16.

Is it possible for a someone with OP level permission on the server to have used the command "/admin unclaim" to unclaim the spawn claim? I don't even know if that is possible. would certainly be a royal mess if it was. I am not for sure how to set a claim as admin on the behalf of another. Let alone for spawn.

Have you checked the FTB utilities mini-map to see if the spawn claim isn't actually there? There are ways to effect claimed areas no matter the settings set by the claimant. If ""allowCreativeInteractSecure": false," is set at true (which is the default) OPs and creative mode players ignore the claim settings and can interact with the chunk as if the claim isn't even there. When set to false OPs and creative players have to obey the same rules as any other player.

 

[DragnMaw]

The FTB Utilities map shows it as claimed, but users are able to interact/modify blocks within that claimed zone.

Edit - And at the start of the server they were unable to (2.1.0)