Am i going insane... or does PocketMine's spawn protection just not work? I just setup two servers to test it out... and used some random non-op accounts. I just logged in and broke stuff that was supposed to be protected. Previously all I had to do was set the server.properties to have the block value I wanted.... and it would work. Is there something else we have to do now? Running - PocketMine-MP 3.0.5 for Minecraft: PE v1.4.0 (protocol version 261) Windows Server DataCenter version 2016 build 17134
There shouldn't be anything else. I've been getting intermittent reports of spawn protection issues for a while, but nothing reproducible. Are you using a custom map?
Do you have at least one name in ops.txt? I ask because if ops.txt is empty spawn protection won't work. (https://github.com/pmmp/PocketMine-...ca692912/src/pocketmine/level/Level.php#L1630)
I was not using a custom map in the server I was testing on. But my ops.txt was blank, adding in a name looks like it fixed it. I'll make a note about that going forward. Now, that does bring me back to the original issue I had noticed, that had caused me to figure out my entire spawn protection was failing- Users without op can still break paintings in the spawn protected area. It looks like a bug to me. If you'd like, Dktapps, I can go fill out the issue form over on GitHub.\\ Edit- Btw, is there a reason we need to have someone set as an op? It'd be nice to not have anyone set there.
As per https://minecraft.gamepedia.com/Spawn/Multiplayer_details, being able to delete paintings matches PC behaviour. Whether this is intended behaviour or not is something I'm not clear on. The behaviour of disabling spawn protection is also the same on PC servers, although I agree it isn't very desirable behaviour. See https://twitter.com/Dinnerbone/status/253986918897942528 and also https://bugs.mojang.com/browse/MC-296.
I see. I'll just set the "Op user" to have a longer name than possible for an Xbox account, and to use disallowed characters. As for paintings... there's a workaround for everything. I'll just add to my resource pack, and create an invisible block to use as a barrier. Thank you SleepSpace9, dktapps, Another solved post.