[MC-9213] Spawn is Unprotected Created: 05/Feb/13  Updated: 05/Feb/13  Resolved: 05/Feb/13

Status: Resolved
Project: Minecraft: Java Edition
Component/s: None
Affects Version/s: Snapshot 13w05b
Fix Version/s: None

Type: Bug
Reporter: hunter B Assignee: Unassigned
Resolution: Invalid Votes: 0
Labels: None
Environment:

mac, latest version of java 7


Confirmation Status: Unconfirmed

 Description   

you can break blocks even of not op in all game modes... also one other question... is adventure mode meant for you to break all the blocks it lets you do? its really annoying, cuz we cant use a lot of blocks because of this issue?

Thank You!



 Comments   
Comment by Kumasasa [ 05/Feb/13 ]

On the bottom of http://www.minecraftwiki.net/wiki/Nbt_format there are some NBT editors. NBTexplorer works well.

Comment by hunter B [ 05/Feb/13 ]

Ok. So can someone close this as resolved? I'm not even sure if I an but
can't anyway I'm on my phone?

Thank You!

Comment by hunter B [ 05/Feb/13 ]

Can I change files like that that I can't edit or see? Stuff like where
server spawn is?

Comment by Mustek [ 05/Feb/13 ]

That is correct. You can change the spawn location by editing some NBT tags (search for a guide on how), and then it will work as intended again.

Comment by hunter B [ 05/Feb/13 ]

Ok so I think I realized my problem, and I'll have to test it later... But
on my world file at some point a bug (a long time ago) had changed the
spawn... It's about 400 blocks away now... But that's ok because I have you
trigger a bunch of command blocks now... Ok so I bet that the protection
must be set there?

Comment by Kumasasa [ 05/Feb/13 ]

Spawn protection does work if:
spawn-protection=16 in server.properties
ops.txt is not empty
current player is non op
(Thanks to Mustek and Tails for testing)

Comment by hunter B [ 05/Feb/13 ]

Spawn protection is at 16 (there is no "true" in that statement? Is that
fine)

Comment by Kumasasa [ 05/Feb/13 ]

Is the spawn protection enabled at the server ?

(Adventure mode: Breaking blocks with the appropriate tool is working as intended, but please put only one issue per ticket.)

Generated at Sun Jan 12 12:20:20 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.